https://bugzilla.novell.com/show_bug.cgi?id=851997 https://bugzilla.novell.com/show_bug.cgi?id=851997#c3 --- Comment #3 from James Carter <jimc@math.ucla.edu> 2013-12-05 05:47:41 UTC --- Thanks for the pointer; it explains a lot about where the device names are coming from. With luck I could automate creating the device name, which would really help in my automated install/upgrade script. However, the reported very intelligent probing strategy did not work for me. I had these misfortunes: On machine #1 I gave it netdevice=enp2s0 but it still got an error configuring the network. This machine also has a USB NIC (unplugged cable to the wild side). I needed to physically remove the USB NIC to get it to boot. Machine #2 has two wired Ethernet ports (with different hardware) and a wireless NIC, all internal. Only one Ethernet port had a cable. If I told it the wanted netdevice it got an error configuring the network. If I omitted netdevice it may have done the round robin thing, but the error caused by the missing cable was fatal. I got this machine to boot by omitting netdevice and specifying brokenmodules=e1000e brokenmodules=rtl8723ae. Tomorrow I'm doing a server at work that has a four port multifunction NIC on the motherboard; only 2 ports are connected. Cross fingers... Maybe I'll take a mini-hub down there and connect the remaining ports to it. Suggestion on the logic of network configuration: If any failure occurs, from failure to bring up the NIC, to failure to get an address, to failure to obtain the installation system from the webserver, report it and go on to the next NIC. Only be fatal if every NIC fails. Also, if the user has positively told you to use a particular device, I think you should not touch the others (unless it fails). Also it would be really nice to bring back the dialog in manual net configuration for choosing the netdevice. Preferably also in the F4 dialog in the initrd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.