You are not logged in.
After I updated to 7.0.7-arch1-1 form 7.0.5-arch1-1 bluetooth just stopped working.
In rfkill hci0: Bluetooth is soft blocked
This is the journalctl after i restart bluetooth.service
May 15 13:06:21 spaceship systemd[1]: Stopping Bluetooth service...
May 15 13:06:21 spaceship bluetoothd[5431]: Stopping SDP server
May 15 13:06:21 spaceship bluetoothd[5431]: Exit
May 15 13:06:21 spaceship systemd[1]: bluetooth.service: Deactivated successfully.
May 15 13:06:21 spaceship systemd[1]: Stopped Bluetooth service.
May 15 13:06:21 spaceship systemd[1]: Starting Bluetooth service...
May 15 13:06:21 spaceship blueman-applet[1828]: blueman-applet 13.06.21 WARNING DiscvManager:122 update_menuitems: warning: Adapter is None
May 15 13:06:21 spaceship bluetoothd[11799]: Bluetooth daemon 5.86
May 15 13:06:21 spaceship systemd[1]: Started Bluetooth service.
May 15 13:06:21 spaceship bluetoothd[11799]: Starting SDP server
May 15 13:06:21 spaceship bluetoothd[11799]: Bluetooth management interface 1.23 initialized
May 15 13:06:21 spaceship systemd[1]: Starting Hostname Service...
May 15 13:06:21 spaceship sudo[11791]: pam_unix(sudo:session): session closed for user root
May 15 13:06:21 spaceship blueman-applet[1828]: blueman-applet 13.06.21 WARNING DiscvManager:122 update_menuitems: warning: Adapter is Nonebluetoothctl list returns nothing
bluetoothctl devices returns:
No default controller availablemy bluetooth adapter is
Bus 001 Device 003: ID 0489:e0e2 Foxconn / Hon Hai Wireless_DeviceI have installed broadcom-bt-firmware but it didn't help
Offline
Same with me after updating from 6.18.29 LTS to 6.18.30 LTS, I too have a Mediatek-based integrated Bluetooth adapter connected via USB (internally), reported as a "Foxconn / Hon Hai Wireless_Device" by lsusb. Rolling back the kernel fixes the issue. I suspect that the modifications done to the mt76 driver are the culprit, if you look in the changelog of 6.18.30 there are several small modifications to mt76, which I guess are a backport of whatever they did on 7.0.xnope mt76 is the wireless driver not the bluetooth driver. the driver is probably btmtk and there are changes in that too
I love how 16 years I just accepted that Linux bugfix updates tend to break stuff more than major releases
Last edited by krnlpk (2026-05-15 13:24:45)
Offline
Ok someone reported the regression and indeed it is btmtk
Just roll back to the older kernel, pin it and wait for a patch
Offline
Heads Up: There's been an update (Linux 7.0.7-arch2-1) but issue still persists.
Offline
The patch to fix this is applied on 7.0.8-arch1 which is in testing currently: https://github.com/archlinux/linux/rele … .0.8-arch1
Last edited by V1del (2026-05-15 17:52:52)
Offline
So in the meantime I'm going to get the cable for my headphone ... Thank you for the information.
Offline
The patch to fix this is applied on 7.0.8-arch1 which is in testing currently: https://github.com/archlinux/linux/rele … .0.8-arch1
Any idea if this has been backported to the LTS kernel too?
Offline
The patch worked for LTS
I was on Linux LTS v6.18.26. Upgrading to v6.18.30 broke my bluetooth adapter. My Adapter is MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
For now I have manually applied the patch and I'm booting into Arch via custom kernel.
Offline
Any idea if this has been backported to the LTS kernel too?
Doesn't look like it: https://gitlab.archlinux.org/archlinux/ … /linux-lts
Offline
krnlpk wrote:Any idea if this has been backported to the LTS kernel too?
Doesn't look like it: https://gitlab.archlinux.org/archlinux/ … /linux-lts
Dang, I suspect they won't do it for LTS because Arch doesn't really have its own fork with patches for it. No fuss, I'll just --ignore linux-lts for a while, hopefully upstream will patch the regression properly in .32
Offline