Bug 2372880 - MT7925 Bluetooth functionality lost after firmware update from 20250311 to 20250509
Summary: MT7925 Bluetooth functionality lost after firmware update from 20250311 to 20...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 42
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-15 04:22 UTC by Lachlan Macnish
Modified: 2025-06-16 14:43 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lachlan Macnish 2025-06-15 04:22:18 UTC
After a system update on June 14, 2025, the Bluetooth functionality of the MediaTek MT7925 wireless card stopped working. The update included mt7xxx-firmware package upgrade from version 20250311-1.fc42 to 20250509-1.fc42.

The MT7925 is a combo WiFi/Bluetooth card, and while WiFi continues to work, Bluetooth is completely non-functional.

**System Information**:
- Distribution: Fedora Linux 42 (KDE Plasma Desktop Edition)
- Kernel: 6.14.9-300.fc42.x86_64
- Hardware: ASUS Zenbook S 16 UM5606WA_UM5606WA
- Wireless Card: MEDIATEK Corp. Device 7925 (MT7925)
- Subsystem: AzureWave Device 6370
- Driver: mt7925e

**Hardware Details**:
```
c3:00.0 Network controller: MEDIATEK Corp. Device 7925
    Subsystem: AzureWave Device 6370
    Kernel driver in use: mt7925e
    Kernel modules: mt7925e
```

**Firmware Versions**:
- Working (initial install): mt7xxx-firmware-20250311-1.fc42.noarch
- Problematic: mt7xxx-firmware-20250509-1.fc42.noarch
- Current (downgraded, still broken): mt7xxx-firmware-20250311-1.fc42.noarch

**Timeline**:
1. Initial Fedora 42 installation: Both WiFi and Bluetooth working
2. June 14, 2025: System update including firmware dated 20250509
3. After update: Bluetooth stopped working, WiFi still functional
4. June 15, 2025: Downgraded firmware to 20250311 - WiFi still works, Bluetooth still broken

**Current Status**:
- WiFi: Working (connected to network)
- Bluetooth: Not working (no controller detected)
- Bluetooth service: Running but reports "No default controller available"

**Expected Behavior**:
Both WiFi and Bluetooth should function as they did on initial installation.

**Actual Behavior**:
Bluetooth completely non-functional after firmware update. Downgrading firmware did not restore Bluetooth functionality.

**Reproduction Steps**:
1. Install Fedora 42 on system with MediaTek MT7925 wireless card
2. Verify both WiFi and Bluetooth are working
3. Update system to include mt7xxx-firmware-20250509-1.fc42
4. Observe that Bluetooth stops working

**Additional Information**:
- This appears to be a firmware regression specific to the Bluetooth component of the MT7925
- The issue may also involve other system components that interact with the firmware
- Multiple users may be affected as this is a common wireless card in ASUS laptops

**Commands to reproduce/verify**:
```bash
# Check hardware
lspci | grep -i network

# Check Bluetooth status
systemctl status bluetooth
bluetoothctl show

# Check firmware version
rpm -qa | grep mt7xxx-firmware

# Check kernel messages
sudo dmesg | grep -i mt79
sudo dmesg | grep -i bluetooth
```

NB: This has been generated by Warp Terminal following its troubleshooting of the issue. However, this has been manually reviewed and refined to ensure correctness.

Reproducible: Always

Comment 1 Lachlan Macnish 2025-06-15 06:02:23 UTC
On returning to Windows 11 I have also found that my Bluetooth device is non-existent. The situation is the same. I can see the WiFi device of the same MediaTek MT7925 in Windows. But there is no Bluetooth device at all. And the Bluetooth button in the control centre is no longer present.

I would still be looking to the Jun 14 2025 update in Fedora as triggering the issue, as I'm not aware of any other change, but I don't understand enough to say whether this may have triggered a broader issue spanning outside of Fedora.

I don't believe there have been any UEFI changes since the initial Fedora install to change the boot order so that Fedora was and then wasn't the default. But the Bluetooth device worked both sides of any changes. 

Bluetooth is enabled in UEFI.

Driver date for "MediaTek Wi-Fi 7 MT7952 Wireless LAN Card" shows Driver Date: Tue 18/3/24, Driver Version: 5.5.0.3548. It has auto-update enablded in MyASUS, so it would not have been out of date and only recently updated, so no obvious change Windows-side.

Comment 2 Lachlan Macnish 2025-06-15 06:41:07 UTC
I performed a device firmware reset (shutdown and then hold Power for 40 seconds for Asus Zenbook S 16) and then on boot the Bluetooth device is once again recognised in both Windows 11 and Fedora. I will perform mtxxx-firmware update in Software Center again to see if that breaks the Bluetooth device again.

Comment 3 Lachlan Macnish 2025-06-15 06:50:03 UTC
Installed mt7xxx-firmware (installe via Software Center auto-updated). Following restart to update, update automatically installed, restart and boot, Bluetooth remains functional in Fedora.

Comment 4 Lachlan Macnish 2025-06-16 14:43:01 UTC
Seems to be a strong correlation to the MT7xxx-firmware package update now. I was using Windows 11 for some time with no issue. Then decided to boot back to Fedora 42, and on Bluetooth was present. Keyboard did not pair. So restarted and booted back to Windows 11, and again no Bluetooth AT ALL (the entire control centre Bluetooth button is gone, as well as no Bluetooth device in Device Manager, now present in Windows 11). So there seems to be a major issue with MT7xxx-firmware that only presents after 1) update; 2)restart/install, and; 3) restart/boot again. And it's not just impacting Fed 42. Impacting the entire device for all host OS.


Note You need to log in before you can comment on or make changes to this bug.