Arch Linux User Repository

I just said, I have external factors that are responsible. So I'm not even looking at linux/windows systems, but my network as a whole. None of my lxc containers on a different host get dynamic IPs anymore on the relevant VLAN /subnet in question. I didn't go into more detail, bc/ don't wat to hijack this package for my personal troubleshooting as my issue is outside of this package, the aur, even arch - so please no more OT, it's already bad enough as it is.

(if any admin wants me to delete the comments, happy to do so)

erdnuesse 1) what happens if you use r8169 kernel module instead? 2) what happens if you boot to windows? (nowadays you can install it for free without pirating)

I am sorry for stirring this up, and was already thinking about deleting my comment. 2 days of digging took a toll, so first:

• using a live distro showed the same problem, so I have to have external problems, I didn't see beforehand. So while I'm still clueless what thi issue is, I think it's safe to say it's not related to this package, and I don't know if I should delete the essay I have down here, just to make sure no one gets the wrong impression.

My bad, sorry, moving along.

UPD: to make it maximally embarrasing; I rebooted my DHCP server, Switches, machine(even more), etc. each at least 4 times, but I needed a hard reset on my switch (pulling the plug!) to fix the issue. I never needed that before, so thanks tp-link I guess. It's fixed, though I will probably never know what device or what moment caused the network stack to hang itself for the past 2/3 days. Again sorry for the fuzz.

@erdnuesse

i have the same adapter and it works with vanilla kernel, which have builtin module r8169 which automatically picks this adapter up

the reason why i tried using this package before was because i thought there is smth wrong with aforementioned module, but apparently my problems were caused by a bad ethernet cable, and replacing it solved them (so it works now with r8169)

UPD: just noticed i have (rev 05) at the end and you (rev 04) - so then i can't guarantee regarding what was said above

For the last two days my NIC stopped working. I would love to be more helpful, but after all debugging, I have not even a clue what the last working config was, because... well I started tinkering without a fully documented home-setup.

• Ruled out the updated networkmanager (update came the day before), as I now switched to systemd-network
• wifi works, so my network stack isn't 100% broken
• tried blocking multiple modules as seen on the web
• removed and re-added the module
• seen errors about WoL capabilities and invalid VPD tag 0x00 in dmesg
• tried BIOS settings to satisfy WoL capabilities (MSI does not have a good track record with their BIOS/UEFI)
• tried r8168-lts as well for the lts kernel I have as fallback, when regular booting into lts didn't help.
• deactivated ipv6 globally
• removed dhcpcd/dhclient from the nm-setup earlier

link is apparently up, but I never get an IP via dhcpcd, static IP seems to be attached to the iface, but it's defunct, as my switch shows just receiving traffic on the iface. Port: TX good: 0pkt | RX good: 300pkt No bad pkts, yes, I tried different ports, just to be sure.

I have no idea what happened during the last 3 days now in terms of updates or regressions, as I update a few times a week.

MB: MSI x570 Tomahawk [RTL8125 2.5GbE Controller (rev 04)], latest BIOS, r8125 Ethernet controller driver 9.014.01-NAPI, 6.12.9-zen1-1-zen (same with arch kernel or lts 6.6.70-1)

tldr:

