[SOLVED] CSR8510 A10 Bluetooth controller issue

Anything related to gaming on Linux Mint including game discussion or questions concerning Steam or Wine.
Forum rules
Before you post please read how to get help
Post Reply
User avatar
nukeCrayon
Level 1
Level 1
Posts: 34
Joined: Fri Apr 09, 2021 1:07 am
Location: Quezon City, NCR, Philippines

[SOLVED] CSR8510 A10 Bluetooth controller issue

Post by nukeCrayon »

Hello Linux community.

I can't connect any of my Bluetooth devices... even my PS3 controller. Linux Mint can detect the dongle but it can't pair.

Please help me guys.
Last edited by nukeCrayon on Thu Jun 03, 2021 6:36 am, edited 2 times in total.
JeremyB
Level 21
Level 21
Posts: 12561
Joined: Fri Feb 21, 2014 8:17 am

Re: Bluetooth controller issue

Post by JeremyB »

Post results from terminal for

Code: Select all

lsusb; dmesg | egrep -i 'blue|firm'
User avatar
nukeCrayon
Level 1
Level 1
Posts: 34
Joined: Fri Apr 09, 2021 1:07 am
Location: Quezon City, NCR, Philippines

Re: Bluetooth controller issue

Post by nukeCrayon »

JeremyB wrote:
Sun May 30, 2021 7:08 am
Post results from terminal for

Code: Select all

lsusb; dmesg | egrep -i 'blue|firm'
Hello JeremyB. Here it is:

Bus 002 Device 009: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n
Bus 002 Device 005: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 004: ID 1c4f:0026 SiGma Micro Keyboard
Bus 002 Device 008: ID 0403:6014 Future Technology Devices International, Ltd FT232H Single HS USB-UART/FIFO IC
Bus 002 Device 006: ID 056a:0390 Wacom Co., Ltd DTK-1660 [Cintiq 16]
Bus 002 Device 003: ID 056a:0395 Wacom Co., Ltd
Bus 002 Device 011: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 0.147497] Spectre V2 : Enabling Restricted Speculation for firmware calls
[ 0.177999] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.183512] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 1.329974] [drm] Found UVD firmware Version: 1.130 Family ID: 16
[ 1.330540] [drm] Found VCE firmware Version: 53.26 Binary ID: 3
[ 3.710574] Bluetooth: Core ver 2.22
[ 3.710589] Bluetooth: HCI device and connection manager initialized
[ 3.710591] Bluetooth: HCI socket layer initialized
[ 3.710593] Bluetooth: L2CAP socket layer initialized
[ 3.710596] Bluetooth: SCO socket layer initialized
[ 3.748907] usb 2-1.6: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[ 4.411703] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.411704] Bluetooth: BNEP filters: protocol multicast
[ 4.411707] Bluetooth: BNEP socket layer initialized
[ 123.766597] Bluetooth: RFCOMM TTY layer initialized
[ 123.766601] Bluetooth: RFCOMM socket layer initialized
[ 123.766604] Bluetooth: RFCOMM ver 1.11
[ 134.364562] Bluetooth: hci0: command 0x0402 tx timeout
[ 136.381329] Bluetooth: hci0: command 0x200c tx timeout
[ 138.398054] Bluetooth: hci0: command 0x0405 tx timeout
[ 156.834859] Bluetooth: hci0: command 0x0409 tx timeout
User avatar
all41
Level 18
Level 18
Posts: 8438
Joined: Tue Dec 31, 2013 9:12 am
Location: Computer, Car, Cage

Re: Bluetooth controller issue

Post by all41 »

nukeCrayon wrote:
Sun May 30, 2021 6:55 am
Hello Linux community.

I can't connect any of my Bluetooth devices... even my PS3 controller. Linux Mint can detect the dongle but it can't pair.

Please help me guys.
Same here--
Bus 002 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

I have not been able to pair with the V5.0 either.
Everything is difficult before it gets easy.
JeremyB
Level 21
Level 21
Posts: 12561
Joined: Fri Feb 21, 2014 8:17 am

Re: Bluetooth controller issue

Post by JeremyB »

About all you can do is try a newer kernel as those devices have a reputation of being difficult as all CSR bluetooth devices have the same ID
I might be able to find something if you post results for

Code: Select all

usb-devices | awk '/0a12/' RS=" 
User avatar
all41
Level 18
Level 18
Posts: 8438
Joined: Tue Dec 31, 2013 9:12 am
Location: Computer, Car, Cage

Re: Bluetooth controller issue

Post by all41 »

