WiFi has stopped working

K4LCIFER · 2022-09-17 01:41:01

I'm not sure what happened, but all of a sudden the WiFi connection on my desktop no longer works; I cannot connect to WiFi through gnome; It just keeps trying and trying and failing. WiFi has worked flawlessly on my desktop in the past.

For the past 3 months or so I've been using an ethernet connection on my desktop, and prior to switching to ethernet the WiFi was working fine. Recently I switched back over to WiFi, and all of a sudden it is not working. I can't chock it up to a bad system/firmware update, as I have updated countless times between now and the last time that the WiFi was known to be working. I know its not an issue with the network itself since all other devices (another linux laptop as well) have no issue. I do notice that, for some reason, its hanging at boot for longer than it has in the past (not sure if that's related at all), I also have been getting huge dumps of ACPI errors in the logs as well.

journalctl -b
GNOME Logs
- OS: Arch Linux
- Kernel: 5.19.8-arch1-1
- DE: Gnome-Wayland
- WiFi card: TP-Link TX50E (AX3000)
All firmware is up to date with fwupdmgr, and all packages are up to date with pacman.

Last edited by K4LCIFER (2022-09-17 01:42:27)

jeffm · 2022-09-17 04:38:53

Could be a kernel module problem , but more information would be helpful.

The journal indicates nothing found (at cfg80211 entries).

For starters, an you post outputs of (just to be sure the device is not known to the system) :

ip addr

lspci

Reading this thread, it does not look promising - https://community.tp-link.com/us/home/f … pic/221500.

According to TPL contributors in this thread, there is no linux support!

But it was working in the past !?

seth · 2022-09-17 05:24:23

Sep 16 16:30:44 <hostname> wpa_supplicant[680]: wlp6s0: CTRL-EVENT-AUTH-REJECT c0:06:c3:3b:7e:e2 auth_type=3 auth_transaction=2 status_code=1
Sep 16 18:18:38 <hostname> ntfs-3g[2162]: Mounted /dev/sda1 (Read-Write, label "", NTFS 3.1)
Sep 16 18:18:44 <hostname> wpa_supplicant[680]: wlp6s0: CTRL-EVENT-AUTH-REJECT c0:06:c3:3b:7e:e2 auth_type=3 auth_transaction=2 status_code=1

The ntfs partition tells me that there's likely a parallel windows?
3rd link below. No, it's not the BIOS setting and windows keeps re-enabling it.

Make sure to reboot windows, linux and probably also the router (to clear stale leases) afterwards.

K4LCIFER · 2022-09-17 06:58:51

% lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0)
00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0)
00:1c.7 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 8 (rev d0)
00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
00:1f.0 ISA bridge: Intel Corporation Z97 Chipset LPC Controller
00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller
01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c7)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] (rev c7)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller
05:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13)
06:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a)

jeffm wrote:

But it was working in the past !?

Yep it was working fine with zero issues; it was plug and play.

seth wrote:

The ntfs partition tells me that there's likely a parallel windows?

There is a windows install on a separate drive, but I haven't touched that in probably a year, if not longer.

seth · 2022-09-17 07:17:30

It doesn't matter which drive it is on and you've also not used the wifi in a long time.
Santize the condition (including a reboot of the devices) to rule out thius very obvious and frequent source of trouble.

ewaller · 2022-09-17 14:24:05

And, as a sanity check. please post the output of:
uname -a
pacman -Q linux
lspci
and
find /etc/systemd

K4LCIFER · 2022-09-18 06:20:12

seth wrote:

It doesn't matter which drive it is on and you've also not used the wifi in a long time.
Santize the condition (including a reboot of the devices) to rule out thius very obvious and frequent source of trouble.

Ok, rebooted the desktop, but the issue persists.

ewaller wrote:

And, as a sanity check. please post the output of:
uname -a
pacman -Q linux
lspci
and
find /etc/systemd

% uname -a
Linux opal 5.19.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 15 Sep 2022 16:08:26 +0000 x86_64 GNU/Linux

% pacman -Q linux
linux 5.19.9.arch1-1

% lspci 
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0)
00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0)
00:1c.7 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 8 (rev d0)
00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
00:1f.0 ISA bridge: Intel Corporation Z97 Chipset LPC Controller
00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller
01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c7)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] (rev c7)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller
05:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13)
06:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a)

