cambridge silicon radio bluetooth dongles

#Cambridge silicon radio bluetooth dongles 64 Bit#
#Cambridge silicon radio bluetooth dongles driver#
#Cambridge silicon radio bluetooth dongles 32 bit#
#Cambridge silicon radio bluetooth dongles software#
#Cambridge silicon radio bluetooth dongles Bluetooth#

Oct 26 00:46:19 Tolnedra bluetoothd: Can't init device hci0: Connection timed out (110)

#Cambridge silicon radio bluetooth dongles driver#

Oct 26 00:45:59 Tolnedra kernel: usbcore: registered new interface driver btusb

#Cambridge silicon radio bluetooth dongles Bluetooth#

Oct 26 00:45:59 Tolnedra kernel: Bluetooth: Generic Bluetooth USB driver ver 0.5 Oct 26 00:45:59 Tolnedra bluetoothd: HCI dev 0 registered All people with a such-like problems had different causes apparently then mine, because none of the plentyful of 'tricks' didn't work. I looked throughout the whole google searchable part of the internet to find more information.

#Cambridge silicon radio bluetooth dongles 64 Bit#

So I expect there is a bug somewhere in the 64 bit version.

#Cambridge silicon radio bluetooth dongles 32 bit#

When I tried the dongles (I have two of them) on a 32 bit system, everything worked perfectly. I also tried this with the stock bluez/libbluetooth etc and with the newest version from the Blueman PPA repository, also all with the same result.

I tried this on 2 (different) 圆4 systems, with the stock kernel (2.6.31-14-generic) and the new 2.6.32-rc5 kernel. This device doesn't work, I always get from the kernel this error: command tx timeout SUBSYSTEM='usb', ATTRS='0'Īfter a reboot the internal chip was deactivated and the stick can be used.I tried to connect an usb bluetooth dongle of this type on Ubuntu Karmic on a 64 bit system:īus 006 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) The file is called les # Intel Bluetooth should be disabled To blacklist the internal device I added a rule in /etc/udev/rules.d/.

Network controller : Intel Corporation Wireless 3165 (rev 91) The wifi part of the combined chip is shown as pci and because it has a different vendor and device ID not blacklisted and still active. So the btusb driver is N/A (not available) for the Intel chip. I blacklisted the internal chip (the device, not the module for obvious reasons) to use only the stick. inxi -Eīluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: N/Aĭevice-2: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusbĪs you can see the USB driver has been used by internal chip AND the external stick. Bluetooth wireless interface is the bluetooth part of the combined bluetooh/wifi chip on that netbook.ĭevice 003: ID 04fc:2802 Sunplus Technology Co., Ltd HD Camera is the internal netbook webcam.ĭevice 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. Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubĭevice 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interfaceīus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. RTS5129 Card Reader Controllerīus 001 Device 004: ID 8087:0a2a Intel Corp. ELAN:Fingerprintīus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp.

Some internal devices (bluetooth, webcams etc) are often displayed as USB devices and for that reason USB driver is used.īus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 003: ID 04fc:2802 Sunplus Technology Co., Ltd HD Cameraīus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 001 Device 007: ID 0911:2188 Philips Speech Processing USB Keyboardīus 001 Device 006: ID 04f3:0c16 Elan Microelectronics Corp. Is it normal for a PCIe wireless card to have Bluetooth loaded by btusb Also if it is worth noting, Bluetooth coexistence is enabled. And if the loaded module is incorrect, any guidance to loading the proper one is appreciated.

#Cambridge silicon radio bluetooth dongles software#

Is it normal for a PCIe wireless card to have Bluetooth loaded by btusb? I would like to verify whether this is a hardware or software issue so I can consider upgrading my hardware if necessary. Using the btusb module has unusable connections quality with the only device somewhat functional is a Bluetooth keyboard (probably due to its low bandwidth). This is after disconnecting all USB Bluetooth dongles so it is referring to the PCIe card.Īdditionally, the module loaded for this is btusb and trying to disable it completely disables Bluetooth functionality. But what I’m not sure if is right is that the Bluetooth of the same card shows up as a USB device.īus 001 Device 006: ID 8087:0a2a Intel Corp. Output of lspci:Ġ4:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)Īnd the kernel module used is listed as Kernel driver in use: iwlwifi. After having no luck with USB Bluetooth dongles, I decided to revisit my onboard PCIe WiFi/Bt module.