I think I see the cause:

Code: Select all


V4.0
[    0.212777] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.377475] acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-05] only partially covers this bridge
[    8.116724] Bluetooth: Core ver 2.22
[    8.116759] Bluetooth: HCI device and connection manager initialized
[    8.116780] Bluetooth: HCI socket layer initialized
[    8.116783] Bluetooth: L2CAP socket layer initialized
[    8.116788] Bluetooth: SCO socket layer initialized
[    8.557962] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    8.557963] Bluetooth: BNEP filters: protocol multicast
[    8.557967] Bluetooth: BNEP socket layer initialized
[   11.622945] Bluetooth: RFCOMM TTY layer initialized
[   11.622950] Bluetooth: RFCOMM socket layer initialized
[   11.622955] Bluetooth: RFCOMM ver 1.11
[   17.969815] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   17.969820] Bluetooth: HIDP socket layer initialized

V5.0

[    0.212777] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.377475] acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-05] only partially covers this bridge
[    8.116724] Bluetooth: Core ver 2.22
[    8.116759] Bluetooth: HCI device and connection manager initialized
[    8.116780] Bluetooth: HCI socket layer initialized
[    8.116783] Bluetooth: L2CAP socket layer initialized
[    8.116788] Bluetooth: SCO socket layer initialized
[    8.557962] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    8.557963] Bluetooth: BNEP filters: protocol multicast
[    8.557967] Bluetooth: BNEP socket layer initialized
[   11.622945] Bluetooth: RFCOMM TTY layer initialized
[   11.622950] Bluetooth: RFCOMM socket layer initialized
[   11.622955] Bluetooth: RFCOMM ver 1.11
[   17.969815] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   17.969820] Bluetooth: HIDP socket layer initialized
[  136.819922] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds..
Notice the last entry---
It's a lying weasle
Everything is difficult before it gets easy.
User avatar
nukeCrayon
Level 1
Level 1
Posts: 34
Joined: Fri Apr 09, 2021 1:07 am
Location: Quezon City, NCR, Philippines

Re: Bluetooth controller issue

Post by nukeCrayon »

JeremyB wrote:
Sun May 30, 2021 8:10 am
About all you can do is try a newer kernel as those devices have a reputation of being difficult as all CSR bluetooth devices have the same ID
I might be able to find something if you post results for

Code: Select all

usb-devices | awk '/0a12/' RS=" 
the code

Code: Select all

usb-devices 
gives me this:

Code: Select all

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=05.04
S:  Manufacturer=Linux 5.4.0-73-generic ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=0000:00:1a.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 4
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=0024 Rev=00.00
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=05.04
S:  Manufacturer=Linux 5.4.0-73-generic ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=0000:00:1d.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 6
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=0024 Rev=00.00
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
P:  Vendor=056a ProdID=0395 Rev=01.00
S:  Manufacturer=Wacom Co., Ltd.
S:  Product=Cintiq 16 HUB
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=2mA
I:  If#=0x0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub

T:  Bus=02 Lev=03 Prnt=03 Port=00 Cnt=01 Dev#=  6 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=056a ProdID=0390 Rev=01.01
S:  Manufacturer=Wacom Co.,Ltd.
S:  Product=Cintiq 16
S:  SerialNumber=0EQ00X1002930
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

T:  Bus=02 Lev=03 Prnt=03 Port=01 Cnt=02 Dev#=  8 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0403 ProdID=6014 Rev=09.00
S:  Manufacturer=FTDI
S:  Product=Single RS232-HS
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#=0x0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio

T:  Bus=02 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  4 Spd=1.5 MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=1c4f ProdID=0026 Rev=01.10
S:  Manufacturer=SIGMACHIP
S:  Product=USB Keyboard
C:  #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=98mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
I:  If#=0x1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

T:  Bus=02 Lev=02 Prnt=02 Port=03 Cnt=03 Dev#=  5 Spd=1.5 MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=093a ProdID=2510 Rev=01.00
S:  Manufacturer=PixArt
S:  Product=USB Optical Mouse
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid

T:  Bus=02 Lev=02 Prnt=02 Port=05 Cnt=04 Dev#=  7 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1
P:  Vendor=0cf3 ProdID=9271 Rev=01.08
S:  Manufacturer=ATHEROS
S:  Product=USB2.0 WLAN
S:  SerialNumber=12345
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#=0x0 Alt= 0 #EPs= 6 Cls=ff(vend.) Sub=00 Prot=00 Driver=ath9k_htc
but the code

