cambridge silicon radio bluetooth dongle driver

#CAMBRIDGE SILICON RADIO BLUETOOTH DONGLE DRIVER PATCH#

* 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.

#CAMBRIDGE SILICON RADIO BLUETOOTH DONGLE DRIVER PATCH#

Bluetooth: hci0: Opcode 0x c5a failed: -110Īnyone who needs a patch for linux 5.15.x LTS series, can use this patch. Bluetooth: hci0: command 0x0c5a tx timeout Bluetooth: hci0: HCI Set Event Filter command not supported. Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported. I`m running Fedora 37 with kernel 6.0.7-301, unmodified.Īlso getting errors, it used to work just fine on Fedora 35 and on older kernels in other distros. Bluetooth: hci0: Opcode 0x c03 failed: -110 Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround 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 NET: Registered PF_BLUETOOTH protocol family Have tried with 6.0.7-060007-generic and still same output Bluetooth: Core ver 2.22 Lsusb: Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Have installed 5.17.1-051701-generic on Ubuntu 22.04.1 and still have the problem Often you can fix a dongle by commenting out something or submitting an one-liner. Just make the jump and learn, even if it's through hacks and experimentation it will help getting to the correct solution if you stick around. Be the change you want to see in the world, if everyone did what I did with the hardware they own everything would be fixed. I'm just a random Linux user doing it as a hobby after arriving at the same place, there is no ETA. I bought one of the Barrot ones that still don't work and ended up with a duplicate that worked out of the box already. I can't really justify buying a sack of random AliExpress dongles and wait months for them to arrive and cross my fingers so that the seller is kind enough to not swap the advertised PCB (which happened two months ago, getting specific controllers is crazy hard) just to submit more patches. Well, it's fixed for all the dongles I have and the ones I bought just to fix more Linux kernel issues.

Cambridge silicon radio bluetooth dongle driver