Wifi driver broken after update to kernel 6.16

English Network/Internet
1

A couple nights ago, I did a system update and my wifi wasn’t working after rebooting. I spent many hours trying to troubleshoot and I have an idea of what may be causing it, but I’m struggling to find a solution.

I’m starting this thread as a continuation from this thread.

Based on the previous thread and some other research, it seems that Linux 6.16.1 introduced a regression where Intel wifi broke. I used snapper to rollback to before my system update, and that didn’t fix the problem. I rolled forward again because I figured there was no point being in the previous snapshot. I have booted into 6.15.8 from Grub, and that also didn’t fix the problem. I am still using 6.15.8 because I figure any solution will likely require me to be on that kernel unless there’s an update that fixes this issue. I wasn’t having this issue before the system update. I tried reinstalling kernel-firmware-iwlwifi and that didn’t do anything.

I am still able to use ethernet, and I am currently writing this by using a tether on my Android phone. I’m going back to college in like 16 hours, and this is quite inconvenient.

Here are some commands I’ve used to get information:

  eclipse@tumbleweed ~
$ sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
     Active: active (running) since Sat 2025-08-23 13:16:58 EDT; 2h 1min ago
 Invocation: 75f2ae7e703c470b81fa1ccf5a1d8ef6
       Docs: man:NetworkManager(8)
   Main PID: 2393 (NetworkManager)
      Tasks: 4 (limit: 18789)
        CPU: 981ms
     CGroup: /system.slice/NetworkManager.service
             └─2393 /usr/sbin/NetworkManager --no-daemon

Aug 23 14:57:18 tumbleweed NetworkManager[2393]: <info>  [1755975438.0499] dhcp4 (enp0s20f0u11): activation: beginning transaction (timeout in 45 seconds)
Aug 23 14:57:18 tumbleweed NetworkManager[2393]: <info>  [1755975438.0569] dhcp4 (enp0s20f0u11): state changed new lease, address=10.142.204.231, acd pending
Aug 23 14:57:18 tumbleweed NetworkManager[2393]: <info>  [1755975438.2297] dhcp4 (enp0s20f0u11): state changed new lease, address=10.142.204.231
Aug 23 14:57:18 tumbleweed NetworkManager[2393]: <info>  [1755975438.2324] policy: set 'Wired connection 1' (enp0s20f0u11) as default for IPv4 routing and DNS
Aug 23 14:57:18 tumbleweed NetworkManager[2393]: <info>  [1755975438.2506] device (enp0s20f0u11): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Aug 23 14:57:18 tumbleweed NetworkManager[2393]: <info>  [1755975438.2997] device (enp0s20f0u11): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Aug 23 14:57:18 tumbleweed NetworkManager[2393]: <info>  [1755975438.2998] device (enp0s20f0u11): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Aug 23 14:57:18 tumbleweed NetworkManager[2393]: <info>  [1755975438.3002] manager: NetworkManager state is now CONNECTED_SITE
Aug 23 14:57:18 tumbleweed NetworkManager[2393]: <info>  [1755975438.3006] device (enp0s20f0u11): Activation: successful, device activated.
Aug 23 14:57:18 tumbleweed NetworkManager[2393]: <info>  [1755975438.6775] manager: NetworkManager state is now CONNECTED_GLOBAL

  eclipse@tumbleweed ~
$ nmcli device status
DEVICE        TYPE      STATE                   CONNECTION
enp0s20f0u11  ethernet  connected               Wired connection 1
lo            loopback  connected (externally)  lo

  eclipse@tumbleweed ~
$ nmcli device wifi list

  eclipse@tumbleweed ~
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
9: enp0s20f0u11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether fa:44:0e:da:e0:e1 brd ff:ff:ff:ff:ff:ff
    altname enxfa440edae0e1

  eclipse@tumbleweed ~
$ uname -r
6.15.8-1-default

  eclipse@tumbleweed ~
$ rpm -q kernel-firmware-iwlwifi
kernel-firmware-iwlwifi-20250609-2.1.noarch

  eclipse@tumbleweed ~
