You are not logged in.
@amadeuspaulussen if the chip remains stable w/ the patched firmware package and in general please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
Hi, I have a thinkpad z13 gen2 with the same wifi card and it's also no longer working. Moreover even shutting down or rebooting failed at the end with "reached poweroff target" or something like that but never really turned off. Downgrading with as described above fixed it
Offline
https://kb.withyouwithme.com/hs-fs/hubf … fined.jpeg
@amadeuspaulussen if the chip remains stable w/ the patched firmware package and in general please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
OK, thanks, I marked it as solved and added an update section to my original post containing the fix.
Offline
Does the firmware package from https://bbs.archlinux.org/viewtopic.php … 5#p2262695 also work?
Offline
Does the firmware package from https://bbs.archlinux.org/viewtopic.php … 5#p2262695 also work?
Yes, that works too. Shall I mention this as well in my update?
Offline
Please try adding the Kernel module option disable_clc=1 for the mt7921_common module and see if cab reproduce the issue with the broken firmware.
Offline
Same issue here. 20250917 is not working for me. Had to downgrade to `linux-firmware-mediatek 20250708-1` from my pacman cache since I didn't have internet. This alone didn't work out.
I ALSO had to unplug my laptop to wait 5 minutes like someone mentioned here. Can't believe that solved my issue.
Offline
Same issue here. 20250917 is not working for me. Had to downgrade to `linux-firmware-mediatek 20250708-1` from my pacman cache since I didn't have internet. This alone didn't work out.
I ALSO had to unplug my laptop to wait 5 minutes like someone mentioned here. Can't believe that solved my issue.
running a different distro (fedora -- so YMMV), but was having the same issue as everybody here. But I read the comments about having to unplug the machine, so I decided to try that _without_ downgrading linux-firmware. And it worked. Powered off and unplugged for a few minutes, turned on again, all issues resolved -- no packages changed or anything.
Offline
raykomayko wrote:Same issue here. 20250917 is not working for me. Had to downgrade to `linux-firmware-mediatek 20250708-1` from my pacman cache since I didn't have internet. This alone didn't work out.
I ALSO had to unplug my laptop to wait 5 minutes like someone mentioned here. Can't believe that solved my issue.running a different distro (fedora -- so YMMV), but was having the same issue as everybody here. But I read the comments about having to unplug the machine, so I decided to try that _without_ downgrading linux-firmware. And it worked. Powered off and unplugged for a few minutes, turned on again, all issues resolved -- no packages changed or anything.
I tried to replicate this on Arch by removing the "linux-firmware-mediatek" package from IgnorePkg in "/etc/pacman.conf", then updating with "pacman -Syu". The package updated successfully. I shut down the machine, disconnected it from power, and let it sit for three hours.
When I started it up after that, my Wi-Fi was gone.
I reinstalled "linux-firmware-mediatek-20250808-1-any.pkg.tar.zst" and put "linux-firmware-mediatek" back on the IgnorePkg list for now.
Offline
There're two independent problems (and some users ITT seem to have encountered both)
1. a specific issue w/ the latest mediatek firmwares (very likely depends on the exact chip)
2. a general problem w/ mediatek chips suffering from some volatile memory corruption (can occur for any number of reasons) that can (only) be overcome by completely cutting the chip from power
Offline
I'm using ASUS Vivobook s16 and got the same problem. Also temporarily resolved by locking the version of
linux-firmware-mediatek-20250808-1-any
Thanks @amadeuspaulussen. My dmesg is almost the same as @jimangel2001 's, so I don't want to post again.
Same issue here. 20250917 is not working for me. Had to downgrade to `linux-firmware-mediatek 20250708-1` from my pacman cache since I didn't have internet. This alone didn't work out.
I ALSO had to unplug my laptop to wait 5 minutes like someone mentioned here. Can't believe that solved my issue.
However, I didn't completely power off the laptop, SysRq reboot worked after the downgrading (as it hung on reboots)
Last edited by Catoverflow (2025-10-11 18:22:37)
Offline
I had the same problem and initially got wi-fi working again with the downgrade of the linux-firmware-mediatek package as suggested above in this thread.
However, the latest linux-firmware-mediatek 20251011-1 package fixes this and everything works once again after this upgrade.
Offline
I had the same problem and initially got wi-fi working again with the downgrade of the linux-firmware-mediatek package as suggested above in this thread.
However, the latest linux-firmware-mediatek 20251011-1 package fixes this and everything works once again after this upgrade.
I am happy to confirm this! \°/
Offline
the latest linux-firmware-mediatek 20251011-1 package fixes this and everything works once again after this upgrade.
upgpkg: 20250917-2: fix #29 revert mediatek firmware update, breakage experienced which was released just before 20251011-1 reverted the problematic commit. Please follow and assist with the issue upstream https://lore.kernel.org/linux-mediatek/ … entoo.org/.
Offline