Created attachment 775015 [details] relevant logs Not sure if the bug here is kernel side or NM side, but trying NM side first. Since kernel 3.11.0-0.rc0.git7.1.fc20.x86_64 , on initial boot of my Rawhide machine, the NetworkManager service reports itself as up, but no network interfaces other than 'lo' appear to be present at all, in ifconfig output or anywhere else. If I do a 'systemctl restart NetworkManager.service', NetworkManager takes a very long time to quit - a couple of minutes (unless I 'kill -9' it) - but it eventually does, and on the restart, my interfaces actually appear. I'm attaching the output of 'journalctl -b _SYSTEMD_UNIT=NetworkManager.service' - NM log messages from the current boot. The messages around 11:45 are the initial start of NM, during system boot. The messages around 11:48 are the restart, after which my network interfaces appear and the network is accessible. The 2-3 minutes in between are the time it took NM to actually restart.
CCing jforbes for the kernel angle.
This issue also affects a freshly composed live image from today's Rawhide - no network connections brought up unless you restart NetworkManager.service .
This looks like a duplicate: Bug 985843 - Can't install Fedora 20: Bug 985843, Comment 9 Bug 985843, Comment 10
*** Bug 985843 has been marked as a duplicate of this bug. ***
I can confirm that this happens on my rawhide machine as well with kernel-3.11.0-0.rc2.git0.1.fc20.x86_64. However, my interfaces show up as expected when I boot 3.8.0-0.rc3.git0.1.fc19.x86_64.
NetworkManager-0.9.9.0-7.git20130724.fc20 - http://koji.fedoraproject.org/koji/buildinfo?buildID=437553 - looks like it fixes this for me, can anyone else confirm?
Hi, Yes, 0.9.9.0-7.git20130724.fc20 solved this issue for me too. Note: I had to update libndp to version 0.1-3.20130723git873037a.fc20. Martin Kho
Indeed, me too, I should've noted that. So, yeah: update libdnp and NetworkManager and this should be good. Thanks Dan!