Hello everyone,
Sorry for the translation with simple translate.
Even with the live usb I have no wired internet and I do have wifi. I also have the same problem with other Linux distributions from kernel 6. and higher, while with LTS kernel 5.15.x I do have wired internet and also wifi. And also with Windows 10 I have no problems with the internet.
I’ve done a lot of searching and asking on other forums, but haven’t found a solution yet.
I have replaced the r8169 driver with r8168 to no avail, and rebooting with and without wifi makes no difference.
I also thought to try Fedora with LTS kernel 5.15, but can’t find how to install it. My system information inxi -Fxz is as follows, if more information is needed please let me know.
Here, on a Dell desktop, the Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet has been troublefree with Fedora 36, 37, and 38. Is you system fully updated?
The vendor:device ID is 10ec:8168. Use this with lspci to see the subsystem ID:
% lspci -d 10ec:8168 -nnvv
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: Dell Device [1028:0930]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at 3000 [size=256]
Region 2: Memory at d1304000 (64-bit, non-prefetchable) [size=4K]
Region 4: Memory at d1300000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: r8169
Kernel modules: r8169
This gets us to http://linux-hardware.org/?id=pci:10ec-8168-1028-0930, which mentions an alternative driver. There, Issue 54 provides a patch for 6.4 kernels.
You should look for details of the failure in dmesg or using journalctl:
% journalctl -b -g eth0
Aug 26 09:30:38 x kernel: r8169 0000:01:00.0 eth0: RTL8168h/8111h, e4:54:e8:7d:e4:12, XID 541, IRQ 134
Aug 26 09:30:38 x kernel: r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
Aug 26 09:30:38 x kernel: r8169 0000:01:00.0 enp1s0: renamed from eth0
You have /org/freedesktop/NetworkManager. Fedora provides:
% type NetworkManager
NetworkManager is /usr/sbin/NetworkManager
% dnf5 info NetworkManager.x86_64
Updating and loading repositories:
Repositories loaded.
Installed packages
Name : NetworkManager
Epoch : 1
Version : 1.42.8
Release : 1.fc38
Architecture : x86_64
Installed size : 5.8 MiB
Source : NetworkManager-1.42.8-1.fc38.src.rpm
From repository : updates
Summary : Network connection manager and user applications
URL : https://networkmanager.dev/
License : GPLv2+ and LGPLv2+
Description : NetworkManager is a system service that manages network interfaces and
: connections based on user or automatic configuration. It supports
: Ethernet, Bridge, Bond, VLAN, Team, InfiniBand, Wi-Fi, mobile broadband
: (WWAN), PPPoE and other devices, and supports a variety of different VPN
: services.
If you replace Fedora components with other stuff it is impossible for users who stick with the Fedora packages to reproduce your problem. Depending on how the non-standard NetworkManager was installed, it may be difficult to restore a normal Fedora configuration.
I don’t understand this, I just installed numlockx and LibreOffice language pack. I have not installed anything else.
Is it possible it’s because I have the Cinnamon desktop?
With me type NetworkManager shows :
[rinus@fedora ~]$ type NetworkManager
NetworkManager is /usr/sbin/NetworkManager
[rinus@fedora ~]$ dnf5 info NetworkManager.x86_64
bash: dnf5: command not found
Do you think the NetworkManager is the problem?
But the problem was already with the live usb with the kernel 6.2.x before I installed Fedora.
I found the reference to /org/freedesktop/NetworkManager/ in one of my systems, but for enp1s0. You appear to have only one ethernet adapter, so
I don’t understand why it would use enp2s0.
Compare your system with:
% journalctl -b -g enp.s0
Aug 26 09:30:38 X kernel: r8169 0000:01:00.0 enp1s0: renamed from eth0
Aug 26 09:30:47 X NetworkManager[1094]: <info> [1693053047.9573] manager: (enp1s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Aug 26 09:30:47 X NetworkManager[1094]: <info> [1693053047.9574] device (enp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 26 09:30:48 X kernel: r8169 0000:01:00.0 enp1s0: Link is Down
Aug 26 09:30:50 X kernel: r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control off
Aug 26 09:30:50 X kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
Aug 26 09:30:50 X NetworkManager[1094]: <info> [1693053050.8864] device (enp1s0): carrier: link connected
Aug 26 09:30:50 X NetworkManager[1094]: <info> [1693053050.8872] device (enp1s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Aug 26 09:30:50 X NetworkManager[1094]: <info> [1693053050.8897] device (enp1s0): Activation: starting connection 'Wired connection 1' (56f3a22c-276d-39fd-b874-d27e3eed879f)
Aug 26 09:30:50 X NetworkManager[1094]: <info> [1693053050.8899] device (enp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 26 09:30:50 X NetworkManager[1094]: <info> [1693053050.8909] device (enp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 26 09:30:50 X NetworkManager[1094]: <info> [1693053050.9009] device (enp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 26 09:30:50 X NetworkManager[1094]: <info> [1693053050.9012] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Aug 26 09:30:52 X systemd-resolved[847]: enp1s0: Bus client set default route setting: no
Aug 26 09:30:53 X NetworkManager[1094]: <info> [1693053053.3005] dhcp4 (enp1s0): state changed new lease, address=192.168.2.226
Aug 26 09:30:53 X avahi-daemon[874]: Joining mDNS multicast group on interface enp1s0.IPv4 with address 192.168.2.226.
Aug 26 09:30:53 X systemd-resolved[847]: enp1s0: Bus client set search domain list to: home
Aug 26 09:30:53 X avahi-daemon[874]: New relevant interface enp1s0.IPv4 for mDNS.
Aug 26 09:30:53 X avahi-daemon[874]: Registering new address record for 192.168.2.226 on enp1s0.IPv4.
Aug 26 09:30:53 X systemd-resolved[847]: enp1s0: Bus client set default route setting: yes
Aug 26 09:30:53 X systemd-resolved[847]: enp1s0: Bus client set DNS server list to: 192.168.2.1, 142.166.166.166
Aug 26 09:30:53 X NetworkManager[1094]: <info> [1693053053.3212] device (enp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Aug 26 09:30:53 X NetworkManager[1094]: <info> [1693053053.3257] device (enp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Aug 26 09:30:53 X NetworkManager[1094]: <info> [1693053053.3261] device (enp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Aug 26 09:30:53 X NetworkManager[1094]: <info> [1693053053.3286] device (enp1s0): Activation: successful, device activated.
Aug 26 09:30:53 X NetworkManager[1094]: <info> [1693053053.5342] policy: set 'Wired connection 1' (enp1s0) as default for IPv4 routing and DNS
Aug 27 21:30:52 X NetworkManager[1094]: <info> [1693182652.9357] dhcp4 (enp1s0): state changed new lease, address=192.168.2.226
If you haven’t installed dnf5 (for testing), use the old dnf.
[rinus@fedora ~]$ export LANG=C
[rinus@fedora ~]$ dnf info NetworkManager .x86_64
Last metadata expiration check: 0:03:14 ago on Mon Aug 28 20:28:59 2023.
Installed Packages
Name : NetworkManager
Epoch : 1
Version : 1.42.8
Release : 1.fc38
Architecture : x86_64
Size : 5.8 M
Source : NetworkManager-1.42.8-1.fc38.src.rpm
Repository : @System
From repo : updates
Summary : Network connection manager and user applications
URL : https://networkmanager.dev/
License : GPLv2+ and LGPLv2+
Description : NetworkManager is a system service that manages network
: interfaces and connections based on user or automatic
: configuration. It supports Ethernet, Bridge, Bond, VLAN, Team,
: InfiniBand, Wi-Fi, mobile broadband (WWAN), PPPoE and other
: devices, and supports a variety of different VPN services.
[rinus@fedora ~]$
And journalctl -b -g enp.s0 shows:
[rinus@fedora ~]$ journalctl -b -g enp.s0
Aug 28 19:45:07 fedora kernel: r8169 0000:02:00.0 enp2s0: renamed from eth0
Aug 28 19:45:25 fedora NetworkManager[796]: <info> [1693244725.6791] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/>
Aug 28 19:45:25 fedora NetworkManager[796]: <info> [1693244725.6848] settings: (enp2s0): created default wired connection 'Bekabelde verbinding 1'
Aug 28 19:45:25 fedora NetworkManager[796]: <info> [1693244725.6848] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-i>
Aug 28 19:45:25 fedora kernel: r8169 0000:02:00.0 enp2s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Aug 28 19:45:25 fedora kernel: r8169 0000:02:00.0 enp2s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
Aug 28 19:45:25 fedora kernel: r8169 0000:02:00.0 enp2s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
Aug 28 19:45:25 fedora kernel: r8169 0000:02:00.0 enp2s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
Aug 28 19:45:25 fedora kernel: r8169 0000:02:00.0 enp2s0: rtl_ocp_gphy_cond == 1 (loop: 10, delay: 25).
Aug 28 19:45:25 fedora kernel: r8169 0000:02:00.0 enp2s0: Link is Down
lines 1-10/10 (END)
After many unsuccessful attempts (download timeout every time) I finally managed to install kernel 5.15.
After rebooting with kernel 5.15.129-200.fc38.86_64 my internet connection is fine.
So with kernel 5.15 I have wired internet and also wifi, but with the current kernel I don’t have wired internet, only wifi.
journalctl -b -g enp.s0 with kernel 5.15 shows:
[rinus@fedora ~]$ journalctl -b -g enp.s0
sep 02 11:44:16 fedora kernel: r8169 0000:02:00.0 enp2s0: renamed from eth0
sep 02 11:44:30 fedora NetworkManager[801]: <info> [1693647870.5649] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
sep 02 11:44:30 fedora NetworkManager[801]: <info> [1693647870.5653] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'exte>
sep 02 11:44:30 fedora kernel: r8169 0000:02:00.0 enp2s0: Link is Down
sep 02 11:44:33 fedora kernel: r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control off
sep 02 11:44:33 fedora kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
sep 02 11:44:33 fedora NetworkManager[801]: <info> [1693647873.8441] device (enp2s0): carrier: link connected
sep 02 11:44:33 fedora NetworkManager[801]: <info> [1693647873.8446] device (enp2s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-s>
sep 02 11:44:33 fedora NetworkManager[801]: <info> [1693647873.8470] device (enp2s0): Activation: starting connection 'Bekabelde verbinding 1' (a0fa2184-622f-346b-8cb>
sep 02 11:44:33 fedora NetworkManager[801]: <info> [1693647873.8471] device (enp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
sep 02 11:44:33 fedora NetworkManager[801]: <info> [1693647873.8476] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
sep 02 11:44:33 fedora NetworkManager[801]: <info> [1693647873.8727] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
sep 02 11:44:33 fedora NetworkManager[801]: <info> [1693647873.8736] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
sep 02 11:44:33 fedora avahi-daemon[669]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::4bd3:6c10:3910:e8bb.
sep 02 11:44:33 fedora avahi-daemon[669]: New relevant interface enp2s0.IPv6 for mDNS.
sep 02 11:44:33 fedora avahi-daemon[669]: Registering new address record for fe80::4bd3:6c10:3910:e8bb on enp2s0.*.
sep 02 11:44:35 fedora systemd-resolved[620]: enp2s0: Bus client set default route setting: no
sep 02 11:44:35 fedora NetworkManager[801]: <info> [1693647875.3931] dhcp6 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
sep 02 11:44:35 fedora avahi-daemon[669]: Leaving mDNS multicast group on interface enp2s0.IPv6 with address fe80::4bd3:6c10:3910:e8bb.
sep 02 11:44:35 fedora NetworkManager[801]: <info> [1693647875.3986] dhcp6 (enp2s0): state changed new lease
sep 02 11:44:35 fedora avahi-daemon[669]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fd00::8b45:3d49:a256:158.
sep 02 11:44:35 fedora avahi-daemon[669]: Registering new address record for fd00::8b45:3d49:a256:158 on enp2s0.*.
sep 02 11:44:35 fedora avahi-daemon[669]: Withdrawing address record for fe80::4bd3:6c10:3910:e8bb on enp2s0.
[rinus@fedora ~]$
@gnwiii ,
With kernel 5.15 i have also /org/freedesktop/NetworkManager/ for enp2s0 see post 10, and with kernel 5.15 i have wired internet and also wifi.
Therefore I think the NetworkManager is not the problem, but something in the kernel of kernel 6. and above
You can get the Subsystem ID for your Realtek chip with lspci -kvnn | sed -n '/Network/,/^$/ p'. With this you can look for entries in the Linux Hardware Database that use a 6.x kernel. There may be information on Lenovo forums.
Sorry for slow reply - long weekend here in Canada and I left the Inbox alone which means it is overflowing
Sounds from the above like a kernel driver problem. Unfortunately the IdeaCenter’s aren’t in the Linux program so I have no experience with them and don’t know why it stopped working. I don’t have access to any of that HW to debug directly.
If you send me the kernel logs (output from ‘journalctl -k’ - send to markpearson at lenovo dot com) I’ll have a look through and see if anything jumps out as wrong. Those rtl_ocp_gphy_cond errors are interesting and I’m intrigued if there is anything else before them.
Sometimes (and I’ve never seen this with a Realtek device) the kernel update and the linux-firmware need to be in sync or things can break. As you tried a Fedora live session that’s likely not the problem here though.
You’re unlikely to get any drivers from the Lenovo site - even with the linux supported platforms we do all our fixes upstream so that any distro can work and avoid putting extras on the support site. Doing out of tree drivers is generally pretty painful (there are a few exceptions, but they’re rare).
You can run this command in your terminal. Just copy and paste the command and it will create this or a txt-file you are choosing the name, it is up to you… mine is just an example.
journalctl -k just prints it in the Terminal. >> network-issue.txt redirects in to a file.
