0a12 0001 Driver
Merri Coffill
Same problem with 0a12/0001 under Ubuntu 20.04.4. My second computer works with debian 11 bullseye, where the adapter works fine. There I found an installed package which isn't installed in Ubuntu 20.04 by default. So in 20.04 try installing the bluetooth package. Works for Vendor 0a12/0001.Open a terminal and type sudo apt install bluetooth
The auto-suspension of USB ports can interfere with Bluetooth USB dongles. While auto-suspend helps to save power and the devices should wake up quickly on their own can this fail and so degrade the Bluetooth connectivity. By default does the kernel suspend USB ports after 2 seconds. This can be disabled either for all USB ports or only for individual ones, and the Bluetooth USB driver has got a parameter, which specifically controls this for USB-attached Bluetooth dongles. For example, to see the current status:
When you are already recompiling the kernel then it is likely best to disable it with the Bluetooth USB kernel module by setting the configuration parameter CONFIG_BT_HCIBTUSB_AUTOSUSPEND to N or by commenting it out in the kernel config file. This will cause the Bluetooth USB driver to disable auto-suspend by default for every port it finds a matching device on, and leaves all other USB devices as they were.
I had issues with two different 0a12:0001 Cambridge Silicon Radio. Both were TRENDnet TBW-106UB. I purchased two new USB Bluetooth Dongles, and haven't had an issue since. I've used the new dongles with Ubuntu 18.04 and 19.10.
The version was updated is 6.1.8-060108-generic . Previous was 5.15.Although I installed many bluetooth drivers/apps like blueman before, I dont know if they was necessary. Now the blue man manager is showing on tray as well the bluetooth of ubuntu configuration
Hi guys, i do not know if i can post it in there, but i bought a generic bluetooth dongle (0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle to be precise) and it's refuses to work on my pop_os with 5.16 kernel version.
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 5.17 and < 6.0. For more information, see Kernel Bug 60824.
If you cannot find the latest version driver (or firmware) for Windows, you can copy the latest firmware file /usr/lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin.xz from Arch Linux and extract to Windows (e.g. C:\WINDOWS\system32\DRIVERS\, you can find the firmware file path in the device manager on Windows).
Hey Lone_Wolf...Thanks for the reply. I've update the bios to the newest available as per your recommendation. I've installed the Intel microcode and it is set up for early loading. I've run a new probe, but I don't see any changes to the acpi errors. Not sure if you were asking me to confirm the dongle info, so here it is; "Bus 001 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)". So far, no change. Dongle still doesn't start with a reboot. Still need to suspend the computer and wake it up to enable.
Most of cheap Bluetooth dongles from Aliexpress do not work natively in Linux. I have been looking the source code of Bluetooth Linux driver looking for this problem and I have found that it is because some of these dongles are blacklisted because they are using for malicious actions. Thus if you want to use one of these dongles you should remove this code which blacklists the dongle.
Note: From I read that the Realtek driver for the rtl8761b firmware should work with this, but i am new to linux dont know how to add that driver with terminal, so i am looking for a .pet file for ease.
Oh you are right actually i thought that as i needed to install driver for my wifi adapter i need it for my bluetooth adapter too . But as i used Janky bluetooth it listed my device so i get to know that my bluetooth adapter is working
I own a USB Dongle 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode). I am not able to scan devices. I plugged in the USB device in and out, restarted the my laptop, restarted the service and still will not be recognized by Wireshark or any other Bluetooth utility.
It works on whatever kernel 15.1 has now, and I also have the 5.5.2-2.g994cf1f-default from kernel-stable repo.
and yes you will need to compile everytime you have a kernel update, or ask one of the regulars here if they can package that thing.
I forgot to mention that I have the kernel-firmware installed as well, there was a version of that package was not able to use the wireless driver but I think it was fixed now.
Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface is the bluetooth part of the combined bluetooh/wifi chip on that netbook.
Device 003: ID 04fc:2802 Sunplus Technology Co., Ltd HD Camera is the internal netbook webcam.
Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) is an external bluetooth stick, which I use due to incompatibility of the internal chip with my bluetooth headset.
As you can see the USB driver has been used by internal chip AND the external stick. I blacklisted the internal chip (the device, not the module for obvious reasons) to use only the stick. So the btusb driver is N/A (not available) for the Intel chip.
This is interesting. I have found Intel wifi cards to be the gold standard in terms of plug and play functionality with linux. You are most likely dealing with a hardware issue as I have a near flawless bluetooth experience with the AC 7265 + BT 4.2 in my laptop and the AX200 + BT 5.0 in my desktop. I actually used the spare AC 7265 to replace the awful realtek wireless N + BT 4.0 1x1 adapter my laptop came with that required drivers from the AUR to work properly.
The usb\vid_0a12&pid_0001&rev_2520 hardware ID is a Cambridge Silicon Radio Bluetooth dongle. Download the Bluetooth driver here. Likewise this is the Bluetooth Dongle (HCI mode). See below how the Hardware ID is identified and then download the driver on here.
Likewise lets breakdown the usb\vid_0a12&pid_0001&rev_2520 hardware ID on here. We will now see what the Hardware ID can tell us about what you are looking for. In addition we already know that this was made by Cambridge Silicon Radio or CSR which is Bluetooth.
Additionally the Vendor ID (VID) 0a12 identifies the hardware vendor which we know is CSR. Again we all know that CSR made most of the Bluetooth hardware on the market. The Vendor 0a12 is the Cambridge Silicon Radio, Ltd vendor code. In addition the Product ID (PID) pid_0001.
Likewise this identifies the product as the Bluetooth Dongle (HCI mode) device. Note also the there is a Revision Number (REV) rev_2520. So we now know that this Hardware ID is for the CSR Bluetooth Dongle (HCI mode). This is from the CSR Bluetooth products. The full installation and troubleshooting can be found under the page Bluetooth CSR 5.0 dongle driver.
Similarly, there are several unique USB device identifiers that play crucial roles in modern technology. One such identifier is usb\vid_0a12&pid_0001&rev_8891 (CSR Bluetooth), denoting a Bluetooth device manufactured by CSR. Likewise, the code usb\vid_0403&pid_6001&rev_0600 (UART) represents Universal Asynchronous Receiver-Transmitter, a fundamental component in communication systems.
If your use case could work with an extension cable, then you might even look at an adapter based on the new mt7921au chipset (WiFi 6e). The driver is in 22.03... 7921u, however the firmware is in the driver 7921e so you either have to also install 7921e or manually install the firmware. There is a bug posted requesting the firmware be moved to common so this will likely be fixed at some point.
I've been using a cheap "CSR V4.0" Bluetooth dongle with my Rpi4 to increase the signal range. It worked great with LibreELEC 9.x, but does not with LE10. The LED on the dongle does not light up, so it appears that the driver is not being loaded, or that the device isn't being recognized for some reason.
Is there something I can do to fix this?
mrogeriodf Could be an issue with your computer, in terms of drivers you have installed. Uninstall any drivers associated with that USB device or try booting into safe mode on your PC or use a secondary PC instead. You have the exact same Bluetooth dongle I have.
0aad45d008