[SOLVED] WiFi stopped working

menteith · 2023-12-26 16:21:10

Hi,

I have a WiFi card based on a a mt7921u chip. It is supported by kernel and doesn't need external drivers. The card (connected via USB) has stopped working recently along with ethernet. I reinstalled Arch and the ethernet started working again but WiFi won't. This is rather problem with Arch as the card is working fine under Debian (I used install medium to test it). Here's a portion of dmesg logs when I connect dongle to my computer:

[  910.496600] usbcore: registered new interface driver mt7921u
[ 1073.354134] usb 2-3: new SuperSpeed USB device number 7 using xhci_hcd
[ 1073.372815] usb 2-3: New USB device found, idVendor=0e8d, idProduct=7961, bcdDevice= 1.00
[ 1073.372831] usb 2-3: New USB device strings: Mfr=6, Product=7, SerialNumber=8
[ 1073.372838] usb 2-3: Product: Wireless_Device
[ 1073.372844] usb 2-3: Manufacturer: MediaTek Inc.
[ 1073.372848] usb 2-3: SerialNumber: 000000000
[ 1073.383397] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20231109191416
[ 1076.360387] Bluetooth: hci0: Device setup in 2912055 usecs
[ 1076.360404] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[ 1078.573991] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[ 1080.710410] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[ 1082.840474] Bluetooth: hci0: AOSP get vendor capabilities (-110)
[ 1088.174060] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[ 1093.507329] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[ 1093.713966] usb 2-3: device not accepting address 7, error -62

Please help

Many thanks in advance!

Last edited by menteith (2023-12-29 10:26:06)

Head_on_a_Stick · 2023-12-26 17:16:33

Smells like a kernel regression. Either downgrade your kernel version or try the linux-lts package to confirm.

Just to be sure: what does "not working" mean, exactly? Can you see the interface in the output of `ip link`?

menteith · 2023-12-26 17:37:55

By "not working" I meant not showing any interface by `ip link`. Also using KDE I see no wireless network. I switched to linux-lts, however without luck - I still cannot see my interface.

Head_on_a_Stick · 2023-12-26 19:40:20

If you also have a Windows system installed make sure fast startup is disabled. That's all I can think of for now.

menteith · 2023-12-26 19:46:14

I don't have Windows installed.

seth · 2023-12-26 19:50:46

This is rather problem with Arch as the card is working fine under Debian (I used install medium to test it). Here's a portion of dmesg logs when I connect dongle to my computer

Does the dongle work w/ the arch install medium?
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

menteith · 2023-12-26 20:25:53

The dongle has worked with Arch install medium. I was able to connect to a wireless network and ping google DNS server.

Here's log: https://0x0.st/HEsn.txt. It weird because this time (after reboot) `ip link` shows my interface and I could even connect. Let me reboot and check this again.

**EDIT**

After reboot I was still able to see my interface and connect to the Internet. After I removed the interface from my computer and then re-attached `ip link` shows no wifi card.

**EDIT 2**
After another restart Arch doesn't find my interface. Here's log: http://0x0.st/HEzs.txt

Last edited by menteith (2023-12-26 20:38:20)

seth · 2023-12-26 20:45:23

From the "good" journal

Dec 26 21:21:58 arch systemd[1]: Starting Load/Save RF Kill Switch Status...
Dec 26 21:21:58 arch systemd[1]: Started Load/Save RF Kill Switch Status.
Dec 26 21:21:58 arch NetworkManager[494]: <info>  [1703622118.8757] manager: NetworkManager state is now CONNECTED_GLOBAL
Dec 26 21:21:58 arch NetworkManager[494]: <warn>  [1703622118.8767] platform-linux: do-add-ip6-address[2: fe80::9df1:d620:258d:aef2]: failure 95 (Operation not supported)
Dec 26 21:21:58 arch kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd

Check the status of "rfkill", does the NIC show up if you re-plug the dongle?

menteith · 2023-12-26 20:52:07

`rkill` returns nothing. When I re-plug the dongle, the interface won't show up (I use `ip link`) . Latest messages from dmesg:

[  815.310652] usb 1-3: device not accepting address 5, error -62
[  815.311703] mt7921u: probe of 1-3:1.3 failed with error -5
[  815.312108] usb 1-3: USB disconnect, device number 5
[  815.437323] usb 1-3: new high-speed USB device number 6 using xhci_hcd
[  820.773835] usb 1-3: device descriptor read/64, error -110
[  836.347349] usb 1-3: device descriptor read/64, error -110
[  836.577320] usb 1-3: new high-speed USB device number 7 using xhci_hcd
[  841.893773] usb 1-3: device descriptor read/64, error -110