Code: Select all

 awk '/0a12/' RS=" 
gives me this:

Code: Select all

>
And how to try another kernel? should I install a new Linux mint for that?
JeremyB
Level 21
Level 21
Posts: 12561
Joined: Fri Feb 21, 2014 8:17 am

Re: Bluetooth controller issue

Post by JeremyB »

Was the bluetooth plugged in when you ran the command?
User avatar
nukeCrayon
Level 1
Level 1
Posts: 34
Joined: Fri Apr 09, 2021 1:07 am
Location: Quezon City, NCR, Philippines

Re: Bluetooth controller issue

Post by nukeCrayon »

JeremyB wrote:
Sun May 30, 2021 12:19 pm
Was the bluetooth plugged in when you ran the command?
its not so heres the code again when its plugged:

Code: Select all

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=05.04
S:  Manufacturer=Linux 5.4.0-73-generic ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=0000:00:1a.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 4
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=0024 Rev=00.00
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=05.04
S:  Manufacturer=Linux 5.4.0-73-generic ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=0000:00:1d.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 6
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=8087 ProdID=0024 Rev=00.00
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  9 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0a12 ProdID=0001 Rev=25.20
S:  Product=CSR8510 A10
C:  #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I:  If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

T:  Bus=02 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#=  3 Spd=480 MxCh= 2
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
P:  Vendor=056a ProdID=0395 Rev=01.00
S:  Manufacturer=Wacom Co., Ltd.
S:  Product=Cintiq 16 HUB
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=2mA
I:  If#=0x0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub

T:  Bus=02 Lev=03 Prnt=03 Port=00 Cnt=01 Dev#=  6 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=056a ProdID=0390 Rev=01.01
S:  Manufacturer=Wacom Co.,Ltd.
S:  Product=Cintiq 16
S:  SerialNumber=0EQ00X1002930
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

T:  Bus=02 Lev=03 Prnt=03 Port=01 Cnt=02 Dev#=  8 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0403 ProdID=6014 Rev=09.00
S:  Manufacturer=FTDI
S:  Product=Single RS232-HS
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#=0x0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio

T:  Bus=02 Lev=02 Prnt=02 Port=02 Cnt=03 Dev#=  4 Spd=1.5 MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=1c4f ProdID=0026 Rev=01.10
S:  Manufacturer=SIGMACHIP
S:  Product=USB Keyboard
C:  #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=98mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
I:  If#=0x1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

T:  Bus=02 Lev=02 Prnt=02 Port=03 Cnt=04 Dev#=  5 Spd=1.5 MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=093a ProdID=2510 Rev=01.00
S:  Manufacturer=PixArt
S:  Product=USB Optical Mouse
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#=0x0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid

T:  Bus=02 Lev=02 Prnt=02 Port=05 Cnt=05 Dev#=  7 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs=  1
P:  Vendor=0cf3 ProdID=9271 Rev=01.08
S:  Manufacturer=ATHEROS
S:  Product=USB2.0 WLAN
S:  SerialNumber=12345
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#=0x0 Alt= 0 #EPs= 6 Cls=ff(vend.) Sub=00 Prot=00 Driver=ath9k_htc
JeremyB
Level 21
Level 21
Posts: 12561
Joined: Fri Feb 21, 2014 8:17 am

Re: CSR8510 A10 Bluetooth controller issue

Post by JeremyB »

See if this helps

Code: Select all

sudo modprobe -r btusb && sleep 10 && sudo modprobe btusb reset=1
It might actually need the 5.8 kernel from Update Manager/View/linux kernels
User avatar
all41
Level 18
Level 18
Posts: 8438
Joined: Tue Dec 31, 2013 9:12 am
Location: Computer, Car, Cage

Re: CSR8510 A10 Bluetooth controller issue

Post by all41 »

I opened the dongle to find the chip id. Looks to have been deliberately obfuscated, but under microscope
and certain lighting I read UF 9679
With that I found a pertinent link on how to make it work.
https://gist.github.com/nevack/6b36b82d ... 9124840a07
There is an image on that link that is exactly like my FAKE dongle
Everything is difficult before it gets easy.
JeremyB
Level 21
Level 21
Posts: 12561
Joined: Fri Feb 21, 2014 8:17 am

Re: CSR8510 A10 Bluetooth controller issue

Post by JeremyB »

Code: Select all

sudo awk -vRS= '/Vendor=0a12/{print $0,"\n"}' /sys/kernel/debug/usb/devices
Post results
User avatar
nukeCrayon
Level 1
Level 1
Posts: 34
Joined: Fri Apr 09, 2021 1:07 am
Location: Quezon City, NCR, Philippines

