0a12:0001 Cambridge Silicon Radio Bluetooth Dongle not working

Bug #460743 reported by Maarten Fonville on 2009-10-25
272
This bug affects 53 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Undecided
Unassigned
dpkg
Invalid
Undecided
Unassigned
linux (Ubuntu)
Medium
Unassigned

Bug Description

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.

DMESG:
Oct 26 00:45:59 Tolnedra bluetoothd[1722]: HCI dev 0 registered
Oct 26 00:45:59 Tolnedra kernel: [235886.939096] Bluetooth: Generic Bluetooth USB driver ver 0.5
Oct 26 00:45:59 Tolnedra kernel: [235886.939226] usbcore: registered new interface driver btusb
Oct 26 00:46:19 Tolnedra bluetoothd[1722]: Can't init device hci0: Connection timed out (110)
Oct 26 00:46:20 Tolnedra NetworkManager: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/pan0, iface: pan0)
Oct 26 00:46:20 Tolnedra bluetoothd[1722]: bridge pan0 removed
Oct 26 00:46:20 Tolnedra bluetoothd[1722]: Stopping SDP server
Oct 26 00:46:20 Tolnedra bluetoothd[1722]: Exit
---
AlsaVersion:
 Advanced Linux Sound Architecture Driver Version 1.0.22.1.
 Compiled on Apr 14 2010 for kernel 2.6.32-21-generic (SMP).
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: maarten 1556 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'MID'/'HDA Intel MID at 0xf3f38000 irq 23'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,104383ce,00100004'
   Controls : 12
   Simple ctrls : 7
CheckboxSubmission: 3415c5cb481fb0dbb00abeaa1eb17e22
CheckboxSystem: b62ae224500b03a9fc2c9b6caf3feb14
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=113ebde9-392f-4d09-8142-e01a7e4fc4e1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: ASUSTeK Computer INC. 1101HA
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=fe2c3e7b-f1a4-4102-804a-5c06d5ef88e8 ro quiet splash mem=2000mb acpi_osi=Linux acpi_enforce_resources=lax
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Regression: No
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
Tags: lucid needs-upstream-testing
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev pulse pulse-access sambashare
dmi.bios.date: 11/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0322
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1101HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0322:bd11/05/2009:svnASUSTeKComputerINC.:pn1101HA:pvrx.x:rvnASUSTeKComputerINC.:rn1101HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1101HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Linux Tolnedra 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux

Ubuntu 2.6.31-14.48-generic

Jeremy Foshee (jeremyfoshee) wrote :

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 http://cdimage.ubuntu.com/releases/ .

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. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . 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.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

The bug is still valid, and as you can see it is also valid at my (new) 32bit laptop. So it is apparently not a 64 bit specific issue :-S

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
importance: Undecided → Medium
summary: - Cambridge Silicon Radio, Bluetooth Dongle doesnt work on 64 bit
+ Cambridge Silicon Radio, Bluetooth Dongle doesnt work

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.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 23'
   Mixer name : 'SigmaTel STAC9227'
   Components : 'HDA:83847618,102801f4,00100201'
   Controls : 32
   Simple ctrls : 22
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=39a09577-21b2-45b8-8227-f77c5967d7de
MachineType: Dell Inc Dimension C521
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: root=UUID=098171d7-bbd6-4d70-8f93-d58e76bd1750 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-21-generic N/A
 linux-firmware 1.26
Uname: Linux 2.6.31-21-generic x86_64
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 08/02/2007
dmi.bios.vendor: Dell Inc
dmi.bios.version: 1.1.11
dmi.board.name: 0HY175
dmi.board.vendor: Dell Inc
dmi.board.version: A03
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc
dmi.modalias: dmi:bvnDellInc:bvr1.1.11:bd08/02/2007:svnDellInc:pnDimensionC521:pvr:rvnDellInc:rn0HY175:rvrA03:cvnDellInc:ct3:cvr:
dmi.product.name: Dimension C521
dmi.sys.vendor: Dell Inc

