I have a Framework Laptop 13 AMD Ryzen AI 300 Series running Fedora Linux 42.20250813.0 (Silverblue).
After a Fedora system update today is seems like bluetooth is no longer detected on my laptop. The settings page asks me to plug a bluetooth dongle in.
I’m a bit of a Linux noob in terms of debugging issues like this so any help in investigating this would be most welcome.
Thank you!
F42 rolled out a firmware update around a day ago, including:
update firmware for MT7925 WiFi device
mediatek MT7925: update bluetooth firmware to 20250721233113
Is that the BT/WiFi adapter on the AI 300 machines?
It looks that way. Framework’s website lists it as AMD RZ717 Wi-Fi 7 in the specs for the Framework 13 but apparently this is also known as the Mediatek MT7925.
I see it referenced in the output of journalctl -k:
Aug 13 12:40:29 divo kernel: mt7925e 0000:c0:00.0: ASIC revision: 79250000
Aug 13 12:40:29 divo kernel: mt7925e 0000:c0:00.0: HW/SW Version: 0x8a108a10, Build Time: 20250526152947a
Aug 13 12:40:30 divo kernel: mt7925e 0000:c0:00.0: WM Firmware Version: ____000000, Build Time: 20250526153043
Aug 13 12:40:30 divo kernel: mt7925e 0000:c0:00.0 wlp192s0: renamed from wlan0
and my wifi seems to be working fine.
I tried an rpm-ostree rollback but obviously if this is a firmware upgrade issue I doubt that would have any effect.
I’m not sure how to roll back on immutable distros, I’m using classic Workstation. If you have older kernels still available on grub it’s worth trying one of those, I think that the initramfs update for the firmware only affects the initramfs/initrd for the currently installed kernel when the firmware is updated.
(this is all loadable-on-boot firmware, not something “burned” into the devices)
Gotcha that makes sense… theoretically rollback should have taken care of that then because it switches back to the previous ‘deployment’ and in my case that should have been the one before the update.
I don’t really want to mess with the immutable part myself though so I guess I might wait for an update or see if others on Fedora have the same issue.
Mmmm… so I booted up the laptop this morning and this time the bluetooth is back on.
journalctl -k shows that the firmware version is now the updated one:
Aug 14 09:39:23 divo kernel: mt7925e 0000:c0:00.0: ASIC revision: 79250000
Aug 14 09:39:23 divo kernel: mt7925e 0000:c0:00.0: HW/SW Version: 0x8a108a10, Build Time: 20250721232852a
Aug 14 09:39:24 divo kernel: mt7925e 0000:c0:00.0: WM Firmware Version: ____000000, Build Time: 20250721232943
Aug 14 09:39:25 divo kernel: mt7925e 0000:c0:00.0 wlp192s0: renamed from wlan0
So I’m completely puzzled. Did the update not work yesterday and somehow this morning it ‘tried again’ during boot time?
I upgraded fedora 42 today, and my bluetooth is no longer detected. I tried to downgrade bluez and that was the instruction from earlier and that had worked before, but this time around, no luck.
Whats the qual process? Does framework get to give some feedback on bluetooth before any release of fedora XX.
I had this happen to me earlier this week with the update, but for whatever reason a second reboot fixed it for me. After that I had issues with my docking station (CalDigit TS3) where only the displayPort port worked, but nothing else. Another reboot after that seems to have fixed that one.
Neither problem has come back since.
That’s really odd. Does that mean that the bluetooth update first failed, caused the hardware to not be detected (in my boot log it clearly is missing) but then eventually succeeds and re-enables the hardware?
Anyone familiar with Linux device firmware able to chime in and explain how this is possible in a bit more details? I’d love to learn.
I see the same issue on my Framework 13 (AMD Ryzen AI 300 Series) since I applied Fedora 42 updates this morning. I see
Aug 17 14:21:53 framework13-fedora kernel: mt7925e 0000:c0:00.0: ASIC revision: 79250000
Aug 17 14:21:53 framework13-fedora kernel: mt7925e 0000:c0:00.0: HW/SW Version: 0x8a108a10, Build Time: 20250721232852a
Aug 17 14:21:53 framework13-fedora kernel: mt7925e 0000:c0:00.0: WM Firmware Version: ____000000, Build Time: 20250721232943
Aug 17 14:21:54 framework13-fedora kernel: mt7925e 0000:c0:00.0 wlp192s0: renamed from wlan0
in my journal and even after 2 reboots, Bluetooth is not coming back. Would love to know how to fix this.
20250721232943 looks like the correct firmware version after the update (I posted to the Fedora forums a comparison of version numbers before/after the update.
So far it doesn’t seem like there are any explanations or solutions. It started working again after a few reboots for me.
Same here, restart won’t fix, but shut down and power on again will fix the issue.
Thank you! 
I can confirm that a proper shutdown and boot fixes the issue. A simple restart does not.
You’re welcome, glad it helps! I actually learned this from an old Reddit post so let’s thank him together 
Ah yes! it must have been the same for me because it started working the day after because I shut down the laptop overnight.
Thanks for finding this!
Hello, I thought the issue was distro related so I went from workstation to plasma and the bluetooth issues stays. I hope that letting the PC off all night would do the tricks but if you have any other advice I’ll be glad to hear them.
Thank you! I recently ran into this issue. A full reboot fixed my issue.
Another confirmation that a full shutdown and restart worked for me after having this issue rather late on 6 October. I also disconnected all peripherals, just for the vibe of extra safety. Everything is fine now.