Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) HCI0 is UP and running : piraspberrypi: sudo hciconfig -a. The BT dongle is detected : piraspberrypi: lsusb. Linux leberman-HD631-Q87CRM 5.18. Bluetooth - Cambridge Silicon Radio Bluetooth Dongle. The problem occurs even when the bluetooth adaptor is the only USB device connected to the Pi (no mouse or keyboard). Bluetooth: hci0: CSR: Local version failed (-32) Bluetooth: hci0: Opcode 0x c03 failed: -110 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001) Cambridge Silicon Radio, Ltd Bluetooth Dongle, CNet CBD-120, USB ID 0a12:0001. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub' Top. Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround Re: Cambridge Silicon Radio, Ltd Bluetooth Dongle - Not Connecting Post by Mihail-Cosmin ยป Sat 6:42 pm ul1sses wrote: Sun 4:35 pm I have the same problem as you. Bus 003 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 003 Device 002: ID 046d:c52b Logitech, Inc.
Bluetooth: hci0: CSR: Unbranded CSR clone detected adding workarounds and force-suspending once. usb 3-6: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 3-6: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=25.20 Discussions related to using VirtualBox on Mac OS X hosts. Hi I have a Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) on Ubuntu 20.04, its recognized but the bluetooth isnt turn on. 1304.304169] usb 3-6: new full-speed USB device number 6 using xhci_hcd This is one of the bluetooth adapters that pretend to be a 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) and appears not to work despite the numerous existing workarounds in the kernel.