

- #Csr 41b14 driver driver#
- #Csr 41b14 driver Patch#
- #Csr 41b14 driver Bluetooth#
- #Csr 41b14 driver windows#
+ * the device was suspended at least once (yes, really). * the device was suspended at least once (yes, really). Their bulk RX endpoint will never report any data unless * These controllers are really messed-up. * Special workaround for these BT 4.0 chip clones, and potentially more:
#Csr 41b14 driver Bluetooth#
* early Bluetooth 1.1 device from -1952,16 +1954,16 static int btusb_setup_csr(struct hci_dev *hdev) * Clear the reset quirk since this is not an actual + set_bit(HCI_QUIRK_NO_SUSPEND_NOTIFIER, &hdev->quirks) + set_bit(HCI_QUIRK_BROKEN_FILTER_CLEAR_ALL, &hdev->quirks) Set_bit(HCI_QUIRK_BROKEN_ERR_DATA_REPORTING, &hdev->quirks) Set_bit(HCI_QUIRK_BROKEN_STORED_LINK_KEY, &hdev->quirks) diff -git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c 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.
#Csr 41b14 driver Patch#
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: Opcode 0x c01 failed: -110 Bluetooth: hci0: command 0x0c01 tx timeout Bluetooth: BNEP socket layer initialized Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround

Bluetooth: hci0: CSR: Unbranded CSR clone detected adding workarounds and force-suspending once.
#Csr 41b14 driver driver#
usbcore: registered new interface driver btusb Bluetooth: L2CAP socket layer initialized Bluetooth: HCI device and connection manager initialized 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.
#Csr 41b14 driver windows#
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.
