No suitable device found for this connection after Kernel 3.10.0-1062 upgrade

Issues related to configuring your network
Post Reply
Concord_nz
Posts: 2
Joined: 2019/10/01 00:34:32

No suitable device found for this connection after Kernel 3.10.0-1062 upgrade

Post by Concord_nz » 2019/10/01 00:51:10

I just performed a yum update, which included Kernel 3.10.0-1062.
Now my wired (on motherboard) network will not work.

journalctl

Code: Select all

NetworkManager[764]: <info>  [1569885360.3296] agent-manager: req[0x55da19f555c0, :1.19/nmcli-connect/0]: agent registered
NetworkManager[764]: <info>  [1569885360.3309] audit: op="connection-activate" uuid="03ce46c7-e008-4570-811c-6a48ff37e1ba" name="enp3s0" result="fail" reason="No suitable device found for this connection (device enp3s0 not available because device has no carrier)."
network[907]: Bringing up interface enp3s0:  Error: Connection activation failed: No suitable device found for this connection (device enp3s0 not available because device has no carrier).
network status

Code: Select all

● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2019-10-01 12:16:00 NZDT; 21s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 907 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

systemd[1]: Starting LSB: Bring up/down networking...
network[907]: Bringing up loopback interface:  [  OK  ]
network[907]: Bringing up interface enp3s0:  Error: Connection activation failed: No suitable device found for this connection (device enp3s0 not available because device has no carrier).
network[907]: [FAILED]
systemd[1]: network.service: control process exited, code=exited status=1
systemd[1]: Failed to start LSB: Bring up/down networking.
systemd[1]: Unit network.service entered failed state.
systemd[1]: network.service failed.
Luckily if I drop back to 3.10.0-957 during boot everything is fine.

ifconfig

Code: Select all

TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="dhcp"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="enp3s0"
UUID="03ce46c7-e008-4570-811c-6a48ff37e1ba"
DEVICE="enp3s0"
ONBOOT="yes"
ZONE=public

chemal
Posts: 606
Joined: 2013/12/08 19:44:49

Re: No suitable device found for this connection after Kernel 3.10.0-1062 upgrade

Post by chemal » 2019/10/01 03:10:36

What brand of ethernet controller do you have? A Realtek RTL8168 perhaps? Check with:

Code: Select all

$ lspci -nn | grep -i net

User avatar
TrevorH
Forum Moderator
Posts: 26942
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: No suitable device found for this connection after Kernel 3.10.0-1062 upgrade

Post by TrevorH » 2019/10/01 05:18:10

Try modprobe realtek
CentOS 5 died in March 2017 - migrate NOW!
CentOS 6 goes EOL sooner rather than later, get upgrading!
Full time Geek, part time moderator. Use the FAQ Luke

Concord_nz
Posts: 2
Joined: 2019/10/01 00:34:32

Re: No suitable device found for this connection after Kernel 3.10.0-1062 upgrade

Post by Concord_nz » 2019/10/01 20:05:30

Hi,

Thanks for the tips.

I read some other topics while I was waiting and came across the "power off & unplug for 20 seconds fix".

Despite having unplugged this box and shifting it to a different cable and switch when this first occurred, I tried it again: powered off, unplugged for 60 seconds and booted back up into the latest kernel and it the network came back online. So odd.

Post Reply

Return to “CentOS 7 - Networking Support”