Hi, You might want to tell us what modules are you loading and what order work and which does not (the way yast creates the initrd).
Anas
Helge Koehn wrote:
... any ideas to that problem from march?! till now not one answer :-( helge.
----- Forwarded by Helge Koehn/Germany/IBM on 06/09/2004 11:57 AM -----
Helge Koehn/Germany/IBM To 03/08/2004 03:14 suse-autoinstall@suse.com PM cc Subject autoyast and loadorder of moduleshi,
we face a problem where we have to load kernelmodules in a specific order to get our scsi devices recognized correctly! we are doing an autoyastinstallation via pxe. we send with the append parameter in the pxe-config file the modules to load, that works. our scsi device are recognized in the correct order. in the autoyast.xml we are partitioning the scsi devices and write the bootloader to /dev/sda. the stuff from disk 1 is transfered to the installed system. after the first initial boot, the order we have with the append parameter in the pxe-config file no longer works, autoyast has build its own initrd for the initial boot and with that the devices are changing because of loading the adapterdrivers in the wrong order!
how can we arrange that our wanted order of devices also works after the initial boot. so that /dev/sda remains /dev/sda and not switches to /dev/sdb
thanks for an answer. helge.