Eugene San (eugenesan) on 2010-05-14
summary: - Cambridge Silicon Radio, Bluetooth Dongle doesnt work
+ [Lucid&Karmic] Cambridge Silicon Radio, Bluetooth Dongles doesnt work
summary: - [Lucid&Karmic] Cambridge Silicon Radio, Bluetooth Dongles doesnt work
+ [Lucid&Karmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
17 comments hidden view all 105 comments

There is a workaround: adding "usbcore.autosuspend=0" to Kernel command line.
But that solution unacceptable for portable machines and should be treated in Linux.

Robin Morero (robin-textalk) wrote :

Tried the workaround listed above "usbcore.autosuspend=0", and am afraid it didn't work for me. Symptoms are the same, "Connection timed out".

hassan121 (k7rata121) wrote :

in lucid too

Changed in linux:
status: Unknown → Confirmed
Changed in linux:
importance: Unknown → Medium
25 comments hidden view all 105 comments
Gustavo Spadari (gspadari) wrote :

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: http://www.sabrent.com/category/wireless/BT-USBT/
My A2DP device is: http://cgi.ebay.com/Bluetooth-2-0-A2DP-AVRCP-Stereo-Portable-Music-Receiver-/170620137671?pt=PDA_Accessories&hash=item27b9c0b0c7

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.

Mark Hobley (markhobley) wrote :

After opening up one of my dongles with a screwdriver, I discovered that there is a marking on the board "AS3620QA1". This appears to be a code for Accel Semiconductor, so the devices that are causing an error may not be made by Cambridge Silicon Radio after all, even though the devices list as Cambridge Silicon
Radio through lsusb.

ignacio (zamcan45) wrote :

Dear Mark,
I am sorry I cannot open my dongle with a screwdriver, it is the only one I have. But my dongle seems to work and it says that is a

ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth

"The only problem" is that once is connected does not appear as a possible output of sound.
I am using ALSA.
Does this information help to solve this bug?

Dennis R (tech-rardin) wrote :

I'm fighting the same issues with the same dongle. Mine looks exactly like the Sabrent unit, except the Sabrent name is missing. http://www.sabrent.com/category/wireless/BT-USBT/

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

On board there are 4 USB (2 for each internal hubs), one of this USB are used by internal sound device. I install bluecove-gpl-2.1.0 and bluecove-2.1.0. When I plug 2 of UD100 they works fine, I cannot use 3 dongle togheter because the third does'nt work.

Using hciconfig I have this message:

hci0: Type: BR/EDR Bus: USB
 BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
 DOWN
 RX bytes:6 acl:0 sco:0 events:1 errors:0
 TX bytes:0 acl:0 sco:0 commands:2 errors:2

hci1: Type: BR/EDR Bus: USB
 BD Address: 00:01:95:0C:8F:76 ACL MTU: 310:10 SCO MTU: 64:8
 UP RUNNING PSCAN ISCAN
 RX bytes:969 acl:0 sco:0 events:27 errors:0
 TX bytes:355 acl:0 sco:0 commands:27 errors:2

hci2: Type: BR/EDR Bus: USB
 BD Address: 00:01:95:0D:D3:41 ACL MTU: 310:10 SCO MTU: 64:8
 UP RUNNING PSCAN
 RX bytes:957 acl:0 sco:0 events:26 errors:0
 TX bytes:358 acl:0 sco:0 commands:26 errors:0

You can see that the hci0 is DOWN, without address and with TX errors, hci2 is fine but with 2 errors (after this it seems work always fine) and hci3 is fine.

I have to use three dongle because I need perfomance to push bluetooth message to many mobile phone and to listen for receive message by other many mobile phones. In future I want use every 4 usb for dongles (I can disable sound device).

I excanged the dongle plugged many times and using other dongle UD100 and also other device with Cambridge Silicon Radio, the problem is the last dongle I plug in a pair of USB of the some internal hub (the dongle in the other hub is always alone, in the example of hciconfig it is hci3). I use other identical board (VDX6318) and I exchange cable, disk on chip, I'am sure I don't have problem with hw. The incredible things is that i plug other dongle "not with Cambridge Silicon Radio" and they works fine with the other 2 UD100.

Thanks in advance

Mihai Capotă (mihaic) on 2011-10-20
affects: linux-latest-2.6 (Debian) → linux-2.6 (Debian)
Changed in linux-2.6 (Debian):
importance: Undecided → Unknown
status: New → Unknown
summary: - [Lucid&Karmic] Cambridge Silicon Radio, Bluetooth Dongles do not work
+ Cambridge Silicon Radio Bluetooth Dongles do not work

Confirming the bug in Ubuntu 11.10. My system even hangs during an attempted file transfer. It requires a hard reset, not even the magic SysRq key works.

mihai@dutier:~$ uname -a
Linux dutier 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

mihai@dutier:~$ lsusb
Bus 004 Device 014: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Changed in linux-2.6 (Debian):
status: Unknown → Confirmed
ignacio (zamcan45) wrote :

Dear all,
I would like to add a piece of information. This dongle Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) did work in Ubuntu 10.04 LTS, I cannot tell you the uname then, because I did not know to use this command then.
It was during one security update that stopped working. I update to Ubuntu 10.10 with the hope that this would work but it did not.
Maybe someone could check if using 10.04 helps to solve this problem.
I am studying Linux command to be able of doing a downgrade, but still did not find the way.
I may be trying a fresh instalation of the Live CD 10.04 LTS
I will let you know.

