You are not logged in.
tl;dr
The root cause of the problem was somehow connected to RTL8111/8168/8211/8411 ethernet driver and slightly older version of the kernel. External system update via archiso resolved the issue
Hello! I've encountered a strange network issue over wired connection when casually loaded to the system and I'm having troubles to solve it. I have posted this issue on r/archlinux and recommendations provided there didn't help.
Description:
One day I loaded my system and found out that network is not reachable. ping 8.8.8.8 gives output that network is unreachable (immediately or after a timeout). After furher investigation I figured out that this ping issue is being solved by simple ip link interface up/down "restart". But when I try to launch my browser (firefox or chromium) ping is again recieving timeouts. Even if I don't start a browser and try to do smth like pacman -Syy, I get network troubles after few seconds of kinda looking normal download (progress bar)
Also strange thing that in the moment I can not reach even my router via ping command. ip link <interface> up/down sequence help to solve it, but then the issue is reproducing
I have dualboot on my PC and on Windows everything works fine, so it's not a hardware issue!
Versions and info:
(I'll add some pictures of some outputs, because I'm forced to write this issue from my phone, therefore it's hard to copy/paste the output)
kernel: 6.7.5-arch1-1
network manager: dhcpcd 10.0.6-1
ip route, ip link, systemctl status dhcpcd, pings output: https://ibb.co/3zBdPGh https://ibb.co/7jmcg5M https://ibb.co/9bnQm3f https://ibb.co/fG3kR9p https://ibb.co/YRLyvxN https://ibb.co/8xW443Q
lspci | grep Ethernet
25:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 11)
What I've tried:
- ip link up/down kinda helps for a while, but it looks like packets heavier than ICMP requests are breaking the network again
- I've checked ip route to check that gateway address is configured
- I've checked dhcpcd logs in case if there will be some specific errors that I could google
- I've tried to restart dhcpcd service and reboot the system
- I've added noipv6 feature to dhcpcd configuration
Actions I did after some help on reddit (unfortunately it didn't help):
- Disabled and stopped `systemd-homed` and `systemd-networkd` services
- Moved from `r8169` package to `r8168`
Please help to resolve this issue! It's so frustrating, I don't understand the root cause of the problem
Last edited by AvgLinuxEnjoyer (2024-05-06 11:22:56)
Offline
I have dualboot on my PC and on Windows everything works fine, so it's not a hardware issue!
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Then please post your complete system journal for a boot covering the network loss:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
kernel: 6.7.5-arch1-1
1. why are you running an old kernel?
2. how then did you install the r8168 module (it's linked to the kernel version, if you installed a module that's too new for your kernel, it'll have blacklisted r8169 but never itself loaded)
Offline
Hello, seth! Thank you for replying! Sorry for the late reply, I couldn't get to this thread on the week
I did have windows fast boot enabled and I disabled it with voodo reboots
Also I uploaded journalctl -b logs to 0x0.st:
https://0x0.st/X-yo.txt
Answers to your questions:
1. I'm running an old kernel because of that network problem which doesn't allow me to update the system. Also I access this PC not that often
2. I did `sudo pacman -S r8168` and it installed flawlessly. Well, it looks like it didn't make any difference at all. If it blacklist r8169 I think I wouldn't succeed in uploading boot logs to 0x0
Last edited by AvgLinuxEnjoyer (2024-04-14 10:13:04)
Offline
Apr 14 12:48:49 f54 kernel: r8168: loading out-of-tree module taints kernel.
You're loading it, presumingly because you also installed it quite a while ago.
Apr 14 12:48:51 f54 dhcpcd[480]: no interfaces have a carrier
Apr 14 12:48:51 f54 dhcpcd[480]: enp37s0: waiting for carrier
Apr 14 12:48:54 f54 dhcpcd[480]: enp37s0: carrier acquired
Apr 14 12:48:54 f54 dhcpcd[480]: enp37s0: IAID c2:61:c9:72
Apr 14 12:48:56 f54 dhcpcd[480]: enp37s0: rebinding lease of 192.168.31.238
Apr 14 12:48:56 f54 dhcpcd[480]: enp37s0: probing address 192.168.31.238/24
Apr 14 12:49:01 f54 dhcpcd[480]: enp37s0: leased 192.168.31.238 for 43200 seconds
Apr 14 12:49:01 f54 dhcpcd[480]: enp37s0: adding route to 192.168.31.0/24
Apr 14 12:49:01 f54 dhcpcd[480]: enp37s0: adding default route via 192.168.31.1
…
Apr 14 12:49:01 f54 dhcpcd[526]: Failed to set DNS configuration: Could not activate remote peer: activation request failed: unknown unit.
You've no issues getting lease and route, but the DNS configuration fails.
The journal then continues for ~8m w/o any issues (redshift fails because there's likely no X11 server) and you draw journals at 12:53, 12:54 and 12:57
Does this actually cover a network loss?
Offline
I fixed my issue by external system update via archiso:
mount /dev/sdX2 /mnt
mount /dev/sdX1 /mnt/boot
pacman -Syyu --sysroot /mnt
After reboot to the main arch system I got a boot error. Maybe --sysroot is not the best way to externally update the system so I did:
mount /dev/sdX2 /mnt
mount /dev/sdX1 /mnt/boot
arch-chroot /mnt
And reinstalled filesystem and linux packages:
pacman -S filesystem linux
mkinitcpio worked perfectly during the re-installation of linux package. Now everything works perfectly. I will mark this issue as solved
I guess the problem was dedicated to broken update on kernel 6.7.5-arch1-1 with strange bugged RTL8111/8168/8211/8411 driver behaviour. Thank you seth for your time on helping to figure this out
Last edited by AvgLinuxEnjoyer (2024-05-06 11:18:52)
Offline