diasbalmash
New Member
Is your laptop with dual boot mode?Thanx guys for the solution! same problem on HP ZBook 14 G10A
I disabled BIOS: "preboot wifi" and "fast boot". now it works perfectly!
Is your laptop with dual boot mode?Thanx guys for the solution! same problem on HP ZBook 14 G10A
I disabled BIOS: "preboot wifi" and "fast boot". now it works perfectly!
Only good thing I have found with MediaTek products, is they make media start [MSI] look dammed awful, I will never buy products by either of them.this Mediatek
I hate Mediatek they cause more problems than RTL, I was expecting a second line on device 2 saying state up or down.
I assume its a laptop of some sort. Occasionally when installing Linux on some machines, it will go into hard block [quite common on Acer] as it is showing a mt driver installed, First thing is to check if a hard block [flight mode] is activated.
hello sir ,can you help me too,i am a newbie .I am also facing issue with wifi adaptor,mt7902 ,Asus vivobook GO15 ,ubuntu 24.04.01Welcome to the forums
can you post the FULL report of inxi -Nnz ?
Welcomehello sir ,can you help me too,i am a newbie
lspci | grep Wireless
10:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
root@LianLi:~# nmcli dev wifi list
IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY
E2:DB:D1:46:C6:D0 -- Infra 6 540 Mbit/s 100 ▂▄▆█ WPA2
E2:DB:D1:46:C6:D2 -- Infra 6 540 Mbit/s 100 ▂▄▆█ WPA2 802.1X
E2:DB:D1:46:C6:D6 -- Infra 6 540 Mbit/s 100 ▂▄▆█ WPA2
What distribution are you using and which kernel?same issue. Currently it is working, but after some time wifi stops. And while shut down i can see logs - Mt7921 driver own failed. Do i need to get a new wifi card?
Purchasing a new wifi adapter worked for me. It instantly connects the wifi and keeps it on for days. The problem is gone.Hello; hoping I'm not breaking any necropost rules here, this post seems recent enough. I have been experiencing nearly identical issues as @aryankb27 above on my ASUS TUF A15 FA506QM for about 3 to 4 weeks, maybe more, but mine are a bit more severe: it tended to happen after an hour or two of usage or sometimes right on boot, but instead of merely stopping network access, it will also prevent me from disconnecting from the Wi-Fi network or using Ethernet, and it also creates a ton of processes that sometimes take up much of my CPU. Once that happens, a kernel panic will likely occur. If I shut down before then, WPA supplicant and NetworkManager will take two or three minutes to complete their stop job and then I'll see that same "mt7921e driver own failed" error, after which the laptop doesn't shut down properly, just stays on a black unpowered screen while remaining powered. I have to force shutdown.
I am running EndeavourOS, but I'm not sure it's actually relevant, because worryingly, this occurred even on a live USB. I tried Fedora KDE on two different thumb sticks first and both kernel panicked soon after reaching the desktop; then I tried EndeavourOS and had the same issue as my own system. This got me thinking it was a recent kernel problem, but I've tried a handful of versions from 6.13.8 (seemed to work before) to 6.14.4, on linux, linux-lts and linux-g14 from the ASUS-Linux project, and none of these kernels seemed to fix it ; I think I noticed linux 6.14.3 being slightly more stable, but that could be placebo.
The one solution I found was to blacklist mt7921e entirely, which has worked perfectly so far. I've been relying on Ethernet for now, but that's not always convenient, especially for work. If anyone has a fix, I would be glad for it. Otherwise, I think I'll get a dongle or replace with an Intel AX210 as I've seen suggested.
Some logs and outputs:
As a sidenote, a battery life increase from blacklisting the driver can be expected, but in this case, it's been TREMENDOUS: more than twice the battery life as far as I can tell. I would never have guessed. I assume it must mean a lot about how awful this card and driver really are.
- sample kernel panic report (thanks Arch for adding this new QR code feature)
- linux-hardware.org probe
- inxi -Nnz
- dmesg
- journalctl -u NetworkManager -b 0 (context: on that boot, I used the machine normally with a wired connection until the error occured, and then I tried to disconnect from the Wi-Fi)
- ps -ef (showcases unusual napy/phy0-0 and ksoftirqd processes which can take up much of the CPU)
I have been experiencing nearly identical issues as @aryankb27 above on my ASUS TUF A15 FA506QM for about 3 to 4 weeks, maybe more, but mine are a bit more severe