Any reason to reboot instead of systemctl enable x.service --now
?
Preference. Enable and starting services or restarting services is “fine” until something misfires and fails to be caught, then becoming a ticket. Rare, but happens.
Mediatek have released some new wifi and bluetooth firmware. The MT7922 is in the FW16.
Maybe someone who is seeing this problem can test.
I picked up the latest linux-firmware from Arch, which is dated 2024-11-11, but got a similar panic screen on resume from hibernate. The panic includes the mt7921e firmware build time, which is listed as 20240716163327. I suppose it’s likely that Arch hasn’t picked up this firmware yet somehow. Strange. Am I missing something here?
EDIT: I see this was merged on 11/12, a day after Arch built their firmware release. I’ll wait for the one this week and try it out then.
Sorry for the delay; had a bit of a family emergency.
I can confirm that resuming from hibernation works correctly with the 20241106...
firmware builds (on kernel 6.12.1). Unfortunately, those just barely missed the November linux-firmware
release, so most folks will be waiting for a few more weeks before things Just Work again.
I’m not totally happy using new firmware to fix a software regression, but it does work, and I’m going to be tracking the latest kernel anyway, so this is a Good Enough resolution for me.
I did a suspend to disk (lid down) on 6.12 Debian testing and it resumed and than crashed (could only get a photo )
at +56 lib/list_debug.c:
I might try bumping up my mt7921e firmware as it seems old:
dmesg | grep mt7921e
[ 24.830459] mt7921e 0000:01:00.0: ASIC revision: 79220010
[ 24.908656] mt7921e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240716163242a
[ 25.280718] mt7921e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20240716163327
[ 26.398263] mt7921e 0000:01:00.0 wlp1s0: renamed from wlan0
Also
ethtool -i wlp1s0
driver: mt7921e
version: 6.12.0-amw-dirty
firmware-version: ____000000-20240716163327
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
Hmm non of the images in linux mediatek firmware tree seem to have a name with mt7921 ??
I updated as per How to update Media Tek USB wifi mt7921 firmware
and reboot but still have:
ethtool -i wlp1s0
...
firmware-version: ____000000-20240716163327
...
But it’s fetching out of initrd …
Quickly do
update-initramfs -v -u
and reboot but still getting:
firmware-version: ____000000-20240716163327
Hmm we have:
% modinfo mt7921e
filename: /lib/modules/6.12.0-amw-dirty/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921e.ko
license: Dual BSD/GPL
description: MediaTek MT7921E (PCIe) wireless driver
author: Lorenzo Bianconi <lorenzo@kernel.org>
author: Sean Wang <sean.wang@mediatek.com>
firmware: mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin
firmware: mediatek/WIFI_RAM_CODE_MT7922_1.bin
firmware: mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin
firmware: mediatek/WIFI_RAM_CODE_MT7961_1.bin
firmware: mediatek/WIFI_MT7961_patch_mcu_1a_2_hdr.bin
firmware: mediatek/WIFI_RAM_CODE_MT7961_1a.bin
alias: pci:v000014C3d00007920sv*sd*bc*sc*i*
alias: pci:v000014C3d00000616sv*sd*bc*sc*i*
alias: pci:v000014C3d00000608sv*sd*bc*sc*i*
alias: pci:v00000B48d00007922sv*sd*bc*sc*i*
alias: pci:v000014C3d00007922sv*sd*bc*sc*i*
alias: pci:v000014C3d00007961sv*sd*bc*sc*i*
depends: mt76-connac-lib,mt7921-common,mt792x-lib,mt76
intree: Y
name: mt7921e
retpoline: Y
vermagic: 6.12.0-amw-dirty SMP preempt mod_unload modversions
parm: disable_aspm:disable PCI ASPM support (bool)
So perhaps it uses MT7922 firmware???..
Yes!
ethtool -i wlp1s0
gives
firmware-version: ____000000-20241106163310
Got here seeking for my issue, even if I am not (yet?) on a framework laptop. Just wanted to drop a line to say that the issue is not specific to the Framework 16 and that the ASUS Zephyrus ROG 14 2022 has exactly the same problem. Also there, the new firmware is not fixing the issue.