Can't connect to Ethernet after update

General system Kernel, boot, graphics & hardware
1

Hi,
I’ve updated Endeavour and after the update I can’t connect to ethernet.
I have been going back with timeshift. This has been happening for 2 weeks (updating and going back because Ethernet isn’t working), so it’s not being solved by waiting to newer updates.
Need help with this.

2

What is the Ethernet chip?

inxi -Na

3

Thanks for the reply, here are the results.

inxi -Na
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: N/A modules: r8169 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000
    bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 06:00.0
    chip-ID: 8086:2725 class-ID: 0280
4

Do you have the r8168 package installed?

Edit: I forgot the r8168 package is now in the AUR.

Edit: Have you tried loading the module? r8169

sudo modprobe r8169

2 Likes
5

Thanks a lot, the command worked.
:slight_smile:

6

I know this is solved but I have a question for you. I’ve lost ethernet a time or 3-4 over the years because of updates…it my case it was always something disabling the networkmanager.service or similar.
My question is how did you rule out–based on what OP showed you–a disabled service and hone right in on modprobe?
I’m asking only to improve my troubleshooting skills. Thanks.

7 
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: N/A modules: r8169 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000
    bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200

This particular Ethernet should run on the r8169 kernel module. It shows it’s not loaded driver: N/A modules: r8169

I asked if they had the r8168 package installed because some of these realtek chips will work on r8168 also or if like mine it works on either. Sometimes there are issues with one or the other depending on the specific chip. They should work on the r8169 kernel module and i see less cases of needing the r8168 package. The r8168 package is also no longer in the pacman repo as it a package in the AUR now. So i just asked if they had it installed because installing it usually blacklists the r8169 module i think. I didn’t think the OP had it installed because now you have to explicitly install it from the AUR where as before on eos it was installed on installation from the pacman repo. Therefore i asked them to load the module r8169 to see if it would work. Why it didn’t load on boot i don’t know. :man_shrugging:

1 Like
8

thank you. did not register the 8168/8169 thing although I read about it often.

1 Like