Bug 12045
| Summary: | Bluetooth dongle not work | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Daniel (lupulescud) |
| Component: | Bluetooth | Assignee: | Stiff (stiff11) |
| Status: | ASSIGNED --- | ||
| Severity: | normal | CC: | alan, brian, chris.scotland, docterdee, dominique, leifer, markhobley, maximi89, maxmusterm, robert1peter, stiff11, zanetu |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.9.0 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: |
lsusb -vv
journal log |
||
|
Description
Daniel
2008-11-16 05:09:10 UTC
Reply-To: akpm@linux-foundation.org (switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Sun, 16 Nov 2008 05:09:10 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=12045 > > Summary: Bluetooth dongle not work > Product: Drivers > Version: 2.5 > KernelVersion: 2.6.27.7 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Bluetooth > AssignedTo: drivers_bluetooth@kernel-bugs.osdl.org > ReportedBy: lupulescud@yahoo.com > > > Latest working kernel version: > Earliest failing kernel version: > Distribution:Ubuntu 8.10 > Hardware Environment:Laptop Hp nx6325 > Software Environment:Gnome, bluetooth wizard > Problem Description: > Some bluetooth dongles are not initiatized and does't work. > It's about device: > 006: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device > Steps to reproduce: > Icon is shown in tray but bluetooth doesn't work proper. If dongle is > previous > initialized by windows it blinks but cannot pair. If dongle is put in or pull > aout and than put back in its not initialized (led does't flash), and it's > not > working. > Same system (ubuntu 8.10), same adapter, same problem. problem is available also in kernel 2.6.27-9-generic when i boot old kernel 2.6.24-21, the adapter works fine. This is true for me as well with kernel 2.6.27-9-generic. Daniel - please can you mark this as a regression as all my bluetooth problems are fixed when reverting to the 2.6.24 kernel series. You could also update the version to 2.6.27.9 as it is still present in that release. My dongle: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter For the record I have just built the vanilla linux 2.6.28-rc7-git2 kernel and the bug is still present. I have the same dongle. This is fixed in git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-testing.git For those of you who want to use the dongle in vanilla 2.6.29: Just copy the "btusb.c" (version 0.5) from bluetooth-testing to "drivers/bluetooth/" (replace 0.4). Get btusb.c here: http://git.kernel.org/?p=linux/kernel/git/holtmann/bluetooth-testing.git;a=blob_plain;f=drivers/bluetooth/btusb.c;hb=HEAD Hasn't been fixed for me: Kernel 2.6.29 Vanilla Bluetooth: Generic Bluetooth USB driver ver 0.5 Bluez: Git from 19.04.2009 This happens when i try to connect to my PS3 Remote: Bluetooth: HIDP (Human Interface Emulation) ver 1.2 input: Sony Computer Entertainment Inc BD Remote Control as /devices/pci0000:00/0000:00:0b.0/usb2/2-5/2-5:1.0/bluetooth/hci0/hci0:1/input6 generic-bluetooth 0005:054C:0306.0001: input,hidraw0: BLUETOOTH HID v1.00 Gamepad [Sony Computer Entertainment Inc BD Remote Control] on 00:11:67:AB:3A:AD usb 2-5: USB disconnect, address 2 btusb_bulk_complete: hci0 urb f5a63e00 failed to resubmit (19) btusb_intr_complete: hci0 urb f5a63d00 failed to resubmit (19) btusb_bulk_complete: hci0 urb f5a63b00 failed to resubmit (19) btusb_send_frame: hci0 urb c25baf00 submission failed I have kernel 2.6.30-rc6 and it's fixed. now my dongle ISSC ID 1131:1004 Integrated System Solution Corp. Bluetooth Device works great, i'm using bluez 4.34 Greetings! this error has been fixed, now the problem are with bluez-gnome and obex-data-server because don´t work properly. Greetings! i have the same device :1004 At least these dongles, that did function with kernel 2.6.26 ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter ID 1131:1004 Integrated System Solution Corp. Bluetooth Device ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter ID 0a5c:200a Broadcom Corp. Bluetooth dongle, ceased to function from kernel 2.6.27. A fix may have been introduced since then for one or the two Integrated System Solutions devices, but not for the D-Link DBT-122 (and maybe not for the Broadcom either). With the D-Link DBT-122, commands end with hci_cmd_task: hci0 command tx timeout 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 Syslog kernel: [14250.936021] usb 3-1: new full speed USB device using uhci_hcd and address 2 kernel: [14251.177549] usb 3-1: configuration #1 chosen from 1 choice bluetoothd[3003]: HCI dev 0 registered kernel: [14251.230374] Bluetooth: Generic Bluetooth USB driver ver 0.3 kernel: [14251.230515] usbcore: registered new interface driver btusb bluetoothd[3003]: HCI dev 0 up bluetoothd[3003]: Starting security manager 0 kernel: [14256.370391] hci_cmd_task: hci0 command tx timeout bluetoothd[3003]: Can't write class of device: Connection timed out (110) bluetoothd[3003]: Adapter /org/bluez/3003/hci0 has been enabled kernel: [14261.378576] hci_cmd_task: hci0 command tx timeout bluetoothd[3003]: Sending getting name command failed: Connection timed out (110) kernel: [14266.383752] hci_cmd_task: hci0 command tx timeout bluetoothd[3003]: Can't read class of device on hci0: Connection timed out (110) kernel: [14271.388810] hci_cmd_task: hci0 command tx timeout sudo 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) This seems not to be a pure btusb problem, but a problem between btusb and bluez 4.xx. A. I did succeed to use the D-Link DBT-122 with kernel 2.6.27 by going back from bluez 4.xx to bluez 3.xx. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502 my entry of 2009-02-07. I think that I could not reproduce this any more because too many things have changed and I would encounter dependencies problems with bluez 3.xx under Ubuntu 9.04. B. There is no timeout error if bluetooth (bluez 4.35) is stopped: sudo /etc/init.d/bluetooth stop * Stopping bluetooth [ OK ] sudo hciconfig hci0 up sudo 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:1015 acl:0 sco:0 events:30 errors:0 TX bytes:632 acl:0 sco:0 commands:36 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) DOES work OK with Bluez 4.40-2 In the case of ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter, it seems that it was not so much a kernel bug than a bluez bug: It still does NOT work with kernel 2.6.29 and the regular Bluez 4.3x from the Ubuntu 9.04 distribution. It DOES work OK with Bluez 4.40-2 from Debian. Using the following bluetooth adapter model in an IBM compatible (IA32) based computer, I am getting an error: Can't read local name on hci0: Connection timed out (110)
NANO TINY USB 2.0 BLUETOOTH ADAPTER DONGLE EDR WIRELESS
Part number 500792110001
Barcode 2000000529837
Bus 003 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Attempting to use a bluetooth dongle, hciconfig gives an error:
Can't read local name on hci0: Connection timed out (110)
hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING
RX bytes:59 acl:0 sco:0 events:5 errors:0
TX bytes:15 acl:0 sco:0 commands:7 errors:2
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
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)
dmesg reveals:
[106069.006003] hci_cmd_task: hci0 command tx timeout
I have retested this again. This time with experimental kernel version 2.6.37-rc5
The timeout error is still occuring, so the latest attempts at fixing this have not worked. THE KERNEL IS STILL BROKEN:
hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
UP RUNNING
RX bytes:413 acl:0 sco:0 events:18 errors:0
TX bytes:67 acl:0 sco:0 commands:21 errors:4
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 PARK
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)
IBM compatible (IA32) based computer
NANO TINY USB 2.0 BLUETOOTH ADAPTER DONGLE EDR WIRELESS
Part number 500792110001
Barcode 2000000529837
Bus 003 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)
I have retested this again. This time with experimental kernel version
2.6.38-rc6.
hciconfig -a hci0
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
DOWN
RX bytes:342 acl:0 sco:0 events:10 errors:0
TX bytes:33 acl:0 sco:0 commands:11 errors:1
Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
The device does not appear in the hcitool list:
hcitool dev
Devices:
The timeout error occurs when an attempt is made to bring the device into an operational mode:
hciconfig hci0 up
Can't init device hci0: Connection timed out (110)
There are some mass market USB Bluetooth Dongles available, which are badged as "NANO TINY USB 2.0 BLUETOOTH ADAPTER DONGLE EDR WIRELESS". These adapters have a part number 500792110001, and a package barcode of 2000000529837. These devices are available from Ebay, and from large online retailers such as Amazon. When plugged into a computer, these devices identify themselves as "Cambridge Silicon Radio" and carry an identity of 0a12:0001. On investigation, it appears that these devices actually contain an AS3620QA1 microchip made by "Accel Semiconductor Corporation" in China. The first three bytes of the MAC address reflect these as being made by Accel Semiconductor Corporation. Currently these devices do not work in Linux and cause an HCI Timeout error (as reported in Kernel bug #10126, Debian bug #525220 and Launchpad #460743). It appears that several people have been "stung" by non operation of these devices. Is is likely that support for these will be included in a future version of the kernel or are Accel Semiconductor devices a non working dead end for us? As a side note, because there is confusion over the manufacturer, and many suppliers list the Accel Semiconductor devices as Cambridge Silicon Radio and do not know that they are Accel (because they work with the CSR driver in Microsoft Windows), it is not easy to find a supplier of genuine CSR bluetooth devices. It would be useful to know a supplier name, model number, and any markings on the packaging that show that the devices for sale are genuine CSR. As I understand it for you all the driver doesn't work at all and just times out. For me the driver "works" as it can scan and connect to a device and sometimes I can even use it for a few seconds but sometimes, just like you, I only get timeouts.But for me it always ends in a crash. I will attach my journal log and a lsusb of my device. I use an older git revision 3.9.0-rc4-00247-g46a1f21 Created attachment 97371 [details]
lsusb -vv
lsusb of the device
Created attachment 97381 [details]
journal log
journal log from the crash
|