![]() For more information, see Kernel Bug 60824. There is a patch available for newer versions. The device ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)has a regression bug, and currently only works in the kernel version ≤ 3.9.11. If what says at ArqchWiki is true, I'm screwed: Bluetooth: hci0: CSR: Unbranded CSR clone detected adding workarounds. usb 3-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 has removed the direct-download link and offers this page for informational purposes only. I compressed and uploaded the drivers which are located at this link as an additional source for driver/install files. usb 3-1: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 12 Here is a picture of the install disk that came with the Bluetooth 4.0 CSR (Cambridge Silicon Radio) usb dongle I purchased. usb 3-1: new full-speed USB device number 7 using xhci_hcd Maybe because of closed source drivers, I would guess.ĭmesg: usb 3-1: USB disconnect, device number 6 I just discovered it doesn't work even on windows.ĭid anyone find any solution to make CSR dongle work on modern kernels? I'm curious why it works on windows, but not on Linux. There are several fake dongles out there and the kernel devs can't cover them all, sadly. Cambridge silicon radio ltd all drivers A musically inclined entrepreneur thinks outside the box. Bluetooth drivers, that can help resolve bluetooth issues. Usb\vid03ee&pid6438&rev0373 usb\vid03ee&pid6440&rev0309, cambridge silicon radio / mitumi electric. I'll come back here if I get any positive results. Hardware id, chip/hardware manufacturer, device. Luckily, I have some experience compiling kernels and patching them. There are some patches out there and an active discussion about this at. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |