Arch Linux

ribbon

Member

Registered: 2025-11-11

Posts: 4

Wifi card firmware failing to initialize after system update

Hello

Last night I did a total system upgrade with pacman -Syu which included a kernel upgrade

via pacman.log

util-linux-libs (2.41.3-2 -> 2.42-1)
util-linux (2.41.3-2 -> 2.42-1)
linux (6.19.10.arch1-1 -> 6.19.11.arch1-1)
linux-headers (6.19.10.arch1-1 -> 6.19.11.arch1-1)

Upon booting my computer this morning the "Linux Ramdisk..." step hung for around a minute before continuing like normal.
Then, my WiFi connection would not start and I no longer had bluetooth. I have all the latest drivers installed.

> lspci -k

0b:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
        Subsystem: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
        Kernel driver in use: mt7921e
        Kernel modules: mt7921e

> journalctl -b

Apr 08 13:16:51 coffeewarmer kernel: mt7921e 0000:0b:00.0: Message 00000010 (seq 1) timeout
Apr 08 13:16:51 coffeewarmer kernel: mt7921e 0000:0b:00.0: Failed to get patch semaphore
Apr 08 13:16:51 coffeewarmer kernel: mt7921e 0000:0b:00.0: HW/SW Version: 0x8a108a10, Build Time: 20251223091050a
Apr 08 13:16:51 coffeewarmer kernel: mt7921e 0000:0b:00.0: WM Firmware Version: ____010000, Build Time: 20251223091148
Apr 08 13:16:54 coffeewarmer kernel: mt7921e 0000:0b:00.0: Message 00000002 (seq 11) timeout
Apr 08 13:16:54 coffeewarmer kernel: mt7921e 0000:0b:00.0: Failed to start WM firmware
Apr 08 13:16:54 coffeewarmer NetworkManager[793]: <info>  [1775679414.6724] manager: startup complete
Apr 08 13:16:57 coffeewarmer kernel: mt7921e 0000:0b:00.0: Message 00000010 (seq 12) timeout
Apr 08 13:16:57 coffeewarmer kernel: mt7921e 0000:0b:00.0: Failed to get patch semaphore
Apr 08 13:16:58 coffeewarmer systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 08 13:17:01 coffeewarmer kernel: mt7921e 0000:0b:00.0: Message 00000010 (seq 13) timeout
Apr 08 13:17:01 coffeewarmer kernel: mt7921e 0000:0b:00.0: Failed to get patch semaphore
Apr 08 13:17:04 coffeewarmer kernel: mt7921e 0000:0b:00.0: Message 00000010 (seq 14) timeout
Apr 08 13:17:04 coffeewarmer kernel: mt7921e 0000:0b:00.0: Failed to get patch semaphore
Apr 08 13:17:07 coffeewarmer kernel: mt7921e 0000:0b:00.0: Message 00000010 (seq 15) timeout
Apr 08 13:17:07 coffeewarmer kernel: mt7921e 0000:0b:00.0: Failed to get patch semaphore
Apr 08 13:17:11 coffeewarmer kernel: mt7921e 0000:0b:00.0: Message 00000010 (seq 1) timeout
Apr 08 13:17:11 coffeewarmer kernel: mt7921e 0000:0b:00.0: Failed to get patch semaphore
Apr 08 13:17:14 coffeewarmer kernel: mt7921e 0000:0b:00.0: Message 00000010 (seq 2) timeout
Apr 08 13:17:14 coffeewarmer kernel: mt7921e 0000:0b:00.0: Failed to get patch semaphore
Apr 08 13:17:17 coffeewarmer kernel: mt7921e 0000:0b:00.0: Message 00000010 (seq 3) timeout
Apr 08 13:17:17 coffeewarmer kernel: mt7921e 0000:0b:00.0: Failed to get patch semaphore
Apr 08 13:17:18 coffeewarmer systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 08 13:17:21 coffeewarmer kernel: mt7921e 0000:0b:00.0: Message 00000010 (seq 4) timeout
Apr 08 13:17:21 coffeewarmer kernel: mt7921e 0000:0b:00.0: Failed to get patch semaphore
Apr 08 13:17:21 coffeewarmer kernel: mt7921e 0000:0b:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0013 address=0xb763cdc0 flags=0x0050]
Apr 08 13:17:21 coffeewarmer kernel: mt7921e 0000:0b:00.0: hardware init failed

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,265

Re: Wifi card firmware failing to initialize after system update

In case there's a parallel windows installation see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Other/else-wise shut the system down, remove the battery, get a cup of coffee (No tea! That won't work and also is disgusting ) and put the battery back and reboot - does the chip work?
MTK has a track record of somehow sullying the chips SRAM even w/o dual booting and the only way out of that is a fully power cycle (which you won't get on a reboot)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc