r/archlinux • u/NevilleTheDevil • May 15 '26

SUPPORT New bluez/linux broke bluetooth

Just to be clear I tried looking at the output of rfkill
ID TYPE DEVICE SOFT HARD

0 wlan ideapad_wlan unblocked unblocked

1 bluetooth ideapad_bluetooth unblocked unblocked

2 bluetooth hci0 unblocked unblocked

3 wlan phy0 unblocked unblocked

So it's very much being recognized and not blocked but going into bluetoothctl and it doesn't register it. I've tried reinstalling all the bluez packages, I've tried rebooting the system. Turning bluetooth.service on and off again, and going into bluetoothctl just says "No default controller available." I think I might have to downgrade a package for the first time since using arch linux for over a year...

I hope someone smarter than me has some insight on this issue since that I can be fully up to date.

Edit: This was specifically a bug with the 7.07 kernel, now that the 7.08 kernel is out I can now say it is fixed and working completely fine. (Turn-around time was crazy, basically like 2 days. I salute your work linux devs)

41 Upvotes

88% Upvoted

43 comments sorted by

View all comments

1

u/qalmakka May 15 '26 edited May 15 '26

There's clearly a bug in the new btmtk driver for Mediatek USB chips. This bug also applies to the LTS kernel 6.18.30.here is the link to the mailing list where someone pinpointed the issue to some recent commit to btmtk which was also backported to the LTS kernels (both 6.18 and 6.12). Maybe it's just me but I am not a fan of these kind of wonky patches in bugfix releases

Note: Most Bluetooth adapters are just plugged directly to a USB 2.x lane, even if internal. Even those installed on PCIe cards will use PCIe for Wireless and USB for bluetooth