Hi! To /etc/sysconfig/kernel, the modules are written in the order the respective adapters are detected. The order the modules were loaded for installation is not used. The reason was that the list of modules needed for installation contains moduels which are not needed in inird of the running system (eg. network card if installing from network). I want to fix it at least for SLES10 (to try to keep the order of the modules during first stage but not modules which are not needed into initrd) Dne sobota 28 květen 2005 00:26 Michael Steinmann napsal(a):

I'm having problems with SLES9 SP1 autoinst on a machine with two qla2300 and one megaraid controller.

In my info file I've got: insmod: megaraid insmod: qla2300

and the drivers load in that order, giving me /dev/sda on the first disk on the megaraid controller which is what I want.

But, autoinst would always add the qla2300 to the beginning of the MKINITRD variable in /etc/sysconfig/kernel before building the initrd. As the qla2300 gets added at the *beginning* this leads to a initrd linuxrc that always loads qla2300 before megaraid. When the machine boots using the initrd built by autoinst the devices are not in the same order as during the install.

When qla gets loaded via info file, the MKINITRD looks like this: "qla2300 megaraid qla2300"

when it doesn't get loaded by 'insmod: qla2300' in info file: "qla2300 megaraid"

Why would autoinst insist on putting qla2300 in the initrd? And why at the beginning of the list?

Shouldn't the order the modules get added to the initrd honor the order given in the info file?

Mike

-- Regards, Jiri Srain YaST2 developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: jsrain@suse.cz Drahobejlova 27 tel: +420 2 9654 2373 190 00 Praha 9 fax: +420 2 9654 2374 Czech Republic http://www.suse.cz