MT7922 firmware not working

[Frozen_byte]

Hey I have a "ASUS ROG Strix B650-A Gaming WIFI" (https://rog.asus.com/motherboards/rog-strix/rog-strix-b650-a-gaming-wifi-model/) Motherboard and the WiFi/Bluetooth is not working.

On windows, the module is working fine.
Using "Kubuntu 22.10" with Kernel "5.19.0-35-generic"

lshw -class network:
  *-network
       description: Network controller
       product: MT7922 802.11ax PCI Express Wireless Network Adapter
       vendor: MEDIATEK Corp.
       physical id: 0
       bus info: pci@0000:0b:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm bus_master cap_list
       configuration: driver=mt7921e latency=0
       resources: iomemory:fc0-fbf irq:119 memory:fc30300000-fc303fffff memory:fc500000-fc507fff

#dmesg | grep mt7921e

[ 17.001057] mt7921e 0000:0b:00.0: enabling device (0000 -> 0002)
[ 17.001199] mt7921e 0000:0b:00.0: ASIC revision: 79220010
[ 20.247369] mt7921e 0000:0b:00.0: Message 0004008a (seq 1) timeout
[ 23.575534] mt7921e 0000:0b:00.0: Message 0004008a (seq 2) timeout
[ 26.907372] mt7921e 0000:0b:00.0: Message 0004008a (seq 3) timeout
[ 30.231376] mt7921e 0000:0b:00.0: Message 0004008a (seq 4) timeout
[ 33.559704] mt7921e 0000:0b:00.0: Message 0004008a (seq 5) timeout
[ 36.887365] mt7921e 0000:0b:00.0: Message 0004008a (seq 6) timeout
[ 40.215367] mt7921e 0000:0b:00.0: Message 0004008a (seq 7) timeout
[ 43.543670] mt7921e 0000:0b:00.0: Message 0004008a (seq 8) timeout
[ 46.871378] mt7921e 0000:0b:00.0: Message 0004008a (seq 9) timeout
[ 50.199714] mt7921e 0000:0b:00.0: Message 0004008a (seq 10) timeout
[ 50.280219] mt7921e 0000:0b:00.0: hardware init failed

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-35-generic 5.19.0-35.36
ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Feb 10 03:33:02 2023
InstallationDate: Installed on 2023-02-09 (0 days ago)
InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
IwConfig:
 lo no wireless extensions.

 eno1 no wireless extensions.
MachineType: ASUS System Product Name
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-35-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-35-generic N/A
 linux-backports-modules-5.19.0-35-generic N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2022
dmi.bios.release: 8.23
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0823
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX B650-A GAMING WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0823:bd11/21/2022:br8.23:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB650-AGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Juerg Haefliger (juergh)]

There's new MT79xx firmware available from upstream kernel.org:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek

Copy the following files to /lib/firmware/mediatek on your machine (make backups first):
BT_RAM_CODE_MT7922_1_1_hdr.bin
BT_RAM_CODE_MT7961_1_2_hdr.bin
WIFI_MT7922_patch_mcu_1_1_hdr.bin
WIFI_RAM_CODE_MT7922_1.bin
WIFI_MT7961_patch_mcu_1_2_hdr.bin
WIFI_RAM_CODE_MT7961_1.bin

Reboot and check if that makes a difference.

[Frozen_byte (frozen-byte)]

Sadly this changes nothing.

The timeout in dmesg persist.

Also tried 6.1 and 6.2 kernel without success.

[Frozen_byte (frozen-byte)]

