WIFI device keeps failing with: mt7921e driver own failed

crazzyfool · 2024-01-22 13:27:33

Hi. I've recently just installed Arch linux on an ASUS TUF Gaming F15 (FX506LH) and everything was going great until I started getting issues with the WIFI where the adapter seems to fail and I can't even do a clean restart - I have to hold the power button towards the end of shutdown.

I really don't know if I have an actual hardware issue or if this is a driver issue. The internet seems to be littered with issues around the mt7921e driver and the same issue so I don't think its a hardware issue but I couldn't find anything that resolved it.

This is what I'm seeing in the logs:

tuf ~ # journalctl -b -1 -g mt7921e
Jan 22 12:48:45 tuf kernel: mt7921e 0000:04:00.0: enabling device (0000 -> 0002)
Jan 22 12:48:45 tuf kernel: mt7921e 0000:04:00.0: ASIC revision: 79610010
Jan 22 12:48:45 tuf kernel: mt7921e 0000:04:00.0: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a
Jan 22 12:48:45 tuf kernel: mt7921e 0000:04:00.0: WM Firmware Version: ____010000, Build Time: 20231109190959
Jan 22 12:48:46 tuf kernel: mt7921e 0000:04:00.0 wlp4s0: renamed from wlan0
Jan 22 12:48:49 tuf NetworkManager[544]: <info>  [1705927729.6657] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.5/0000:04:00.0/ieee80211/phy0/rfkill0) (driv$'\E[38;5;246m'>$'\E[0m'
Jan 22 12:52:43 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:52:44 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:52:45 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:52:46 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:52:47 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:52:48 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:52:49 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:52:50 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:52:51 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:52:52 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:52:53 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:52:54 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:52:55 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:52:56 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:52:57 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:52:58 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:52:59 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:53:00 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:53:01 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:53:03 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:53:03 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:53:05 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:53:05 tuf kernel: mt7921e 0000:04:00.0: chip reset failed
Jan 22 12:53:08 tuf kernel: mt7921e 0000:04:00.0: Message 00020001 (seq 10) timeout
Jan 22 12:53:11 tuf kernel: mt7921e 0000:04:00.0: Message 00020002 (seq 11) timeout
Jan 22 12:53:12 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:53:21 tuf kernel: mt7921e 0000:04:00.0: Message 00020003 (seq 14) timeout
Jan 22 12:53:21 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:53:23 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:53:24 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:53:25 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:53:31 tuf kernel: mt7921e 0000:04:00.0: Message 00020003 (seq 15) timeout
Jan 22 12:53:37 tuf kernel: mt7921e 0000:04:00.0: Message 00020003 (seq 1) timeout
Jan 22 12:53:38 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:53:40 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:53:40 tuf kernel: mt7921e 0000:04:00.0: driver own failed
Jan 22 12:53:42 tuf kernel: mt7921e 0000:04:00.0: Timeout for driver own
Jan 22 12:53:48 tuf kernel: mt7921e 0000:04:00.0: Message 00020003 (seq 2) timeout
Jan 22 12:53:54 tuf kernel: mt7921e 0000:04:00.0: Message 00020003 (seq 3) timeout
Jan 22 12:53:55 tuf kernel: mt7921e 0000:04:00.0: driver own failed
...

It seems like this driver is really buggy at the moment so maybe it will just get fixed with a future update......or maybe I have an actual hardware issue - it would be great if someone could help confirm either way.

Thanks.

xanderxanderfto · 2024-01-25 16:57:50

Check this https://bbs.archlinux.org/viewtopic.php?id=213449. You have both networkd and network manager working at the same time

m8 · 2024-02-02 22:03:36

Wow I'm having the exact same error on the same hardware on random occasions. I only have NetworkManager enabled, and I wasn't having such errors anyway until a recent upgrade. I can only fix this with rebooting

seth · 2024-02-02 23:26:23

ASUS TUF Gaming F15 as well?
There's no indication that the OP has multiple processes dogging on the same NIC, but the journal excerpt is pretty useless either - it records the failure but no hint at the possible reasons.

Please post your complete system journal for the boot:

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

m8 · 2024-02-08 22:14:21

seth wrote:

ASUS TUF Gaming F15 as well?
There's no indication that the OP has multiple processes dogging on the same NIC, but the journal excerpt is pretty useless either - it records the failure but no hint at the possible reasons.
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

Update: My computer is hanging on reboot too now...

http://0x0.st/Hdzy.txt

Yes, I am using ASUS TUF Gaming F15.

Last edited by m8 (2024-02-08 22:14:51)

seth · 2024-02-08 22:33:21

Do you have a journal for the hanging reboot?
(The one you posted is only 3 minutes and doesn't even cover the wifi issues)
Itr, can you break/continue the reboot w/ https://wiki.archlinux.org/title/Keyboa … el_(SysRq) ? (REISUB)

Did you try the LTS kernel on either situation?
You don't have nvidia_drm.modeset enabled, https://wiki.archlinux.org/title/NVIDIA … de_setting

m8 · 2024-02-10 09:01:29

seth wrote:

Do you have a journal for the hanging reboot?
(The one you posted is only 3 minutes and doesn't even cover the wifi issues)
Itr, can you break/continue the reboot w/ https://wiki.archlinux.org/title/Keyboa … el_(SysRq) ? (REISUB)
Did you try the LTS kernel on either situation?
You don't have nvidia_drm.modeset enabled, https://wiki.archlinux.org/title/NVIDIA … de_setting

Got it, that was the journal after the system was rebooted (with no wifi issues). I'll post the things you mentioned once this occurs again (I don't know what causes this yet).

edit: I am using the LTS kernel
edit2: 6.7.1 specifically, just made a system update and I will be at 6.7.4 at the next reboot.

Last edited by m8 (2024-02-10 09:05:06)

m8 · 2024-02-21 16:44:37

seth wrote:

Do you have a journal for the hanging reboot?
(The one you posted is only 3 minutes and doesn't even cover the wifi issues)
Itr, can you break/continue the reboot w/ https://wiki.archlinux.org/title/Keyboa … el_(SysRq) ? (REISUB)
Did you try the LTS kernel on either situation?
You don't have nvidia_drm.modeset enabled, https://wiki.archlinux.org/title/NVIDIA … de_setting

Managed to get this to happen again today
http://0x0.st/H5qK.txt

seth · 2024-02-21 17:00:14

Feb 21 18:34:14 arch-tuf kernel: Linux version 6.7.4-arch1-1 (linux@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Mon, 05 Feb 2024 22:07:49 +0000
# NM scans around
Feb 21 18:34:17 arch-tuf NetworkManager[489]: <info>  [1708533257.6148] device (wlp45s0): set-hw-addr: set MAC address to 9A:80:CC:25:00:51 (scanning)
Feb 21 18:34:20 arch-tuf NetworkManager[489]: <info>  [1708533260.9948] device (wlp45s0): set-hw-addr: set MAC address to F6:34:58:89:B8:DB (scanning)
Feb 21 18:34:23 arch-tuf NetworkManager[489]: <info>  [1708533263.4445] device (wlp45s0): supplicant interface state: interface_disabled -> scanning
Feb 21 18:34:23 arch-tuf NetworkManager[489]: <info>  [1708533263.4446] device (p2p-dev-wlp45s0): supplicant management interface state: interface_disabled -> scanning
Feb 21 18:34:23 arch-tuf NetworkManager[489]: <info>  [1708533263.5344] device (wlp45s0): set-hw-addr: set MAC address to 6E:2D:E4:08:45:1B (scanning)
Feb 21 18:34:23 arch-tuf NetworkManager[489]: <info>  [1708533263.6104] device (wlp45s0): supplicant interface state: scanning -> disconnected
Feb 21 18:34:23 arch-tuf NetworkManager[489]: <info>  [1708533263.6104] device (p2p-dev-wlp45s0): supplicant management interface state: scanning -> disconnected
Feb 21 18:34:25 arch-tuf NetworkManager[489]: <info>  [1708533265.9760] device (wlp45s0): supplicant interface state: inactive -> scanning
Feb 21 18:34:25 arch-tuf NetworkManager[489]: <info>  [1708533265.9760] device (p2p-dev-wlp45s0): supplicant management interface state: inactive -> scanning
# You try to connect to an AP
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <info>  [1708533282.4264] device (wlp45s0): disconnecting for new activation request.
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <info>  [1708533282.4264] device (wlp45s0): state change: need-auth -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <info>  [1708533282.4265] manager: NetworkManager state is now DISCONNECTING
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <info>  [1708533282.4268] audit: op="connection-activate" uuid="2c8d1b4e-a0f5-4938-b143-1875ea998d11" name="WIND_E11A71" pid=753 uid=1000 result="success"
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <warn>  [1708533282.4554] device (wlp45s0): Deactivation failed: GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <info>  [1708533282.4555] device (wlp45s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Feb 21 18:34:42 arch-tuf wpa_supplicant[559]: wlp45s0: WPS-CANCEL
Feb 21 18:34:45 arch-tuf kernel: mt7921e 0000:2d:00.0: Message 00020002 (seq 10) timeout
Feb 21 18:34:46 arch-tuf systemd[1]: systemd-hostnamed.service: Deactivated successfully.
# Things went south
Feb 21 18:34:46 arch-tuf kernel: mt7921e 0000:2d:00.0: driver own failed
Feb 21 18:34:47 arch-tuf kernel: mt7921e 0000:2d:00.0: Timeout for driver own

Disable https://wiki.archlinux.org/title/Networ … domization

Feb 21 18:34:14 arch-tuf kernel:  nvme0n1: p1 p2 p3 p4 p5 p6
Feb 21 18:34:15 arch-tuf kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Parallel windows?
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

m8 · 2024-02-21 19:41:42

seth wrote:

Feb 21 18:34:14 arch-tuf kernel: Linux version 6.7.4-arch1-1 (linux@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Mon, 05 Feb 2024 22:07:49 +0000
# NM scans around
Feb 21 18:34:17 arch-tuf NetworkManager[489]: <info>  [1708533257.6148] device (wlp45s0): set-hw-addr: set MAC address to 9A:80:CC:25:00:51 (scanning)
Feb 21 18:34:20 arch-tuf NetworkManager[489]: <info>  [1708533260.9948] device (wlp45s0): set-hw-addr: set MAC address to F6:34:58:89:B8:DB (scanning)
Feb 21 18:34:23 arch-tuf NetworkManager[489]: <info>  [1708533263.4445] device (wlp45s0): supplicant interface state: interface_disabled -> scanning
Feb 21 18:34:23 arch-tuf NetworkManager[489]: <info>  [1708533263.4446] device (p2p-dev-wlp45s0): supplicant management interface state: interface_disabled -> scanning
Feb 21 18:34:23 arch-tuf NetworkManager[489]: <info>  [1708533263.5344] device (wlp45s0): set-hw-addr: set MAC address to 6E:2D:E4:08:45:1B (scanning)
Feb 21 18:34:23 arch-tuf NetworkManager[489]: <info>  [1708533263.6104] device (wlp45s0): supplicant interface state: scanning -> disconnected
Feb 21 18:34:23 arch-tuf NetworkManager[489]: <info>  [1708533263.6104] device (p2p-dev-wlp45s0): supplicant management interface state: scanning -> disconnected
Feb 21 18:34:25 arch-tuf NetworkManager[489]: <info>  [1708533265.9760] device (wlp45s0): supplicant interface state: inactive -> scanning
Feb 21 18:34:25 arch-tuf NetworkManager[489]: <info>  [1708533265.9760] device (p2p-dev-wlp45s0): supplicant management interface state: inactive -> scanning
# You try to connect to an AP
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <info>  [1708533282.4264] device (wlp45s0): disconnecting for new activation request.
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <info>  [1708533282.4264] device (wlp45s0): state change: need-auth -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <info>  [1708533282.4265] manager: NetworkManager state is now DISCONNECTING
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <info>  [1708533282.4268] audit: op="connection-activate" uuid="2c8d1b4e-a0f5-4938-b143-1875ea998d11" name="WIND_E11A71" pid=753 uid=1000 result="success"
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <warn>  [1708533282.4554] device (wlp45s0): Deactivation failed: GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected
Feb 21 18:34:42 arch-tuf NetworkManager[489]: <info>  [1708533282.4555] device (wlp45s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Feb 21 18:34:42 arch-tuf wpa_supplicant[559]: wlp45s0: WPS-CANCEL
Feb 21 18:34:45 arch-tuf kernel: mt7921e 0000:2d:00.0: Message 00020002 (seq 10) timeout
Feb 21 18:34:46 arch-tuf systemd[1]: systemd-hostnamed.service: Deactivated successfully.
# Things went south
Feb 21 18:34:46 arch-tuf kernel: mt7921e 0000:2d:00.0: driver own failed
Feb 21 18:34:47 arch-tuf kernel: mt7921e 0000:2d:00.0: Timeout for driver own

Disable https://wiki.archlinux.org/title/Networ … domization

Feb 21 18:34:14 arch-tuf kernel:  nvme0n1: p1 p2 p3 p4 p5 p6
Feb 21 18:34:15 arch-tuf kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Parallel windows?
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Thanks! Turned off MAC randomization, will report on updates.
As for the other thing, I do have a windows partition but haven't booted in ages. By disable should I disable fast startup or hibernation?

seth · 2024-02-21 21:09:39

Both - "fast start" is just hibernation in disguise. And the default behavior. And it means that two OS are operating the HW at the same time.
Radio is the most common victim of that condition.

Please also try to avoid bloating the thread by fully quoting posts.

Hiradexo · 2024-03-29 14:14:45

Hello Im experiencing the same issue here on my ASUS TUF FX506HCB laptop
my main OS is Arch and Im dual booted with windows i havent used it for a long time
my issues started after i updated my laptop including my kde moving to kde6 and ...
every time I boot in to my OS I work with it for a while then my wifi goes out and the whole KDE crashes I can switch to other tty but i get spamed with

mt7921e 0000:04:00.0: driver own failed

here is output of
journalctl -b | curl -F 'file=@-' 0x0.st
journalctl -b -1 -g mt7921e | curl -F 'file=@-' 0x0.st

I have had several problems with my asus laptop including optimus and power management when unpluged but this one is new
I have the latest bios version and I didnt have problem with it before the update
my kernel is currently 6.6.23-1-lts
And Im sure that fast boot and secure boot is off

Last edited by Hiradexo (2024-03-29 14:20:45)

seth · 2024-03-29 16:27:53

https://0x0.st/XzrQ.txt is not a complete log

Both show MASSIVE bus issues along

Mar 29 17:25:15 Gharch kernel: mt7921e 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Mar 29 17:25:15 Gharch kernel: mt7921e 0000:02:00.0:   device [14c3:7961] error status/mask=00000001/00006000
Mar 29 17:25:15 Gharch kernel: mt7921e 0000:02:00.0:    [ 0] RxErr                  (First)

1. wrt window, long not used or not: 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

nb. the terminology:
"fast boot" is a BIOS feature to skip self tests, "fast-start" is windows emulating the ability to start fast by just secretely hibernating.
Also windows keeps re-enabling it w/ updates, so check to be sure that it's (still) disabled.

2. Try to add "pcie_aspm=off" to the https://wiki.archlinux.org/title/Kernel_parameters
"pci=noaer" should™ make the system a bit more silent but will not fix the underlying problem!

m8 · 2024-04-13 08:41:16

I don't really have any new good news but just to give an update: I'm still getting the same errors (which are most likely the same as Hiradexo since I always see that driver own message). I didn't have the chance of disabling windows fast-start since my windows dual boot was broken and bluescreened before I had any issues on arch, so I'm curious if Hiradexo is able to fix it with this. Is there any way I can disable Windows fast start if my Windows isn't even bootable? Will it work if I just delete all windows partitions?

seth · 2024-04-13 13:47:07

I can disable Windows fast start if my Windows isn't even bootable?

No, but it's also not clear whether there'd be any hibernation entry left if windows just BSODs - what's the nature of the BSOD? It might hint at deper (hw?) issues that also affect linux.

Try to power down the system, remove the battery, get a cup of coffe, return the battery, see whether that fixed anything.
If so and as long as you're not even trying to boot windows it would not be able to hibernate again…

m8 · 2024-05-22 14:15:54

seth wrote:

No, but it's also not clear whether there'd be any hibernation entry left if windows just BSODs - what's the nature of the BSOD? It might hint at deper (hw?) issues that also affect linux.
Try to power down the system, remove the battery, get a cup of coffe, return the battery, see whether that fixed anything.
If so and as long as you're not even trying to boot windows it would not be able to hibernate again…

I was very busy with work and ended up working around the issue by preventing sleep on my laptop and constantly running ping on the background.

4 days ago I finally had the opportunity to open my laptop and remove the battery and after 4 days of no problems I'm gonna call this problem finally solved. I can't believe windows was still ruining my life months after it's death.

ps: the BSOD was unrelated to hardware, I just force-shrunk that partition since I wasn't going to use windows again.

Arch Linux

#1 2024-01-22 13:27:33

WIFI device keeps failing with: mt7921e driver own failed

#2 2024-01-25 16:57:50

Re: WIFI device keeps failing with: mt7921e driver own failed

#3 2024-02-02 22:03:36

Re: WIFI device keeps failing with: mt7921e driver own failed

#4 2024-02-02 23:26:23

Re: WIFI device keeps failing with: mt7921e driver own failed

#5 2024-02-08 22:14:21

Re: WIFI device keeps failing with: mt7921e driver own failed

#6 2024-02-08 22:33:21

Re: WIFI device keeps failing with: mt7921e driver own failed

#7 2024-02-10 09:01:29

Re: WIFI device keeps failing with: mt7921e driver own failed

#8 2024-02-21 16:44:37

Re: WIFI device keeps failing with: mt7921e driver own failed

#9 2024-02-21 17:00:14

Re: WIFI device keeps failing with: mt7921e driver own failed

#10 2024-02-21 19:41:42

Re: WIFI device keeps failing with: mt7921e driver own failed

#11 2024-02-21 21:09:39

Re: WIFI device keeps failing with: mt7921e driver own failed

#12 2024-03-29 14:14:45

Re: WIFI device keeps failing with: mt7921e driver own failed

#13 2024-03-29 16:27:53

Re: WIFI device keeps failing with: mt7921e driver own failed

#14 2024-04-13 08:41:16

Re: WIFI device keeps failing with: mt7921e driver own failed

#15 2024-04-13 13:47:07

Re: WIFI device keeps failing with: mt7921e driver own failed

#16 2024-05-22 14:15:54

Re: WIFI device keeps failing with: mt7921e driver own failed

Board footer