[9fans] problems with SCSI card and file server

[anothy@cosym.net]

two seperate problems: adding SCSI to a terminal and setting up a fs.

1)	i've got an IDE terminal running the current distribution. works great.
i've added a SCSI card (buslogic BT-948). still no problem. but when i
attach disks to that card, the system hangs halfway through booting.

after a bunch of debugging prints, it seems that things are hanging in this
line in init.c:
	execl("/bin/rc", "rc", "-c", ". /rc/bin/termrc; home=/usr/$user; cd; . lib/profile", 0);
it's completing termrc properly - adding "rc" to the end gives me a prompt
from which things like 'cat' work. so i did the rest of the line manually.
it fails on 'cd'. it just hangs. the kernel's still working (mouse moves,
responds to ^t^tp), but cd never returns. skipping that, it'll fail on
'rio' in my lib/profile. does anyone understand what's going on? the
system is an AMD Athlon 1.2Ghz system, ASUS A7V133 motherboard.

2)	i'm trying to build a file server. i've built the kernel, but it hangs
before getting up to config. turning on chat in dosfs.c indicates it's
hanging in getclust (i see the 'getclust read addr 0' line, then nothing).
this is on the above system, but the behaviour is the same with or without
SCSI card and/or disks. 

i then tried the same floppy on another system - a Pentium 100, unknown
motherboard - and it fails very differently: it gets to the normal cpu0:
line, then prints 'cpu0:	100Mhz' five times on a line, for several
lines, before panicing.

confused by the two very different failure modes, i threw the disk into
someone else's Compaq Presario - and it came up fine, dropping right
into config mode (the nvr on the floppy is junk). this isn't useful, as
this system has no SCSI disks (and isn't mine), but might be informative.

so again, i'm confused here. the floppy drive on these systems are all
known to be good - i can read back and verify the entire contents of the
disk - and the floppy itself is aparently fine, as it works on the
compaq. i've also tried getting the kernel via bootp, which doesn't
change the behaviour at all. anyone? help on either of these problems
would be very appreciated.
-α.