RE: SuSE mailinglist [suse-autoinstall] Autoinstall, multiple NICs.htm
SuSE mailinglist: [suse-autoinstall] Autoinstall, multiple NICsHi Sebastien,
Before reboot: eth0: 3com-card eth1: 3com card eth2: realtek card
after reboot: eth0: realtek card (WHY?) eth1: 3com card eth2: 3com card
The interfaces are defined based on the order in which the modules are loaded, if the realtek module is loaded before the 3com module, then you will get the affect you observed. During auto-install it probes for the cards in a certain order, this may not be reflected in the final config. I had ths problem and resolved it by settting the variable INITRD_MODULES in /etc/rc.config with the modules listed in the order I wanted them loaded. e.g.: INITRD_MODULES="pcnet32 eepro100" Then run 'mk_initrd' to generate the initial ramdisk containing these modules. Check that the /etc/lilo.conf (or whatever boot loader you use) loads the initrd generated above. e.g.: In /etc/lilo.conf, the entry would read: image = /boot/vmlinuz root = /dev/xxx label = linux initrd=/boot/initrd After reboot, the modules are loaded in the order specified. This method makes sure that modules are loaded before the root partition boots. If you use LVM are as module and want to boot from an LVM partition then you also need to include 'lvm' in the INITRD_MODULES list. Rgds, Simon
participants (1)
-
Simon Thornton