The D-Link DBT-122 USB dongle does not work with btusb and Bluez 4.xx.
lsusb
Bus 003 Device 002: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
uname -a
Linux library 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:27:06 UTC 2009 i686 
GNU/Linux
dpkg -l | grep bluez
ii  bluez                                      4.35-0ubuntu1   

Abstract:
Section A. In the normal situation (bluetooth running) inserting the dongle 
gives messages like
> hci_cmd_task: hci0 command tx timeout 
and 
> Connection timed out (110)
Commands like hciconfig -a, hcitool scan and l2ping end with similar messages 
and there is no bluetooth functionality like pairing to a phone.

Section B. With bluetooth stopped, there is of course no more real
bluetooth functionality (no pairing) but it may be interesting to note
that hciconfig -a, hcitool scan and l2ping DO give normal results. There
is some low level functionality provided by btusb, but (section A) this
is broken by the daemon.

I'll gladly provide more information if instructed to do so and how (and
if it is not above my level of competence :-).

***************
Section A:
=====
syslog (inserting the dongle)
May 17 03:49:06 library kernel: [ 2024.384017] usb 3-1: new full speed USB 
device using uhci_hcd and address 2
May 17 03:49:06 library kernel: [ 2024.570047] usb 3-1: configuration #1 chosen 
from 1 choice
May 17 03:49:06 library bluetoothd[2991]: HCI dev 0 registered
May 17 03:49:06 library kernel: [ 2024.630733] Bluetooth: Generic Bluetooth USB 
driver ver 0.3
May 17 03:49:06 library kernel: [ 2024.630862] usbcore: registered new 
interface driver btusb
May 17 03:49:06 library bluetoothd[2991]: HCI dev 0 up
May 17 03:49:06 library bluetoothd[2991]: Starting security manager 0
May 17 03:49:11 library kernel: [ 2029.773914] hci_cmd_task: hci0 command tx 
timeout
May 17 03:49:16 library bluetoothd[2991]: Can't write class of device: 
Connection timed out (110)
May 17 03:49:16 library bluetoothd[2991]: Adapter /org/bluez/2991/hci0 has been 
enabled
May 17 03:49:16 library kernel: [ 2034.795178] hci_cmd_task: hci0 command tx 
timeout
May 17 03:49:21 library bluetoothd[2991]: Sending getting name command failed: 
Connection timed out (110)
May 17 03:49:21 library kernel: [ 2039.800343] hci_cmd_task: hci0 command tx 
timeout
May 17 03:49:26 library bluetoothd[2991]: Can't read class of device on hci0: 
Connection timed out (110)
May 17 03:49:26 library kernel: [ 2044.805647] hci_cmd_task: hci0 command tx 
timeout

hciconfig -a
hci0:   Type: USB
        BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING 
        RX bytes:667 acl:0 sco:0 events:19 errors:0
        TX bytes:591 acl:0 sco:0 commands:24 errors:0
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: 
        Link mode: SLAVE ACCEPT 
Can't read local name on hci0: Connection timed out (110)

hcitool scan
[sudo] password for mic: 
Scanning ...
Inquiry failed: Connection timed out

***************
Section B:
=====
Searching in Google about this issue, I came across a conversation in a forum 
where Marcel Holtman suggested to somebody to test btusb alone, by stopping 
bluetooth. The other person did not provide the results of such a test, but I 
tried this and it gives surprising results:
/etc/init.d/bluetooth stop
 * Stopping bluetooth                                                    [ OK ] 

Inserting the dongle:
syslog
May 17 04:14:24 library kernel: [ 3542.688020] usb 3-1: new full speed USB 
device using uhci_hcd and address 3
May 17 04:14:25 library kernel: [ 3542.934139] usb 3-1: configuration #1 chosen 
from 1 choice

hciconfig -a
hci0:   Type: USB
        BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING 
        RX bytes:342 acl:0 sco:0 events:10 errors:0
        TX bytes:35 acl:0 sco:0 commands:10 errors:0
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: 
        Link mode: SLAVE ACCEPT 
        Name: 'Broadcom BCM2035'
        Class: 0x000000
        Service Classes: Unspecified
        Device Class: Miscellaneous, 
        HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
        Manufacturer: Broadcom Corporation (15)

sudo hcitool scan
Scanning ...
        00:13:70:0E:8A:77       Nokia 6021

l2ping 00:13:70:0E:8A:77
Ping: 00:13:70:0E:8A:77 from 00:13:46:00:55:A0 (data size 44) ...
0 bytes from 00:13:70:0E:8A:77 id 0 time 10.84ms
0 bytes from 00:13:70:0E:8A:77 id 1 time 10.72ms
et cetera

-- 
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/377225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to