$ lsmod | grep iwl
iwlmvm                638976  0
mac80211             1531904  1 iwlmvm
iwlwifi               507904  1 iwlmvm
cfg80211             1396736  3 iwlmvm,iwlwifi,mac80211
rfkill                 45056  7 iwlmvm,bluetooth,cfg80211

  eclipse@tumbleweed ~
$ dmesg | grep wifi
[    5.466492] [    T757] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[    5.809859] [    T757] iwlwifi 0000:02:00.0: CSR_RESET = 0x10
[    5.809870] [    T757] iwlwifi 0000:02:00.0: Host monitor block 0x0 vector 0x0
[    5.810000] [    T757] iwlwifi 0000:02:00.0:     value [iter 0]: 0x3f7f8c30
[    5.810121] [    T757] iwlwifi 0000:02:00.0:     value [iter 1]: 0x3f7f8430
[    5.810246] [    T757] iwlwifi 0000:02:00.0:     value [iter 2]: 0x3f7f8430
[    5.810362] [    T757] iwlwifi 0000:02:00.0:     value [iter 3]: 0x3f7f8c30
[    5.810490] [    T757] iwlwifi 0000:02:00.0:     value [iter 4]: 0x3f7f0830
[    5.810618] [    T757] iwlwifi 0000:02:00.0:     value [iter 5]: 0x3f7f0830
[    5.810746] [    T757] iwlwifi 0000:02:00.0:     value [iter 6]: 0x3f7f0830
[    5.810801] [    T757] iwlwifi 0000:02:00.0:     value [iter 7]: 0x3f7f8030
[    5.810855] [    T757] iwlwifi 0000:02:00.0:     value [iter 8]: 0x3f7f0030
[    5.810910] [    T757] iwlwifi 0000:02:00.0:     value [iter 9]: 0x3f7f8c30
[    5.810964] [    T757] iwlwifi 0000:02:00.0:     value [iter 10]: 0x3f7f0430
[    5.811085] [    T757] iwlwifi 0000:02:00.0:     value [iter 11]: 0x3f7f8430
[    5.811212] [    T757] iwlwifi 0000:02:00.0:     value [iter 12]: 0x3f7f0430
[    5.811328] [    T757] iwlwifi 0000:02:00.0:     value [iter 13]: 0x3f7f0830
[    5.811382] [    T757] iwlwifi 0000:02:00.0:     value [iter 14]: 0x3f7f0030
[    5.811385] [    T757] iwlwifi 0000:02:00.0: Host monitor block 0x0 vector 0x1
[    5.811511] [    T757] iwlwifi 0000:02:00.0:     value [iter 0]: 0x044466c2
[    5.811639] [    T757] iwlwifi 0000:02:00.0:     value [iter 1]: 0x044466c2
[    5.811759] [    T757] iwlwifi 0000:02:00.0:     value [iter 2]: 0x044466c2
[    5.811888] [    T757] iwlwifi 0000:02:00.0:     value [iter 3]: 0x044466c2
[    5.812009] [    T757] iwlwifi 0000:02:00.0:     value [iter 4]: 0x044466c2
[    5.812130] [    T757] iwlwifi 0000:02:00.0:     value [iter 5]: 0x044466c2
[    5.812262] [    T757] iwlwifi 0000:02:00.0:     value [iter 6]: 0x044466c2
[    5.812380] [    T757] iwlwifi 0000:02:00.0:     value [iter 7]: 0x044466c2
[    5.812508] [    T757] iwlwifi 0000:02:00.0:     value [iter 8]: 0x044466c2
[    5.812630] [    T757] iwlwifi 0000:02:00.0:     value [iter 9]: 0x044466c2
[    5.812750] [    T757] iwlwifi 0000:02:00.0:     value [iter 10]: 0x044466c2
[    5.812871] [    T757] iwlwifi 0000:02:00.0:     value [iter 11]: 0x044466c2
[    5.813000] [    T757] iwlwifi 0000:02:00.0:     value [iter 12]: 0x044466c2
[    5.813128] [    T757] iwlwifi 0000:02:00.0:     value [iter 13]: 0x044466c2
[    5.813186] [    T757] iwlwifi 0000:02:00.0:     value [iter 14]: 0x044466c2
[    5.813191] [    T757] iwlwifi 0000:02:00.0: Host monitor block 0x0 vector 0x6
[    5.813325] [    T757] iwlwifi 0000:02:00.0:     value [iter 0]: 0xf00c4471
[    5.813454] [    T757] iwlwifi 0000:02:00.0:     value [iter 1]: 0xe00c4471
[    5.813575] [    T757] iwlwifi 0000:02:00.0:     value [iter 2]: 0xe00c4471
[    5.813696] [    T757] iwlwifi 0000:02:00.0:     value [iter 3]: 0xe00c4471
[    5.813824] [    T757] iwlwifi 0000:02:00.0:     value [iter 4]: 0xa00c4471
[    5.813945] [    T757] iwlwifi 0000:02:00.0:     value [iter 5]: 0xe00c4471
[    5.814073] [    T757] iwlwifi 0000:02:00.0:     value [iter 6]: 0xe00c4471
[    5.814197] [    T757] iwlwifi 0000:02:00.0:     value [iter 7]: 0xa00c4471
[    5.814326] [    T757] iwlwifi 0000:02:00.0:     value [iter 8]: 0xf00c4471
[    5.814447] [    T757] iwlwifi 0000:02:00.0:     value [iter 9]: 0xf00c4471
[    5.814568] [    T757] iwlwifi 0000:02:00.0:     value [iter 10]: 0xf00c4471
[    5.814688] [    T757] iwlwifi 0000:02:00.0:     value [iter 11]: 0xf00c4471
[    5.814817] [    T757] iwlwifi 0000:02:00.0:     value [iter 12]: 0xb00c4471
[    5.814938] [    T757] iwlwifi 0000:02:00.0:     value [iter 13]: 0xb00c4471
[    5.815067] [    T757] iwlwifi 0000:02:00.0:     value [iter 14]: 0xb00c4471
[    5.815070] [    T757] iwlwifi 0000:02:00.0: Host monitor block 0x22 vector 0x0
[    5.815191] [    T757] iwlwifi 0000:02:00.0:     value [iter 0]: 0x00000000
[    5.815510] [    T757] iwlwifi 0000:02:00.0: probe with driver iwlwifi failed with error -110

  eclipse@tumbleweed ~
