Ethernet will sometimes connect, but most of the time it won't

Issues & Assistance
1

Hi this is my first post, but long time lurker.

I have browsed a few forums at this point and nothing has seems to help thus far. I have attach a bug report system log: 4853646

Context: My WiFi works perfectly fine. A few weeks ago I decided to try ethernet for the first time. It work fine up until I restarted my computer. After that initial point my computer has failed to register it. I have messed around with the drivers and that had little to no effect. Although at first it seemed promising when I did the following: sudo pacman -S linux-firmware

My system registered the ethernet, but also recommended to reboot which put be right back at the beginning.

failed_input_connection
failed_input_connection381×141 25.5 KB

2

I am still messing about with these terminal commands some how I got my computer to register the ethernet. I am still scratching my head tho…

❯ ls -lh /lib/firmware/rtl_nic/rtl8126*
Permissions Size User Date Modified Name
.rw-r--r--  7.9k root 11 Mar 13:07   /lib/firmware/rtl_nic/rtl8126a-2.fw.zst
.rw-r--r--  4.4k root 11 Mar 13:07   /lib/firmware/rtl_nic/rtl8126a-3.fw.zst

~
❯ # 1. Load the driver
  sudo modprobe r8169

  # 2. Verify interface exists
  ip link show
  # Look for: enp14s0 with MAC 34:5a:60:be:61:bd

  # 3. Check current status (should show "Link detected: no")
  sudo ethtool enp14s0
[sudo] password for whobuddy: 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether f4:28:9d:ad:af:cb brd ff:ff:ff:ff:ff:ff
3: enp10s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether fc:9d:05:04:9f:78 brd ff:ff:ff:ff:ff:ff
    altname enxfc9d05049f78
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
No data available

After running #3 it suddenly connected! I am going to reboot to see if it persists.

3

So it did not persist after rebooting. But merely running

sudo modprobe r8169

my system will then recognize the existence of my ethernet. So my question how can I get it to persist after rebooting/shutdown?

4

Hello and welcome,

Can you please return the output of;

lsmod | grep r8

(maybe before its ‘fixed’)

5

I got the following:

❯ lsmod | grep r8
r8169                 176128  0
mdio_devres            12288  1 r8169
libphy                196608  3 r8169,mdio_devres,realtek
mdio_bus               65536  3 r8169,libphy,realtek

~
6

Odd so its already loaded.

Well anyways we can try to have it force loaded by adding it to /etc/modules-load.d;

bash -c 'echo "r8169" | sudo tee /etc/modules-load.d/r8169.conf'

Or otherwise we can create a service or script to perform the modprobe after login or similar.

7

The command returned r8169, but upon reboot it did not persist.

Its interesting that when I used modprobe I get this popup.
activated

Typically it lags a few seconds after the command.

8

Just to make sure the file was created successfully;

cat /etc/modules-load.d/r8169.conf
9

Do modules need to be activated on startup?

❯ cat /etc/modules-load.d/r8169.conf
r8169

~
10

Yup it is what we wanted. But if it does not help then you can delete the file.

sudo rm /etc/modules-load.d/r8169.conf

Most normally dont need anything extra and start automatically.

Your r8169 seems to also start automatically - as shown by the lsmod output.

Yet you report using modprobe enables the ethernet connection.

11

Did you ever get any movement on this @Whobuddy ?

Did we ever try with one of the 8125 or 8126 packages ?