Wifi Access Point Mode Results In Freeze on Bazzite

[JumperLabs]

Describe the bug

Bug Report: Wifi Access Point Mode Results In Freeze on Bazzite

Hardware

Legion Go and Asus Ally
MT7922 aka AMD RZ626 Wifi Module

Issue Description

Trying to use Wifi as an Access Point or Hotspot freezes the system entirely (kernel panic?) when another device tries to connect. This occurs on both Legion Go and Asus Ally (both report MT7922 aka RZ626 as Wifi adapter) with Bazzite.

Steps to Reproduce

1. Install Bazzite-Deck on a Legion Go or ROG Ally.
2. Turn on Wifi and configure Wifi to host as a Hotspot or Access Point (any/all security options and other configurations appear to trigger bug, including no security at all - my intent was to use manual ip addresses, but auto has the same bug).
3. Attempt to connect to Wifi from another computer. About ~4 seconds after connection success the host computer will freeze (client appears largely unaffected, just announces connection dropped).

What did you expect to happen?

I expected to be able to network two mobile computers without a router by using the Wifi module in "Access Point" mode.

Output of rpm-ostree status

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:d39a074cc8df8db25a56998f20bf4fc4fe55b4ccd2594e956b65e59a8bd95408
                  Version: 41.20250301.1 (2025-03-03T05:15:12Z)
          LayeredPackages: hostapd python3.9

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:d39a074cc8df8db25a56998f20bf4fc4fe55b4ccd2594e956b65e59a8bd95408
                  Version: 41.20250301.1 (2025-03-03T05:15:12Z)
          LayeredPackages: hostapd

Hardware

Legion Go: 83E1
ROG Ally: ROG ALLY RC71L

Extra information or context

When using the Mint 22 live-install it appears to work as expected, and the Wifi works just fine when connecting in Infrastructure mode to a router. (For reference: A Steam Deck with original OS hosts the Access Point just fine, but causes exactly the same behavior when it tries to connect to a Bazzite host.)

Investigating what Mint 22 might be doing differently lead me to differences in the output from "modinfo mt7921e". Mint 22 uses kernel "6.8.0-38-generic" vs. Bazzite's "6.13.5-102". Also, while both use these firmware files:
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
Bazzite also uses:
firmware: mediatek/WIFI_MT7961_patch_mcu_1a_2_hdr.bin
firmware: mediatek/WIFI_RAM_CODE_MT7961_1a.bin
Alas, this is as far as I could go. I haven't been able to figure out exactly why those exist, and can't figure out how to remove those files to test Bazzite's behavior without them (I don't know how to blacklist firmware files, just entire modules - and I don't know how to make changes to the non-mutable filesystem).

Other information:

1. Freeze appears to be "complete" (originally I theorized it might just crash Wayland, but the system stops sending/responding to pings and drops open SSH connections over Ethernet), and requires a hard reboot to clear. It doesn't appear to respond to any input (like "Ctrl+Alt+F2") other than holding the power button long enough for it to shutdown.
2. If there are any messages because of the crash, I don't think they make it into the log as seen with "journalctl -r" or "ujust logs-last-boot".
3. Disabling SE_Linux with "sudo setenforce 0" doesn't help.
4. Setting NetworkManager to ignore the Wifi device and manually using hostapd to create an access point doesn't seem to help.