Steffen Winterfeldt wrote
Could it be the other modules have already been loaded (by udev at startup)?
Where could I see that? The output on console 3 starts with "remount of / ok", followed by a list of modules that I haven't specified (like lockd.ko, fan.kom nfs.ko etc.). Then follow some of my own modules, as described. I pressed Ctrl-S after I saw my modules started to load and then switched to console 9 and typed "lsmod". Indeed I see a lot of modules, like the e1000 or ata_piix in this list. Does it mean they were already loaded? If so, why did that happen? If all those modules are preloaded at some stage, then I could never ensure that a SCSI disks is detected before a SATA disk if ata_piix is always loaded before my own SCSI modules via insmod. I thought the insmod mechanism is meant to load modules before any other modules are loaded automatically, to override the order in which hardware is detected. My current problem is that the card reader devices fetch sda-sdd and the SATA disk is sde. I need the SATA disk to be sda and I can't start to work with by-id or by-path because we have too many different hosts systems (IDE+SCSI, Sata+SCSI, Sata+FC, IDE+Sata etc.). The only method we ever found to handle all of those was to ensure that the main disk is always detected as first disk by load-ordering the modules. So how can we ensure the sata disk is detected before the USB devices? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org