Yesterday there are update for NetworkManager: NetworkManager-0.9.10.0-13.git20140704.fc21 to NetworkManager-0.9.10.1-1.git20150105.fc21 With this update, my Ethernet don't load on boot, I can see in the applet that search and fail. If I disconnect and reconnect that work. I downgrade to NetworkManager-0.9.10.0-13.git20140704.fc21 and that work at boot. I don't know where search the error in log, if you want another information say me where I can search.
The logs can be displayed using journalctl command. Please try again and then attach the logs. $ sudo journalctl -b -u NetworkManager Would you get output of these commands too? $ nmcli device $ nmcli connection
Ok Jirka: [root@host-192-168-1-2 ~]# nmcli device PÉRIPHÉRIQUE TYPE ÉTAT CONNECTION p5p1 ethernet connexion (obtention de la configuration IP) p5p1 wlp3s0 wifi indisponible -- lo loopback non-géré [root@host-192-168-1-2 ~]# nmcli connection NOM UUID TYPE PÉRIPHÉRIQUE p5p1 28b77c6f-f22d-4ec7-8fbc-55ad31aaf920 802-3-ethernet p5p1
Created attachment 978092 [details] networkmanager-log.txt networkmanager.log
Just a precision: --If I reboot, my ethernet is active and work fine. --If I shutdown and restart my ethernet don't work
My Ethernet doesn't work at all, had to downgrade NM (and openconnect) to NetworkManager-0.9.10.0-13.git20140704.fc21 to get it working again. Looking in the logs I see that NM can't handle a NAK. Rather severe regression Jan 12 16:52:22 stinkpad kernel: [ 38.805283] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Jan 12 16:52:22 stinkpad kernel: [ 38.805316] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready Jan 12 16:52:22 stinkpad kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Jan 12 16:52:22 stinkpad kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> (enp0s25): link connected Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> (enp0s25): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Auto-activating connection 'enp0s25'. Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) starting connection 'enp0s25' Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 1 of 5 (Device Prepare) scheduled... Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 1 of 5 (Device Prepare) started... Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> (enp0s25): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 2 of 5 (Device Configure) scheduled... Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 1 of 5 (Device Prepare) complete. Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 2 of 5 (Device Configure) starting... Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> (enp0s25): device state change: prepare -> config (reason 'none') [40 50 0] Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 2 of 5 (Device Configure) successful. Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 2 of 5 (Device Configure) complete. Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 3 of 5 (IP Configure Start) scheduled. Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 3 of 5 (IP Configure Start) started... Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> (enp0s25): device state change: config -> ip-config (reason 'none') [50 70 0] Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Beginning DHCPv4 transaction (timeout in 45 seconds) Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> dhclient started with pid 3178 Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 3 of 5 (IP Configure Start) complete. Jan 12 16:52:22 stinkpad NetworkManager[1151]: <info> (enp0s25): DHCPv4 state changed nbi -> preinit Jan 12 16:52:22 stinkpad dhclient[3178]: DHCPREQUEST on enp0s25 to 255.255.255.255 port 67 (xid=0x2c4b5cff) Jan 12 16:52:23 stinkpad dhclient[3178]: DHCPNAK from 192.168.160.2 (xid=0x2c4b5cff) Jan 12 16:52:23 stinkpad NetworkManager[1151]: <info> (enp0s25): DHCPv4 state changed preinit -> expire Jan 12 16:52:23 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... Jan 12 16:52:23 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 4 of 5 (IPv4 Configure Timeout) started... Jan 12 16:52:23 stinkpad NetworkManager[1151]: <info> (enp0s25): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Jan 12 16:52:23 stinkpad NetworkManager[1151]: <warn> Activation (enp0s25) failed for connection 'enp0s25' Jan 12 16:52:23 stinkpad NetworkManager[1151]: <info> Activation (enp0s25) Stage 4 of 5 (IPv4 Configure Timeout) complete. Jan 12 16:52:23 stinkpad NetworkManager[1151]: <info> (enp0s25): device state change: failed -> disconnected (reason 'none') [120 30 0] Jan 12 16:52:23 stinkpad NetworkManager[1151]: <info> (enp0s25): deactivating device (reason 'none') [0] Jan 12 16:52:23 stinkpad NetworkManager[1151]: <info> (enp0s25): canceled DHCP transaction, DHCP client pid 3178
Well, it is the same as bug 1181477. We will pushed update for it shortly. In the meantime, see workarounds in that bug. *** This bug has been marked as a duplicate of bug 1181477 ***