[Framework 13 AMD on Arch] Issues with wireless after resume

I’m on 6.8.1-arch1-1 now, and I hit the issue this morning, and have been having the issue ongoing with 6.7 for a while.

1 Like

…and I’m having this problem on the LTS kernel (6.6.19) on Manjaro. Started occurring about a month ago. Tried 6.8, which (surprisingly) didn’t help.

Is there a way to automatically run the “sudo rmmod mt7921e && sudo modprobe mt7921e” command on resume?

I am also on 6.8 now on OpenSuse and it is still not working…

Edit: I actually did a fresh install (because I booked something trying to get hibernate to work) and now it works as expected.

I’ve put my dmesg logs and stuff over here, hopefully this is the right issue to be adding to. All of the details seem right to me.

https://bugzilla.kernel.org/show_bug.cgi?id=217415

Sadly this problem remains in 6.8.2.

1 Like

Hit this very same problem just now on my Framework 16, with the new Gemini release of EndeavourOS (arch based distro), which is on kernel 6.8.7. Reloading the mt7921e module does re-enable the wifi, so it is still usable but not ideal.

Is this issue present with the AX210?

I am an Arch user and can confirm that this issue has been resolved as of linux-6.8.7.arch1-2. It was present up to linux-6.8.5.arch1-1. (Please excuse the version jumps as I don’t update very frequently.)

The time it takes for the computer to become responsive upon resume has significantly decreased, making it much more comfortable to use. I’ve also realized that the system used to freeze for a while due to issues with the mt7921e module.

1 Like

On my EndeavorOs install (which is now running arch kernel 6.8.8-arch1-1) the problem still persists.

I still have this issue on NixOS 23.11 with kernel 6.8.8.

Have updated this morning to kernel 6.8.9-arch1-1, but the problem still persists, in fact it seemed worse, since the system hung up after reloading the mt7921e module (but that could just be an incidental fail, have not tried to repeat this).
Then I switched to 6.6.30-1-lts, and that seems to work without issues. I guess I’ll stay on LTS for a while until this is ironed out.

2 Likes

Unfortunately, this is not the case with 6.8.9 on ArchLinux. If people find this thread, please be aware its not safe to update.

I’m also still having this issue on nixos 6.8.9

I think I just experienced this issue, but after waking up from hibernation, not suspend.

Glad I found this thread, as a workaround I will try to reload the kernel module as instructed here:

EDIT: I just tried reproducing this again by hibernating and waking up a few seconds later, but couldn’t. WiFi reconnected instantly.

Maybe it depends on the duration of suspend/hibernate.

I’m on kernel 6.8.9, linux-firmware 20240510

Probable continues in Arch with Linux 6.9.1.

Have just updated my system to 6.6.31-2-lts, now i have a different problem, my system won’t shutdown/reset, i have to manually powercycle (but wifi does work after resume from hibernate). Tried the new 6.9.1-arch1-2 as well, but there the mt7921e module still needs to be reloaded otherwise there’s no wifi after resume from hibernate. I’m switching back to 6.6.30-1-lts.

I was wondering if I was the only one having this issue, but I’m having the same issue on 6.6.31

I’m having this issue with my Framework 16 on Arch with kernel 6.9.2.

This has been my experience with hibernation too: all’s well if I resume within a few hours, but I have to reload the module if it’s left hibernating for longer periods. I haven’t been keeping close track of that but it could be an interesting clue e.g. if the DHCP lease expires while it’s hibernated?

1 Like

issue persists on Kernel 6.9.1 with NixOS 23.11 & NetworkManager the sudo rmmod mt7921e && sudo modprobe mt7921e actually resolves it. But would be nice for this to just not happen :slight_smile:

1 Like