https://bugzilla.novell.com/show_bug.cgi?id=842450 https://bugzilla.novell.com/show_bug.cgi?id=842450#c2 --- Comment #2 from Per Jessen 2013-09-26 08:22:52 UTC --- Also probably related, but feel free to ask me to open another report - after calling /usr/lib/yast/startup/yast2.ssh, I disabled the firewall and continued. I left both network interfaces untouched, one with dhcp4, the other unconfigured. I was surprised to see a config file for the _unconfigured_ interface: # cat /etc/sysconfig/network/ifcfg-enp13s0 BOOTPROTO='dhcp' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='82573E Gigabit Ethernet Controller (Copper)' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='nfsroot' USERCONTROL='no' -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=842450 https://bugzilla.novell.com/show_bug.cgi?id=842450#c4 --- Comment #4 from Per Jessen 2013-09-28 06:50:07 UTC --- (In reply to comment #3)

I cannot verify this bug: installed suse 13.1 on two computers, this Dell T7400 and a Dell Inspiron One. Have tested for wireless and wired. I changed the computer ID with YaST and both Ethernet options are available, wired as eth0 and the wireless with the assigned netgear designation.

Are your systems booting from network disks (iSCSI, NFS) ? I suspect the issue is that devices active before systemd are not properly renamed. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=842450 https://bugzilla.novell.com/show_bug.cgi?id=842450#c6 --- Comment #6 from Per Jessen 2013-09-29 08:41:12 UTC --- (In reply to comment #5)

I guess my comment was not clear. I could not verify the bug thus maybe there is no bug. My installation worked fine. I am suggesting that we close this bug.

Humberto, I wonder if you could not reproduce because you don't have the correct environment to test with. Did you or did you not boot from a network-attached (iSCSI or NFS) root filesystem? Also, in general, just because an arbitrary individual cannot reproduce a particular bug does not mean there is no bug. Besides, on another reboot, none of the interfaces were renamed, I currently have eth0 and eth1. The new renaming scheme is a bit of mess, methinks. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=842450 https://bugzilla.novell.com/show_bug.cgi?id=842450#c8 Per Jessen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #8 from Per Jessen 2013-10-01 09:02:04 UTC --- This is duplicate of 820407 which I opened back in May on 13.1m1 *** This bug has been marked as a duplicate of bug 820407 *** http://bugzilla.novell.com/show_bug.cgi?id=820407 -- 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.