[SOLVED] Network devices are not "loaded"

mattarch · 2017-10-12 14:11:48

After doing a system upgrade (about 3 weeks ago) I have finally got round to rebooting my machine.... However, my ethernet device seems to be completely foo-bar'd

netctl failed: Timed out waiting for device sys-subsystem-net-devices-enp0s3.device

Let's have a look at the network devices.....

# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever

It turns out my Ethernet card isn't listed! So I double check by booting using the live USB......

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 50:7b:9d:e4:3a:c6 brd ff:ff:ff:ff:ff:ff
    inet 192.168.62.140/24 brd 192.168.62.255 scope global enp0s31f6
       valid_lft forever preferred_lft forever
    inet6 fe80::527b:9dff:fee4:3ac6/64 scope link 
       valid_lft forever preferred_lft forever

Proving the physical device is not blown (it's connected and I can reach the outside world).

So, where to look next? I ran systemctl -a to find out the status of stuff....

# systemctl -a
....
  sys-subsystem-net-devices-enp0s3.device loaded    inactive   dead   sys-subsystem-net-devices-enp0s3.device
....

Ok, so it's definitely dead..... What do I need to do to bring it back from the dead (because it's not really dead)?

Last edited by mattarch (2017-10-12 15:29:19)

seth · 2017-10-12 14:36:43

lspci/lsusb on broken and working system?

mattarch · 2017-10-12 14:59:27

I just realised what it was!

I tried manually loading the driver for my ethernet device, and it came back with "file not found" error..... So I looked in /lib/modules and low and behold I instantly realised my stupid mistake!

After system upgrade, the kernel was updated, but for some reason, my boot partition wasn't mounted, so it wrote the new Linux kernel to the wrong place, and the old kernel was being booted, so there was a mis-match and nothing worked...... The reason I looked into networking first is because I rely on NFS mounts for my home directories and a NIS server to login with network user credentials!

Mark as solved please.

For reference if anyone else runs into this problem, check:

uname -a

and

pacman -Q linux

and check they are the same version; otherwise you will have major issues like this

Last edited by mattarch (2017-10-12 14:59:49)

seth · 2017-10-12 15:01:20

Edit your first post and adjust the title (prepend "[SOLVED] ") - nobody else can/should do that.

V1del · 2017-10-12 15:02:07

You should mark as SOLVED, by editing the title of your initial post.

Edit. Argh. Too slow.

Last edited by V1del (2017-10-12 15:02:36)

Arch Linux

#1 2017-10-12 14:11:48

[SOLVED] Network devices are not "loaded"

#2 2017-10-12 14:36:43

Re: [SOLVED] Network devices are not "loaded"

#3 2017-10-12 14:59:27

Re: [SOLVED] Network devices are not "loaded"

#4 2017-10-12 15:01:20

Re: [SOLVED] Network devices are not "loaded"

#5 2017-10-12 15:02:07

Re: [SOLVED] Network devices are not "loaded"

Board footer