https://bugzilla.novell.com/show_bug.cgi?id=441384
User kasievers@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=441384#c17
Kay Sievers
Come on, udev does _not_ load modules mentioned in INITRD_MODULES.
No, but INITRD_MODULES lists (among others) the modules that udev *did* load for the storage controller.
No, modprobe loads drivers, udev just calls modprobe for _every_ device with a hardware modalias not a module name. There is not a single hardware->driver definition in udev. Btw, why does the installer copy all loaded storage modules into that variable? Modprobe, by current definition, always loads all matching drivers. Why isn't the installer picking only the one that is bound to the device? Seems the installer and udev have no idea what driver is to load for which device, so find someone else who to blame. :) Modprobe loads the modules, and modprobe relies on the kernel supplied modules.order file to prefer libata drivers. That file is missing in the kernel rpm. Reassign to kernel, to make sure modules.order is shipped. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.