Re: bluetooth problems Cambridge Silicon Radio
Jeremy Ardley wrote: > I have seen several references to the Cambridge Radio bug, with at least > some patches being generated back in 2013 and in 2020, none of which > seem to have made it to the kernel. > > Given how hard it is to compile packages on debian without going down > never ending rabbit holes of dependencies, it may be easier for me to > just get a USB dongle that is known to work in the current distro. > > Any suggestions on USB dongles that are known to work? Preferably V5. 1. this is the kernel - you do not have many dependencies and it is not hard to compile. 2. I have one that reports the same ID but could be V3 or V4 - I bought it many many years ago. 3. it could be this is a new generation (V5) that does not work. 4. Look forward to buy genuine one - there is a lot of crap made in China out there. Some other options pop up in my mind. Are you using it on USB3 port? Is it a LE device? there are rumors that both were causing problems?
Re: bluetooth problems Cambridge Silicon Radio
On 26/3/21 8:33 am, deloptes wrote: Jeremy Ardley wrote: Mar 25 15:30:46 client.bronzemail.com kernel: usb 1-3.2: new full-speed USB device number 7 using xhci_hcd Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Did you by chance read this? I wonder if it is something with the stock kernel https://askubuntu.com/questions/1098165/bluetoothctl-cant-find-default-device-but-hciconfig-hcitool-can-see-my-device https://askubuntu.com/questions/1205962/bluetooth-dongle-problem I have seen several references to the Cambridge Radio bug, with at least some patches being generated back in 2013 and in 2020, none of which seem to have made it to the kernel. Given how hard it is to compile packages on debian without going down never ending rabbit holes of dependencies, it may be easier for me to just get a USB dongle that is known to work in the current distro. Any suggestions on USB dongles that are known to work? Preferably V5. Jeremy OpenPGP_signature Description: OpenPGP digital signature
Re: bluetooth problems Cambridge Silicon Radio
Jeremy Ardley wrote: > Mar 25 15:30:46 client.bronzemail.com kernel: usb 1-3.2: new full-speed > USB device number 7 using xhci_hcd > Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device > found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 > Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device > strings: Mfr=0, Product=2, SerialNumber=0 Did you by chance read this? I wonder if it is something with the stock kernel https://askubuntu.com/questions/1098165/bluetoothctl-cant-find-default-device-but-hciconfig-hcitool-can-see-my-device https://askubuntu.com/questions/1205962/bluetooth-dongle-problem
Re: bluetooth problems Cambridge Silicon Radio
On 25/3/21 3:18 pm, deloptes wrote: Jeremy Ardley wrote: sudo rfkill ID TYPE DEVICE SOFT HARD 2 bluetooth hci0 unblocked unblocked what says dmesg -T when you plugin the dongle? what says syslog (journalctl)? sudo dmesg -T [Thu Mar 25 15:30:43 2021] usb 1-3.2: USB disconnect, device number 6 [Thu Mar 25 15:30:46 2021] usb 1-3.2: new full-speed USB device number 7 using xhci_hcd [Thu Mar 25 15:30:47 2021] usb 1-3.2: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 [Thu Mar 25 15:30:47 2021] usb 1-3.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [Thu Mar 25 15:30:47 2021] usb 1-3.2: Product: BT DONGLE10 (unplug and replug dongle) sudo journalctl -xe Mar 25 15:30:43 client.bronzemail.com systemd[1]: Stopped target Bluetooth. -- Subject: A stop job for unit bluetooth.target has finished -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A stop job for unit bluetooth.target has finished. -- -- The job identifier is 7697 and the job result is done. Mar 25 15:30:43 client.bronzemail.com systemd[1]: Started Load/Save RF Kill Switch Status. -- Subject: A start job for unit systemd-rfkill.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit systemd-rfkill.service has finished successfully. -- -- The job identifier is 7689. Mar 25 15:30:46 client.bronzemail.com kernel: usb 1-3.2: new full-speed USB device number 7 using xhci_hcd Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Mar 25 15:30:47 client.bronzemail.com kernel: usb 1-3.2: Product: BT DONGLE10 Mar 25 15:30:47 client.bronzemail.com systemd-udevd[8630]: Process '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 6 e0' failed with exit code 1. Mar 25 15:30:47 client.bronzemail.com systemd[1]: Reached target Bluetooth. -- Subject: A start job for unit bluetooth.target has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit bluetooth.target has finished successfully. -- -- The job identifier is 7698. Mar 25 15:30:52 client.bronzemail.com systemd[1]: systemd-rfkill.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-rfkill.service has successfully entered the 'dead' state. -- Jeremy OpenPGP_signature Description: OpenPGP digital signature
Re: bluetooth problems Cambridge Silicon Radio
Jeremy Ardley wrote: > sudo rfkill > ID TYPE DEVICE SOFT HARD > 2 bluetooth hci0 unblocked unblocked what says dmesg -T when you plugin the dongle? what says syslog (journalctl)?
Re: bluetooth problems Cambridge Silicon Radio
On 25/3/21 2:45 pm, deloptes wrote: Jeremy Ardley wrote: Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) these are widely spread I have the same (at least from the usb id) Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) what says rfkill list ??? sudo rfkill ID TYPE DEVICE SOFT HARD 2 bluetooth hci0 unblocked unblocked -- Jeremy OpenPGP_signature Description: OpenPGP digital signature
Re: bluetooth problems Cambridge Silicon Radio
Jeremy Ardley wrote: > Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth > Dongle (HCI mode) these are widely spread I have the same (at least from the usb id) Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) what says rfkill list ???
Re: bluetooth problems Cambridge Silicon Radio
On Thu, 25 Mar 2021 12:05:19 +0800 Jeremy Ardley wrote: > lsusb ... > Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd > Bluetooth Dongle (HCI mode) It doesn't hurt to search on the word Linux and the USB ID: https://duckduckgo.com/?q=linux+0a12:0001 That should give you some reading to do. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/ pgpIiq3KBRStw.pgp Description: OpenPGP digital signature
bluetooth problems Cambridge Silicon Radio
I've just got a new bluetooth dongle that says V5.0 on the case. I think it uses Cambridge Silicon Radio lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 0c45:6340 Microdia Camera Bus 003 Device 002: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0480:0900 Toshiba America Inc Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub sudo hcitool dev Devices: bluetoothctl Agent registered [bluetooth]# show No default controller available Running hciconfig and monitoring with hcidump I get sudo hciconfig hci0 up Can't init device hci0: Invalid argument (22) sudo hcidump -X HCI sniffer - Bluetooth packet analyzer ver 5.50 device: hci0 snap_len: 1500 filter: 0x < 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: 0xbf 0x3e 0x4d 0xfa 0xdb 0x3d 0x7b 0xc7 < 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: 5.0 (0x9) HCI Revision: 0x810 LMP Version: 5.0 (0x9) LMP Subversion: 0x2312 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:13 < 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:8 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 0x00 < 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 'CSR8510 A10.' < 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 0x < 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 : 00 02 .. < 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 0x12 Error: Invalid HCI Command Parameters On kernel Linux client.bronzemail.com 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux Any suggestions on how to progress? -- Jeremy OpenPGP_signature Description: OpenPGP digital signature
