Hi Christopher, thanks for your reply. I'm using SLE11-SP1 and keep_install_network. We also use the xml syntax to achieve persistent names. But that is not related to this point in time when the error occurs. I try to describe the configuration in detail: boot via PXE/DHCP transtec desktop/server with 2 nics, one nic not connected. For an unknown reason installation takes place via eth1 even if I change the cable to the other nic. When booting into stage 2 the device naming automatically changes. eth1 becomes eth0 and vice versa We have a udev rule in autoinst.xml which persists one mac to eth0 because we need eth0 as bridge port. The file /etc/sysconfig/network/ifcfg-eth0 is missing since eth1 has been used in stage 1. Yast initializes network interfaces in stage 2, does not find any configuration for eth0 and will not initialize eth0 which now is the active card. eth1 (previously eth0) is now the interface which has no connection to the network source but a valid interface description. I solved the problem by creating /etc/sysconfig/network/ifcfg-eth0 via a chroot (chrooted=true) script. We just need to tell Yast executing dhcp at this interface. Something like "BOOTPROTO='dhcp4', STARTMODE="onboot" and NAME='XYZ' is sufficient since autoyast will change the network configuration within the LAN part anyway. But nevertheless I don't understand why the interface change always happens. And I would like to resign the workarround. Best Regards, Jochen

...

...

686f6c6d <686f6c6d@googlemail.com> schrieb am 5/17/2012 um 1.34 Uhr in Nachricht : Which oS/SL release do you use? Do you use keep_install_network?

Does the SLE11 fix (Q1.10) work for you? http://turing.suse.de/~ug/AutoYaST_FAQ.html#a9

(@Uwe: The link in Q1.12 is dead.)

Is/are the card/s bnx2? (There's a bug in SL10 SP2 IIRC.)

-- Mit freundlichen Grüßen Christopher 'm4z' Holm Am 14.05.2012 19:11 schrieb "Jochen Schaefer" :

...

Hi list,

I have a problem when installing a machine via pxe with two network cards. Doesn't matter if both cards are connected or the first or the second card the naming of the devices always changes.

eth0 in stage 1 becomes eth1 in stage two (before static network configuration takes place) and vice versa. When the machine is comming up into stage two it claims that no configuration is found for eth1 and tries to connect via the other interface but that one is not connected to the installation source.

If changing the cables than the process is going vice versa. In stage one network source will be accessed via eth1 which becomes eth0 in second stage. But no configuration found for eth0.

Is there anything known about that behaviour. Can I workarround that?

I already tried with netdevice parameter but that didn't help.

Thanks, Jochen

-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org