Manjaro sway bluetooth no default controller

Which Linux distro are you using?
Manjaro Sway
Which release version?
latest

Which kernel are you using?
I tried 6.3.17, 6.12.10, 6.11.9 (on 6.11.9 after restart bluetooth start working but then system freezed and I had to reboot it - then it stopped working again)
Also 6.12.19 linux-lts

Which BIOS version are you using?
probably latest

Which Framework Laptop 16 model are you using?
AMD Ryzen 9 7940HS w/ Radeon 780M Graphics

So the problem is that I can’t access bluetooth controller, bluetoothctl just says that there is no controllers at all

rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sat 2025-03-22 22:41:07 +04; 1s ago
 Invocation: caade77cf5314987bf8f79dce2836c2c
       Docs: man:bluetoothd(8)
   Main PID: 8446 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 37473)
     Memory: 652K (peak: 2.2M)
        CPU: 23ms
     CGroup: /system.slice/bluetooth.service
             └─8446 /usr/lib/bluetooth/bluetoothdMar 22 22:41:07 dkeysil-fw systemd[1]: Starting Bluetooth service...
Mar 22 22:41:07 dkeysil-fw bluetoothd[8446]: Bluetooth daemon 5.80
Mar 22 22:41:07 dkeysil-fw systemd[1]: Started Bluetooth service.
Mar 22 22:41:07 dkeysil-fw bluetoothd[8446]: Starting SDP server
Mar 22 22:41:07 dkeysil-fw bluetoothd[8446]: Bluetooth management interface 1.23 initialized

sudo dmesg | grep Bluetooth
[   13.031898] Bluetooth: Core ver 2.22
[   13.031938] Bluetooth: HCI device and connection manager initialized
[   13.031946] Bluetooth: HCI socket layer initialized
[   13.031950] Bluetooth: L2CAP socket layer initialized
[   13.031955] Bluetooth: SCO socket layer initialized
[   13.176541] Bluetooth: hci0: Failed to get device id (-108)
[   13.176551] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[   13.436828] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   13.436832] Bluetooth: BNEP filters: protocol multicast
[   13.436836] Bluetooth: BNEP socket layer initializedlsmod | grep btusb
btusb                  81920  0
btrtl                  32768  1 btusb
btintel                69632  1 btusb
btbcm                  24576  1 btusb
btmtk                  32768  1 btusb
bluetooth            1097728  15 btrtl,btmtk,btintel,btbcm,bnep,btusb

The strangest part is Bluetooth: hci0: Failed to get device id (-108) but I wasn’t able to find a solution in google

1 Like

update: I reconnected Wi-Fi module and it started working. For 2 days.

Then laptop just freezed once again and after restart - no default controller for bluetooth.

Feels like something is wrong with hardware, like it’s glitching because of the voltage or something.

I tried to reconnect Wi-Fi module once again but it didn’t work out.

1 Like

I’m running into the same issue on Arch Linux with my Framework Desktop.
Have you been able to work around the issue @Dmitry_Kisel?

Edit: A simple reboot fixed this.

Ran into the same issue on my Arch. BT did work but after a kernel update, it stopped working. I though this might work better with an officially supported distro so I move to Fedora. After install, BT worked but after a system update, I’m now back to no bluetooth working :joy:

Guess I can move back to my trusted Arch again, knowing that bluetooth doesn’t work on Fedora either…

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.