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?
--
Drew Bertola | Send a text message to my pager or cell ...
| http://jpager.com/Drew
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".
>
> 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?
>
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
Michael Pacey wrote:
> 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".
> >
> > 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?
> >
>
> 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.
Just some fine tuning on that answer. The relevant kernel
boot time option in the 2.4 series is "scsihosts" and it
is available whether or not devfs is selected. [Richard
Gooch did introduce this option together with devfs. It
is now part of the scsi mid level code.]
If you apply Richard's devfs patch to the lk 2.2 series
you will also get the "scsihosts" kernel boot time option
(but I suspect it doesn't work as it needed to some
tweaking in 2.4).
As for scsi device naming issues, you could look at:
http://linuxdoc.org/HOWTO/SCSI-2.4-HOWTO
for more information.
Doug Gilbert