[3071] in linux-scsi channel archive
Re: new scsi code
daemon@ATHENA.MIT.EDU (Eric Youngdale)
Mon Jan 12 00:09:48 1998
Date: Mon, 12 Jan 1998 00:21:51 -0500
From: Eric Youngdale <eric@andante.jic.com>
To: Ed.Welbon.-.welbon@bga.com
CC: linux-scsi@vger.rutgers.edu
>If aha1542 is built as a module, linuxrc attempts to insmod aha1542 but
>aha1542 fails to load. I don't recall the specific failure but because it
>doesn't load the module and do the scan of its own bus, it does not find
>its disk (the boot media) and hence does not label that disk the the next
>disk that is supposed to be /dev/sdb eventually shows up as /dev/sda and
>this screws me up something awful becuase the raid is started with
>/dev/sdb. If I renumber the raid devices to start with /dev/sda, then
>the raid will come up and the boot can proceed.
The last bit (devices not being correctly numbered is
"normal". I know - it is rather sub-optimal, and it isn't a
satisfactory way for things to work, but that part has been around for
ages. I eventually plan to fix it, but first I need to fix the new
bugs that got introduced in the latest round of diffs.
The main question I have is why the 1542 module won't load.
It sounds like you have temporarily worked around this, and I will
study the 1542 diffs to see if there was something stupid that was
being done which could explain it.
Could you email me the modified aha1542.c/h that you are using
with 2.1.77? From this I may be able to identify what is broken with
the real driver in 2.1.77.
>If I build aha1542 into the kernel, then it seems to find the devices on
>its own scsi bus OK but when nc553c8xx loads, nc553c8xx only finds the
>devices /dev/sdb /dev/sdc /dev/sdf /dev/sdj and does not find /dev/sdd
>/dev/sde /dev/sdg /dev/sdh /dev/sdi. The mdadd fails and no boot 8-(.
It sound like when you are using the modified 1542 driver that
you hacked, that all of the devices on the NCR busses are correctly
detected. Is this correct? This will give me something else to go on.
-Eric