• switch says it gets pkgs, but somewhere between layer 1 and 2 it determines it can't / won't send out
• device appears and loads modules on host, but network traffic just does not happen (dhcp) (requests don't reach the dhcpd)
• even with static IP (L3) there's no L2 traffic

• lspci + dmesg output below

  ~# lspci -v -d ::0200 26:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 04) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c84 Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 23 I/O ports at f000 [size=256] Memory at fc900000 (64-bit, non-prefetchable) [size=64K] Memory at fc910000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: r8125 Kernel modules: r8169, r8125

  ~# sudo dmesg | grep r8125 [ 3.300623] r8125 Ethernet controller driver 9.014.01-NAPI loaded [ 3.300656] r8125 0000:26:00.0: enabling device (0000 -> 0003) [ 3.663406] r8125: <Patents trimmed> [ 4.411900] r8125 0000:26:00.0 enp38s0: renamed from eth0 [ 6.807234] r8125 0000:26:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM [ 8.593054] r8125: enp38s0: link up

  ~# sudo networkctl status enp38s0 2: enp38s0 Link File: /etc/systemd/network/99-default.link Network File: /etc/systemd/network/00-enp38s0.network State: carrier (configuring) Online state: offline

not all r8125 chips are the same. rev 0c is not supported by the r8169 driver. for those who need instructions. (you'll obviously need some sort of internet connection)

sudo nano /etc/modprobe.d/r8169.conf

type this in

blacklist r8169

save and exit

install linux-headers, dkms, and r8125-dkms (yay or however you install aur packages)

sudo pacman -Syu linux-headers dkms
yay -Syu r8125-dkms

reboot gtg

also, your upstream url goes to a 404.

@Korialo No issues with r8129 for me either. This module might still be useful with LTS kernels, but I'm not completely sure.

@Melody666 Support for rtl8125 is already included in the r8169 driver, a simple modinfo into r8169 module will show the following:

❯ modinfo r8169
filename:       /lib/modules/6.11.5-arch1-1/kernel/drivers/net/ethernet/realtek/r8169.ko.zst
firmware:       rtl_nic/rtl8126a-2.fw
firmware:       rtl_nic/rtl8125b-2.fw <-- look here 
firmware:       rtl_nic/rtl8125a-3.fw <-- look also here
firmware:       rtl_nic/rtl8107e-2.fw 
firmware:       rtl_nic/rtl8168fp-3.fw
firmware:       rtl_nic/rtl8168h-2.fw
firmware:       rtl_nic/rtl8168g-3.fw
firmware:       rtl_nic/rtl8168g-2.fw
firmware:       rtl_nic/rtl8106e-2.fw
firmware:       rtl_nic/rtl8106e-1.fw
firmware:       rtl_nic/rtl8411-2.fw
firmware:       rtl_nic/rtl8411-1.fw
firmware:       rtl_nic/rtl8402-1.fw
firmware:       rtl_nic/rtl8168f-2.fw
firmware:       rtl_nic/rtl8168f-1.fw
firmware:       rtl_nic/rtl8105e-1.fw
firmware:       rtl_nic/rtl8168e-3.fw
firmware:       rtl_nic/rtl8168e-2.fw
firmware:       rtl_nic/rtl8168e-1.fw
firmware:       rtl_nic/rtl8168d-2.fw
firmware:       rtl_nic/rtl8168d-1.fw
license:        GPL
softdep:        pre: realtek
description:    RealTek RTL-8169 Gigabit Ethernet driver
author:         Realtek and the Linux r8169 crew <netdev@vger.kernel.org>
srcversion:     03BE299419F20E3AF93C3BF
alias:          pci:v000010ECd00003000sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008126sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008125sv*sd*bc*sc*i* <-- check lspci
alias:          pci:v00000001d00008168sv*sd00002410bc*sc*i*
alias:          pci:v00001737d00001032sv*sd00000024bc*sc*i*
alias:          pci:v000016ECd00000116sv*sd*bc*sc*i*
alias:          pci:v00001259d0000C107sv*sd*bc*sc*i*
alias:          pci:v00001186d00004302sv*sd*bc*sc*i*
alias:          pci:v00001186d00004300sv*sd*bc*sc*i*
alias:          pci:v00001186d00004300sv00001186sd00004B10bc*sc*i*
alias:          pci:v000010ECd00008169sv*sd*bc*sc*i*
alias:          pci:v000010FFd00008168sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008168sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008167sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008162sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008161sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008136sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008129sv*sd*bc*sc*i*
alias:          pci:v000010ECd00002600sv*sd*bc*sc*i*
alias:          pci:v000010ECd00002502sv*sd*bc*sc*i*
depends:        libphy,mdio_devres
retpoline:      Y
intree:         Y
name:           r8169
vermagic:       6.11.5-arch1-1 SMP preempt mod_unload 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        26:5B:4C:74:B5:2A:1C:69:CD:81:4A:65:46:35:E3:E1:71:30:AF:ED
sig_hashalgo:   sha512
signature:      30:64:02:30:49:53:45:D9:62:BD:38:7A:F5:BD:75:D7:1C:38:47:B7:
        F9:FF:F9:84:B1:FC:0D:96:9F:95:57:56:E4:B0:DB:9A:75:82:5D:47:
        57:F1:DC:3E:74:00:02:61:89:08:41:73:02:30:5F:53:89:46:50:68:
        AB:40:1B:45:32:36:DD:F7:BA:31:9D:8B:C5:1B:FA:5A:19:02:9B:25:
        9F:07:2B:56:C0:39:16:49:19:A5:57:01:51:EE:0B:DE:3A:78:8B:B6:
        6B:5E

I generally use this driver for testing and to compare it to the builtin kernel module, I have no issues with the r8169 driver.

@Melody666 You can use patch from devome https://aur.archlinux.org/packages/r8125-dkms#comment-977750 I can build successfully after applying it.

Just to save people time, this driver does not work out of the box with the latest kernel and does not install. This is probably meant for LTS kernels.