no need to reinstall simply run sudo pacman -Syu linux-lts linux-lts-headers and reboot
1 Like
I reinstalled the system from scratch to have a clean situation. I selected kernel-LTS in the options. After a dozen minutes the system was ready. I booted the new kernel.
Unfortunately, the situation is the same as on Live: the eth connection is disconnected and I cannot activate it with ip or ifconfig commands.
The attempt did not work.
[ 0.347832] pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000
[ 4.641654] r8169 0000:01:00.0 eth0: RTL8168h/8111h, 68:1d:ef:32:6e:3b, XID 541, IRQ 127
[ 4.641669] r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
[ 5.398655] r8169 0000:01:00.0 enp1s0: renamed from eth0
[ 5.774265] Generic FE-GE Realtek PHY r8169-0-100:00: attached PHY driver (mii_bus:phy_addr=r8169-0-100:00, irq=MAC)
[ 5.999074] r8169 0000:01:00.0 enp1s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
[ 5.999648] r8169 0000:01:00.0 enp1s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
[ 6.000205] r8169 0000:01:00.0 enp1s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
[ 6.000233] r8169 0000:01:00.0 enp1s0: Link is Down
Using the r8168 module, the LAN âdisappearsâ
I guess this is a long shot (especially if Windows works on the same machine and hardware), but could the issue be something as simple as a faulty cable, or the cable not properly plugged?
And have you tried re-plugging the cable?
The cable works very well in Windows 11. However, I have re-plugged it.
I have been using EOS, formerly Antergos, for a dozen years, but I always consider myself a beginner who is still learning 
After start-up in the NIC, the yellow and green lights come on briefly, then the yellow one remains steady.
In correspondence on the syslog are the messages:
[ 5.999074] r8169 0000:01:00.0 enp1s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
[ 5.999648] r8169 0000:01:00.0 enp1s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
[ 6.000205] r8169 0000:01:00.0 enp1s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
I am, however, becoming convinced that perhaps there is a hardware-related problem.
As I said, I recently installed EOS on another system with the same NIC, without any problems, as many others have.
It might be some simple NIC setting too, but seems extremely hard to figure out. Would need the expert of that particular hardware and driver dev.
Or, could be something related to the router⌠but this is just another wild guess, and less likely.
Sorry about not being able to help solving this. 
It may also just work when installed. One doesnât always know. 
I think he said it is still not working after install.
But who knows⌠there have been older reports some years ago that a particular kernel version has failed, but a later one was working. Hard to know if that is the case here or not.
Again this is a different chip. It is RTL8168h/8111h.
https://www.realtek.com/en/products/connected-media-ics/item/rtl8111h-s-cg
I am tired of wasting my time and making others waste it with a strange hw.
With an ETH â USB adapter it works!
End of my issue. Solved
1 Like
That is a great solution in this case! 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.