This bug with myrinet devices is fixed already and should appear on the upcoming Service Pack. Anas Karsten Petersen wrote:
Hi,
I have a problem with SuSE 9.1 autoyast, a static network setup and Myrinet host adapters which are in the machines.
My autoyast files have a network configuration that looks like this: <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>192.168.21.127</broadcast> <device>eth-0</device> <ipaddr>192.168.21.102</ipaddr> <netmask>255.255.255.224</netmask> <network>192.168.21.96</network> <startmode>onboot</startmode> </interface> </interfaces> There is no <modules> declaration in <networking>, just the above <interfaces>, <dns> and <routing>.
But if a machine is installed with this configuration, the network setup ends up totally wrong: Autoyast assigns the given IP to the Myrinet interface - which is senseless because there is no driver loaded and Myrinet does not need an IP to work. This is because the hwinfo tool detects the Myrinet card and yast declares it to be a "netcard" named "myri". When autoyast goes to use the given interface setup, it calls SelectHW() which returns the first netcard: myri.
Neither of the following attempts worked: - add another <interface> declaration in front of the eth-0 one - add a <modules> section - rename <device> to eth0
Fixing this in a postinstall script failed because the ifcfg-* files are only created afterwards. So now I am trying a postinstall script that patches the file /usr/share/YaST2/modules/NetworkDevices.ycp and runs ycpc afterwards. :-/ Does anyone have a better idea?
Nevertheless I believe this is a bug - autoyast should just ignore the Myrinet card.
A related problem is, that it seems impossible to exactly declare which device an interface configuration is for, without giving the MAC address in <device>. This is very impractical for large amounts of mostly identical machines. :-( It would be good if I could tell autoyast something like this: <interface> <device>eth0</device> ... </interface> And autoyast would then use this declaration for the kernels eth0 device, no matter what other devices are around or what MAC this device has.
Best wishes Karsten Petersen