Arch Linux

krafczyk

Member

Registered: 2015-09-08

Posts: 37

[SOLVED] Bluetooth can't power on

Bluetooth on my desktop machine won't power on.

When I try through bluetoothctl, I get the error message:

[bluetooth]# power on
Failed to set power on: org.bluez.Error.Busy

I've restarted bluetooth:

sudo systemctl restart bluetooth

Checked rfkill:

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

but this doesn't make a difference.

When I restart bluetooth, I noticed in dmesg, I get the following little error message on hci0:

[  +2.187688] Bluetooth: hci0: Opcode 0x c03 failed: -110

Any ideas what's going on? I remember it worked at some point in the past. Could it be a firmware issue? Could there be a kernel config which needs to be updated which failed to be updated in a kernel update?

More info:

bluetooth controller info through 'bluetoothctl show':

Controller C0:38:96:2F:7D:C0 (public)
	Name: schumann
	Alias: schumann
	Class: 0x00000000
	Powered: no
	Discoverable: yes
	Pairable: yes
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0540
	Discovering: no

Linux kernel info:

uname -a
Linux schumann 5.18.14-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 23 Jul 2022 11:46:17 +0000 x86_64 GNU/Linux

Motherboard info:

# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: MSI
	Product Name: X99A GODLIKE GAMING (MS-7883)
	Version: 1.0
	Serial Number: Default string
	Asset Tag: Default string
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: Default string
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

I couldn't find more detailed information about the actual bluetooth device other than what bluetoothctl says.

Last edited by krafczyk (2022-08-31 14:22:53)

jonno2002

Member

Registered: 2016-11-21

Posts: 688

Re: [SOLVED] Bluetooth can't power on

bluetooth can be a massive pain, i rarely use bluetooth so i leave it off/disabled/rfkilled until i need it, i use these 3 simple scripts, and if there is ever a problem i just run "btrestart" and it usually fixes it.

bton:

#!/bin/bash
sudo rfkill unblock bluetooth
sudo systemctl start bluetooth
sleep 1
bluetoothctl power on
exit 0

btoff:

#!/bin/bash
bluetoothctl power off
sudo systemctl stop bluetooth
sudo rfkill block bluetooth
exit 0

btrestart:

#!/bin/bash
bluetoothctl power off
sudo systemctl stop bluetooth
sudo rfkill block bluetooth
sudo rfkill unblock bluetooth
sudo systemctl start bluetooth
sleep 1
bluetoothctl power on
exit 0

krafczyk

Member

Registered: 2015-09-08

Posts: 37

Re: [SOLVED] Bluetooth can't power on

jonno2002, Appreciate the response.

Unfortunately, that isn't helping me. I still get the mysterious 'org.bluez.Error.Busy' and the dmesg about the opcode failed. Curiously, it's also occuring with 'power off' so that coupled with the opcode is leading me to think my bluetooth module is broken somehow.

bash ~/bin/btrestart
Failed to set power off: org.bluez.Error.Busy
Failed to set power on: org.bluez.Error.Busy

[  +2.334642] Bluetooth: hci0: Opcode 0x c03 failed: -110

Additionally, looking at my kernel log, I see the first time 'hci0' is mentioned has a bunch of messages like this:

Aug 15 12:05:40 schumann bluetoothd[609]: Failed to remove UUID: Authentication Failed (0x05)
Aug 15 12:05:40 schumann kernel: Bluetooth: hci0: Opcode 0x c24 failed: -110
Aug 15 12:05:40 schumann kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Aug 15 12:05:42 schumann bluetoothd[609]: Failed to remove UUID: Authentication Failed (0x05)
Aug 15 12:05:42 schumann kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Aug 15 12:05:42 schumann kernel: Bluetooth: hci0: Opcode 0x c24 failed: -110
Aug 15 12:05:45 schumann kernel: Bluetooth: hci0: command 0x0c24 tx timeout
Aug 15 12:05:45 schumann kernel: Bluetooth: hci0: Opcode 0x c24 failed: -110
Aug 15 12:05:45 schumann bluetoothd[609]: Failed to remove UUID: Authentication Failed (0x05)

So the first time it tries to use bluetooth it has a bunch of these messages.

TKO__GLOBAL__

Member

Registered: 2022-01-18

Posts: 6

Re: [SOLVED] Bluetooth can't power on

I would try first upgrading (since there has been a new kernel version since you first posted), if that doesn't work try the LTS kernel. You can also try downgrading Bluez. Someone had a similar problem here and 5.55.3 worked for them so you could try too.

Also what is the output of

journalctl -xeu bluetooth.service

?

krafczyk

Member

Registered: 2015-09-08

Posts: 37

Re: [SOLVED] Bluetooth can't power on

Its time for me to update my software anyway, I'll do that soon, and try bluez 5.55.3.

because my machine has been up for a while, the output of that journalctl is now hundreds of lines long. Here's a snippet.

```
Aug 26 11:16:11 schumann bluetoothd[942700]: Starting SDP server
Aug 26 11:16:11 schumann bluetoothd[942700]: Bluetooth management interface 1.22 initialized
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/ldac_hq
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/ldac_sq
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/ldac_mq
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/aptx_hd
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/aptx_hd
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/aptx
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/aptx
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/sbc
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/sbc
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Aug 26 11:16:11 schumann bluetoothd[942700]: Endpoint registered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Aug 26 11:16:13 schumann bluetoothd[942700]: Failed to set mode: Authentication Failed (0x05)
Aug 26 11:16:32 schumann bluetoothd[942700]: Terminating
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/ldac_hq
Aug 26 11:16:32 schumann systemd[1]: Stopping Bluetooth service...
░░ Subject: A stop job for unit bluetooth.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/l … temd-devel
░░
░░ A stop job for unit bluetooth.service has begun execution.
░░
░░ The job identifier is 21212.
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/ldac_sq
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/ldac_mq
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/aptx_hd
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/aptx_hd
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/aptx
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/aptx
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/sbc
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/sbc
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Aug 26 11:16:32 schumann bluetoothd[942700]: Endpoint unregistered: sender=:1.51849 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Aug 26 11:16:32 schumann bluetoothd[942700]: Stopping SDP server
Aug 26 11:16:32 schumann bluetoothd[942700]: Exit
Aug 26 11:16:32 schumann systemd[1]: bluetooth.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
```

krafczyk

Member

Registered: 2015-09-08

Posts: 37

Re: [SOLVED] Bluetooth can't power on

Okay, well I updated software, and installed https://aur.archlinux.org/packages/mkinitcpio-firmware To stop the little messages saying WARNING: Possibly missing firmware for module: blah blah which were popping up when pacman was finalizing a software installation.

So now bluetooth is powering on and I can scan, however I have a new problem. discovery returns a single device which my phone also sees, but doesn't see any of the other devices like my headphones or 8bitdo sf30 controller. (I made sure they were in pairing mode). I'll create a separate issue for this. Marking this as solved.