Bluetooth dongle not working

Hello, I bought a bluetooth dongle which is supposed to work under linux. However this one does not work.

Here are some commands:

install:/home/florian # lsusb
Bus 001 Device 023: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

install:/home/florian # service bluetooth status
* bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disable>
   Active: active (running) since Tue 2019-12-17 18:23:38 CET; 3 days ago
     Docs: man:bluetoothd(8)
 Main PID: 1404 (bluetoothd)
    Tasks: 1 (limit: 4915)
   Memory: 2.2M
   CGroup: /system.slice/bluetooth.service
           `-1404 /usr/lib/bluetooth/bluetoothd

install:/home/florian # rfkill
ID TYPE      DEVICE     SOFT     HARD
 0 wlan      phy0     bloqué débloqué
 1 bluetooth hci0   débloqué débloqué
 3 bluetooth hci1   débloqué débloqué

install:/home/florian # hciconfig hci1 reset
Can't init device hci1: Operation not supported (95)

install:/home/florian # hcidump -i hci1 
< HCI Command: Delete Stored Link Key (0x03|0x0012) plen 7
    bdaddr 00:00:00:00:00:00 all 1
> HCI Event: Command Complete (0x0e) plen 6
    Delete Stored Link Key (0x03|0x0012) ncmd 1
    status 0x11 deleted 0
    Error: Unsupported Feature or Parameter Value

In short the problem would come from the dongle which informs the kernels of its compatibility with the Delete Stored Link Key function but it is not.

However in the btusb.c file there is a compatibility mode for this kind of dongles:

if (!rp->status) {
        if (le16_to_cpu(rp->manufacturer) != 10) {
            /* Clear the reset quirk since this is not an actual
             * early Bluetooth 1.1 device from CSR.
             */
            clear_bit(HCI_QUIRK_RESET_ON_CLOSE, &hdev->quirks);
            /* These fake CSR controllers have all a broken
             * stored link key handling and so just disable it.
             */
            set_bit(HCI_QUIRK_BROKEN_STORED_LINK_KEY,
                &hdev->quirks);
if (id->driver_info & BTUSB_CSR) {
        struct usb_device *udev = data->udev;
        u16 bcdDevice = le16_to_cpu(udev->descriptor.bcdDevice);
        /* Old firmware would otherwise execute USB reset */
        if (bcdDevice < 0x117)
            set_bit(HCI_QUIRK_RESET_ON_CLOSE, &hdev->quirks);
        /* Fake CSR devices with broken commands */
        if (bcdDevice <= 0x100)
            hdev->setup = btusb_setup_csr;
    }

I tried to modify btusb, and to recompile it doesn’t seem to work. In fact it seems that the compatibility mode is not taken into account on tumbleweed. Have you got an idea on how to make this work, how to deactivate the command “Delete Stored Link Key”?

Thank you

Hi
Perhaps device age? Whilst this is may not help, have a read of this Mailing list thread and try the new tools?
[opensuse-factory] Heads up: bluez-package will get rid of the deprecated binaries.](https://lists.opensuse.org/opensuse-factory/2019-12/msg00091.html)

Hello, I’m not sure I understand. The new package will not be released until the end of 2020! So how do you test it?

Does the journal show any bluetooth-related problems?

# journalctl -b 0 | grep blue

If your device needs some firmware which gets loaded on boot time:

Do you have the latest version of that firmware installed? (Check the suppliers web page)
Does the firmware load? (check the journal)

Regards

susejunky

Open a root terminal:

jornalctl -f

put in your bluetooth dongle and post all new messages from terminal here.

When I plug the dongle, nothing appears on journalctl -f.

Here is the bluetooth logs:

**install:/home/florian #** journalctl -b 0 | grep blue   
déc. 24 14:34:52 install kernel: **blue**tooth hci0: Direct firmware load for rtl_bt/rtl8723b_conf
ig.bin failed with error -2
déc. 24 14:34:54 install **blue**toothd[1468]: Bluetooth daemon 5.52
déc. 24 14:34:56 install **blue**toothd[1468]: Starting SDP server
déc. 24 14:34:56 install dbus-daemon[1470]: [system] Activating via systemd: service name='org
.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1' (uid
=0 pid=1468 comm="/usr/lib/**blue**tooth/**blue**toothd ")
déc. 24 14:34:56 install **blue**toothd[1468]: Bluetooth management interface 1.14 initialized
déc. 24 14:35:13 install NetworkManager[1653]: <info>  [1577194513.0574] Loaded device plugin:
 NMBluezManager (/usr/lib64/NetworkManager/1.18.4/libnm-device-plugin-**blue**tooth.so)
déc. 24 14:35:14 install NetworkManager[1653]: <info>  [1577194514.0766] **blue**z: use BlueZ vers
ion 5
déc. 24 14:35:14 install NetworkManager[1653]: <info>  [1577194514.0869] **blue**z5: NAP: added in
terface CC:B0:DA:40:27:1A
déc. 24 14:36:09 install **blue**toothd[1468]: Endpoint registered: sender=:1.39 path=/MediaEndpoi
nt/A2DPSink/sbc
déc. 24 14:36:09 install **blue**toothd[1468]: Endpoint registered: sender=:1.39 path=/MediaEndpoi
nt/A2DPSource/sbc
déc. 24 14:36:16 install kdeinit5[2290]: **blue**devil: Created
déc. 24 14:36:19 install kdeinit5[2290]: **blue**devil: ObexManager operational changed false
déc. 24 14:36:19 install dbus-daemon[2235]: [session uid=1000 pid=2235] Activating service nam
e='org.**blue**z.obex' requested by ':1.5' (uid=1000 pid=2290 comm="kded5 [kdeinit5]              
                    ")
déc. 24 14:36:19 install kdeinit5[2290]: **blue**devil: Bluetooth operational changed true
déc. 24 14:36:19 install kdeinit5[2290]: **blue**devil: Agent registered
déc. 24 14:36:19 install kdeinit5[2290]: **blue**devil: Requested default Agent
déc. 24 14:36:19 install dbus-daemon[2235]: [session uid=1000 pid=2235] Successfully activated
 service 'org.**blue**z.obex'
déc. 24 14:36:19 install kdeinit5[2290]: **blue**devil: ObexManager operational changed true
déc. 24 14:36:19 install kdeinit5[2290]: **blue**devil: ObexAgent registered
déc. 24 14:36:24 install plasmashell[2329]: org.kde.plasma: invalid metadata "/usr/lib64/qt5/p
lugins/kio_**blue**tooth.so"
déc. 24 20:38:49 install plasmashell[2329]: plasma-pk-updates: Got update package: "**blue**z-qt-i
mports;5.65.0-1.1;x86_64;download.opensuse.org-oss" , summary: "Async Bluez wrapper library" ,
 type: "enhancement"
déc. 24 20:38:49 install plasmashell[2329]: plasma-pk-updates: Got update package: "**blue**z-qt-u
dev;5.65.0-1.1;x86_64;download.opensuse.org-oss" , summary: "**blue**z-qt integration with udev" ,
 type: "enhancement"
déc. 24 20:38:57 install plasmashell[2329]: plasma-pk-updates: Got update package: "**blue**z-qt-i
mports;5.65.0-1.1;x86_64;download.opensuse.org-oss" , summary: "Async Bluez wrapper library" ,
 type: "enhancement"
déc. 24 20:38:57 install plasmashell[2329]: plasma-pk-updates: Got update package: "**blue**z-qt-u
dev;5.65.0-1.1;x86_64;download.opensuse.org-oss" , summary: "**blue**z-qt integration with udev" ,
 type: "enhancement"
déc. 25 21:08:06 install kdenlive[19601]: "frei0r.**blue**screen0r" is blacklisted
déc. 25 21:13:37 install kdenlive[19787]: "frei0r.**blue**screen0r" is blacklisted
déc. 25 21:45:18 install plasmashell[2329]: plasma-pk-updates: Got update package: "**blue**z-qt-i
mports;5.65.0-1.1;x86_64;download.opensuse.org-oss" , summary: "Async Bluez wrapper library" ,
 type: "enhancement"
déc. 25 21:45:18 install plasmashell[2329]: plasma-pk-updates: Got update package: "**blue**z-qt-u
dev;5.65.0-1.1;x86_64;download.opensuse.org-oss" , summary: "**blue**z-qt integration with udev" ,
 type: "enhancement"
déc. 25 21:45:47 install plasmashell[2329]: plasma-pk-updates: Got update package: "**blue**z-qt-i
mports;5.65.0-1.1;x86_64;download.opensuse.org-oss" , summary: "Async Bluez wrapper library" ,
 type: "enhancement"
déc. 25 21:45:47 install plasmashell[2329]: plasma-pk-updates: Got update package: "**blue**z-qt-u
dev;5.65.0-1.1;x86_64;download.opensuse.org-oss" , summary: "**blue**z-qt integration with udev" ,
 type: "enhancement"
déc. 26 15:21:45 install kdenlive[2284]: "frei0r.**blue**screen0r" is blacklisted
déc. 26 15:47:19 install kdenlive[3374]: "frei0r.**blue**screen0r" is blacklisted


More info: My computer has a built in bluetooth adaptator: rtl_bt/rtl8723b_conf but this one is not very effective ! The USB dongle dont seems to be present in the journalctl logs.

The reason for this might be

Probably this https://bbs.archlinux.org/viewtopic.php?pid=1698195#p1698195 can provide some information on that topic.

Does

# journalctl -b 0 | grep hci1

provide some useful information?

What is the result of

# hwinfo --bluetooth

(with the dongle plugged in)?

And have you tried the dongle on different USB-ports?

Regards

susejunky

**install:/home/florian #** journalctl -b 0 | grep hci1 
déc. 27 12:23:21 install kernel: Bluetooth: **hci1**: RTL: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723
déc. 27 12:23:21 install kernel: Bluetooth: **hci1**: RTL: rom_version status=0 version=1
déc. 27 12:23:21 install kernel: Bluetooth: **hci1**: RTL: rtl: loading rtl_bt/rtl8723b_fw.bin
déc. 27 12:23:21 install kernel: Bluetooth: **hci1**: RTL: rtl: loading rtl_bt/rtl8723b_config.bin
déc. 27 12:23:21 install kernel: Bluetooth: **hci1**: RTL: cfg_sz 44, total sz 22540
déc. 27 12:29:27 install bluetoothd[1466]: /org/bluez/**hci1**/dev_00_19_5D_35_57_D1/sep1/fd0: fd(49) ready
déc. 27 12:31:24 install bluetoothd[1466]: /org/bluez/**hci1**/dev_00_19_5D_35_57_D1/sep1/fd1: fd(48) ready
**install:/home/florian #** journalctl -b 0 | grep hci0
**install:/home/florian #** hwinfo --bluetooth
03: USB 00.0: 11500 Bluetooth Device                             
  [Created at usb.122]
  Unique ID: 33sj.sCiejPSFZo9
  Parent ID: ADDn.M4_hFzuaxRD
  SysFS ID: /devices/pci0000:00/0000:00:12.0/usb1/1-1/1-1.4/1-1.4:1.0
  SysFS BusID: 1-1.4:1.0
  Hardware Class: bluetooth
  Model: "Realtek Bluetooth Radio"
  Hotplug: USB
  Vendor: usb 0x0bda "Realtek Semiconductor Corp."
  Device: usb 0xb008 "Bluetooth Radio"
  Revision: "2.00"
  Serial ID: "00e04c000001"
  Driver: "btusb"
  Driver Modules: "btusb"
  Speed: 12 Mbps
  Module Alias: "usb:v0BDApB008d0200dcE0dsc01dp01icE0isc01ip01in00"
  Driver Info #0:
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #15 (Hub)

06: USB 00.0: 11500 Bluetooth Device
  [Created at usb.122]
  Unique ID: lfzD.nQKjiuCfL84
  Parent ID: ADDn.M4_hFzuaxRD
  SysFS ID: /devices/pci0000:00/0000:00:12.0/usb1/1-1/1-1.1/1-1.1:1.0
  SysFS BusID: 1-1.1:1.0
  Hardware Class: bluetooth
  Model: "Cambridge Silicon Radio Bluetooth Dongle (HCI mode)"
  Hotplug: USB
  Vendor: usb 0x0a12 "Cambridge Silicon Radio, Ltd"
  Device: usb 0x0001 "Bluetooth Dongle (HCI mode)"
  Revision: "88.91"
  Driver: "btusb"
  Driver Modules: "btusb"
  Speed: 12 Mbps
  Module Alias: "usb:v0A12p0001d8891dcE0dsc01dp01icE0isc01ip01in00"
  Driver Info #0:
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
**install:/home/florian #** rfkill
ID TYPE      DEVICE     SOFT     HARD
 0 wlan      phy0     bloqué débloqué
 1 bluetooth hci0   débloqué débloqué
 2 bluetooth hci1   débloqué débloqué
**install:/home/florian #** hciconfig hci0 reset
Can't init device hci0: Operation not supported (95)

**install:/home/florian #** hcidump -i hci0
HCI sniffer - Bluetooth packet analyzer ver 5.52
device: hci0 snap_len: 1500 filter: 0xffffffffffffffff
< HCI Command: Reset (0x03|0x0003) plen 0
> HCI Event: Command Complete (0x0e) plen 4
    Reset (0x03|0x0003) ncmd 1
    status 0x00
< HCI Command: Read Local Supported Features (0x04|0x0003) plen 0
> HCI Event: Command Complete (0x0e) plen 12
    Read Local Supported Features (0x04|0x0003) ncmd 1
    status 0x00
    Features: 0xff 0xff 0xcd 0xfa 0xdb 0xbf 0x7b 0x87
< HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> HCI Event: Command Complete (0x0e) plen 12
    Read Local Version Information (0x04|0x0001) ncmd 1
    status 0x00
    HCI Version: 4.0 (0x6) HCI Revision: 0x811
    LMP Version: 4.0 (0x6) LMP Subversion: 0x811
    Manufacturer: Cambridge Silicon Radio (10)
< HCI Command: Read BD ADDR (0x04|0x0009) plen 0
> HCI Event: Command Complete (0x0e) plen 10
    Read BD ADDR (0x04|0x0009) ncmd 1
    status 0x00 bdaddr 00:1A:7D:DA:71:11
< HCI Command: Read Buffer Size (0x04|0x0005) plen 0
> HCI Event: Command Complete (0x0e) plen 11
    Read Buffer Size (0x04|0x0005) ncmd 1
    status 0x00
    ACL MTU 679:9 SCO MTU 48:16
< HCI Command: Read Class of Device (0x03|0x0023) plen 0
> HCI Event: Command Complete (0x0e) plen 7
    Read Class of Device (0x03|0x0023) ncmd 1
    status 0x00 class 0x000000
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
    Read Local Name (0x03|0x0014) ncmd 1
    status 0x00 name ''
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Command Complete (0x0e) plen 6
    Read Voice Setting (0x03|0x0025) ncmd 1
    status 0x00 voice setting 0x0000
< HCI Command: Read Number of Supported IAC (0x03|0x0038) plen 0
> HCI Event: Command Complete (0x0e) plen 5
    Read Number of Supported IAC (0x03|0x0038) ncmd 1
< HCI Command: Read Current IAC LAP (0x03|0x0039) plen 0
> HCI Event: Command Complete (0x0e) plen 8
    Read Current IAC LAP (0x03|0x0039) ncmd 1
    IAC 0x9e8b33 (General Inquiry Access Code)
< HCI Command: Set Event Filter (0x03|0x0005) plen 1
    type 0 condition 0
    Clear all filters
> HCI Event: Command Complete (0x0e) plen 4
    Set Event Filter (0x03|0x0005) ncmd 1
    status 0x00
< HCI Command: Write Connection Accept Timeout (0x03|0x0016) plen 2
    timeout 32000
> HCI Event: Command Complete (0x0e) plen 4
    Write Connection Accept Timeout (0x03|0x0016) ncmd 1
    status 0x00
< HCI Command: LE Read Buffer Size (0x08|0x0002) plen 0
> HCI Event: Command Complete (0x0e) plen 7
    LE Read Buffer Size (0x08|0x0002) ncmd 1
    status 0x00 pktlen 0x001b maxpkt 0x0c
< HCI Command: LE Read Local Supported Features (0x08|0x0003) plen 0
> HCI Event: Command Complete (0x0e) plen 12
    LE Read Local Supported Features (0x08|0x0003) ncmd 1
    status 0x00 features 0x0100000000000000 (Link Layer supports LE Encryption)
< HCI Command: LE Read Supported States (0x08|0x001c) plen 0
> HCI Event: Command Complete (0x0e) plen 12
    LE Read Supported States (0x08|0x001c) ncmd 1
< HCI Command: Read Local Supported Commands (0x04|0x0002) plen 0
> HCI Event: Command Complete (0x0e) plen 68
    Read Local Supported Commands (0x04|0x0002) ncmd 1
    status 0x00
    Commands: bfffff03feffffff0fffff1ff20fe8fe3ff78fff1c00000061f7ffff7f18
< HCI Command: Write Extended Inquiry Response (0x03|0x0052) plen 241
    fec 0x00
> HCI Event: Command Complete (0x0e) plen 4
    Write Extended Inquiry Response (0x03|0x0052) ncmd 1
    status 0x00
< HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1
    mode 2
> HCI Event: Command Complete (0x0e) plen 4
    Write Inquiry Mode (0x03|0x0045) ncmd 1
    status 0x00
< HCI Command: Read Inquiry Response Transmit Power Level (0x03|0x0058) plen 0
> HCI Event: Command Complete (0x0e) plen 5
    Read Inquiry Response Transmit Power Level (0x03|0x0058) ncmd 1
    status 0x00 level 8
< HCI Command: Read Local Extended Features (0x04|0x0004) plen 1
    page 1
> HCI Event: Command Complete (0x0e) plen 14
    Read Local Extended Features (0x04|0x0004) ncmd 1
    status 0x00 page 1 max 0
    Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
< HCI Command: Set Event Mask (0x03|0x0001) plen 8
    Mask: 0xfffffbff07f8bf3d
> HCI Event: Command Complete (0x0e) plen 4
    Set Event Mask (0x03|0x0001) ncmd 1
    status 0x00
< HCI Command: Read Stored Link Key (0x03|0x000d) plen 7
    bdaddr 00:00:00:00:00:00 all 1
> HCI Event: Command Complete (0x0e) plen 8
    Read Stored Link Key (0x03|0x000d) ncmd 1
    status 0x00 max 0 num 0
< HCI Command: Write Default Link Policy Settings (0x02|0x000f) plen 2
    policy 0x0f
    Link policy: RSWITCH HOLD SNIFF PARK  
> HCI Event: Command Complete (0x0e) plen 4
    Write Default Link Policy Settings (0x02|0x000f) ncmd 1
    status 0x00
< HCI Command: Read Page Scan Activity (0x03|0x001b) plen 0
> HCI Event: Command Complete (0x0e) plen 8
    Read Page Scan Activity (0x03|0x001b) ncmd 1
    status 0x00 interval 512 window 18
< HCI Command: Read Page Scan Type (0x03|0x0046) plen 0
> HCI Event: Command Complete (0x0e) plen 5
    Read Page Scan Type (0x03|0x0046) ncmd 1
< HCI Command: LE Set Event Mask (0x08|0x0001) plen 8
    mask 0x1f00000000000000 (Reserved)
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Event Mask (0x08|0x0001) ncmd 1
    status 0x00
< HCI Command: LE Read Advertising Channel Tx Power (0x08|0x0007) plen 0
> HCI Event: Command Complete (0x0e) plen 5
    LE Read Advertising Channel Tx Power (0x08|0x0007) ncmd 1
    status 0x00 level 0x8 (dBm)
< HCI Command: LE Read White List Size (0x08|0x000f) plen 0
> HCI Event: Command Complete (0x0e) plen 5
    LE Read White List Size (0x08|0x000f) ncmd 1
< HCI Command: LE Clear White List (0x08|0x0010) plen 0
> HCI Event: Command Complete (0x0e) plen 4
    LE Clear White List (0x08|0x0010) ncmd 1
    status 0x00
< HCI Command: Delete Stored Link Key (0x03|0x0012) plen 7
    bdaddr 00:00:00:00:00:00 all 1
> HCI Event: Command Complete (0x0e) plen 6
    Delete Stored Link Key (0x03|0x0012) ncmd 1
    status 0x11 deleted 0
    Error: Unsupported Feature or Parameter Value

I have copied the rtl8723b_config file, but integrated Bluetooth does not work better even if the error message has disappeared. For the dongle, which became HCI0, the same problem remains.

Once more:
plug of the Bluetooth dongle, post (completly):

lsusb

open an root terminal, type in:

journalctl -f

plugin the Bluetooth dongle and post all new rows from root terminal.
Also post now:

lsusb

Your system does recognize the dongle.

When you plug the dongle in

# journalctl -f

should produce some output.

Please keep in mind: Only “root” or a user who is member of the group systemd-journal can see all journal entries.

Have you tried the dongle on different USB-ports or on different machines?

Does the dongle work with other operating systems (e.g. MS Windows)?

Regards

susejunky

I have added root user to the systemd-journal group :

install:/home/florian # lsusb
Bus 003 Device 004: ID 0bda:0177 Realtek Semiconductor Corp. 
Bus 003 Device 003: ID 04f2:b52d Chicony Electronics Co., Ltd 
Bus 003 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0bda:b008 Realtek Semiconductor Corp. 
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 012: ID 275d:0ba6  
Bus 002 Device 011: ID 062a:0201 MosArt Semiconductor Corp. Defender Office Keyboard (K7310) S Zodiak KM-9010
Bus 002 Device 010: ID 0a05:7211 Unknown Manufacturer hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
install:/home/florian # journalctl -f
-- Logs begin at Mon 2019-09-09 12:58:05 CEST. --
déc. 28 15:38:16 install kernel: usb 1-1.1: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91
déc. 28 15:38:16 install kernel: usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
déc. 28 15:38:16 install systemd[1]: Starting Load/Save RF Kill Switch Status...
déc. 28 15:38:17 install org_kde_powerdevil[2517]: UdevQt: unhandled device action "bind"
déc. 28 15:38:17 install plasmashell[2480]: UdevQt: unhandled device action "bind"
déc. 28 15:38:17 install systemd[1]: Started Load/Save RF Kill Switch Status.
déc. 28 15:38:17 install org_kde_powerdevil[2517]: UdevQt: unhandled device action "bind"
déc. 28 15:38:17 install plasmashell[2480]: UdevQt: unhandled device action "bind"
déc. 28 15:38:17 install org_kde_powerdevil[2517]: UdevQt: unhandled device action "bind"
déc. 28 15:38:17 install plasmashell[2480]: UdevQt: unhandled device action "bind"
déc. 28 15:38:22 install org_kde_powerdevil[2517]: powerdevil: Releasing inhibition with cookie  3756
déc. 28 15:38:22 install org_kde_powerdevil[2517]: powerdevil: Scheduling inhibition from ":1.12" "My SDL application" with cookie 3757 and reason "Playing a game"
déc. 28 15:38:22 install org_kde_powerdevil[2517]: powerdevil: Can't contact ck
déc. 28 15:38:22 install systemd[1]: systemd-rfkill.service: Succeeded.
déc. 28 15:38:27 install org_kde_powerdevil[2517]: powerdevil: Enforcing inhibition from ":1.12" "My SDL application" with cookie 3757 and reason "Playing a game"
déc. 28 15:38:27 install org_kde_powerdevil[2517]: powerdevil: Added change screen settings
déc. 28 15:38:27 install org_kde_powerdevil[2517]: powerdevil: Added interrupt session
déc. 28 15:38:27 install org_kde_powerdevil[2517]: powerdevil: Can't contact ck
déc. 28 15:38:28 install org_kde_powerdevil[2517]: powerdevil: Releasing inhibition with cookie  3757
déc. 28 15:38:28 install org_kde_powerdevil[2517]: powerdevil: Can't contact ck
déc. 28 15:38:56 install org_kde_powerdevil[2517]: powerdevil: Scheduling inhibition from ":1.12" "My SDL application" with cookie 3758 and reason "Playing a game"
^C
install:/home/florian # lsusb
Bus 003 Device 004: ID 0bda:0177 Realtek Semiconductor Corp. 
Bus 003 Device 003: ID 04f2:b52d Chicony Electronics Co., Ltd 
Bus 003 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0bda:b008 Realtek Semiconductor Corp. 
Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 012: ID 275d:0ba6  
Bus 002 Device 011: ID 062a:0201 MosArt Semiconductor Corp. Defender Office Keyboard (K7310) S Zodiak KM-9010
Bus 002 Device 010: ID 0a05:7211 Unknown Manufacturer hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Thanks for your help !

Only non-root-users need to be member of the*** systemd-journal***-group if they want to see all journal entries. “root” will always see all journal entries.

Does the dongle produce this result on every USB-port of your machine?

Does the dongle work with other operating systems (e.g. MS Windows)?

It makes no sense to investigate this problem any further if the problem is caused by a faulty USB-port or the dongle itself does not work at all.

Regards

susejunky

Could you please give more details?

The latest version of Tumbleweed (20191227) provides an updated bluetooth stack (bluez 5.52-2.1) and the tools mentioned by malcolmlewis in post #2.

Here https://lists.opensuse.org/opensuse-factory/2019-12/msg00109.html you can find a comparison of old/new tools.

Regards

susejunky

Hello,

I have tested my bluetooth dongle with windows xp It works fine !

https://nsa40.casimages.com/img/2019/12/31/191231022550304827.png

I have also updated Tumbleweed but I till have the same error ! Why don’t you take this into consideration?

install:/home/florian # hcidump -i hci1 < HCI Command: Delete Stored Link Key (0x03|0x0012) plen 7
    bdaddr 00:00:00:00:00:00 all 1
> HCI Event: Command Complete (0x0e) plen 6
    Delete Stored Link Key (0x03|0x0012) ncmd 1
    status 0x11 deleted 0
    Error: Unsupported Feature or Parameter Value

In short the problem would come from the dongle which informs the kernels of its compatibility with the Delete Stored Link Key function but it is not.

However in the btusb.c file there is a compatibility mode for this kind of dongles:

if (!rp->status) {        if (le16_to_cpu(rp->manufacturer) != 10) {
            /* Clear the reset quirk since this is not an actual
             * early Bluetooth 1.1 device from CSR.
             */
            clear_bit(HCI_QUIRK_RESET_ON_CLOSE, &hdev->quirks);
            /* These fake CSR controllers have all a broken
             * stored link key handling and so just disable it.
             */
            set_bit(HCI_QUIRK_BROKEN_STORED_LINK_KEY,
                &hdev->quirks);
if (id->driver_info & BTUSB_CSR) {        struct usb_device *udev = data->udev;
        u16 bcdDevice = le16_to_cpu(udev->descriptor.bcdDevice);
        /* Old firmware would otherwise execute USB reset */
        if (bcdDevice < 0x117)
            set_bit(HCI_QUIRK_RESET_ON_CLOSE, &hdev->quirks);
        /* Fake CSR devices with broken commands */
        if (bcdDevice <= 0x100)
            hdev->setup = btusb_setup_csr;
    }

I have a fake CSR device but the Fake CSR device condition dont work in btusb.c !! That’s all !

I guess by CSR you are talking about the CSR harmony wireless software stack?

“hcidump” was replaced by “btmon” with the latest Tumbleweed release!

Anyway i have no idea what a “fake CSR device” is and what you are trying to achieve. So i won’t be able to help you any further. Sorry!

Good luck and a happy new year!

Regards

susejunky

CSR like

install:/home/florian # lsusb
Bus 001 Device 023: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

This “Fake CSR” thing is present in the btusb.c file…

Hi
Does the device work in Windows 10? Install a linux operating of the XP era, does the device work (probably likely). CSR means Cambridge Silicon Radio, my suggestion is get a newer device, I have a CSR bluetooth mouse and it’s pain to connect, I wrote a script to cycle through connecting and then pressing the pair button on the mouse…

My question is why my system try to use the “stored link key” command while there is this in btusb.c

if (!rp->status) {        if (le16_to_cpu(rp->manufacturer) != 10) {            /* Clear the reset quirk since this is not an actual
             * early Bluetooth 1.1 device from CSR.
             */
            clear_bit(HCI_QUIRK_RESET_ON_CLOSE, &hdev->quirks);
**            /* These fake CSR controllers have all a broken**
**             * stored link key handling and so just disable it.**
**             */**
            set_bit(HCI_QUIRK_BROKEN_STORED_LINK_KEY,
                &hdev->quirks);

And how to disable “stored link key” command…

Hi
I don’t think you can, life moves on and I would surmise the hardware is no longer supported by the bluetooth maintainers… you might be able to do it via adding a quirk to the USB driver.