km (km-mathcs) wrote :

I am seeing the same issues on Ubuntu 11.04

Linux flinux 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:34:47 UTC 2011 i686 i686 i386 GNU/Linux

and Ubuntu 10.10

Linux kmsys 2.6.38-12-generic #51-Ubuntu SMP Wed Sep 28 14:27:32 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

with a Chinese CSR knock off, that does work properly under Windows.

zenon (zenon222) wrote :

Running 64-bit Lucid with the 3.0.0-13 kernel on an HP 4430s laptop. HP offers closed source linux drivers for this laptop. I will try the driver and complain to their tech support if it doesn't work

zenon@ubuntu-laptop:~$ lsmod | grep bt
btusb 17289 1
bluetooth 150740 5 rfcomm,bnep,btusb

zenon@ubuntu-laptop:~$ uname -a
Linux ubuntu-laptop 3.0.0-13-lowlatency #21~ppa1-Ubuntu SMP PREEMPT Tue Oct 18 06:45:34 UTC 2011 x86_64 GNU/Linux

zenon@ubuntu-laptop:~$ hciconfig -a
hci0: Type: USB
 BD Address: 68:A3:C4:2C:31:62 ACL MTU: 310:10 SCO MTU: 64:8
 UP RUNNING
 RX bytes:1672 acl:0 sco:0 events:81 errors:0
 TX bytes:1549 acl:0 sco:0 commands:69 errors:0
 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x87
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT
 Name: 'CSR8510'
 Class: 0x000000
 Service Classes: Unspecified
 Device Class: Miscellaneous,
 HCI Ver: 3.0 (0x5) HCI Rev: 0x1aa1 LMP Ver: 3.0 (0x5) LMP Subver: 0x1aa1
 Manufacturer: Cambridge Silicon Radio (10)

Jeb E. (jebeld17) wrote :