$ lspci -nnk | grep -A3 -i network
02:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
        Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
        Kernel modules: iwlwifi
03:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808]

  eclipse@tumbleweed ~
$ inxi -Na
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: N/A modules: iwlwifi pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:2723 class-ID: 0280

My guess is that the problem has something to do with this:

probe with driver iwlwifi failed with error -110

And the driver is not listed in the lspci or inxi command outputs.

Are a bunch of other people having the same issue as me? Are there any known solutions? Should I be using a different version of kernel-firmware-iwlwifi? Do I just have to wait for a kernel/firmware update?

I would appreciate any information or help anyone can provide.

Thank you!

2

Hey @eclipse! I recently had this issue today, and i found it was because windows was blocking access to my wireless card. I had the same exact error -110. The error i believe is a timeout error.

If you are dual booting windows. You will need to boot into windows and disable fast startup or fast boot. That is the feature that blocks your access to the wireless card. If you are not but previously had windows, and your device is still unable to use the wireless card, you may want to completely remove power from the device (unplug your battery if possible on a laptop) and then press the power button for 30 seconds to drain any electricity remaining in the computer. Then plug it back in and boot back into OpenSuse.

I just recently went through these same shenanigans and disabling fastboot ended up fixing it for me.

Also, as a general tip. If you have wifi at home, and a phone you can usb tether your device to the computer. That way you can use your computer to research how to fix this issue.

Thanks, and i hope your issue gets resolved :slight_smile: .

2 Likes
3

OMG it worked! I removed the power cable and held the power button down for 30 seconds, and I had access on reboot! I used to have Windows on this machine, but I don’t dual boot. I can’t believe that was the solution.

Thank you so much!

2 Likes
4

glad to help :slight_smile:

1 Like
5

I had the same problem - and removing the battery and pressing the On button helped! Thank you soooo much - I really needed my laptop for work being away from home! :slight_smile:

6

Shame, it worked only for so long. Froze again. :frowning:

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.