I am seeing questions like https://askubuntu.com/questions/1554208/ubuntu-25-04-mediatek-foxconn-mt7925e-bluetooth-not-functional but I see that device in a commit ~ubuntu-kernel/ubuntu/+source/linux/+git/plucky - [no description]
Does anyone know how this can happen?
1 Like
Maybe missing firmware? Impossible to tell without logs.
What logs do you want? I sent a comment to the user from the askubuntu question and have another user trying Ubuntu 25.04 from ISO on USB. I will try to get the users involved to file bug reports against linux. Some info from the one user is at https://forums.linuxmint.com/viewtopic.php?p=2677695#p2677695 while running Ubuntu 25.04 ISO
Sometimes bluetooth can have issues when there’s wifi adapter near by cranking out power. I had that issue. Loading from live usb and it works fine, then with wifi connected it keeps dropping connection. But also with select devices, for some odd reason it didn’t for Apple Magic Keyboard. I guess it’s in the name…Magic 
This is nothing like that. The btusb kernel module isn’t even trying to load for this device so it doesn’t even attempt to find firmware or anything and btusb should load for anything that even matches some of the generic entries in that source code and what makes this even more weird is that this device ID 0489:e111 seems to be in the 6.14 source code.
I did some further searching and it seems the 3 users I know of that have this issue are using Lenovo Legion 5 laptops with fairly recent BIOS
Similar issue with kernel 6.14 + MediaTek MT7925
the Bluetooth service is skipped because /sys/class/bluetooth does not exist, and dmesg only shows the core stack — no btusb/btmtk device lines at all. That means the controller never enumerated, so bluetoothctl blocks waiting on D-Bus and appears to hang. This matches a known 6.14 + MediaTek MT7925 trend where the USB side of the combo card doesn’t show up, often after firmware/kernel updates or certain BIOS setting
What is weird is it was working fine for some time.
Is this also a Lenovo? What result from terminal for lsusb
Asus Z Flow
~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0bda:636e Realtek Semiconductor Corp. ASUS 5M webcam
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 006: ID 0b05:1a30 ASUSTek Computer, Inc. GZ302EA-Keyboard
Bus 003 Device 007: ID 0b05:18c6 ASUSTek Computer, Inc. N-KEY Device
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Likely not the same issue as your bluetooth isn’t shown in lsusb
It is either the same or very similar issue. The Bluetooth part for the (MediaTek MT7925 a dual component wifi+bluetooth) is/(should be) detected via USB but when kernel loads it gives errors on that port and finally fails. As a result there is no detected bluetooth device in lsusb.
The Lenovo issue is that the btusb driver doesn’t attach to the device, the device is listed in lsusb and even inxi results show it with no driver like
Bluetooth:
Device-1: Foxconn / Hon Hai Wireless_Device driver: N/A type: USB rev: 2.1 speed: 480 Mb/s
lanes: 1 bus-ID: 1-5:4 chip-ID: 0489:e111 class-ID: e001 serial: <filter>```Actually their bug report is Bug #2128661 “🩸 regression on 20250317.git1d4c88ee-0ubuntu1.9” : Bugs : linux-firmware package : Ubuntu
Seems a fix is at GitHub - LuanAdemi/mediatek7925e-bluetooth-fix: A fix for the 0489:e111 wireless card's bluetooth functionality for GNOME (e.g. Fedora on a Lenovo IdeaPad Pro 5 14AKP10)
Not sure why it is needed
1 Like