Felix Miata wrote:
Why was sata_sil included in INITRD_MODULES in
the first place? The accessory (PCI) SiI 3512 hardware controller...
That answers the Q. A HW probe detected a "possible boot-device controller"
on your system. That got flagged as necessary for a ram disk because you
***MIGHT*** boot from it.
(How would the automatic selection tool know, even if you "promised",
if you would remain consistent? You are, after all, a human -- and
as long as you live, you might change your mind! ;-)).
If you used lilo, I might be able to tell you how to solve it... (from
would say that your SCSI disk is the first BIOS disk (0x80),
that your (primary master) IDE disk is the second BIOS disk
(0x81), and that your second SCSI disk (perhaps a USB device)
receives no device code, and is therefore inaccessible at boot
used to have to do something similar back when ata drives were hda & scsi were
the bios giving preference to ata drives...
you use grub?
Doesn't it have some way of assigning/reassigning a partition
to be treated as bios disk 0x80? (= cdrive ).
Also, not sure, but doesn't your bios have something to say about
the order it looks for boot disks in? I.e. my dell lets me decide on
the order to try to boot from, that, in turn, affects the kernel's
OR... you could build your own kernel and build in your 'internal' drivers
needed for boot, but leave the sil drivers as loadable modules.
OR... you could write a renaming rule (?maybe?) like is done for network
devices -- IF the kernel supports that (not sure it does, would have to
research & try it...).
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org