Re: How to get USB bluetooth device working/supported?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Andrew,

> How does one go about getting a device that should work with btusb but doesn’t? It works fine with Microsoft generic bt drivers. There must be some sort of quirk.
> 
> This is for a Bluetooth 5.3 transceiver. There’s not a lot of these about yet but I think important for accessing newer/upcoming audio purposes.
> 
> 
> From /sys/kernel/debug/usb/devices:
> 
> T:  Bus=02 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=12   MxCh= 0
> D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
> P:  Vendor=10d7 ProdID=b012 Rev=88.91
> S:  Manufacturer=Actions
> S:  Product=general adapter
> S:  SerialNumber=ACTIONS1234
> C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=100mA
> I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=1ms
> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E:  Ad=01(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
> I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E:  Ad=01(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
> E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
> I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E:  Ad=01(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
> I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E:  Ad=01(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
> I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E:  Ad=01(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
> I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E:  Ad=01(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
> E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms
> 
> 
> dmesg | grep Bluetooth
> [   11.375035] Bluetooth: Core ver 2.22
> [   11.375054] Bluetooth: HCI device and connection manager initialized
> [   11.375057] Bluetooth: HCI socket layer initialized
> [   11.375059] Bluetooth: L2CAP socket layer initialized
> [   11.375062] Bluetooth: SCO socket layer initialized
> [   11.450398] Bluetooth: hci0: Opcode 0x c5a failed: -56
> [   12.455169] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [   12.455173] Bluetooth: BNEP filters: protocol multicast
> [   12.455176] Bluetooth: BNEP socket layer initialized
> 
> 
> This is on Linux Kernel: 6.0.8-300.fc37.aarch64
> 
> 
> This needs to be added to the usb.ids (I’ve tried submitting to the update robot but I don’t know if that is still alive):
> 
> 10d7 Actions Semiconductor Co., Ltd
> b012 ATS2851 Bluetooth 5.3 Transceiver [Ugreen CM591]

this seems to be problem:

< HCI Command: Read Default Erroneous Data Reporting (0x03|0x005a) plen 0
> HCI Event: Command Status (0x0f) plen 4
      Read Default Erroneous Data Reporting (0x03|0x005a) ncmd 1
        Status: Unknown HCI Command (0x01)

The device declares support for it, but then doesn’t actually support
it.

We have a HCI_QUIRK_BROKEN_ERR_DATA_REPORTING that most likely needs
to be set for this hardware.

Regards

Marcel




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux