Cambridge Silicon Radio Bluetooth Driver Windows 7 X64 Service

I tried to connect an usb bluetooth dongle of this type on Ubuntu Karmic on a 64 bit system: Bus 006 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) This device doesn't work, I always get from the kernel this error: command tx timeout I tried this on 2 (different) x64 systems, with the stock kernel (2.6.31-14-generic) and the new 2.6.32-rc5 kernel. Both show the same behaviour. 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. When I tried the dongles (I have two of them) on a 32 bit system, everything worked perfectly. (Also Karmic) So I expect there is a bug somewhere in the 64 bit version. I looked throughout the whole google searchable part of the internet to find more information.

All people with a such-like problems had different causes apparently then mine, because none of the plentyful of 'tricks' didn't work. Hi Maarten, This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue?

Can you try with the latest development release of Ubuntu? ISO CD images are available from. If it remains an issue, could you run the following command from a Terminal (Applications- >Accessories- >Terminal). It will automatically gather and attach updated debug information to this report. Apport-collect -p linux 460743 Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue.

Vista Profile Pack is a software program developed by Cambridge Silicon Radio. BthFilterHelper.exe runs as a service named 'Bluetooth Feature Support'. Feb 14, 2008 - In the world of Bluetooth, there are 'chipset' makers and 'software'. CSR (Cambrisge Silicon Radio) BlueCore (ex. Sold under the name Azio, etc.). And it disables the built-in Microsoft Bluetooth Service (normally, this is not. Fable 2 pc rip torrent.

Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text.

Please let us know your results. Thanks in advance. [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.].

AplayDevices: **** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA NVidia], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/ controlC0: kamil 2610 F. Bam, I've tried it and didn't work. Maybe I need to install some package or configure something else. I'm running Ubuntu 10.10 64 bits and I put the computer in S3 through SSH using this command (after a 'sudo su'): echo -n mem > /sys/power/state I could see that the system went in sleep and then I start to press the buttons on the A2DP device, but the computer remains in sleep mode.

The only way to wake up the computer was to press the power button. This is a HTPC without keyboard and mouse. My dongle is: My A2DP device is: This dongle is working well. It's working too after the computer went back from the sleep mode. I'm telling this because I read somewhere that using 'usbcore. Autosuspend= 0' is a workarround, but this dongle doesn't need it.

If you need something else or do a more test, please let me know. I'm fighting the same issues with the same dongle. Mine looks exactly like the Sabrent unit, except the Sabrent name is missing. Lapdog ~ # lsusb Bus 002 Device 009: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) lapdog ~ # uname -a Linux lapdog 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux Here's the interesting part. If I plug the dongle into my laptop while my Microsoft Bluetooth Mouse is trying to associate, I can pair with the mouse, and everything works OK. But if I reboot, move the dongle, etc., then things don't work any more until I put the mouse back in pairing mode, plug in the dongle, and re-associate them.

When the Linux bluetooth stack is loading after the dongle goes in, apparently the 'hey, this device is trying to associate' message causes the software not to use the code that causes the error. It's quite disappointing that all over the web, people report these issues, the hardware works fine in that other OS, but 3 years later we have no fix for LInux. Hi to everyone, (for Gustavo. I sent you a message abput the same argument. Sorry for the duplication) I hope there are new about this bug I am using a board (VDX6318D) by Icop Technologies with their linux 2.6.34. 1-vortex86- sg. The dongle I use is 'Sena Parani UD100' (that uses Cambridge Silicon Radio).