Nov 03 13:02:57 akshay-System-Product-Name systemd: Started Bluetooth service. Nov 03 13:02:57 akshay-System-Product-Name bluetoothd: Bluetooth daemon 5.53 Nov 03 13:02:57 akshay-System-Product-Name systemd: Starting Bluetooth service. Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Tue 13:02:57 IST 16min ago In HCI mode, I can see it Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) What am I doing wrong? systemctl bluetooth status is running. It's getting shown in lsusb, but not shown in bluetoothctl. = Note: Bluetooth subsystem version 2.22 MGMT Open: bluetoothd (privileged) version 1.I want to connect my bluetooth headsets to Ubuntu 20.04. On Arch Linux 5.16.1-arch1-1 my ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) worked after simple solution ~ $ sudo btmon I would like to thank and congratulate everyone involved in this gist, you are clearly putting a lot of effort into making this BT dongle work. I have a spare machine for compiling and testing some paches, please let me know if I can test any new version of your patchset, or if I can provide more info about my device. I loaded the btusb module using reset=1 and enable_autosuspend=0. My device has a different bcdDevice, but it's still recognized as a 'fake' one: Device Descriptor: Bluetooth: hci0: setting interface failed (110) Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround Sorry, something went just tested your patch on top of 5.16-rc8, but it still fails for me: Bluetooth: hci0: CSR: Unbranded CSR clone detected adding workarounds and force-suspending once. This is how I figured out what was missing after several attempts. To anyone who wants to try and is a Linux beginner like me, I strongly encourage you to modprobe the module after you finish installing and check the outputs with dmesg | grep btusb or something. I'm using 5.15.7-1-MANJARO x86_64, though I also tested it with kernel 5.14.21-2 and it worked. IdProduct 0x0001 Bluetooth Dongle (HCI mode) IdVendor 0x0a12 Cambridge Silicon Radio, Ltd config file to disable module signing and to tinker with version magic before compilation.ĭon't know if it helps but here's info about my device with lsusb: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)Ĭouldn't open device, some information will be missing I was using a newer version of the kernel anyways (5.15.7), so the force-suspend patch was already in as well. What worked for me was basically using the script above to automate kernel module compilation, but I modified it to apply the HCI_FLT_CLEAR_ALL patch instead of the old patch. On dmesg the product name is BT DONGLE10.Īs for the suspend workaround: I do get " hci0: CSR: Failed to suspend the device for our Barrot 8041a02 receive-issue workaround" removing that workaround doesn't affect my device, but it doesn't seem to do any harm afaict (other than having an error in dmesg, maybe this can be replaced by a warning instead)įeel free to add Tested-by: Gonzalo Tornaría if that helps in any way to get this merged.Īfter a couple days banging my head around this, I finally was able to get my CSR "5.0" dongle to work. Some info about my dongle: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)įeatures: 0xbf 0x3e 0x4d 0xfa 0xdb 0x3d 0x7b 0xc7 I hope this can be merged in the mainline kernel. I've submitted a PR to the kernel package on void linux with this patch added ( void-linux/void-packages#34359) and I'm using this kernel on my main desktop. My bt dongle needs the patch Bluetooth: Add a new quirk to skip "HCI_FLT_CLEAR_ALL" proposed by am testing on 5.15.6 which already contains all the suspend patches the patch exactly as in the comment applies cleanly and works.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |