Arch Linux

Vinesh

Member

Registered: 2017-08-01

Posts: 12

Website

[SOLVED] bluetoothctl : No default controlller available

bluetoothctl used to work perfectly fine and it stopped working yesterday. It shows no default controller available.

I tried online solutions like sudo bluetoothctl, sudo modprobe -r btusb, sudo modprobe btusb, cold restart and none of them worked.

Here are outputs of some commands:

rfkill list

[vinesh@lx ~]$ rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

systemctl status bluetooth 

● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2019-07-07 14:24:50 IST; 5h 14min left
     Docs: man:bluetoothd(8)
 Main PID: 390 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4537)
   Memory: 2.7M
   CGroup: /system.slice/bluetooth.service
           └─390 /usr/lib/bluetooth/bluetoothd

Jul 07 14:24:49 lx systemd[1]: Starting Bluetooth service...
Jul 07 14:24:50 lx bluetoothd[390]: Bluetooth daemon 5.50
Jul 07 14:24:50 lx systemd[1]: Started Bluetooth service.
Jul 07 14:24:50 lx bluetoothd[390]: Starting SDP server
Jul 07 14:24:50 lx bluetoothd[390]: Bluetooth management interface 1.14 initialized

dmesg | egrep -i 'blue|firm'

[vinesh@lx ~]$ dmesg | egrep -i 'blue|firm'
[    0.033369] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)
[    0.283349] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    9.828793] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   10.529394] Bluetooth: Core ver 2.22
[   10.529423] Bluetooth: HCI device and connection manager initialized
[   10.529427] Bluetooth: HCI socket layer initialized
[   10.529429] Bluetooth: L2CAP socket layer initialized
[   10.529437] Bluetooth: SCO socket layer initialized
[   11.152968] Bluetooth: hci0: BCM: chip id 70
[   11.153965] Bluetooth: hci0: BCM: features 0x06
[   11.169949] Bluetooth: hci0: BCM43142A
[   11.173971] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
[   13.381187] Bluetooth: hci0: command 0xfc4c tx timeout
[   15.129327] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   15.129329] Bluetooth: BNEP filters: protocol multicast
[   15.129332] Bluetooth: BNEP socket layer initialized
[   21.781317] Bluetooth: hci0: BCM: Patch command fc4c failed (-110)
[   23.861307] Bluetooth: hci0: command 0x0c03 tx timeout
[   32.021308] Bluetooth: hci0: BCM: Reset failed (-110)

lspci

[vinesh@lx ~]$ lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3)
00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3)
00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3)
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
06:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller 

lsusb

[vinesh@lx ~]$ lsusb
Bus 001 Device 006: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 005: ID 0a5c:21d7 Broadcom Corp. BCM43142 Bluetooth 4.0
Bus 001 Device 004: ID 0c45:6a04 Microdia
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

journalctl -b | grep Bluetooth

[vinesh@lx ~]$  journalctl -b | grep Bluetooth
Jul 07 14:24:46 lx kernel: Bluetooth: Core ver 2.22
Jul 07 14:24:46 lx kernel: Bluetooth: HCI device and connection manager initialized
Jul 07 14:24:46 lx kernel: Bluetooth: HCI socket layer initialized
Jul 07 14:24:46 lx kernel: Bluetooth: L2CAP socket layer initialized
Jul 07 14:24:46 lx kernel: Bluetooth: SCO socket layer initialized
Jul 07 14:24:46 lx kernel: Bluetooth: hci0: BCM: chip id 70
Jul 07 14:24:46 lx kernel: Bluetooth: hci0: BCM: features 0x06
Jul 07 14:24:46 lx kernel: Bluetooth: hci0: BCM43142A
Jul 07 14:24:46 lx kernel: Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
Jul 07 14:24:49 lx kernel: Bluetooth: hci0: command 0xfc4c tx timeout
Jul 07 14:24:49 lx systemd[1]: Starting Bluetooth service...
Jul 07 14:24:50 lx bluetoothd[390]: Bluetooth daemon 5.50
Jul 07 14:24:50 lx systemd[1]: Started Bluetooth service.
Jul 07 14:24:50 lx systemd[1]: Reached target Bluetooth.
Jul 07 14:24:50 lx bluetoothd[390]: Bluetooth management interface 1.14 initialized
Jul 07 14:24:50 lx kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jul 07 14:24:50 lx kernel: Bluetooth: BNEP filters: protocol multicast
Jul 07 14:24:50 lx kernel: Bluetooth: BNEP socket layer initialized
Jul 07 14:24:57 lx kernel: Bluetooth: hci0: BCM: Patch command fc4c failed (-110)
Jul 07 14:24:59 lx kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Jul 07 14:25:07 lx kernel: Bluetooth: hci0: BCM: Reset failed (-110)

uname -r

4.19.57-1-lts

I decided to try with depreciated tools bluez-utils-compat.

Last edited by Vinesh (2019-07-07 14:31:12)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,824

Re: [SOLVED] bluetoothctl : No default controlller available

There is an issue with the current stable bluetooth stack: see https://bbs.archlinux.org/viewtopic.php?id=247442 as well

Try on linux 5.1.16 or an older 4.19.55-lts kernel.

Vinesh

Member

Registered: 2017-08-01

Posts: 12

Website

Re: [SOLVED] bluetoothctl : No default controlller available

I got this fixed just now, I took a backup of /lib/firmware/brcm and deleted everything inside and then did a cold restart and it detected my controller. Later I download a hcd file on github and replaced back brcm with new hcd.

*Cold restart is a must, I replaced hcd many times it didnt work but only after cold restart it worked.

What I think caused this is I renamed original hcd file in brcm to BCM43142A0-0a5c-21d7.hcd, yes it worked but temporarily.

Solution: Replace hcd file and cold restart

Last edited by Vinesh (2019-07-07 14:35:00)