Ubuntu

Bluetooth Adapter not recognized (precise)

Reported by tim on 2012-05-01
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Undecided
Unassigned

Bug Description

My specific dongle has worked flawlessly on 11.04, since upgrading, my system no longer recognizes it.

blueman-applet reports no adapters found.

hcitool dev reports nothing, just "Devices:"

lsusb finds this however:
Bus 006 Device 002: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device

If I pull the dongle out, the applet disapears. If the dongle is not evident on boot, the applet will not start.

hciconfig show this:
hci0: Type: BR/EDR Bus: USB
 BD Address: [snip] ACL MTU: 1021:4 SCO MTU: 48:10
 DOWN
 RX bytes:2270 acl:0 sco:0 events:80 errors:0
 TX bytes:365 acl:0 sco:0 commands:85 errors:0

Tailing syslog while attempting to `hciconfig hci0 up`shows this:
May 1 13:44:44 beta kernel: [ 137.992056] Bluetooth: hci0 command tx timeout

tim (acmeinc) on 2012-05-01
affects: linux-firmware (Ubuntu) → ubuntu
description: updated
affects: ubuntu → bluez (Ubuntu)
tags: added: precise
Launchpad Janitor (janitor) wrote :

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

Changed in bluez (Ubuntu):
status: New → Confirmed
Grizzly (sven-witterstein) wrote :

My dongle is regognised:

hci0: Type: BR/EDR Bus: USB
 BD Address: 00:1F:81:00:08:30 ACL MTU: 1021:4 SCO MTU: 180:1
 UP RUNNING PSCAN
 RX bytes:3160 acl:0 sco:0 events:136 errors:0
 TX bytes:838 acl:0 sco:0 commands:155 errors:33
 Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF
 Link mode: SLAVE ACCEPT
 Name: 'Accel-OB2'
 Class: 0x6e0100
 Service Classes: Networking, Rendering, Capturing, Audio, Telephony
 Device Class: Computer, Uncategorized
Can't read version info hci0: Connection timed out (110)

However. two weeks ago it found devices, then the wholy system froze. Now, it searches an never finds devices...
Audio Out via HDMI is also not working on my now "ancient" amd-780G-based phenom quad... Sad, oneiric did not have these problems, instead it refused to shut the computer down...

glennric (glennric) wrote :

I have a dongle that seems to be affected as well. I tried booting to a live cd of Natty and found that it still works fine there. I also tried booting a live cd of oneiric and found that it doesn't work there. Of course it still doesn't work with precise.

Having same problem since 12.04

vlc (vlc) wrote :

Same here:

$ lsusb | grep Bluetooth
Bus 005 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

$ hciconfig
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:429 acl:0 sco:0 events:14 errors:0
 TX bytes:64 acl:0 sco:0 commands:16 errors:2

$ hcitool dev
Devices:

$ dmesg
[ 1746.528017] usb 5-2: new full-speed USB device number 3 using uhci_hcd
[ 1746.742044] usb 5-2: New USB device found, idVendor=0a12, idProduct=0001
[ 1746.742049] usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1747.772011] Bluetooth: hci0 command tx timeout
[ 1748.772009] Bluetooth: hci0 command tx timeout

Mukesh H Jaiswal (mukeshj81) wrote :

Hi,

I am still affected by this issue.

$ lsusb
Bus 002 Device 004: ID 0461:4e22 Primax Electronics, Ltd
Bus 002 Device 003: ID 413c:2111 Dell Computer Corp.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ hcitool dev
Devices:

It is still not fixed on most undated ubuntu os as on Mar 6, 2014 and that is ubuntu 13.10. Any workarounds?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers