No bluetooth after update

[mow]

Describe the bug

After updating to Bazzite 42.20250817.1: Stable (F42.20250817.1), the Bluetooth controller disappears like there is no BT controller on the system at all. I tried to unload/load btusb, changed the order of loading MT7925 and related modules all didn't work either generate any noticeable errors.

Then I found a (weird but) effective workaround on an upstream discussion forum related to MT7925 chipset that states powering off the device and removing power cable for 30 seconds will clear some sort of cache on the chip itself, it worked. So the workaround is so-called cold reset, shutting off and removing power cable for 30 seconds.

As this is a bug, the solution might be a proper reset while initializing the driver after an update (or always) which may require upstream to act. Additionally a pci function reset can also solve the issue.

What did you expect to happen?

Bluetooth and other functionalities to work as expected.

Output of rpm-ostree status

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-asus:stable
                   Digest: sha256:e83aaae8712a9db9d30dea2f8c2c7156aca3f07a7b1494c3af5bcdbabbc04043
                  Version: 42.20250817.1 (2025-08-18T06:16:02Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-asus:stable
                   Digest: sha256:e6e97deafa6bbf4c15bbf84867994a6be5f99a06e818f8aea7367ed19f29ba94
                  Version: 42.20250712 (2025-07-12T02:30:57Z)

Hardware

I'm using Asus ROG Flow Z13 2025; Chipset: MediaTek MT7925 Kernel driver: mt7925e, BT handled via btusb/btmtk without modificaitons as is.

Extra information or context

https://discussion.fedoraproject.org/t/bluetooth-does-not-work-f42-mt7925/162265

[azuredusk10]

I have had the same issue occur twice now. First time was at the start of July. It happened again today.

After a stable Bazzite update, Bluetooth is switched off in Gaming Mode. No bluetooth devices will connect. I am also logged out of all Steam user accounts.

I have to plug in a mouse to my HTPC, log into a Steam account with the QR code, then go to the 'Settings' menu, then 'Bluetooth', then turn the bluetooth toggle on. Then bluetooth works as normal, including after rebooting.

I wrote a related forum post in July

[throughthetrees]

Having similar and maybe adjacent issue on the Z13, 128 gb variant.

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:a1684ba4bf00d36ba56a9db5c0fcde3a6278000748d42d9e8195432dd3b6d8c0
Version: 42.20250809 (2025-08-10T02:02:03Z)

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:a1684ba4bf00d36ba56a9db5c0fcde3a6278000748d42d9e8195432dd3b6d8c0
Version: 42.20250809 (2025-08-10T02:02:03Z)

Bluetooth drops/ disconnects/ freezes video etc. I might try reinstalling to the asus version.

[stereolead]

The solution has been found for a very similar problem, I have described it here: https://universal-blue.discourse.group/t/bluetooth-is-disabled-by-default-in-game-mode/9549/3

[arjhun]

Had exactly this problem. Fixed this in my Asrock bios by setting the BT on/off option from auto to enabled.

The solution has been found for a very similar problem, I have described it here: https://universal-blue.discourse.group/t/bluetooth-is-disabled-by-default-in-game-mode/9549/3

[azuredusk10]

I use a USB Bluetooth dongle and turned the wireless chip on my Asrock motherboard off, because the Asrock chip can't handle more than 3 controllers connected via Bluetooth at a time. So unfortunately I don't have this bios setting.

I'm glad you found something that works for you though!

[SkylarSouthard]

I'm having the same problem