Project

General

Profile

The Bluetooth Saga

anarcobuda - 27 days ago -

I've been troubleshooting for a while Bluetooth issues that my laptop has, and I've managed to have some insights about it, however, at the moment I'm just stumped.

Firstly, my on-board bluetooth controller wasn't being recognized, so I searched and found that it had something to do with rfkill.

So I ran rfkill unblock all. Now, when I run rfkill, I get:

ID TYPE DEVICE SOFT HARD
0 wlan ideapad_wlan unblocked unblocked
1 bluetooth ideapad_bluetooth unblocked unblocked
2 wwan ideapad_3g unblocked unblocked

And, for a while, that solution worked. However, for some reason, it stopped working once again. This is what I get when I run systemctl status bluetooth:

● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2020-01-27 08:52:18 -03; 10min ago
Docs: man:bluetoothd(8)
Main PID: 493 (bluetoothd)
Tasks: 1 (limit: 9446)
Memory: 3.5M
CGroup: /system.slice/bluetooth.service
└─493 /usr/lib/bluetooth/bluetoothd

Jan 27 08:52:30 marx-pc bluetoothd[493]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc
Jan 27 08:52:54 marx-pc bluetoothd[493]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink/sbc
Jan 27 08:52:54 marx-pc bluetoothd[493]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource/sbc
Jan 27 08:52:54 marx-pc bluetoothd[493]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Jan 27 08:52:54 marx-pc bluetoothd[493]: RFCOMM server failed for :1.83/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb: rfcomm_bind: Address already in use (98)
Jan 27 08:53:05 marx-pc bluetoothd[493]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc
Jan 27 08:53:05 marx-pc bluetoothd[493]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc
Jan 27 08:54:00 marx-pc bluetoothd[493]: Failed to set mode: Failed (0x03)
Jan 27 08:54:00 marx-pc bluetoothd[493]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSink/sbc
Jan 27 08:54:00 marx-pc bluetoothd[493]: Endpoint unregistered: sender=:1.83 path=/MediaEndpoint/A2DPSource/sbc

It shows some errors, but I have no idea what they mean. Sometimes bluetooth works, sometimes it don't, and I see no clear pattern as to why. Sometimes my controller appear in bluetoothctl list of controllers, sometimes it don't. When it does, sometimes I can successfully power on, sometimes I can't.

Running dmesg | grep -i blue gives me this output:

[ 11.736755] Bluetooth: Core ver 2.22
[ 11.736796] Bluetooth: HCI device and connection manager initialized
[ 11.736800] Bluetooth: HCI socket layer initialized
[ 11.736803] Bluetooth: L2CAP socket layer initialized
[ 11.736806] Bluetooth: SCO socket layer initialized
[ 11.919547] Bluetooth: hci0: read Intel version: 370710018002030d00
[ 11.919598] Bluetooth: hci0: failed to open Intel firmware file: /*(DEBLOBBED)*/ (-2)
[ 11.919606] Bluetooth: hci0: failed to open default fw file: /*(DEBLOBBED)*/
[ 16.243572] Bluetooth: hci0: command 0xfc3f tx timeout
[ 19.230731] Bluetooth: hci0: setting interface failed (110)
[ 24.350235] Bluetooth: hci0: turning off Intel device LED failed
[ 110.184935] audit: type=1130 audit(1580127491.631:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 110.220285] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 110.220287] Bluetooth: BNEP filters: protocol multicast
[ 110.220292] Bluetooth: BNEP socket layer initialized
[ 110.478854] Bluetooth: RFCOMM TTY layer initialized
[ 110.478860] Bluetooth: RFCOMM socket layer initialized
[ 110.478865] Bluetooth: RFCOMM ver 1.11

Which hints at this hci0: failed to open Intel firmware file: /*(DEBLOBBED)*/ (-2). Any ideas?


Replies (2)

The Bluetooth Saga - bill-auger - 21 days ago -

i dont know much about bluetooth things, except that that often
do not work with libre drivers - even if the same card has
working wifi, often the bluetooth will not work

RE: The Bluetooth Saga - anarcobuda - 5 days ago -

I've recently noticed how sometimes I get this error for both the internal bluetooth device and the external one which I connect through USB: org.freedesktop.DBus.Error.NoReply

The only thing I tried to do so far is systemctl restart dbus, and that usually restarts the whole system GUI, but it doesn't change a thing on the bluetooth issue. As far as my knowledge goes, this laptop seems to show signs of intelligence, and it apparently doesn't like working so it goes on strike for a few hours. Then it works again.

    (1-2/2)