Cambridge Silicon Radio CSR 4.0 USB Bluetooth Dongle I had to solve this problem once and for all.įrustrated, I headed to Amazon and set out to find a new Bluetooth 4.0 USB dongle. I recently had a renewed interest in training courses, so I bought an awesome set of Hiearcool L-1 Bluetooth Headphones. Until a few days ago, I lived with this problem because it was not a big deal. Devices would stop working, and I would need to remove them from the system and add them again along with several other tap dances to keep things working. Unfortunately, the Bluetooth 3.0 on the Thinkpad was flaky. Life was good until about two years ago when I decided I wanted to regularly pair my Amazon Tap, Sharkk Boombox, and a pair of Jabra Bluetooth earbuds to the system. When it was new from the factory, I installed a Samsung 500Gb SSD to eliminate the weakest link, a Western Digital mechanical hard drive. diff -git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.I have an older Lenovo Thinkpad W520 notebook computer running Windows 10 Professional that, for the most part, has been an ultra-reliable workhorse. diff file and apply it on the kernel source. I just combined them and made it compatible with linux 5.15.x LTS. Credit goes to for creating the original patches. You should use Linux 5.17.1.Īnyone who needs a patch for linux 5.15.x LTS series, can use this patch. Linux 5.17 still needs the v4 patches to be applied manually. dmesg report of second dongle: usb 1-4: USB disconnect, device number 4 I plug another dongle which has exactly the same housing (CSR 4.0 on both), and it works. I updated to linux 5.17, and my dongle is still not working :(( dmesg report: usb 1-4: new full-speed USB device number 4 using xhci_hcd usb 1-4: new full-speed USB device number 5 using xhci_hcd I plug another dongle which has exactly the same cover (CSR 4.0 on both), and it works.ĭmesg report of second dongle: usb 1-4: USB disconnect, device number 4 Bluetooth: hci0: command 0x0c01 tx timeout Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround usbcore: registered new interface driver btusb NET: Registered PF_BLUETOOTH protocol family usb 1-4: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-4: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 usb 1-4: Duplicate descriptor for config 1 interface 1 altsetting 5, skipping I updated to linux 5.17, and my dongle is still not working :((ĭmesg report: usb 1-4: new full-speed USB device number 4 using xhci_hcd I have no idea if they like or despise it and it doesn't even build against the current sources anymore. P.S.: How did you get the kernel guys to respond to you? I have recently made my first kernel patch that even made it into their so far, no one has actually made a single comment to me about it. What's worse, trying them in a windows virtual machine actually worked :( Anyways, you did it! I was so happy that I thought I just had to read through the git log and find out who fixie wixied this fucksy upsy! However, none seemed to cover this specific hardware version. I have read about how support for these devices is known problem and there are even blog articles with kernel patches. I knew it was a gamble from the beginning. Never read through this whole long thread, but thanks so much senpai! I just updated to linux 5.17 and my dongle works now! I bought a metric ton of them (like 8 or whatever) on aliexpress because they were like 2€s and I keep losing my normal 10€ dongles. Bluetooth: hci0: setting interface failed (110) Bluetooth: hci0: CSR: Failed to suspend the device for our Barrot 8041a02 receive-issue workaround Manufacturer: Cambridge Silicon Radio (10) LMP version: Bluetooth 5.0 (0x09) - Subversion 8891 (0x22bb) Read Local Version Information (0x04|0x0001) ncmd 1 ![]() ![]() ![]() HCI Event: Command Complete (0x0e) plen 12 #2 6.857698 However the dmesg logs are slightly different Bluetooth: hci0: Opcode 0x c01 failed: -110 Bluetooth: BNEP socket layer initialized Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP (Ethernet Emulation) ver 1.3 ![]() Bluetooth: hci0: CSR: Unbranded CSR clone detected adding workarounds and force-suspending once. Bluetooth: L2CAP socket layer initialized Bluetooth: HCI device and connection manager initialized Try deleting these lines and recompiling your bluetooth-next kernel. Either the insides are different or they don't get along with certain USB ports/controllers.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |