You are not logged in.

Pages: 1

#1 2020-02-08 10:28:20

woodape
Member
Registered: 2015-03-25
Posts: 159

Bluetooth detected by rfkill, but not by bluetoothctl

I have a Bluetooth dongle has stopped working on my desktop. I don't often use bluetooth on my desktop so I really don't know if a particular upgrade in the last month or so caused the issue. If I plug the dongle into my laptop, also a fully upgraded Arch system, it works fine. Below are some relevant commands on my desktop. Any ideas to get the device detected  by bluetoothctl?

bluetoothctl devices:

No default controller available

lsusb:

...
BUS 002 Device 002: ID 0a5c:21ec Broadcom Corp. BCM20702A0

rfkill list:

0: hci0: Bluetooth
          Soft blocked: no
          Hard blocked: no
...

usb-devices:

T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0a5c ProdID=21ec Rev=01.12
S:  Manufacturer=Broadcom Corp
S:  Product=BCM20702A0
S:  SerialNumber=0019860025AC
C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I:  If#=0x1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I:  If#=0x2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=btusb
I:  If#=0x3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

dmesg | grep Bluetooth:

[    3.202839] Bluetooth: Core ver 2.22
[    3.202855] Bluetooth: HCI device and connection manager initialized
[    3.202859] Bluetooth: HCI socket layer initialized
[    3.202861] Bluetooth: L2CAP socket layer initialized
[    3.202866] Bluetooth: SCO socket layer initialized
[    3.417494] Bluetooth: hci0: BCM: chip id 63
[    3.418489] Bluetooth: hci0: BCM: features 0x07
[    3.434513] Bluetooth: hci0: Broadcom Bluetooth Device
[    3.435488] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1460
[    3.790395] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.790396] Bluetooth: BNEP filters: protocol multicast
[    3.790400] Bluetooth: BNEP socket layer initialized
[    4.174579] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1460
[    4.190579] Bluetooth: hci0: Broadcom Bluetooth Device

pacman -Qs bluetooth

local/bcm20702a1-firmware 1201710-8
    Broadcom bluetooth firmware for BCM20702A1 based devices.
local/blueman 2.1.1-2
    GTK+ Bluetooth Manager
local/bluez 5.52-2
    Daemons for the bluetooth protocol stack
local/bluez-libs 5.52-2
    Deprecated libraries for the bluetooth protocol stack
local/bluez-tools 0.2.0-4
    A set of tools to manage Bluetooth devices for Linux
local/bluez-utils 5.52-2
    Development and debugging utilities for the bluetooth protocol stack
local/gnome-bluetooth 3.34.0+1+g96295afd-1
    The GNOME Bluetooth Subsystem
local/hidapi 0.9.0-1
    Simple library for communicating with USB and Bluetooth HID devices
local/pulseaudio-bluetooth 13.0-3
    Bluetooth support for PulseAudio
local/qt5-connectivity 5.14.1-1 (qt qt5)
    Provides access to Bluetooth hardware
local/sbc 1.4-1
    Bluetooth Subband Codec (SBC) library

systemctl status bluetooth

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Sat 2020-02-08 11:57:41 SAST; 25min ago
       Docs: man:bluetoothd(8)
   Main PID: 557 (bluetoothd)
      Tasks: 1 (limit: 38449)
     Memory: 3.6M
     CGroup: /system.slice/bluetooth.service
             └─557 /usr/lib/bluetooth/bluetoothd

Feb 08 11:57:41 kiwi systemd[1]: Starting Bluetooth service...
Feb 08 11:57:41 kiwi bluetoothd[557]: Bluetooth daemon 5.52
Feb 08 11:57:41 kiwi systemd[1]: Started Bluetooth service.
Feb 08 11:57:41 kiwi bluetoothd[557]: Starting SDP server
Feb 08 11:57:41 kiwi bluetoothd[557]: Bluetooth management interface 1.14 initialized

Offline

#2 2020-02-09 08:20:41

sredna
Member
Registered: 2008-11-29
Posts: 51

Re: Bluetooth detected by rfkill, but not by bluetoothctl

My bluetooth controller completely dissapeared after last update.

[anders@elias anders]$ dmesg|grep bluetooth
[ 1230.036903] audit: type=1130 audit(1581234823.729:82): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1425.171536] audit: type=1131 audit(1581235018.859:90): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1425.185701] audit: type=1130 audit(1581235018.879:93): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1583.382048] audit: type=1131 audit(1581235177.076:107): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1583.397500] audit: type=1130 audit(1581235177.089:108): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1648.871926] audit: type=1131 audit(1581235242.566:150): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1648.898574] audit: type=1130 audit(1581235242.592:153): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1671.726963] audit: type=1131 audit(1581235265.419:163): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1671.745584] audit: type=1130 audit(1581235265.439:166): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

anders@elias anders]$ dmesg|grep usb
[    0.574295] usbcore: registered new interface driver usbfs
[    0.574295] usbcore: registered new interface driver hub
[    0.574295] usbcore: registered new device driver usb
[    0.785852] usbcore: registered new interface driver usbserial_generic
[    0.785855] usbserial: USB Serial support registered for generic
[    0.945001] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.05
[    0.945002] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.945004] usb usb1: Product: xHCI Host Controller
[    0.945005] usb usb1: Manufacturer: Linux 5.5.2-arch1-1 xhci-hcd
[    0.945006] usb usb1: SerialNumber: 0000:00:14.0
[    0.947444] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.05
[    0.947446] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.947448] usb usb2: Product: xHCI Host Controller
[    0.947449] usb usb2: Manufacturer: Linux 5.5.2-arch1-1 xhci-hcd
[    0.947451] usb usb2: SerialNumber: 0000:00:14.0
[    0.966444] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.05
[    0.966446] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.966448] usb usb3: Product: EHCI Host Controller
[    0.966450] usb usb3: Manufacturer: Linux 5.5.2-arch1-1 ehci_hcd
[    0.966452] usb usb3: SerialNumber: 0000:00:1d.0
[    1.278148] usb 1-4: new high-speed USB device number 2 using xhci_hcd
[    1.298149] usb 3-1: new high-speed USB device number 2 using ehci-pci
[    1.321979] usb 3-1: New USB device found, idVendor=8087, idProduct=8000, bcdDevice= 0.04
[    1.321992] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.354357] usb 1-4: New USB device found, idVendor=1bcf, idProduct=28a0, bcdDevice=35.13
[    1.354359] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.354360] usb 1-4: Product: Laptop_Integrated_Webcam_HD
[    1.354361] usb 1-4: Manufacturer: CN07YYTT72487394B10YA00
[    1.421557] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[    1.439265] usb 2-2: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=11.00
[    1.439268] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.439269] usb 2-2: Product: Flash Drive FIT
[    1.439270] usb 2-2: Manufacturer: Samsung
[    1.439271] usb 2-2: SerialNumber: 0374819030008708
[    1.573986] usb-storage 2-2:1.0: USB Mass Storage device detected
[    1.574105] scsi host3: usb-storage 2-2:1.0
[    1.574170] usbcore: registered new interface driver usb-storage
[    1.575399] usbcore: registered new interface driver uas
[    1.601491] usb 3-1.3: new full-speed USB device number 3 using ehci-pci
[    3.143269] input: Laptop_Integrated_Webcam_HD: In as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/input/input8
[    3.143703] usbcore: registered new interface driver uvcvideo
[   16.968131] usb 3-1.3: device descriptor read/64, error -110
[   32.541495] usb 3-1.3: device descriptor read/64, error -110
[   32.721465] usb 3-1.3: new full-speed USB device number 4 using ehci-pci
[   48.114795] usb 3-1.3: device descriptor read/64, error -110
[   63.688126] usb 3-1.3: device descriptor read/64, error -110
[   63.794928] usb 3-1-port3: attempt power cycle
[   64.388125] usb 3-1.3: new full-speed USB device number 5 using ehci-pci
[   70.001433] usb 3-1.3: device not accepting address 5, error -32
[   70.074792] usb 3-1.3: new full-speed USB device number 6 using ehci-pci
[   75.544833] usb 3-1.3: device not accepting address 6, error -32
[   75.545102] usb 3-1-port3: unable to enumerate USB device
[   75.618125] usb 3-1.5: new full-speed USB device number 7 using ehci-pci
[   75.726357] usb 3-1.5: config 0 has an invalid interface number: 3 but max is 2
[   75.726359] usb 3-1.5: config 0 has no interface number 2
[   75.740984] usb 3-1.5: New USB device found, idVendor=0a5c, idProduct=5801, bcdDevice= 1.01
[   75.740986] usb 3-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   75.740988] usb 3-1.5: Product: 5880
[   75.740989] usb 3-1.5: Manufacturer: Broadcom Corp
[   75.740990] usb 3-1.5: SerialNumber: 0123456789ABCD
[   75.741092] usb 3-1.5: config 0 descriptor??
[ 1193.630997] usbcore: registered new interface driver btusb

Offline

#3 2020-02-09 09:05:15

woodape
Member
Registered: 2015-03-25
Posts: 159

Re: Bluetooth detected by rfkill, but not by bluetoothctl

sredna, yes it looks like there have been many new bluetooth issues with the latest kernel. It doesn't look like your issue relates to mine though, so perhaps you should start a new thread.

Last edited by woodape (2020-02-09 09:06:19)

Offline

#4 2024-10-10 22:35:40

anarcobafif
Member
Registered: 2022-12-15
Posts: 9

Re: Bluetooth detected by rfkill, but not by bluetoothctl

four years later, I have the same problem.

usbview:

BT DONGLE10
Speed: 12Mb/s (full)
Bus:   1
Address:   2
USB Version:  2.00
Device Class: e0
Device Subclass: 01
Device Protocol: 01
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 0a12
Product Id: 0001
Revision Number: 88.91

Config Number: 1
	Number of Interfaces: 2
	Attributes: e0
	MaxPower Needed: 100mA

	Interface Number: 0
		Name: btusb
		Alternate Number: 0
		Class: e0
		Sub Class: 01
		Protocol: 01
		Number of Endpoints: 3

			Endpoint Address: 02
			Direction: out
			Attribute: 2
			Type: Bulk
			Max Packet Size: 64
			Interval: 0ms

			Endpoint Address: 81
			Direction: in
			Attribute: 3
			Type: Interrupt
			Max Packet Size: 16
			Interval: 1ms

			Endpoint Address: 82
			Direction: in
			Attribute: 2
			Type: Bulk
			Max Packet Size: 64
			Interval: 0ms

	Interface Number: 1
		Name: btusb
		Alternate Number: 0
		Class: e0
		Sub Class: 01
		Protocol: 01
		Number of Endpoints: 2

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 0
			Interval: 1ms

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 0
			Interval: 1ms

systemctl status bluetooth:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Thu 2024-10-10 19:04:00 -03; 17min ago
 Invocation: 3d7f9068994349b8910915c0642e2176
       Docs: man:bluetoothd(8)
   Main PID: 493 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 9011)
     Memory: 736K (peak: 3M swap: 424K swap peak: 424K)
        CPU: 31ms
     CGroup: /system.slice/bluetooth.service
             └─493 /usr/lib/bluetooth/bluetoothd

oct 10 19:04:00 BAFFLIND bluetoothd[493]: src/plugin.c:init_plugin() System does not support bap plugin
oct 10 19:04:00 BAFFLIND bluetoothd[493]: src/plugin.c:init_plugin() System does not support bass plugin
oct 10 19:04:00 BAFFLIND bluetoothd[493]: src/plugin.c:init_plugin() System does not support mcp plugin
oct 10 19:04:00 BAFFLIND bluetoothd[493]: src/plugin.c:init_plugin() System does not support vcp plugin
oct 10 19:04:00 BAFFLIND bluetoothd[493]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
oct 10 19:04:00 BAFFLIND bluetoothd[493]: src/plugin.c:init_plugin() System does not support micp plugin
oct 10 19:04:00 BAFFLIND bluetoothd[493]: src/plugin.c:init_plugin() System does not support ccp plugin
oct 10 19:04:00 BAFFLIND bluetoothd[493]: src/plugin.c:init_plugin() System does not support csip plugin
oct 10 19:04:00 BAFFLIND bluetoothd[493]: src/plugin.c:init_plugin() System does not support asha plugin
oct 10 19:04:00 BAFFLIND bluetoothd[493]: Bluetooth management interface 1.23 initialized

bluetoothctl show:

No default controller available

Offline

#5 2024-10-10 23:08:32

anarcobafif
Member
Registered: 2022-12-15
Posts: 9

Re: Bluetooth detected by rfkill, but not by bluetoothctl

sudo inxi --bluetooth --filter:

Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    type: USB
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: no
    address: <filter>

sudo inxi --usb --filter:

USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
  Device-1: 1-4:2 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
    type: bluetooth rev: 2.0
  Device-2: 1-8:3 info: Razer USA RZ01-0036 Optical Gaming Mouse [Abyssus]
    type: mouse rev: 2.0
  Device-3: 1-11:4 info: Elan Micro Gaming KB type: keyboard rev: 1.1
  Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.0
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
  Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1

Offline

#6 2024-10-12 18:44:33

anarcobafif
Member
Registered: 2022-12-15
Posts: 9

Re: Bluetooth detected by rfkill, but not by bluetoothctl

I started btmon and tried tu set hci0 up using hciconfig and it says this:

...

< HCI Command: Write Extended Inquiry Response (0x03|0x0052) plen 241                           #13 [hci0] 4.261833
        FEC: Not required (0x00)
> HCI Event: Command Complete (0x0e) plen 4                                                     #14 [hci0] 4.264704
      Write Extended Inquiry Response (0x03|0x0052) ncmd 1
        Status: Success (0x00)
< HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1                                          #15 [hci0] 4.264832
        Mode: Inquiry Result with RSSI or Extended Inquiry Result (0x02)
> HCI Event: Command Complete (0x0e) plen 4                                                     #16 [hci0] 4.266647
      Write Inquiry Mode (0x03|0x0045) ncmd 1
        Status: Success (0x00)
< HCI Command: Read Inquiry Response TX Power Level (0x03|0x0058) plen 0                        #17 [hci0] 4.266748
> HCI Event: Command Complete (0x0e) plen 5                                                     #18 [hci0] 4.268634
      Read Inquiry Response TX Power Level (0x03|0x0058) ncmd 1
        Status: Success (0x00)
        TX power: 6 dbm (0x06)
< HCI Command: Read Local Extended Features (0x04|0x0004) plen 1                                #19 [hci0] 4.268788
        Page: 1
= Close Index: 00:1A:7D:DA:71:13                                                                    [hci0] 6.285318
[6719]: @ RAW Close: hciconfig                                                                    {0x0002} 6.286394

Offline

Pages: 1

Board footer

Powered by FluxBB