I searched for the Internet and some Anons suggested resetting the Network-Adapter by disconnecting them from power. (i.E.: https://unix.stackexchange.com/a/723829 )

So, I executed the following steps:

1. Removing the Motherboard from ANY power source (even took the battery off)
2. pressed power button several times to unload capacitors
3. waited ~5 mins and connected power cable and inserted battery
- Then, after booting into the system, the network was not loaded at all.
4. opened the shell and executed `$ sudo modprobe mt7921e`
- Everything was working now.

I am using/restarting my PC daily and there was only on occurrence where the WLAN was not working, a second
`$ sudo modprobe mt7921e`
fixed it.

Strangely enough, I loaded the mod before I did the power surge, so I only can narrow it down to that step.

[Aeon (aeondave)]

I have tested the some suggested solution.. but unfortunately, the bug still persists. I would like to mention that the power reset solution is not applicable for laptops unless you disassemble the built-in battery. Additionally, I have also tested the latest daily build (version 23.10) with latest kernel, but the issue remains unresolved. The error in dmesg continues to occur and wifi still don't do anything. Please let me know if there are any further suggestions or updates on this bug. Thank you.

[Andrew Marshall (planetmarshalluk)]

Reproduced on ASUS G14 Laptop (model number GA402NV).

Ubuntu 23.04
6.2.0-23-generic

`dmesg | grep mt7` gives the following -

```
[ 14.665322] mt7921e 0000:03:00.0: ASIC revision: 79220010
[ 17.955295] mt7921e 0000:03:00.0: Message 00000010 (seq 1) timeout
[ 17.955309] mt7921e 0000:03:00.0: Failed to get patch semaphore
[ 21.287296] mt7921e 0000:03:00.0: Message 00000010 (seq 2) timeout
[ 21.287325] mt7921e 0000:03:00.0: Failed to get patch semaphore
[ 24.611295] mt7921e 0000:03:00.0: Message 00000010 (seq 3) timeout
[ 24.611309] mt7921e 0000:03:00.0: Failed to get patch semaphore
[ 27.939637] mt7921e 0000:03:00.0: Message 00000010 (seq 4) timeout
[ 27.939653] mt7921e 0000:03:00.0: Failed to get patch semaphore
[ 31.267262] mt7921e 0000:03:00.0: Message 00000010 (seq 5) timeout
[ 31.267268] mt7921e 0000:03:00.0: Failed to get patch semaphore
[ 34.599284] mt7921e 0000:03:00.0: Message 00000010 (seq 6) timeout
[ 34.599294] mt7921e 0000:03:00.0: Failed to get patch semaphore
[ 37.923354] mt7921e 0000:03:00.0: Message 00000010 (seq 7) timeout
[ 37.923371] mt7921e 0000:03:00.0: Failed to get patch semaphore
[ 41.251277] mt7921e 0000:03:00.0: Message 00000010 (seq 8) timeout
[ 41.251289] mt7921e 0000:03:00.0: Failed to get patch semaphore
[ 44.579666] mt7921e 0000:03:00.0: Message 00000010 (seq 9) timeout
[ 44.579681] mt7921e 0000:03:00.0: Failed to get patch semaphore
[ 47.907627] mt7921e 0000:03:00.0: Message 00000010 (seq 10) timeout
[ 47.907641] mt7921e 0000:03:00.0: Failed to get patch semaphore
[ 47.989282] mt7921e 0000:03:00.0: hardware init failed
```

Occasionally after a reboot I instead see the following:
```
[ 19.143835] mt7921e 0000:03:00.0: driver own failed
[ 19.143886] mt7921e: probe of 0000:03:00.0 failed with error -5
```

Have tried all suggested workarounds including disconnecting the battery, no change.

[Artem S. Tashkinov (birdie-github)]

Please try this patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/mediatek/mt76/mt7921?id=525c469e5de9bf7e53574396196e80fc716ac9eb

or wait until Linux 6.5 gets released.

[Andrew Marshall (planetmarshalluk)]

Thanks for the update. I have applied the patch on 6.4.3 but no effect. I see the following error in the kernel log -

```
Jul 16 12:51:26 andrew-laptop kernel: mt7921e 0000:03:00.0: enabling device (0000 -> 0002)
Jul 16 12:51:26 andrew-laptop kernel: mt7921e 0000:03:00.0: driver own failed
Jul 16 12:51:26 andrew-laptop kernel: mt7921e: probe of 0000:03:00.0 failed with error -5

```

[Juerg Haefliger (juergh)]

Has this worked with older (<5.19) kernel, i.e., is it a regression?

[Juerg Haefliger (juergh)]

You could try newest mainline kernels from [1] to see if that makes it any better. Note that these are not supported and only for testing and you need to disable Secure Boot.

[1] https://kernel.ubuntu.com/~juergh/dashboard.html

[Alex Tarasenko (alextars)]

I tried 6.5-rc6 mainline kernel on Ubuntu 22.04.3 LTS, but no effect.

[Alex Tarasenko (alextars)]

6.5.0-1003 OEM fixed this bug.