Kernel 6.5.12 or later on Fedora 39 broken network on Lenovo T570

Ask Fedora
, , ,
1

Hi all,
on advice @computersavvy i opened a separate thread
im using Lenovo t570 and if im using kernel 6.5.12 i have no possibility to use network (ethernet and wifi) dmesg showing the cards but network-manager cannot use them. My workaround was too to use kernel 6.5.11 again.

gdm
gdm1920×2560 271 KB

The buttons on picture where normally network and wifi appearing are empty and disappearing after some seconds.
If im logging in then some commands are not possible. “ip addr” makes it hanging as “nmcli” too.

What im surely know is that 6.5.11 can be booted normally without problems, 6.5.12 problem is reproducable every boot.

lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1199:9079 Sierra Wireless, Inc. EM7455
Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 005: ID 04f2:b5ab Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 006: ID 138a:0097 Validity Sensors, Inc. [unknown]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 005: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 006: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 006: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 004 Device 007: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 004 Device 008: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 004 Device 009: ID 046d:086b Logitech, Inc. BRIO 4K Stream Edition

lspci:

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
	Subsystem: Lenovo ThinkPad T570 [17aa:2247]
	Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02)
	Subsystem: Lenovo Device [17aa:2247]
	Kernel driver in use: i915
	Kernel modules: i915
00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
	Subsystem: Lenovo ThinkPad T570 [17aa:2247]
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
	Subsystem: Lenovo ThinkPad T570 [17aa:2247]
	Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
	Subsystem: Lenovo ThinkPad T570 [17aa:2247]
	Kernel driver in use: intel_pch_thermal
	Kernel modules: intel_pch_thermal
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
	Subsystem: Lenovo ThinkPad T570 [17aa:2247]
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:16.3 Serial controller [0700]: Intel Corporation Sunrise Point-LP Active Management Technology - SOL [8086:9d3d] (rev 21)
	Subsystem: Lenovo ThinkPad T570 [17aa:2247]
	Kernel driver in use: serial
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1)
	Subsystem: Lenovo Device [17aa:2247]
	Kernel driver in use: pcieport
00:1c.6 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #7 [8086:9d16] (rev f1)
	Subsystem: Lenovo Device [17aa:2247]
	Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1)
	Subsystem: Lenovo ThinkPad T570 [17aa:2247]
	Kernel driver in use: pcieport
00:1d.2 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #11 [8086:9d1a] (rev f1)
	Subsystem: Lenovo Device [17aa:2247]
	Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point LPC/eSPI Controller [8086:9d4e] (rev 21)
	Subsystem: Lenovo Device [17aa:2247]
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21)
	Subsystem: Lenovo ThinkPad T570 [17aa:2247]
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21)
	Subsystem: Lenovo Device [17aa:2247]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel, snd_soc_skl, snd_soc_avs, snd_sof_pci_intel_skl
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21)
	Subsystem: Lenovo ThinkPad T570 [17aa:2247]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (4) I219-LM [8086:15d7] (rev 21)
	Subsystem: Lenovo Device [17aa:2247]
	Kernel driver in use: e1000e
	Kernel modules: e1000e
04:00.0 Network controller [0280]: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
	Subsystem: Intel Corporation Dual Band Wireless-AC 8265 [Windstorm Peak] [8086:0010]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
07:00.0 PCI bridge [0604]: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] [8086:15c0] (rev 01)
	Subsystem: Device [2222:1111]
	Kernel driver in use: pcieport
08:00.0 PCI bridge [0604]: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] [8086:15c0] (rev 01)
	Subsystem: Device [2222:1111]
	Kernel driver in use: pcieport
08:01.0 PCI bridge [0604]: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] [8086:15c0] (rev 01)
	Subsystem: Device [2222:1111]
	Kernel driver in use: pcieport
08:02.0 PCI bridge [0604]: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] [8086:15c0] (rev 01)
	Subsystem: Device [2222:1111]
	Kernel driver in use: pcieport
3f:00.0 USB controller [0c03]: Intel Corporation JHL6240 Thunderbolt 3 USB 3.1 Controller (Low Power) [Alpine Ridge LP 2016] [8086:15c1] (rev 01)
	Subsystem: Device [2222:1111]
	Kernel driver in use: xhci_hcd
40:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 [144d:a804]
	Subsystem: Samsung Electronics Co Ltd SM963 2.5" NVMe PCIe SSD [144d:a801]
	Kernel driver in use: nvme
	Kernel modules: nvme

inxi -Fzxx → Command hangs too

with kernel 6.5.11 inxi -Fzxx command, maybe it helps:

inxi -Fzxx
System:
  Kernel: 6.5.11-300.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-13.fc39 Desktop: GNOME v: 45.1 tk: GTK v: 3.24.38 wm: gnome-shell
    dm: GDM Distro: Fedora release 39 (Thirty Nine)
Machine:
  Type: Laptop System: LENOVO product: 20HAS2U500 v: ThinkPad T570
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 20HAS2U500 serial: <superuser required> UEFI: LENOVO
    v: N1VET65W (1.55 ) date: 09/05/2023
Battery:
  ID-1: BAT0 charge: 23.1 Wh (79.4%) condition: 29.1/32.0 Wh (90.8%)
    volts: 16.2 min: 15.3 model: SMP 00UR891 serial: <filter>
    status: not charging
  ID-2: BAT1 charge: 5.9 Wh (25.0%) condition: 23.6/24.0 Wh (98.3%)
    volts: 12.6 min: 11.5 model: SMP 01AV452 serial: <filter> status: charging
  Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus
    M705 serial: <filter> charge: 55% (should be ignored) status: discharging
  Device-2: hidpp_battery_1 model: Logitech MK700 serial: <filter>
    charge: 70% (should be ignored) status: discharging
