Cambridge Silicon Radio Bluetooth dongle not working

English Network/Internet
1

Hello, need some help with a Bluetooth dongle, just can’t make it work. This is like the third piece of s… bought (at least is Bluetooth 5.0, if it would work) and I am out of ideas… Was running Leap 15.1 with the latest stable 5.7 kernel, but I upgraded to 15.2 with the 5.3 kernel, my Vega 64 wouldn’t run on 4.x versions. Anyways:


FakeMoth-PC:/home/fakemoth # uname -a
Linux FakeMoth-PC 5.3.18-lp152.33-default #1 SMP Wed Jul 22 06:32:33 UTC 2020 (e5a8383) x86_64 x86_64 x86_64 GNU/Linux

FakeMoth-PC:/home/fakemoth # systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2020-08-02 10:02:40 EEST; 30min ago
     Docs: man:bluetoothd(8)
 Main PID: 10090 (bluetoothd)
   Status: "Running"
    Tasks: 1
   CGroup: /system.slice/bluetooth.service
           └─10090 /usr/lib/bluetooth/bluetoothd

aug 02 10:02:40 FakeMoth-PC systemd[1]: Starting Bluetooth service...
aug 02 10:02:40 FakeMoth-PC bluetoothd[10090]: Bluetooth daemon 5.48
aug 02 10:02:40 FakeMoth-PC bluetoothd[10090]: Starting SDP server
aug 02 10:02:40 FakeMoth-PC bluetoothd[10090]: Bluetooth management interface 1.14 initialized
aug 02 10:02:40 FakeMoth-PC systemd[1]: Started Bluetooth service.

FakeMoth-PC:/home/fakemoth # rfkill list
1: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

FakeMoth-PC:/home/fakemoth # dmesg | grep Bluetooth
   16.667975] Bluetooth: Core ver 2.22
   16.667986] Bluetooth: HCI device and connection manager initialized
   16.667989] Bluetooth: HCI socket layer initialized
   16.667990] Bluetooth: L2CAP socket layer initialized
   16.667992] Bluetooth: SCO socket layer initialized
   22.211247] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
   22.211248] Bluetooth: BNEP filters: protocol multicast
   22.211251] Bluetooth: BNEP socket layer initialized

FakeMoth-PC:/home/fakemoth # lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 005: ID 1532:006c Razer USA, Ltd 
Bus 001 Device 004: ID 1e7d:3264 ROCCAT 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

So the device works and it’s a Cambridge chip, but:


FakeMoth-PC:/home/fakemoth # hciconfig 
hci0:   Type: Primary  Bus: USB
        BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
        DOWN 
        RX bytes:574 acl:0 sco:0 events:30 errors:0
        TX bytes:368 acl:0 sco:0 commands:30 errors:0

FakeMoth-PC:/home/fakemoth # hciconfig -a hci0
hci0:   Type: Primary  Bus: USB
        BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
        DOWN 
        RX bytes:574 acl:0 sco:0 events:30 errors:0
        TX bytes:368 acl:0 sco:0 commands:30 errors:0
        Features: 0xff 0xff 0xcd 0xfa 0xdb 0xbf 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT

FakeMoth-PC:/home/fakemoth # hcitool scan
Device is not available: No such device

FakeMoth-PC:/home/fakemoth # hciconfig hci0 up
Can't init device hci0: Operation not supported (95)

FakeMoth-PC:/home/fakemoth # bluetoothctl
Agent registered
[bluetooth]# list
[bluetooth]# NOTHING HERE!

Any ideeas, any experience with this? I read about recompiling the kernel but it is overkill, isn’t there some module or something I can just load? Thanks!

2

An illuminating Ubuntu thread on the same topic…
https://askubuntu.com/questions/1208296/bluetoot-adapter-configuration-issue-id-0a120001

In particular, you might consider starting by disabling USB autosuspend by adding the following boot parameter to grub ‘usbcore.autosuspend=-1’

Just in case you need specific advice about doing that…
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha-grub2.html#sec-grub2-yast2-configLet’s see if that helps with keeping the device powered up.

3

That option didn’t change anything for me, not working in this case…

FakeMoth-PC:/home/fakemoth # hciconfig -a
hci0:   Type: Primary  Bus: USB
        BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
        DOWN 
        RX bytes:574 acl:0 sco:0 events:30 errors:0
        TX bytes:368 acl:0 sco:0 commands:30 errors:0
        Features: 0xff 0xff 0xcd 0xfa 0xdb 0xbf 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT 

FakeMoth-PC:/home/fakemoth # hciconfig hci0 up
Can't init device hci0: Operation not supported (95)
4

You mentioned in your opening post…

Was running Leap 15.1 with the latest stable 5.7 kernel, but I upgraded to 15.2 with the 5.3 kernel,…

Have you tried using the latest stable kernel again?

5

Thanks for answering and taking the time in this! But I already did, already tried with the 5.7 on 15.1 (that being my OS at the time I bought this bluetooth dongle), and than with the default 5.3 kernel on 15.2. Are you saying I should try with 5.7/8 on Leap 15.2? Should it make a difference driver wise?
Because I would rather skip that and have a slower pace, the cycle of releases is maddening and I have to compile ZFS each time a new update is out… as I am a compulsive updater :slight_smile:

6

Maybe I misunderstood you…I thought that you had indicated that you had this working with openSUSE 15.1 (and kernel 5.7.x).

7

Sorry, my bad, wasn’t very clear: the device never worked on openSUSE, will get a laptop today with a Windows 10 just to rule out a defective product. But the error is too widely spread it seems.

So what do you think I should try next?

8

An optional bluetooth connection radio?

9

Try the newest Live Tumbleweed. I plugged in a ‘Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)’ and it readily tries to connect with devices found:

i3-4130:~ # bluetoothctl 
Agent registered 
[bluetooth]# list 
Controller xx:xx:xx:xx:xx:xx i3-4130 [default] 
[bluetooth]# quit 
i3-4130:~ # 

i3-4130:~ # journalctl --since 12:30 _KERNEL_SUBSYSTEM=usb 
-- Journal begins at Sun 2021-07-11 15:51:53 CEST, ends at Fri 2021-07-16 12:46:36 CEST. -- 
Jul 16 12:39:04 i3-4130 kernel: usb 3-9: USB disconnect, device number 9 
Jul 16 12:39:40 i3-4130 kernel: usb 3-9: new full-speed USB device number 10 using xhci_hcd 
Jul 16 12:39:40 i3-4130 kernel: usb 3-9: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 
Jul 16 12:39:40 i3-4130 kernel: usb 3-9: New USB device strings: Mfr=0, Product=2, SerialNumber=0 
Jul 16 12:39:40 i3-4130 kernel: usb 3-9: Product: CSR8510 A10 
i3-4130:~ #
10

The entertainment experience is amazing.