Linux Mint Debian Edition fixed the issue, but it is still a problem in Ubuntu! :(

Jeb E. (jebeld17) wrote :

The bluetooth radio works perfect in Ubuntu 10.04 - 11.04, but all of a sudden, it doesn't work properly again when I upgrade to 11.10. This problem NEEDS to be fixed, or I am switching to Linux Mint!

amias (amias) wrote :

i can confirm that the same problem exists with 11.10 and a 3.0.0-17-generic kernel.

am starting to think this device cannot do a2dp at all.

Radu Cristescu (radu.c) wrote :

Still a problem on 12.04 - kernel 3.2.0-20-generic-pae.

Exact same behaviour on 10.10 - kernel 2.6.36-020636-generic (from PPA) on totally different machine when I move the adapter to it.

The autosuspend workaround seems to work though.

Radu Cristescu (radu.c) wrote :

Spoke too early. It only worked "better" for a while (I could do a few scans), then went back to its own self.

Jan Schneider (yunosh) wrote :

I can confirm #72. It worked fine until I upgraded the Kernel while still on 10.04 LTS. The new version is 2.6.32-40.87, I upgraded from 2.6.32-33.72.

Jeb E. (jebeld17) wrote :

Ubuntu 12.04 now recognizes the bluetooth dongle device, but it usually never stays connected to any device I try to pair, and when I try to send a file from my phone to my Ubuntu PC with the dongle, my phone will ALWAYS give me an error message as "not sent". I have tried other dongles that are the exact same type, and the same thing happens every time. A fix needs to be committed.

Jeb E. (jebeld17) on 2012-07-26
Changed in linux (Ubuntu):
status: Confirmed → In Progress
status: In Progress → Confirmed
Rodger Fox (rodgerfox) wrote :

I tried these dongles on two PCs running 12.04 and they actually cause the systems to freeze, so that I have to reboot with the power button. They seem to work when I plug them in, but I try to pair them with PS3 controllers using sixad and then the system freezes. This was repeated many times through reboots and on two systems. I have not tried with any other bluetooth devices.

summary: - Cambridge Silicon Radio Bluetooth Dongles do not work
+ 0a12:0001 Cambridge Silicon Radio Bluetooth Dongles do not work

Maarten Fonville, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

tags: added: lucid
removed: needs-kernel-logs
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
affects: linux-2.6 (Debian) → bluez
affects: bluez → bluez (Ubuntu)
no longer affects: bluez (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

affects: gnome-bluetooth → bluez (Ubuntu)
Changed in bluez (Ubuntu):
status: New → Confirmed
no longer affects: bluez (Ubuntu)
oraslaci (oraslaci) wrote :

This bug still affects me in Ubuntu 12.10 and 12.04 too.

tags: added: quantal running-unity

ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: oraslaci 2004 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=1ca3452a-0aff-4ef1-a8c2-606914a0e4c2
InstallationDate: Installed on 2013-02-03 (0 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MachineType: Dell Inc. Latitude E5510
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=8c8fdb49-b8bf-4162-b831-d62835058487 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-23-generic N/A
 linux-backports-modules-3.5.0-23-generic N/A
 linux-firmware 1.95
Tags: quantal running-unity
Uname: Linux 3.5.0-23-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/08/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 023HKR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd07/08/2010:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

oraslaci (oraslaci) on 2013-02-04
description: updated
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.7.0-030700rc2-i386
removed: needs-upstream-testing

oraslaci, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

tags: added: i386 needs-upstream-testing
removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.7.0-030700rc2-i386 quantal running-unity
summary: - 0a12:0001 Cambridge Silicon Radio Bluetooth Dongles do not work
+ 0a12:0001 Cambridge Silicon Radio Bluetooth Dongle not working
cyd (cyd) wrote :

bug still present: hci0 is UP, but i can't scan for any devices.
Ubuntu 13.04 x64 full updated

also tested with kernel 3.10, issue remains the same :'(

tags: added: bios-outdated-0323
Jeb E. (jebeld17) wrote :

I'm getting similar issues again with my current Bluetooth dongle... Ubuntu, Debian, and Linux Mint all recognize it now, but the connection is very unstable, sending and receiving files may work or may not work, and if they do, the files usually time out mid-transmission.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Jeb E., thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
dino99 (9d9) wrote :

Fixed upstream as per #10126 status

Changed in linux:
importance: Medium → Undecided
status: Confirmed → New
status: New → Fix Released
affects: linux (Fedora) → dpkg
Changed in dpkg:
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
Changed in linux (Ubuntu):
status: Incomplete → Invalid
Displaying first 40 and last 40 comments. View all 105 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.