[Bug 205685] New: Initialization failure for Cambridge Silicon Radio, Ltd Bluetooth Dongle

[Bug 205685] New: Initialization failure for Cambridge Silicon Radio, Ltd Bluetooth Dongle

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=205685

            Bug ID: 205685
           Summary: Initialization failure for Cambridge Silicon Radio,
                    Ltd Bluetooth Dongle
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.19.67-2+deb10u2
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: net@dalmat.net
        Regression: No

Created attachment 286091
  --> https://bugzilla.kernel.org/attachment.cgi?id=286091&action=edit
btmon trace

Hello,

I own a bluetooth USB adapter that fails to initialize.
The other bugs I saw deal with other device, hence this new one.


$ sudo hciconfig
hci0:   Type: Primary  Bus: USB
        BD Address: 00:1A:7D:DA:XX:XX  ACL MTU: 679:9  SCO MTU: 48:16
        DOWN 
        RX bytes:1722 acl:0 sco:0 events:90 errors:0
        TX bytes:1104 acl:0 sco:0 commands:90 errors:0

$ sudo hciconfig hci0 up
Can't init device hci0: Operation not supported (95)

The device is the following one (full lsusb output attached as file)
Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          224 Wireless
  bDeviceSubClass         1 Radio Frequency
  bDeviceProtocol         1 Bluetooth
  bMaxPacketSize0        64
  idVendor           0x0a12 Cambridge Silicon Radio, Ltd
  idProduct          0x0001 Bluetooth Dongle (HCI mode)
  bcdDevice           88.91
  iManufacturer           0 
  iProduct                2 
  iSerial                 0 

I attach a btmon trace that seems to indicate that the "Delete Stored Link Key"
is not supported.

Is there a way to support this device in degraded mode in case the feature is
not supported ?

Cheers

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 205685] Initialization failure for Cambridge Silicon Radio, Ltd Bluetooth Dongle

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=205685

--- Comment #1 from Matthieu Dalstein (net@dalmat.net) ---
Created attachment 286093
  --> https://bugzilla.kernel.org/attachment.cgi?id=286093&action=edit
lsusb output

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 205685] Initialization failure for Cambridge Silicon Radio, Ltd Bluetooth Dongle

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=205685

sisisisol@disroot.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sisisisol@disroot.org

--- Comment #2 from sisisisol@disroot.org ---

lsusb output

Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)

It also doesn't work with the kernel of AVLinux (Debian + Ubuntu)

uname -a

Linux ***** 5.4.28avl2-lowlatency #22 SMP PREEMPT Fri Apr 3 05:54:55 EDT 2020
x86_64 GNU/Linux

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 205685] Initialization failure for Cambridge Silicon Radio, Ltd Bluetooth Dongle

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=205685

--- Comment #3 from sisisisol@disroot.org ---
(In reply to sisisisol from comment #2)
> lsusb output
> 
> Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
> Dongle (HCI mode)
> 
> It also doesn't work with the kernel of AVLinux (Debian + Ubuntu)
> 
> uname -a
> 
> Linux ***** 5.4.28avl2-lowlatency #22 SMP PREEMPT Fri Apr 3 05:54:55 EDT
> 2020 x86_64 GNU/Linux

I forgot to mention is USB to Bluetooth Version 5.0

-- 
You are receiving this mail because:
You are the assignee for the bug.