Re: bluetooth problems Cambridge Silicon Radio

2021-03-25 Thread deloptes
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 rab

Re: bluetooth problems Cambridge Silicon Radio

2021-03-25 Thread Jeremy Ardley
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

Re: bluetooth problems Cambridge Silicon Radio

2021-03-25 Thread deloptes
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.

Re: bluetooth problems Cambridge Silicon Radio

2021-03-25 Thread Jeremy Ardley
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 disconne

Re: bluetooth problems Cambridge Silicon Radio

2021-03-25 Thread deloptes
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

2021-03-25 Thread Jeremy Ardley
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

Re: bluetooth problems Cambridge Silicon Radio

2021-03-24 Thread deloptes
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

2021-03-24 Thread Charles Curley
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 read