Re: CSR8510 A10 Bluetooth controller issue

Post by nukeCrayon »

JeremyB wrote:
Sun May 30, 2021 3:26 pm

Code: Select all

sudo awk -vRS= '/Vendor=0a12/{print $0,"\n"}' /sys/kernel/debug/usb/devices
Post results

Code: Select all

T:  Bus=02 Lev=02 Prnt=02 Port=00 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=0a12 ProdID=0001 Rev=25.20
S:  Product=CSR8510 A10
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=81(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=02(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=82(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=02(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=82(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=02(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=82(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=02(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
E:  Ad=82(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=02(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
E:  Ad=82(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=02(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
E:  Ad=82(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms 
I also tried updating the kernel. it is version 5.8.0-53 now. But it is still not pair.
User avatar
nukeCrayon
Level 1
Level 1
Posts: 34
Joined: Fri Apr 09, 2021 1:07 am
Location: Quezon City, NCR, Philippines

Re: CSR8510 A10 Bluetooth controller issue

Post by nukeCrayon »

all41 wrote:
Sun May 30, 2021 3:03 pm
I opened the dongle to find the chip id. Looks to have been deliberately obfuscated, but under microscope
and certain lighting I read UF 9679
With that I found a pertinent link on how to make it work.
https://gist.github.com/nevack/6b36b82d ... 9124840a07
There is an image on that link that is exactly like my FAKE dongle
Trying to read this github.
JeremyB
Level 21
Level 21
Posts: 12561
Joined: Fri Feb 21, 2014 8:17 am

Re: CSR8510 A10 Bluetooth controller issue

Post by JeremyB »

nukeCrayon wrote:
Sun May 30, 2021 6:35 pm
JeremyB wrote:
Sun May 30, 2021 3:26 pm

Code: Select all

sudo awk -vRS= '/Vendor=0a12/{print $0,"\n"}' /sys/kernel/debug/usb/devices
Post results

Code: Select all

T:  Bus=02 Lev=02 Prnt=02 Port=00 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=0a12 ProdID=0001 Rev=25.20
S:  Product=CSR8510 A10
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=81(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=02(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=82(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=02(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=82(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=02(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=82(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=02(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
E:  Ad=82(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=02(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
E:  Ad=82(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=02(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
E:  Ad=82(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms 
I also tried updating the kernel. it is version 5.8.0-53 now. But it is still not pair.
Try this command again

Code: Select all

sudo modprobe -r btusb && sleep 10 && sudo modprobe btusb reset=1
User avatar
nukeCrayon
Level 1
Level 1
Posts: 34
Joined: Fri Apr 09, 2021 1:07 am
Location: Quezon City, NCR, Philippines

Re: CSR8510 A10 Bluetooth controller issue

Post by nukeCrayon »

Try this command again

Code: Select all

sudo modprobe -r btusb && sleep 10 && sudo modprobe btusb reset=1
I tried this code and it still can't pair. i also reboot it and still same result.

I tried to go back on the site https://shopee.ph/HdoorLink-Bluetooth-5 ... 4509518366 where I purchased the Bluetooth dongle and I found out it doesn't say it supports Linux.
Maybe that's why its not working now because this one works back when I'm in win7.
User avatar
Adriano_Müller
Level 1
Level 1
Posts: 12
Joined: Mon Aug 02, 2021 8:18 pm

CSR8510 A10 Bluetooth controller issue

Post by Adriano_Müller »

I'm having the same problem.
My report is viewtopic.php?t=373771
This is a possible solution https://unam.re/blog/fixing-chinese-blu ... ngle-linux
However I could not make It work, because in terms of instaling custom kernel, Im not the best choise for the job.
Would like to invite anyone to try to do that tutorial and share it so we can fix our Kernel in order to use this dongle.
Observation: The dongle works fine on Windows 10. And works fine.
Please help! ^_^
nukeCrayon wrote:
Mon May 31, 2021 8:03 pm
Try this command again

Code: Select all

sudo modprobe -r btusb && sleep 10 && sudo modprobe btusb reset=1
I tried this code and it still can't pair. i also reboot it and still same result.

I tried to go back on the site https://shopee.ph/HdoorLink-Bluetooth-5 ... 4509518366 where I purchased the Bluetooth dongle and I found out it doesn't say it supports Linux.
Maybe that's why its not working now because this one works back when I'm in win7.
Post Reply

Return to “Gaming”