Last edited by menteith (2023-12-26 20:52:59)

seth · 2023-12-26 21:17:41

The relevant difference seems

Dec 26 21:21:58 arch kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd

after which the device works.
Can you (w/o removing the dongle)

modprobe -r mt7921u
modprobe -v mt7921u

Ceterum censeo: there isn't a parallel windows installation, is there?

menteith · 2023-12-26 21:21:56

No, I don't have any Windows installation. After executing `modprobe` commands my doongle didn't show up.

seth · 2023-12-26 21:44:25

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

Was unloading the module successful to begin with and what was the exact result of re-loading it?
This looks like a race condition and livedistro is probably more important than livedistro (because of the slow usb medium)

menteith · 2023-12-26 21:51:26

seth wrote:

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Was unloading the module successful to begin with and what was the exact result of re-loading it?

Here's what I did:

❯ sudo modprobe -r mt7921u
❯ sudo modprobe -v mt7921u
insmod /lib/modules/6.1.69-1-lts/kernel/drivers/net/wireless/mediatek/mt76/mt76-usb.ko.zst 
insmod /lib/modules/6.1.69-1-lts/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921-common.ko.zst 
insmod /lib/modules/6.1.69-1-lts/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921u.ko.zst

seth · 2023-12-26 21:54:20

Ok, and what impact did the latter have on the dmesg?

menteith · 2023-12-26 21:57:47

Only one line appeared: `[ 1319.738878] usbcore: registered new interface driver mt7921u`

seth · 2023-12-26 22:16:35

What if you add "modprobe.blacklist=mt7921u" to the kernel parameters, reboot with the dongle attached, check whether the blacklist applied ("lsmod | grep mt7") and then explicitly load the mt7921u module. Also always check for the NICs presence in rfkill first. If it's (initially) blocked there, you won't see it in "ip l"

menteith · 2023-12-26 22:29:36

I did what you told me. Here's logs. Loading module:

❯ lsmod | grep mt7
❯ sudo modprobe -v mt7921u
insmod /lib/modules/6.1.69-1-lts/kernel/net/wireless/cfg80211.ko.zst 
insmod /lib/modules/6.1.69-1-lts/kernel/lib/crypto/libarc4.ko.zst 
insmod /lib/modules/6.1.69-1-lts/kernel/net/mac80211/mac80211.ko.zst 
insmod /lib/modules/6.1.69-1-lts/kernel/drivers/net/wireless/mediatek/mt76/mt76.ko.zst 
insmod /lib/modules/6.1.69-1-lts/kernel/drivers/net/wireless/mediatek/mt76/mt76-usb.ko.zst 
insmod /lib/modules/6.1.69-1-lts/kernel/drivers/net/wireless/mediatek/mt76/mt76-connac-lib.ko.zst 
insmod /lib/modules/6.1.69-1-lts/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921-common.ko.zst 
insmod /lib/modules/6.1.69-1-lts/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921u.ko.zst

Dmesg:

[   92.595222] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   92.595559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   92.595974] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   92.595978] cfg80211: failed to load regulatory.db
[   97.877311] usb 2-3: Disable of device-initiated U1 failed.
[  102.997340] usb 2-3: Disable of device-initiated U2 failed.
[  108.330591] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  113.663959] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  113.873879] usb 2-3: device not accepting address 2, error -62
[  119.210594] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  124.543931] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  124.750546] usb 2-3: device not accepting address 2, error -62
[  130.090651] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  135.423902] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  135.630574] usb 2-3: device not accepting address 2, error -62
[  140.970778] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  146.307333] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  146.517255] usb 2-3: device not accepting address 2, error -62
[  146.530628] usb 2-3: USB disconnect, device number 2
[  146.530993] mt7921u: probe of 2-3:1.3 failed with error -5
[  146.531026] usbcore: registered new interface driver mt7921u
[  151.850674] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  157.184174] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  157.390789] usb 2-3: device not accepting address 3, error -62
[  162.733958] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  168.063895] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  168.270638] usb 2-3: device not accepting address 4, error -62
[  168.277370] usb usb2-port3: attempt power cycle
[  174.250878] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  179.584172] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  179.790786] usb 2-3: device not accepting address 5, error -62
[  185.130682] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  190.464177] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  190.670602] usb 2-3: device not accepting address 6, error -62
[  190.677428] usb usb2-port3: unable to enumerate USB device

`rfkill` returns nothing. Interface is still not shown.

Last edited by menteith (2023-12-26 22:30:00)

seth · 2023-12-26 22:42:50

So doesn't help, the device is still not responding.

I assume that if you boot the install iso again and then reboot into the installed system the NIC (reliably) shows up?

Can you remove the kingston usb key and both logitech receivers and plug the wifi dongle into one of those ports and see wether it responds there?
(It might be simply underpowered for the init)

menteith · 2023-12-27 10:01:12

seth wrote:

I assume that if you boot the install iso again and then reboot into the installed system the NIC (reliably) shows up?

Yes, I've just checked

seth wrote:

Can you remove the kingston usb key and both logitech receivers and plug the wifi dongle into one of those ports and see wether it responds there?
(It might be simply underpowered for the init)

It didn't work.

I noticed that after I boot the install iso and then reboot into the installed system NIC shows up and I can connect to Internet.

seth · 2023-12-27 14:30:01

It didn't work.

Exact same errors in dmesg?

Maybe we should look at

The card (connected via USB) has stopped working recently along with ethernet.

What happened before that? Why did the ethernet fail?
Sanity check b/c of

I reinstalled Arch

pacman -Qs linux-firmware

menteith · 2023-12-27 18:56:22

Exact same errors in dmesg?

Yes.

What happened before that? Why did the ethernet fail?

I didn't play with my Arch installation nor with the hardware. Internet (both ethernet and wifi) just stopped working. Then I decided to do clean install of Arch - now ethernet is working fine.

pacman -Qs linux-firmware

❯ pacman -Qs linux-firmware
local/linux-firmware 20231211.f2e52a1c-1
    Firmware files for Linux
local/linux-firmware-whence 20231211.f2e52a1c-1
    Firmware files for Linux - contains the WHENCE license file which documents the vendor license details

seth · 2023-12-27 21:13:47

I didn't play with my Arch installation nor with the hardware.

Not even updates?
Chances are the dongle broke and the ethernet got affected trough NM (did you check whether that NIC was also gone)?

Do you have access to other systems to test that dongle on?

menteith · 2023-12-28 08:51:14

I installed updates.

I have access to Debian live. There were no problems using the dongle.

seth · 2023-12-28 13:16:36

I rather meant some different hardware (desktop, notebook, …)
We had established that live systems work.

Another thing you could try is to downgrade linux-firmware to match the previous version (pre 2023-12-1) of the install iso.

menteith · 2023-12-28 18:05:58

I will go with downgrading and post the results.

**EDIT**

Many thanks for the suggestion to downgrade linux-firmware! It did the trick!

Last edited by menteith (2023-12-28 18:55:42)

Arch Linux

#1 2023-12-26 16:21:10

[SOLVED] WiFi stopped working

#2 2023-12-26 17:16:33

Re: [SOLVED] WiFi stopped working

#3 2023-12-26 17:37:55

Re: [SOLVED] WiFi stopped working

#4 2023-12-26 19:40:20

Re: [SOLVED] WiFi stopped working

#5 2023-12-26 19:46:14

Re: [SOLVED] WiFi stopped working

#6 2023-12-26 19:50:46

Re: [SOLVED] WiFi stopped working

#7 2023-12-26 20:25:53

Re: [SOLVED] WiFi stopped working

#8 2023-12-26 20:45:23

Re: [SOLVED] WiFi stopped working

#9 2023-12-26 20:52:07

Re: [SOLVED] WiFi stopped working

#10 2023-12-26 21:17:41

Re: [SOLVED] WiFi stopped working

#11 2023-12-26 21:21:56

Re: [SOLVED] WiFi stopped working

#12 2023-12-26 21:44:25

Re: [SOLVED] WiFi stopped working

#13 2023-12-26 21:51:26

Re: [SOLVED] WiFi stopped working

#14 2023-12-26 21:54:20

Re: [SOLVED] WiFi stopped working

#15 2023-12-26 21:57:47

Re: [SOLVED] WiFi stopped working

#16 2023-12-26 22:16:35

Re: [SOLVED] WiFi stopped working

#17 2023-12-26 22:29:36

Re: [SOLVED] WiFi stopped working

#18 2023-12-26 22:42:50

Re: [SOLVED] WiFi stopped working

#19 2023-12-27 10:01:12

Re: [SOLVED] WiFi stopped working

#20 2023-12-27 14:30:01

Re: [SOLVED] WiFi stopped working

#21 2023-12-27 18:56:22

Re: [SOLVED] WiFi stopped working

#22 2023-12-27 21:13:47

Re: [SOLVED] WiFi stopped working

#23 2023-12-28 08:51:14

Re: [SOLVED] WiFi stopped working

#24 2023-12-28 13:16:36

Re: [SOLVED] WiFi stopped working

#25 2023-12-28 18:05:58

Re: [SOLVED] WiFi stopped working

Board footer