On 2014-01-12 19:45 (GMT-0800) Linda Walsh composed:
Felix Miata wrote:
Why was sata_sil included in INITRD_MODULES in /etc/sysconfig.kernel 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.
OK, so somebody might, but then in /var/log/zypp/history is this left-hand-blind-to-right-hand-activity gem: # Additional rpm output: # Creating: target|kernel|dracut args|basicmodules # Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --hostonly --force --add-drivers " ata_piix sata_sil pata_acpi ata_generic" /boot/initrd-3.12.1-2-desktop 3.12.1-2-desktop If might is desirable, then why is dracut called with --hostonly (and done no less in absence of anything uncommented about hostonly in /etc/dracut.conf or /etc/dracut.conf.d/)? Where is that switch coming from? Can anyone spell bloat?
(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! ;-)).
Yup, I might, even though I'm a male. :-D
If you used lilo, I might be able to tell you how to solve it... (from lilo.conf(5) page)... For example,
disk=/dev/sda bios=0x80 disk=/dev/hda bios=0x81
No way. Even if I wanted to with either Lilo or Grub, it would only compound an existing logistical nightmare. All my systems are multiboot. Instead of 20 or 30 or 40 stanzas, needing to do that would create a need to double the size of the boot menu to 40 or 60 or 80 stanzas. And, all because of something that *might* happen someday, *if* I changed my mind about something that *might* affect booting. LOL
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 naming.
Does your Dell BIOS boot config menu allow to include addin devices? My Dells are really persnickity about having HDs added or removed. I don't remember ever seeing one's BIOS present any option to allow a HD connected to an eSATA addin card as an explicit boot choice to be preferred to the 4 more or less standard options, floppy, OM, HD, network/PXE. Even if they were, I wouldn't be wanting them even as an option, much less preferred to internally installed options. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org