% find /etc/systemd
/etc/systemd
/etc/systemd/system.conf
/etc/systemd/homed.conf
/etc/systemd/coredump.conf
/etc/systemd/system
/etc/systemd/system/sysinit.target.wants
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/bluetooth.target.wants
/etc/systemd/system/bluetooth.target.wants/bluetooth.service
/etc/systemd/system/dbus-org.freedesktop.timesync1.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/lm_sensors.service
/etc/systemd/system/multi-user.target.wants/tlp.service
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/multi-user.target.wants/syncthing@isaac.service
/etc/systemd/system/multi-user.target.wants/cups.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/mullvad-daemon.service
/etc/systemd/system/multi-user.target.wants/cups.path
/etc/systemd/system/dbus-org.bluez.service
/etc/systemd/system/network-online.target.wants
/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service
/etc/systemd/system/sockets.target.wants
/etc/systemd/system/sockets.target.wants/cups.socket
/etc/systemd/system/printers.target.wants
/etc/systemd/system/printers.target.wants/cups.service
/etc/systemd/system/mullvad-daemon.service
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/system/display-manager.service
/etc/systemd/network
/etc/systemd/journald.conf
/etc/systemd/logind.conf
/etc/systemd/resolved.conf
/etc/systemd/oomd.conf
/etc/systemd/journal-upload.conf
/etc/systemd/sleep.conf
/etc/systemd/networkd.conf
/etc/systemd/pstore.conf
/etc/systemd/timesyncd.conf
/etc/systemd/user.conf
/etc/systemd/journal-remote.conf
/etc/systemd/user
/etc/systemd/user/pipewire.service.wants
/etc/systemd/user/pipewire.service.wants/wireplumber.service
/etc/systemd/user/default.target.wants
/etc/systemd/user/default.target.wants/xdg-user-dirs-update.service
/etc/systemd/user/pipewire-session-manager.service
/etc/systemd/user/sockets.target.wants
/etc/systemd/user/sockets.target.wants/gcr-ssh-agent.socket
/etc/systemd/user/sockets.target.wants/pipewire-pulse.socket
/etc/systemd/user/sockets.target.wants/gnome-keyring-daemon.socket
/etc/systemd/user/sockets.target.wants/pipewire.socket
/etc/systemd/user/sockets.target.wants/p11-kit-server.socket

seth · 2022-09-18 06:34:47

Ok, rebooted the desktop, but the issue persists.

Rebooting the desktop isn't the point - you've to get windows out of hibernation mode and also reboot the AP (router) to clear stale leases - if this is the problem.

Next to that, the AP might dislike https://wiki.archlinux.org/title/Networ … domization so you could try to disable that.
Whatever the cause, the problem is that the AP explicitly keeps telling you to fuck off, so there is some collision (or a really!! weird bug that consistently creates the same reply out of random input)

K4LCIFER · 2022-09-18 06:48:49

seth wrote:

Whatever the cause, the problem is that the AP explicitly keeps telling you to fuck off

Out of curiosity, and for my own future reference when looking at the logs, what part of the logs told you that this was the case?

Last edited by K4LCIFER (2022-09-18 06:51:21)

seth · 2022-09-18 07:08:06

"CTRL-EVENT-AUTH-REJECT" - the protocol is of course more polite than I

K4LCIFER · 2022-09-18 07:57:48

seth wrote:

Ok, rebooted the desktop, but the issue persists.
Rebooting the desktop isn't the point - you've to get windows out of hibernation mode and also reboot the AP (router) to clear stale leases - if this is the problem.

Alright so I got booted into windows, and weirdly enough, at first, windows couldn't even see the wireless card; however, after windows ran its plethora of updates (and of course forcing me to wait at its god-awful "getting windows ready. don't shut down the computer" screen for 20 minutes, and of course overwriting grub), the wifi card was then able to be seen in windows, but unfortunately, when booted back into Linux, it was still unable to connect to wifi.

Also, the router was rebooted.

Last edited by K4LCIFER (2022-09-18 08:08:05)

seth · 2022-09-18 12:55:01

at first, windows couldn't even see the wireless card

Very likely an outucome of and indicator for the hibernating windows and linux trying to operate the same HW at the same time.

wait at its god-awful "getting windows ready. don't shut down the computer

https://i.imgur.com/xrTppkE.png

when booted back into Linux, it was still unable to connect to wifi.

You didn't mention whether you disabled windows fast-start…

Otherwise, again: see and disable https://wiki.archlinux.org/title/Networ … domization

ewaller · 2022-09-18 16:19:39

ewaller wrote:

And, as a sanity check. please post the output of:
uname -a
pacman -Q linux
lspci
and
find /etc/systemd

That all looks sane. Thanks.

K4LCIFER · 2022-09-21 00:59:11

