2 SCSI controllers causing boot problems...
I know I've seen this in the past, but the answer slips my mind and I can't find anything in the archives.
I've just set up a box w/ an aic7xxx card. The boot drive hangs off that card. During installation, the boot drive is sda. Lilo contains "root=/dev/sda8".
I compiled a new kernel with the 3ware raid driver. When I rebooted, the 3ware card driver must have been loaded first; /dev/sda8 was no longer the root device.
How do I control the device designations during boot?
Signature · 7 lines
Drew Bertola | Send a text message to my pager or cell ...
| http://jpager.com/Drew
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/Quoted 8 lines · On Fri, 02 Feb 2001 10:09:21 Drew Bertola wrote:
I know I've seen this in the past, but the answer slips my mind and I can't find anything in the archives.
I've just set up a box w/ an aic7xxx card. The boot drive hangs off that card. During installation, the boot drive is sda. Lilo contains "root=/dev/sda8".
Quoted 6 lines
I compiled a new kernel with the 3ware raid driver. When I rebooted, the 3ware card driver must have been loaded first;
/dev/sda8was no longer the root device.How do I control the device designations during boot?
Drew,
If you check the archive's I've had a similar problem.
Possible answers:
Compile the to-be-loaded-2nd driver as a module and keep the first builtin Use devfs (it lets you pass a 'scsi=driver1:driver2:...' to the kernel, controlling load order)
There are devfs 2.2 patches and 2.4.1 includes devfs natively; I chose 2.4.1 and it worked.
--
Michael Pacey
[email protected]
ICQ: 105498469
wd21 ltd - world domination in the 21st century
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/