Hi List, hi Anas, Anas Nashif's great documentation of his tool AutoYast2 mentions this: Putting this to the bootcd kernel commandline, I expected the use of network device "eth1" for network setup (with dhcp): linux netdevice=eth1 install=nfs://1.2.3.4/x/suse8.0 autoyast=nfs://1.2.3.5/y/auto.xml Unluckily the information of the "netdevice" keyword seems to be ignored: ----- Trying to activate eth0 Setting up localhost...done timed out waiting for a valid DHCP server response Sending DHCP request to eth0... no/incomplete answer Ok, that didn't work; see if we can activate another network device... No further network cards found; giving up. ----- If I do a "manual Installation", I *can* choose between two network devices. And fetching dhcp information and the following installation from "eth1" works. (An installation over "eth0" works, too - if there is a cable. But there are good reasons to use eth1 in this case. ) Other parameters (I tried e.g. ip,netmask,gateway) work as expected, so why netdevice doesn't? Somebody else with this problem? Did I do something wrong? Or do I have to create an info file on my boot cd? Best Regards, Hella - my next boot cd should include that. (Somebody interested in a description, how to build a crude boot cd for network installation?)