I managed to get the WiFi connected (although I'm honestly not sure how), but it is suffering from some major issues. It cannot hold a steady connection (ie it drops constantly) with little to no useable speed, and it has very abnormally large pings. It's also spitting out a lot of stuff in the logs.

seth wrote:

You didn't mention whether you disabled windows fast-start…

Ah yeah, sorry I did disable that as well.

Side note: I also tried connecting on a live usb, but it had some of the same issues, although, weirdly enough, after spitting out

iwlwifi 0000:06:00.0: Not associated and the session protection is over already...

a couple times during connection on the live usb using iwctl, it did seem to properly connect to the wifi; however, windows still was able to connect to the wifi with no problem at all.

Aside: Is this possibly a known bug?

Last edited by K4LCIFER (2022-09-21 02:41:00)

seth · 2022-09-21 06:20:37

The firmware crashes and in restarting it you miss the association window.
The journal context might be interesting and try to pass

iwlwifi.swcrypto=1 iwlwifi.11n_disable=8 iwlwifi.power_save=0

to the kernel.
If that doesn't help try "iwlwifi.11n_disable=1" instead of "8"

K4LCIFER · 2022-09-21 06:23:49

seth wrote:

try to pass

iwlwifi.swcrypto=1 iwlwifi.11n_disable=8 iwlwifi.power_save=0

to the kernel.

Where/how do I pass those parameters?

seth · 2022-09-21 06:31:04

https://wiki.archlinux.org/title/Kernel_parameters

K4LCIFER · 2022-10-14 02:24:31

I believe that I have found a temporary workaround that solves this issue. It may be that the firmware from intel for my wireless card is borked. See this bug report. By following the workaround as posted in the comments, my wifi appears to be functioning correctly now.

Workaround as suggested:
Remove the following files

/lib/firmware/iwlwifi-ty-a0-gf-a0-[>63]

It seems that any of the firmware versions greater than 63 cause the aformentioned issues.

K4LCIFER · 2022-10-14 02:45:19

Nevermind, it appears to have stopped working again; however, the issue does seem related.

K4LCIFER · 2022-10-14 03:12:06

It appears that there is an update to iwlwifi firmware (iwlwifi-so-a0-gf-a0-74.ucode). When that is released to Arch Linux, we'll see if it fixes the issue.

loqs · 2022-10-14 03:28:54

iwlwifi in linux 6.0 only supports up to ucode API 72, updates to 73 or the addition of 74 will be ignored. You can see that in your journal the first ucode the kernel tries to load is:

iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-72.ucode failed with error -2

K4LCIFER · 2022-10-14 03:31:55

loqs wrote:

iwlwifi in linux 6.0 only supports up to ucode API 72, updates to 73 or the addition of 74 will be ignored. You can see that in your journal the first ucode the kernel tries to load is:
iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-72.ucode failed with error -2

Yeah I just found that in dmesg. Is it possible to override it so that it loads 74? I got 74 with linux-firmware-git from the AUR, so possibly linux-git will support it?

Last edited by K4LCIFER (2022-10-14 03:35:15)

loqs · 2022-10-14 03:36:12

K4LCIFER wrote:

Yeah I just found that in dmesg. Is it possible to override it so that it loads 74?

No you would need to edit the source. Even if you did load 74 the iwlwifi module has not had support for that API version added yet which is why the version limit has not been increased from 72 so you would be introducing new issues.

K4LCIFER · 2022-10-14 03:46:50

loqs wrote:

K4LCIFER wrote:
Yeah I just found that in dmesg. Is it possible to override it so that it loads 74?
No you would need to edit the source. Even if you did load 74 the iwlwifi module has not had support for that API version added yet which is why the version limit has not been increased from 72 so you would be introducing new issues.

Ah okay. Do you, by chance, know when 74 will be supported?

loqs · 2022-10-14 03:58:24

K4LCIFER wrote:

Ah okay. Do you, by chance, know when 74 will be supported?

Not until at least 6.2, https://git.kernel.org/pub/scm/linux/ke … 2000.c#n13
Older iwlwifi ucodes can be updated if there is an issue with them. The change in API indicates the supported feature set has changed.

Arch Linux

#1 2022-09-17 01:41:01

WiFi has stopped working

#2 2022-09-17 04:38:53

Re: WiFi has stopped working

#3 2022-09-17 05:24:23

Re: WiFi has stopped working

#4 2022-09-17 06:58:51

Re: WiFi has stopped working

#5 2022-09-17 07:17:30

Re: WiFi has stopped working

#6 2022-09-17 14:24:05

Re: WiFi has stopped working

#7 2022-09-18 06:20:12

Re: WiFi has stopped working

#8 2022-09-18 06:34:47

Re: WiFi has stopped working

#9 2022-09-18 06:48:49

Re: WiFi has stopped working

#10 2022-09-18 07:08:06

Re: WiFi has stopped working

#11 2022-09-18 07:57:48

Re: WiFi has stopped working

#12 2022-09-18 12:55:01

Re: WiFi has stopped working

#13 2022-09-18 16:19:39

Re: WiFi has stopped working

#14 2022-09-21 00:59:11

Re: WiFi has stopped working

#15 2022-09-21 06:20:37

Re: WiFi has stopped working

#16 2022-09-21 06:23:49

Re: WiFi has stopped working

#17 2022-09-21 06:31:04

Re: WiFi has stopped working

#18 2022-10-14 02:24:31

Re: WiFi has stopped working

#19 2022-10-14 02:45:19

Re: WiFi has stopped working

#20 2022-10-14 03:12:06

Re: WiFi has stopped working

#21 2022-10-14 03:28:54

Re: WiFi has stopped working

#22 2022-10-14 03:31:55

Re: WiFi has stopped working

#23 2022-10-14 03:36:12

Re: WiFi has stopped working

#24 2022-10-14 03:46:50

Re: WiFi has stopped working

#25 2022-10-14 03:58:24

Re: WiFi has stopped working

Board footer