CPU:
  Info: dual core model: Intel Core i7-7600U bits: 64 type: MT MCP
    arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB
    L3: 4 MiB
  Speed (MHz): avg: 3523 high: 3600 min/max: 400/3900 cores: 1: 3494 2: 3500
    3: 3500 4: 3600 bogomips: 23199
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel
    arch: Gen-9.5 ports: active: DP-1,eDP-1 empty: DP-2,HDMI-A-1,HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:5916
  Device-2: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-8:4 chip-ID: 04f2:b5ab
  Device-3: Logitech BRIO 4K Stream Edition
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.1
    speed: 5 Gb/s lanes: 1 bus-ID: 4-1.1.1:4 chip-ID: 046d:086b
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.2
    compositor: gnome-shell driver: X: loaded: modesetting dri: crocus gpu: i915
    display-ID: 0
  Monitor-1: DP-1 model: Philips PHL 346B1C res: 3440x1440 dpi: 110
    diag: 864mm (34")
  Monitor-2: eDP-1 model: LG Display 0x0541 res: 1920x1080 dpi: 142
    diag: 395mm (15.5")
  API: OpenGL v: 4.6 vendor: intel mesa v: 23.2.1 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel HD Graphics 620 (KBL GT2)
    device-ID: 8086:5916 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
  Device-2: Logitech BRIO 4K Stream Edition
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.1
    speed: 5 Gb/s lanes: 1 bus-ID: 4-1.1.1:4 chip-ID: 046d:086b
  API: ALSA v: k6.5.11-300.fc39.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 0.3.85 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d7
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24fd
  IF: wlp4s0 state: down mac: <filter>
  Device-3: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 3.0 speed: 5 Gb/s lanes: 1 bus-ID: 4-1.2:5 chip-ID: 0bda:8153
  IF: enp63s0u1u2 state: down mac: <filter>
  IF-ID-1: wwp0s20f0u6i12 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-7:3 chip-ID: 8087:0a2b
  Report: btmgmt ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 4.2
    lmp-v: 8
Drives:
  Local Storage: total: 238.47 GiB used: 15.6 GiB (6.5%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLW256HEHP-000L7
    size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 27.9 C
Partition:
  ID-1: / size: 236.87 GiB used: 15.29 GiB (6.5%) fs: btrfs dev: /dev/dm-0
    mapped: luks-00ab2b43-22fa-4062-8781-c01fda52b288
  ID-2: /boot size: 973.4 MiB used: 307.9 MiB (31.6%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 17.4 MiB (2.9%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 236.87 GiB used: 15.29 GiB (6.5%) fs: btrfs
    dev: /dev/dm-0 mapped: luks-00ab2b43-22fa-4062-8781-c01fda52b288
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 75.0 C pch: 49.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 327 Uptime: 6m Memory: total: 16 GiB note: est.
  available: 15.32 GiB used: 4.69 GiB (30.6%) Init: systemd v: 254
  target: graphical (5) default: graphical Compilers: gcc: 13.2.1 Packages:
  pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 2 Shell: Bash v: 5.2.21
  running-in: gnome-terminal inxi: 3.3.31
2

If this not works it is possible that the driver is missing on the latest 6.5 kernel or simply the hardware is recognized as a different one. The Intel drivers should not be a problem.

It got released the 6.6 kernel, you might give this a chance. But before check the /etc/dnf/dnf.conf about
the entry: installonly_limit=3 set it to 3 or higher. So it will keep the older kernels, an you have still a fallback.

3

Hi @ilikelinux ,
no, the full update and Kernel 6.6 was not solving. I had to fall back again to kernel 6.5.11.
What i got out from journalctl -u NetworkManager|egrep '31f6|Boot'

unsuccessful network after boot kernel 6.6

-- Boot 226d881418d3424885c5bd6c954f82f5 --
Nov 29 14:29:52 NetworkManager[2186]: <info>  [1701264592.7360] manager: (enp0s31f6): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Nov 29 14:29:52 NetworkManager[2186]: <info>  [1701264592.7374] settings: (enp0s31f6): created default wired connection 'Kabelgebundene Verbindung 1'
Nov 29 14:29:52 NetworkManager[2186]: <info>  [1701264592.7375] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Nov 29 14:29:56 NetworkManager[2186]: <info>  [1701264596.4155] device (enp0s31f6): carrier: link connected
Nov 29 14:29:56 NetworkManager[2186]: <info>  [1701264596.4158] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')

as i searched more to timestamp i also got out

Nov 29 14:29:56 kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Nov 29 14:29:56 NetworkManager[2186]: <info>  [1701264596.4155] device (enp0s31f6): carrier: link connected
Nov 29 14:29:56 NetworkManager[2186]: <info>  [1701264596.4158] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')

here a successful network with 6.5.11 for comparision:

-- Boot e324e04d99c64da2a9aa6d5cccaff53d --
Nov 29 14:33:48 NetworkManager[2262]: <info>  [1701264828.9250] manager: (enp0s31f6): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Nov 29 14:33:48 NetworkManager[2262]: <info>  [1701264828.9269] settings: (enp0s31f6): created default wired connection 'Kabelgebundene Verbindung 1'
Nov 29 14:33:48 NetworkManager[2262]: <info>  [1701264828.9270] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Nov 29 14:33:53 NetworkManager[2262]: <info>  [1701264833.4364] device (enp0s31f6): carrier: link connected
Nov 29 14:33:53 NetworkManager[2262]: <info>  [1701264833.4366] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Nov 29 14:33:53 NetworkManager[2262]: <info>  [1701264833.4378] device (enp0s31f6): Activation: starting connection 'Kabelgebundene Verbindung 1' (08e669cc-ff02-34ce-a865-0c462c92a717)
Nov 29 14:33:53 NetworkManager[2262]: <info>  [1701264833.4378] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 29 14:33:53 NetworkManager[2262]: <info>  [1701264833.4382] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 29 14:33:54 NetworkManager[2262]: <info>  [1701264834.1090] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 29 14:33:54 NetworkManager[2262]: <info>  [1701264834.1113] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds)
Nov 29 14:33:57 NetworkManager[2262]: <info>  [1701264837.4388] dhcp4 (enp0s31f6): state changed new lease, address=192.168.2.41
Nov 29 14:33:57 NetworkManager[2262]: <info>  [1701264837.4394] policy: set 'Kabelgebundene Verbindung 1' (enp0s31f6) as default for IPv4 routing and DNS
Nov 29 14:33:57 NetworkManager[2262]: <info>  [1701264837.4538] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Nov 29 14:33:57 NetworkManager[2262]: <info>  [1701264837.4580] device (enp0s31f6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Nov 29 14:33:57 NetworkManager[2262]: <info>  [1701264837.4584] device (enp0s31f6): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Nov 29 14:33:57 NetworkManager[2262]: <info>  [1701264837.4621] device (enp0s31f6): Activation: successful, device activated.

Im seeing there a difference from what NetworkManager is doing but cannot get out why and what i can do to solve it

4

Can it be, that you use a docking station and use your network USB Network there? Or an external USB Hub?

I already saw problems, where the USB ID changed and so the device connected and disconnected. This seams to happen while checking your Log you posted, it connects and then it says that it disconnects. I can see it while you boot with 6.5.11 and 6.5.12/6.6 Just on 6.5.11 it maintains the connection after some reconnects.

Can it be that you installed the driver for r8152 separately and it is not ready for the newer kernels ?!

5

Hi @ilikelinux
no, i did not installed a separate driver. Its all standard driver like its installed from workstation-image. There is no dockingstation in use. Its the normal onboard lan-adapter which a cable is in there. This is connected to my main switch in cellar.

There is an usb-hub in the monitor (monitor is plugged in via usbc-connector). also the lan adapter of monitor is not in use.
I now booted the newest kernel also with plugged out usb to see if there would be a difference. There is no difference.
Also the monitor is there in use since about 2 years.

6

Hi,

I’m having the same exact issue on my Fedora 39 workstation. Asus Crosshair VIII hero (5950x) using a onboard Realtek RTL8125 2.5GbE Controller.

Just updated to the latest 6.6 kernel and the issue persists.

There are no direct errors listed on boot, network appears to come up according to Network Manager, but it’s not there and totally hoses my system… Can’t sudo, everything just goes haywire.

7

Hello. Just wanted to add me to this. Updated to 6.5.12 which introduced the issue. Was not fixed in 6.6.2. However, 6.5.11 works fine.

I have an Asus Crosshair VIII Hero Wifi motherboard with Ryzen 9 3900x. When the 2.5GbE realtek RTL8125 NIC is enabled and connected to the router then nothing works at all. The system is unresponsive and anything to do with root permission freezes the system. The system becomes a bit more responsive when you unplug the ethernet cable, however, it is still having trouble.

When I disable the network adaptor and enable the Intel 1GbE NIC in UEFI and use that instead then my computer works just fine. It’s a workaround that will work for now.

This is unfortunately not the first time a new linux kernel release causes trouble with the Realtek NIC.

8

Good to know that it’s not just me at least.

I can confirm that the 6.6.3-200 kernel in Testing does not solve the issue.

9

It is the opposite Realtek Nic causes trouble with new Kernels. While by release the drivers are not ready they can not be included in the newer Kernel … The complain goes in first case to Realtek and not really to the Kernel.

I do have two network adapter in my system, the Realtek makes trouble too. So i just use the Intel one :wink:

10

I wish I didn’t have to use it, but it’s the only one that’s 2.5GB and I’m out of room for an intel card :frowning:

11

If it causes problems when used as 2.5GB interface then use the 1GB interface as a work-around until the problem is fixed.

I am sorry that the newer nics are not yet 100% supported, but that should be only a short term setback.

12

Hi,

thats not really an option. My RTL8153 is only Gigabit and it is not usable. That was the reason i opened the thread.
The thing is that networking is blocking totally usage of system. So it is not possible to use wifi and its also not possible to use sudo. Graphical logins by gdm completely impossible. Switching to textconsole and login with local user was the only possible thing. After login prompt hangs until ctrl-c and then you can enter some commands, but never enter one which asks network hardware. The simple “ip addr” made system hanging and so on. Because sudo not working you can only login as root if it has a password on which normally is not because of security.
It is not only that the adapter is not usable.
So the system is not fully usabe as a car which you cannot open the doors and which lost the possibility to be used on the streets to drive to the internet.
So my only workaround is to use with 6.5.11 because all newer kernels makes my computer useless.

13

Yeah, I agree. I can use an older kernel, but the fact that it completely screws the system otherwise makes it pretty bad. If I didjr have the old kernel still available, I would be unable to even boot to a usable system to even switch network cards cause it be nearly impossible with no sudo.

14

Just wanted to add that I understand the situation with the kernel and hardware and it’ll get fixed when it happens, it’s just a pretty severe outcome as opposed to the network just going down by itself.

15

Sorry for my incorrect phrasing. Of course, I meant that Realtek is the problem here and not the Linux kernel, since I can make it work with the intel adapter.

I do wonder if there is a way that 6.6.2 can be patched with the Realtek drivers when they are released. Will they be updated with the realtek-firmware package in the fedora repositories, or are they a part of the kernel? Asking out of curiosity since I don’t know how they are distributed.

16

In your motherboards UEFI you can disable the Realtek adaptor, and use the intel adaptor until the problem is fixed. Then you don’t have to deal with disabling it in Fedora and you would be able to use the new kernel without having to lock yourself to 6.5.11.

You say you’re out of room for an intel adaptor. But since we have the same motherboard you should have one onboard.

17

I think so yes.
You can also run an LTS kernel by side the official one.

https://copr.fedorainfracloud.org/coprs/kwizart/kernel-longterm-6.1/

so you have always a fallback.

18

from your discussion i searched the dmesg for “enp”

[Fr Dez  1 07:26:22 2023] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[Fr Dez  1 07:26:24 2023] r8152 4-1.2:1.0 enp63s0u1u2: renamed from eth0
[Fr Dez  1 08:44:48 2023] r8152 4-1.2:1.0 enp63s0u1u2: Stop submitting intr, status -71
[Fr Dez  1 08:44:51 2023] r8152 4-1.2:1.0 enp63s0u1u2: renamed from eth0
[Fr Dez  1 08:59:46 2023] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
[Fr Dez  1 08:59:52 2023] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[Fr Dez  1 09:00:00 2023] r8152 4-1.2:1.0 enp63s0u1u2: renamed from eth0
[Fr Dez  1 09:37:36 2023] r8152 4-1.2:1.0 enp63s0u1u2: Stop submitting intr, status -108
[Fr Dez  1 09:37:39 2023] r8152 4-1.2:1.0 enp63s0u1u2: renamed from eth0
[Fr Dez  1 09:44:47 2023] r8152 4-1.2:1.0 enp63s0u1u2: Stop submitting intr, status -108
[Fr Dez  1 09:44:51 2023] r8152 4-1.2:1.0 enp63s0u1u2: renamed from eth0
[Fr Dez  1 09:52:34 2023] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
[Fr Dez  1 09:52:35 2023] r8152 4-1.2:1.0 enp63s0u1u2: carrier on
[Fr Dez  1 09:52:36 2023] r8152 4-1.2:1.0 enp63s0u1u2: carrier on
[Fr Dez  1 09:52:41 2023] r8152 4-1.2:1.0 enp63s0u1u2: renamed from eth0
[Fr Dez  1 09:52:44 2023] r8152 4-1.2:1.0 enp63s0u1u2: carrier on

1.) we are speaking in my laptop from e1000e which is not usable in my laptop. The r8152 was unused in the monitor
2.) in second part of log i taken out the cable and plugged into monitor. r8152 then comes up and my system is usable also with newest 6.6 kernel.

i will test next minutes what if im not using the monitor plugged in if the availability of unused r8152 makes the problems

19

Laptop solo without monitor and r8152 has problem too with kernel newer 6.5.11. So the problem is not really in relation with r8152.

Dec 01 10:07:28  NetworkManager[1977]: <info>  [1701421648.4397] device (enp0s31f6): carrier: link connected
Dec 01 10:07:28  NetworkManager[1977]: <info>  [1701421648.4425] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Dec 01 10:07:28  NetworkManager[1977]: <info>  [1701421648.4445] device (enp0s31f6): Activation: starting connection 'Kabelgebundene Verbindung 1' (08e669cc-ff02-34ce-a865-0c462c92a717)
Dec 01 10:07:28  NetworkManager[1977]: <info>  [1701421648.4447] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 01 10:07:28 NetworkManager[1977]: <info>  [1701421648.4454] manager: NetworkManager state is now CONNECTING
Dec 01 10:07:28  NetworkManager[1977]: <info>  [1701421648.4462] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')

conclusion from what we knowing this time:

  • problem can be there in relation of different network cards?!
  • seems to be a problem from networking-tools in relation to newer than 6.5.11-kernels?!
  • system integrity, usage and rights-expansion is affected?!
  • offline usage seems also no more possible usecase of computer?!
20

Booting with the older kernel should allow you to do what is needed to perform repairs. If networking is functional there then the updated drivers should be accessible and may be installed. Doing so would likely make it possible to also have networking functional with the newer kernels.

There are 2 parts to the networking issue – drivers and firmware.
What is the output of dnf list installed \*firmware

1 Like