Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)

Output of lsusb

:~$ lsusb
Bus 002 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I had the same problem with Intrepid Alpha 5, then I tried to send a photo from my Nokia N70 to the PC (no problem with that), then tried to associate again my Bluetooth headset and it worked!
I use a D-Link DBT-120.

No change with 2.6.27-4

Have clean installed Intrepid Beta, and updated now to 2.6.27-6, and the problem persists.

I can confirm this bug with the same bluetooth controller.
I'm wondering if it is a specific bug with this controller?

danny@danny-laptop:~$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

seems #281949 is a duplicate of this one but assigned to a wrong package.

i have the same issue. Mine usb adapter is dlink dbt-122.

Here is a snip of dmesg:
[138209.665630] Bluetooth: Generic Bluetooth USB driver ver 0.3
[138209.666632] usbcore: registered new interface driver btusb
[138214.844410] hci_cmd_task: hci0 command tx timeout
[138219.848340] hci_cmd_task: hci0 command tx timeout
[138224.853676] hci_cmd_task: hci0 command tx timeout
[138229.856417] hci_cmd_task: hci0 command tx timeout
[138234.860719] hci_cmd_task: hci0 command tx timeout
[138239.960585] hci_cmd_task: hci0 command tx timeout
[138240.464277] bluetoothd[5133]: segfault at 3 ip b7e39938 sp bfb8fcc8 error 4 in libc-2.8.90.so[b7dc8000+158000]

# lsusb
..
Bus 004 Device 007: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
..

Same Problem:
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
Dmesg :
[ 55.092421] hci_cmd_task: hci0 command tx timeout
[ 60.096506] hci_cmd_task: hci0 command tx timeout
[ 65.100369] hci_cmd_task: hci0 command tx timeout
[ 70.104358] hci_cmd_task: hci0 command tx timeout
[ 75.108196] hci_cmd_task: hci0 command tx timeout
[ 80.112996] hci_cmd_task: hci0 command tx timeout

It works with regression of these package :
'bluez-utils_3.26-0ubuntu6_i386.deb'
'bluez-hcidump_1.40-0ubuntu1_i386.deb'
'bluez-cups_3.26-0ubuntu6_i386.deb'
'bluez-audio_3.26-0ubuntu6_i386.deb'
'bluetooth_3.26-0ubuntu6_all.deb'
No other solution found.

I confirm this as a bug Bus 004 Device 003: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

does not work on mine system to :-/

Intrepid with Linux 2.6.27-7

If I boot with old linux 2.6.26-* it works. So its probadly kernel problem. or maybe bluez related...

I have been able to pair (intermittently) from phone to computer using a different phone, an LG rather than a Sony Ericsson. The LG allows me to enter the passcode much more quickly than the Sony (which normally thinks for about 25 seconds before asking me to choose a passcode). Is this a timeout issue?

Having said that, even when paired I am still unable to browse files on the LG.

its not a time only a timerissue in the bluz stack its seems to be an KY-BT100 driver issue or/and the ehci/uhci_hsd as far as I could understand it when reading some mailinglists.

My other bt adapter ( 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)) works nicely.

Same problem on my site.

 ID 1131:1004 Integrated System Solution Corp. Bluetooth Device

It's a no name device which worked in hardy but not in intrepid.

It seems my problem is more severe...

I have 2 different bluetooth dongles (Kensington & Ambicom). They both used to work fine in Hardy, but all I'm showing is timeout errors since I upgraded to Ibex. I can't pair, I can't search devices, obex... Anything.

At first, the BT icon didn't even show, but after installing a few packages through Synaptic and rebooting, that problem went away.

Another weird thing is that the timeout errors occur within a second of attempting any kind of interaction with bluetoothd.

Let me know if you guys need any extra info, and I'll try to post it up ASAP.

The same problem for me with the final 8.10 intrepid ibex and a D-Link DBT-122.

Blink green power and link and nothing more...

lsusb:
Bus 006 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

lsmod | grep bt:
btusb 21912 3
bluetooth 70820 15 btusb,rfcomm,sco,bnep,l2cap
usbcore 175376 8 btusb,snd_usb_audio,uvcvideo,snd_usb_lib,usbhid,ehci_hcd,uhci_hcd

If I plus and unplus my key I have a normal dmesg like:
[ 851.624013] usb 5-1: new full speed USB device using uhci_hcd and address 3
[ 851.857750] usb 5-1: configuration #1 chosen from 1 choice
[ 923.456037] usb 5-1: USB disconnect, address 3

but the first time I plus and unplug, I have it:
[ 359.864020] usb 6-1: new full speed USB device using uhci_hcd and address 3
[ 360.060177] usb 6-1: configuration #1 chosen from 1 choice
[ 365.196166] hci_cmd_task: hci0 command tx timeout
[ 370.200185] hci_cmd_task: hci0 command tx timeout
[ 375.204223] hci_cmd_task: hci0 command tx timeout
[ 380.208153] hci_cmd_task: hci0 command tx timeout
[ 385.212186] hci_cmd_task: hci0 command tx timeout
[ 390.216194] hci_cmd_task: hci0 command tx timeout
[ 437.128037] usb 6-1: USB disconnect, address 3
[ 437.129858] btusb_intr_complete: hci0 urb ffff88006289cd80 failed to resubmit (19)
[ 437.130126] btusb_send_frame: hci0 urb ffff880062522a80 submission failed
[ 437.130161] __ratelimit: 3 callbacks suppressed
[ 437.130164] bluetoothd[5470]: segfault at 100000007 ip 00007f165b228339 sp 00007fff64096490 error 4 in libc-2.8.90.so[7f165b1ae000+169000]

Thanks in advance...

Suite of my post, I have forget my kernel "uname -a":
Linux syl21-desktop 2.6.27-7-generic #1 SMP Thu Oct 30 04:12:22 UTC 2008 x86_64 GNU/Linux

How as in other users my D-Link DBT-122 not work in 8.10 Untrepid Ibex Release.
--------------------
"uname -a":
Linux leolik-komp 2.6.27-7-generic #1 SMP Thu Oct 30 04:12:22 UTC 2008 x86_64 GNU/Linux

I see this problem when I hibernate... It also vomits other errors as i have included a bug i opened
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/293115

I also have this problem with kernel 2.6.27.4.

hci_cmd_task: hci0 command tx timeout
btusb_intr_complete: hci0 urb failed to resubmit (19)

Things like that.

After replacing the bluetooth subsystem with the codes from 2.6.26.7
and recompiling the kernel, the problem is solved. My bluetooth mouse
works again on "2.6.27.4".

My adapter is a KY-BT100 one.

I have the same problem. If i request authentification from my phone, it works. But i cant pair device from computer.
hcitool scan scans devices good, but i cant connect to phone via obex or rfcomm. sdptool outputs connetion timeout.
string from lsusb:

Bus 002 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

We are lot of people having loosing our Bluetooth connection... Thanks in Advance.

Same problem with 2 bluetooth adapters, this one is from my usb dongle:

Bus 001 Device 006: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device

And the error on dmesg:

[ 235.132015] hci_cmd_task: hci0 command tx timeout

I can see (and pair) the devices, but any other activity fails.

Same here, seems another kernel regression....

I can pair nearly at will - but what happens to me is that the bluetooth connection will not "stick". I have been getting intermittent syncing and file file transferring to work for two days then it stops for a 3 or 4 and then it will work for 8 hours and then stop.

Here is a log from the last week

1/12/2008 21:45 | kyle Amadio
      Nope that does not seem to make any difference.
      Can send files between my phone and wifes.

01/12/2008 21:37 | kyle Amadio
      Monday morning 1/12/2008 - went to work, started PC - interestingly the Dell Bluetooth switch was not on.
      Noticed this well after the PC had booted. Turned on the switch and the sync process and other Bluetooth functions worked.
     Have now returned home and 5 hours after leaving work. Bluetooth has stopped working.
     Will see if the Dell bluetooth switch being off make during the boot process makes any difference.

30/11/2008 21:03 | kyle Amadio
     Ok its Sunday 30th still not syncing - have tried a variety of things, resetting phone, re-pairing, restarting PC bluetooth.
     I can send images and music files between my 6233 and my wifes successfully, both ways.

29/11/2008 08:07 | kyle Amadio
    Shutdown - went to bed - 8 hours later - it works.
    Changed nothing on the phone

28/11/2008 22:48 | kyle Amadio
    Ok - did a shutdown and reboot. Syncing / Bluetooth stopped working.

28/11/2008 22:36 | kyle Amadio
       Well- went home and syncing is all good again.

28/11/2008 12:15 | kyle Amadio
      Syncing worked fine for two days - failed this morning (Fri 28th).

Same problem, i tried 2 different bt usb-dongles (based on different chipsets), but no luck.
Everything works for me, when i start up with 2.6.24-21 stable kernel from array.org ^_^
_________________
root@gazenwagen:~# rfcomm connect 0
Can't connect RFCOMM socket: Operation now in progress

root@gazenwagen:~# hciconfig dev
hci0: Type: USB
BD Address: 00:11:67:C6:F0:6B ACL MTU: 1021:4 SCO MTU: 48:10
UP RUNNING
RX bytes:2180 acl:0 sco:0 events:85 errors:0
TX bytes:890 acl:0 sco:0 commands:70 errors:0

root@gazenwagen:~# dmesg|tail
[ 2876.984143] hci_cmd_task: hci0 command tx timeout
[ 4710.928544] usb 1-2: USB disconnect, address 5
[ 4710.928742] btusb_intr_complete: hci0 urb e4f5d200 failed to resubmit (19)
[ 4710.928742] btusb_bulk_complete: hci0 urb e4c30780 failed to resubmit (19)
[ 4710.929414] btusb_bulk_complete: hci0 urb e4c30b80 failed to resubmit (19)
[ 4710.940056] btusb_send_frame: hci0 urb e4ee4980 submission failed
[ 4710.952039] __set_isoc_interface: hci0 setting interface failed (19)
[ 4727.752273] usb 1-2: new full speed USB device using uhci_hcd and address 6
[ 4737.927583] usb 1-2: configuration #1 chosen from 1 choice
[ 4990.780188] hci_cmd_task: hci0 command tx timeout
_________________

I just built 2.6.28-rc7-git2 from kernel.org and I have the same problems with bluetooth so this is obviously not something that has been addressed upstream.

Is it worth reporting this upstream?

Bug 288613 seems related (https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/288613) and interestingly the reporter claims bluetooth worked fine in beta but not when the first intrepid RC was released. What changed kernel wise?

Ok : here is what I think is going: (I have a Dell E6500 laptop)

IF I have my Bluetooth radio switch turned OFF during the Boot Up process and only turn it ON AFTER Gnome is fully loaded and all processes are finished THEN Bluetooth processes work.

Have proven this with repeated tests:

IF the Bluetooth radio switch is ON during the boot up then Bluetooth will not work.

SO what is going on - surely this is enough for you guys to make a search now. Can we change the load sequence of the Bluetooth daemon to load last ?

kylea, I usually boot with the Bluetooth radio off. It's USB internally and disconnected when I boot, then I switch it on after logging in.

I still have this pairing problem every time with 2.6.27 kernels.
So changing the load sequence wouldn't fix it.

The information we need may be to bisect between the last kernel which works reliably and the one after, trying it on someone's machine until the change which breaks it is identified. Alas I don't have the time for it, so I just run old kernels with Intrepid.

In the same pc on Ubuntu with 2.6.27-7 bluez doesn't pair with any device, with gentoo 2.6.27-r1 bluez-3.36 it does...
I don't know is a kernel problem or what else, but with regression of bluez association works well

Update: ubuntu kernel 2.6.27-10 doesn't solve my problem

it doesn't solve my problem too )

New kernel @ Jaunty, 2.6.28 series fixes my problem.
Now I got my bluetooth headset working on Skype....finally.

Intrepid remains "unpreant" release for me, it was still fine with Hardy.

I too have just tried the Jaunty kernel.
I added this line to my apt/sources.list

deb http://gb.archive.ubuntu.com/ubuntu/ jaunty main restricted multiverse universe

and first of all just upgraded the bluez related packages to 4.21-0ubuntu1.

Now when I try to pair with my phone it immediately fails and gives an error message rather than timing out like before. I then downgraded these packages back to the intrepid version and installed the Jaunty kernel packages (2.6.28). Rebooted the new kernel. Bluetooth still wont work.

I then upgrade the bluez packages again and try to pair with my phone. Success - I am given a 4 digit password and enter this on my phone and it pairs correctly. I am however unable to do any file transfers or use my phone as an HID remote control or modem. So progress at least but still not fixed.

It seems to be a combination of factors related to bluez and the kernel as each one on its own didn't fix the problem however when they were both upgraded i was able to pair at least...

I tested file receiving/sending on my laptop (Compal FT00 VBI) with two Nokia mobile phones: N70 and 6600.
Sending files to the phones was fine. Receiving files doesn't work.

same problem with me..............
have tried everything exept different kernel virsion
will do that today

comp is able to detect devices but cant connect

is some developer listening
SOS

SOS

SOS

This seems like a pretty bad bug for no one to look into. Is there a workaround yet? 8.10 released ages ago, and bluetooth is a pretty standard technology. Is someone going to look into why this broke between 8.04 and 8.10? Seems like a lot of stuff broke in 64bit 8.10.

I don't get - I have paid for support and still cannot get a sensible answer on this.

Just another reason why MS will keep its market share. How can we always be moving towards a new version when the basics don;t work on the majority of the hardware out there.

This behaviour is as bad - in fact worse than MS as the Linux community spends its time rightly bagging MS but then we do the same thing.

I just don't get it, can some of the zealots please explain what is going on here?

No - please keep the bug report on topic. If you paid for Ubuntu commercial support, please contact them - however support implies solving user issues most likely. (at least, the contract that came with ubuntu on my laptop did).

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

What does the comment above actually mean then? Does this mean this major bug is not going to be looked at any further? Or assigned to another team? Who should it be assigned to? This is a major flaw and causes extreme disruption particularly to users who rely on services such as calendar/event syncing.

Ok campers - here is good some news:

refer to my comment in this bug

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/285283

using 4.12 bluetooth on Kubuntu 8.10 64 - using blues-gnome bluetooth worked!!!!

Ok - it worked the session !! - re-booted and it stopped!!

Here are some errors

kylea-E6500-KDE kernel [ 772.393351] __set_isoc_interface: hci0 setting interface failed (110)
kylea-E6500-KDE bluetoothd[4545] Unable to start periodic inquiry: Connection timed out (110)
kylea-E6500-KDE kernel [ 819.626513] hci_cmd_task: hci0 command tx timeout
kylea-E6500-KDE kernel [ 824.631775] __set_isoc_interface: hci0 setting interface failed (110)

Still doesn't work with latest ubuntu updates. Mine bluetooth is Linksys Class 1:

Bus 001 Device 003: ID 0a5c:200a Broadcom Corp. Bluetooth dongle

Yes, it worked before.Some dmesgs (if helps):

[ 598.986598] hci_cmd_task: hci0 command tx timeout
[ 1450.720220] usb 1-2: USB disconnect, address 2
[ 1450.723379] btusb_intr_complete: hci0 urb dd3b6e80 failed to resubmit (19)
[ 1450.734137] btusb_send_frame: hci0 urb d110a780 submission failed
[ 1451.704288] usb 1-2: new full speed USB device using uhci_hcd and address 3
[ 1452.136397] usb 1-2: configuration #1 chosen from 1 choice
[ 1457.356989] hci_cmd_task: hci0 command tx timeout

Anyone care fixing it?

Hi, has anything happened about this bug?
i too have the Integrated System Solution Corp. KY-BT100 Bluetooth Adapter, worked fine under hardy, has anyone of the developers responded to this bug?

Dilldappe,

The answer to both of your questions is no. None of the developers seem to care that they broke bluetooth sometime between 8.04 and 8.10. It's great, eh?

Sincerely annoyed,
Mike

I'm pretty sure this is a Kernel / Gnome issue.
I made the switch to Fedora 10 on my home box with TDK bluetooth dongle attached and it did exactly the same thing.
Worked fine under Gutsy / Hardy.
On my desktop it gnome doesn't see there's a dongle attached, and as such the pairing devices screen is blank.
On my laptop (Intrepid) I can run 'hcitool scan' and see devices, but again, nothing in Gnome

bug is kernel related, but nobody cares. Best answer that i got "Fix
repairs more devices then it breaks". Thats just ridiculus, but
stil...

On 1/23/09, influencd <email address hidden> wrote:
> I'm pretty sure this is a Kernel / Gnome issue.
> I made the switch to Fedora 10 on my home box with TDK bluetooth dongle
> attached and it did exactly the same thing.
> Worked fine under Gutsy / Hardy.
> On my desktop it gnome doesn't see there's a dongle attached, and as such
> the pairing devices screen is blank.
> On my laptop (Intrepid) I can run 'hcitool scan' and see devices, but again,
> nothing in Gnome
>
> --
> Bluetooth association no longer works
> https://bugs.launchpad.net/bugs/268502
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Alex

I am not a developer, but I can assure you this is being worked on: the
bluetooth support lib (bluez) has been updated in a way which is not
backwards-compatible with the existing stuff (v4). All distributions are
affected, this is not Ubuntu-specific in any way.

KDE has recently been updated to support it and Kubuntu packages should soon
appear with the fix integrated. If Jaunty still had no support and Fedora 11
had, I think a lot of people would choose the latter...

I've solved my problem (with a bluetooth headset) by adding the following repository and upgrading all bluez-related (bluez*, bluetooth, libbluetooth3). It will upgrade the bluez 4.27. Now works discover, pairing (using bluetooth-applet)... Etc.

So, step by step:

1) Add the repositories

deb http://philip.magicalforest.se/ intrepid extra
deb-src http://philip.magicalforest.se/ intrepid extra

2) Add the repo's GPG sig

wget http://philip.magicalforest.se/Philip5.gpg | sudo apt-key add key.asc

3) Update the repository using Synaptic or apt-get update

4) Mark the upgrades to bluez*, bluetooth, libbluetooth3

5) Apply

Afterwards, just restart the service (sudo /etc/init.d/bluetooth restart) and everything working again. You can test by using the following command:

aplay -D bluetooth /usr/share/sounds/question.wav

Cheers,

Igor Gomes

Thank you very much, Igor.

After this update everything is fine, except for just one thing: there are problems when there are empty files among those being copied. In this case there is no file transfer at all. And when I try to cancel this unsuccessfull file transfer, my computer just starts hanging. Nothing helps but removing the dongle and inserting it again and then removing empty files from the list of files which I want to copy from my cell phone to my computer.

Of course I understand that this has nothing to do with the bug being discussed, but still...

Thank you one more time,
Igor Bronstein.

Igor Gomes' solution didn't work for me. By the way, don't try sudo apt-get install bluez*, it will install a lot of bluetooth-unrelated packages, instead, try this command:

sudo apt-get install bluez bluez-* bluetooth libbluetooth3

My bluetooth dongle:
Bus 004 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

yngd wrote:
> New kernel @ Jaunty, 2.6.28 series fixes my problem.
> Now I got my bluetooth headset working on Skype....finally.
>
> Intrepid remains "unpreant" release for me, it was still fine with
> Hardy.

Jaunty's 2.6.28-4 doesn't do it for me. Still can't connect to PAN on
my Sony-Ericsson K850i phone. Intrepid's 2.6.27 kernels can't
connect, but Hardy's 2.6.24 kernels can.

(So I have to reboot to a 2.6.24 kernel to use bluetooth 3g broadband
through my phone, but it that kernel breaks a bunch of other things).

Someone else reports similar, they can't connect to ther S-E phone
starting from Interpid.

-- Jamie

OMG kernel 2.6.28 + bluez 4.27 = don't work !!!

$ lsusb
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

$ dmesg
[ 737.054214] Bluetooth: L2CAP ver 2.11
[ 737.054217] Bluetooth: L2CAP socket layer initialized
[ 737.068295] Bluetooth: RFCOMM socket layer initialized
[ 737.068313] Bluetooth: RFCOMM TTY layer initialized
[ 737.068315] Bluetooth: RFCOMM ver 1.10
[ 737.731793] Bluetooth: SCO (Voice Link) ver 0.6
[ 737.731796] Bluetooth: SCO socket layer initialized
[ 737.743677] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 737.743682] Bluetooth: BNEP filters: protocol multicast
[ 737.780733] Bridge firewalling registered
[ 757.399557] hci_cmd_task: hci0 command tx timeout
[ 906.021827] hci_cmd_task: hci0 command tx timeout
[ 940.098262] hci_cmd_task: hci0 command tx timeout

Do I must install and use M$ Windows only for sending/receiving files from Bluetooth Dongle? This is joke?

As an Ubuntu user living in Ubuntu country and proud of it,I can only comment as follows:
At the last Linux Foundation International Gathering it was concluded that we,the Ubuntu users, amongst others,are the vitally needed guinea-pig force needed to achieve the ultimate goal of a near-as-possible perfect operating system to oppose Windows/Gates.They further expressed their gratitude for software development but wowed the serious lack of TESTING it before putting into it practice.This is our problem.
An operating system as advanced as Intrepid 8.10 should, when launched ,not have vital components like bluetooth all facets, printer drivers and the like, not functioning properly as thousands of us use these machines to earn our daily living
and dis-functionality of 'vital' components force us to Windows.A totally unacceptable situation.
I realise the problems are vast but cannot accept that after all the bug reports and comments all over the forums, Intrepid is just not delivering what it was intended to do and its the modern day basics that are troublesome.

You kidding? Bluetooth works perfectly for me on Intrepid, so please don't talk as though the entire Ubuntu community is affected. Either way, can someone who is affected open up a Jaunty installation (or LiveCD) and see if the issue is fixed over there?

For me this works flawlessly on my laptop with built in bluetooth.
However mt bluetooth dongle doesn't work at all (or so slowly that it is unusable)

I'm now wondering if it might have something to do with gvfs any thoughts?

hyperair wrote:
> You kidding? Bluetooth works perfectly for me on Intrepid, so please
> don't talk as though the entire Ubuntu community is affected. Either
> way, can someone who is affected open up a Jaunty installation (or
> LiveCD) and see if the issue is fixed over there?

It does not work for me with Jaunty kernels and Jaunty bluez on an
otherwise Intrepid system. I boot a Hardy kernel when I want to use
Bluetooth, then it works fine. The bluez version doesn't seem to make
any difference, only the kernel version.

This is definitely a kernel bug. I have an affected dongle and I'm a developer, so I'll be able to look at it in a few days.

Until then, if someone could bisect the kernel and find the bad commit, or at least narrow it down, it could speed things up a lot.

I have recently received a major update to the kernel that included a number of fixes that referenced Bluetooth. I have also have updated to 4.28 of the various Bluez modules. Previously only Bluez 3.26 along with Blueman would work. This new combination is working.

I still keep the Dell Bluetooth radio switch off until the desktop is loaded.

Now for some more weirdness, sometimes my Multisync calendar sync stops, however if I start anyremote on the phone and link to the PC, then the Multisync process will start working and keep working for as long as Anyremote is connected.

Next re-boot it just works normally. There may be a Kernel issue - but sometimes I wonder if the phone is also not playing its part.

Upgraded the following packages:
bluetooth (4.27-intrepid~ppa1) to 4.28-0ubuntu1~git20090125
bluez (4.27-intrepid~ppa1) to 4.28-0ubuntu1~git20090125
bluez-alsa (4.27-intrepid~ppa1) to 4.28-0ubuntu1~git20090125
bluez-cups (4.27-intrepid~ppa1) to 4.28-0ubuntu1~git20090125
bluez-gstreamer (4.27-intrepid~ppa1) to 4.28-0ubuntu1~git20090125
bluez-pcmcia-support (4.27-intrepid~ppa1) to 4.28-0ubuntu1~git20090125
bluez-utils (4.27-intrepid~ppa1) to 4.28-0ubuntu1~git20090125
libbluetooth3 (4.27-intrepid~ppa1) to 4.28-0ubuntu1~git20090125

linux-headers-2.6.27-11 (2.6.27-11.26) to 2.6.27-11.27
linux-headers-2.6.27-11-generic (2.6.27-11.26) to 2.6.27-11.27
linux-image-2.6.27-11-generic (2.6.27-11.26) to 2.6.27-11.27
linux-libc-dev (2.6.27-11.26) to 2.6.27-11.27

Linux kylea-e6500 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux

It would be nice that someone paste there diff patch which fixes this bug, because 2.6.27-11.27 only fixed bug of * USB: isp1760: Fix probe in PCI glue code ...

@kylea: did you compile the bluez stuff yourself or did you get packages somewhere?

I think that bluez is from ppa:
https://launchpad.net/~blueman/+archive/ppa

but we want code from kernel which fixes this bug...

in response to kylea: upgrading to the latest linux 2.6.27-11.27 ubuntu kernel hasnt fixed a thing for me. my bluetooth dongle can still "see" the phone however pairing always fails and no connection can be established. i'm still using the default ubuntu bluez packages.

in terms of kernel commits i think we need to look at what changed 2.6.24-->2.6.27 rather than in this latest update - maybe thats what you meant anyway Ari...

i will try again with the updated bluez packages just in case.

I can confirm that there is no improvement after all upgrades and everything I wrote in the bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/281949 is still valid:

My USB bluetooth adapter worked well under Hardy.

Under Intrepid the Bluetooth manger can only detect connectible devices in neighborhood, but any attempt for pairing them (when pairing is started from PC) is unsuccessful - there appear no dialogues for "key" both on my PC and mobiles. But I can pair mobile phones to my PC, when I start pairing from a phone to be paired. Unfortunately after pairing there is no "mounted phone icon" on a desktop / in Nautilus and I cannot browse the mobile from PC even neither through the bluetooth applet "browse" option.

 I have tried to connect two Nokia phones 6021 a 6310i. (Note: under WinXP it still works => no hardware failure)

USB bluetooth adapter:
Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

OS Ubuntu 8.10 beta 64-bit (2.6.27-11-generic)
Motherboard Asus P5KPL (Intel chipset with Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GH)

Same issue exactly. Also using ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter.

Definitely seems to be a driver issue with this hardware.

How can we go about finding the maintainer (if such a thing exists) for the kernels "Bluetooth: Generic Bluetooth USB driver ver 0.3"? Comments in the code? Maybe i'll download the kernel source and have a poke about and try contacting them directly to at least bring it to their attention. Even if i have to mail them my bluetooth dongle to test with.

Ok i have subscribed Marcel Holtmann to this bug as he is listed in the /drivers/bluetooth/btusb.c file as the drivers author.

I hope you don't mind this Marcel.

Marcel: Any chance you could take a look at this bug for us in case it does happen to be related to your driver?
If not do you have any suggestions that might help us get the attention of the right people?
I am happy to provide you with any details/logs and even hardware to test it with to the best of my ability.

Thanks.

One definitely exists, you can see which commit was the one that broke
this... but I'm unsure where to start

http://kerneltrap.org/mailarchive/linux-netdev/2008/9/8/3233464
probably thats the place.

$ uname -a
Linux ds 2.6.28-6-generic #17-Ubuntu SMP Fri Jan 30 15:34:36 UTC 2009 i686 GNU/Linux

bug is still here

I just booted the Jaunty Alpha 4 live cd and it looks like this issue is fixed.

I can successfully use ubuntu to associate with my phone, setup a pass code and then browse and receive files from my phone. None of that worked with intrepid.

Unfortunately I have no time to test it further.

I confirm this

2009/2/5 BrowneR <email address hidden>

> I just booted the Jaunty Alpha 4 live cd and it looks like this issue is
> fixed.
>
> I can successfully use ubuntu to associate with my phone, setup a pass
> code and then browse and receive files from my phone. None of that
> worked with intrepid.
>
> Unfortunately I have no time to test it further.
>
> --
> Bluetooth association no longer works
> https://bugs.launchpad.net/bugs/268502
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Booting Jaunty doesn't fix it for me.

Or actually, I haven't tried that yet. I tried installing Jaunty Alpha 4 (from alternate CD) into a vm in VirtualBox, then connected my Bluetooth adapter to that.

The result was fail. Nothing happened. Still dead. Bupkus.

But I'll try the Jaunty live-cd tomorrow and see if that changes anything - which I really doubt.

The problem still exists on the very latest upstream kernel. I'm going to bisect between 2.6.26 and 2.6.27, and report the bad commit to the Bluetooth guys. Then it shouldn't be too long before we have a fix.

Can be this bug added for Ubuntu 9.04 milestone?

Brian Rogers wrote:
> The problem still exists on the very latest upstream kernel. I'm going
> to bisect between 2.6.26 and 2.6.27, and report the bad commit to the
> Bluetooth guys. Then it shouldn't be too long before we have a fix.

If you narrow it down to the bad commit, I'll be happy to test it with
my S-E phone, which has similar but not quite the same problems.

(Btw, is it even possible to bisect Ubuntu kernels? A recent article
from lwn.net notes that distro kernels have distro-specific initramfs
setups making it impossible to use vanilla kernels on some laptop
configurations now...)

-- Jamie

Well it turns out it's not as simple as just a bad commit. The problem is with the newer btusb driver that replaced hci_usb by default in 2.6.27. It looks like that newer driver never worked correctly with certain Bluetooth dongles.

Is it not possible to bring the old driver back for some devices, coexisting with the new driver? At least until the new driver gets support for the problematic hardware.

Alternatively, how much work would it be to port the working code from hci_usb into btusb? How different are the two drivers?

The configuration menu only lets you select one of the two drivers, but I don't see a reason the two should conflict as long as you only allow one of them to load.

Switching to the older driver is more of a workaround than a solution. The new driver needs to be fixed one way or another, and once we have the fix, we can backport it.

But anyone who wants working Bluetooth today can build a custom kernel with hci_usb instead of btusb.

1. I do use a D-Link DBT-122 Bluetooth adapter with kernel 2.6.27
=====================================

Kernel: uname -r
2.6.27-11-generic

Bluetooth dongle: lsusb
Bus 001 Device 006: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

Bluetooth software: dpkg --get-selections | grep blue
blueman deinstall
bluetooth3 install
bluez deinstall
bluez-audio deinstall
bluez-cups install
bluez-gnome install
bluez-utils deinstall
bluez3-audio install
bluez3-utils install
gnome-bluetooth install
libbluetooth2 install
libbluetooth3 install
python-bluez install

Bluetooth software version: dpkg -l bluetooth3
... bluetooth3 3.26-0ubuntu14 Bluetooth stack utilities
(This workaround -- blue3 instead of blue4 -- was given by emersom on 2008-11-07 in https://bugs.launchpad.net/bugs/289836 and I confirmed there the same day that it worked for me also)

This combination recognises the adapter: hcitool dev
Devices:
 hci0 00:13:46:00:55:A0

Adapter is active: hciconfig
hci0: Type: USB
 BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
 UP RUNNING PSCAN ISCAN
 RX bytes:937 acl:0 sco:0 events:22 errors:0
 TX bytes:332 acl:0 sco:0 commands:22 errors:0

Adapter sees my phone: hcitool inq
Inquiring ...
 00:13:70:0E:8A:77 clock offset: 0x30c9 class: 0x520204

but reads the details only as root: sudo hcitool info 00:13:70:0E:8A:77
Requesting information ...
 BD Address: 00:13:70:0E:8A:77
 LMP Version: 1.2 (0x2) LMP Subversion: 0x4db
 Manufacturer: Cambridge Silicon Radio (10)
 Features: et cetera
(funny: a few years ago I has also: Device Name: Nokia 6021)

The most important: I could pair (don't ask me how) and I use to backup my phone's address book and calendar about once a week with Wammu, wich is all I ask to Bluetooth.

2. There seems to be Bluetooth problems at three different levels
=====================================
A. Kernel
---------
Some Bluetooth adapters may not function with kernel 2.6.27. This is definitely NOT the case with D-Link DBT-122 because I DO use it successfully. See 1. above. See also 2008-11-07 in https://bugs.launchpad.net/bugs/289836

B. Bluetooth version
-------------------
Some Bluetooth adapters may not function with Bluetooth 4 -- see my initial post as https://bugs.launchpad.net/bugs/291298 and on 2008-11-04 in https://bugs.launchpad.net/bugs/289836 -- but function with Bluetooth 3 as explained above and on 2008-11-07 in https://bugs.launchpad.net/bugs/289836.

C. Pairing
----------
Even if one has no kernel problem and/or solved the Bluetooth version problem to the point that hciconfig shows an active device, there can be still problems of pairing. A lot of people in this and other bugs (marked as duplicates) complain about pairing.
Pairing has always been tricky and poorly documented. Forums are full of advice about different flavours of "pin helper", including replacing the pin helper altogether by 'echo "PIN:1234" '. When I began using my dongle with my Nokia phone two or three years ago, I had to hack the pairing in this way. (Story, in French, http://www.meeus-d.be/linux/bluetooth.html.) This was under control of /etc/bluetooth/hcid.conf. I do not now if it is still the case.

Ideally, one should fil...

With the latest Jaunty kernel source 2.6.28-6.17 and a custom compiled kernel that has the old hci_usb driver , bluetooth works on my laptop. It was only working with 2.6.24 kernel before. Other relevant packages:
bluez 4.12
bluez-utils 4.12
libbluetooth2 3.29
libbluetooth3 4.12

I tried Integrated System Solution Corp. KY-BT100 Bluetooth Adapter on Ubuntu 9.04 Alpha 4 (Live CD downloaded from ubuntu.org website) and it works on my laptop (Toshiba M40X) but only one usb port recognizes it; on the other two it doesn't work.

This is fixed in the bluetooth-testing repository at git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-testing.git

With this, I have my KY-BT100 working perfectly.

Brian Rogers wrote:
> The configuration menu only lets you select one of the two drivers, but
> I don't see a reason the two should conflict as long as you only allow
> one of them to load.
>
> Switching to the older driver is more of a workaround than a solution.
> The new driver needs to be fixed one way or another, and once we have
> the fix, we can backport it.
>
> But anyone who wants working Bluetooth today can build a custom kernel
> with hci_usb instead of btusb.

Thanks for finding that, but it didn't help.

I've tried hci_usb with Jaunty's 2.6.28-7, and it didn't solve my
problem.

My next attempt will be to try and build the entire Bluetooth stack
from 2.6.24 grafted into the newer kernel, and see if that works...

(I suspect my problem is a different bug.)

-- Jamie

I tried Jaunty Alpha 4 i386 live cd this afternoon - dongle and Samsung A411 phone paired but would not share files

Whereas current Intrepid kernel will not pair

I too tried jaunty alpha 4, however I saw no difference. My bt dongle is recognized but my logitech keyboard is not detected like it used to.

I've tested kernel 2.6.24-22 from hardy in jaunty with bluez 4.30. Receiving files is working, but nautilus-sendto gives information: "Obex push file transfer not supported". I'll soon check kernel 2.6.24 with blueman.

ID 1131:1004 Integrated System Solution Corp. Bluetooth Device

Brian Rogers wrote on 2009-02-09:
> This is fixed in the bluetooth-testing repository at git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-testing.git
>
> With this, I have my KY-BT100 working perfectly.

Is there a chance that this fix will be available for Intrepid ever? I'm really thinking on switching to another distro because of the issues in Ubuntu like this.

@Deje

>I'm really thinking on switching to another distro because of the issues in Ubuntu like this.

Bluetooth for my devices are broken in fedora 10 as well. In fact as far as I have experienced all all fedora releases have this regression since package updates that came out ~August 2008. Unfortunately it seems this regression does not affect all dongles/devices so little has been done. Very disappointing. Personally I have gone back to requiring Windows Vista just so I can use my bluetooth devices.

If just OBEX push doesn't work, then you're now seeing nautilus-sendto bug 282325. You can work around it using 'send files to device' in context menu of the Bluetooth applet icon.

Today I got Bluetooth working on 2.6.27 by cherry-picking several commits leading up to the fix, then the fix. I needed to do that because the fix is entangled with other work in the same file. Now that I know it works on this kernel version, I need to re-write the fix on top of 2.6.27 so it doesn't need those other changes.

Then we'll have a patch suitable for a stable release update for Intrepid.

Thanks, Brian, you are the man! I hope it will be possible again to use my KY-BT100 under Ubuntu without reverting to Hardy. Thank you for your work on this!

Props to all those who have encountered and worked on this - I just ran into this same problem (KY-BT100 dongle works under Hardy, not under Intrepid). I have to say that while I had about 10 minutes of frustration, it's outstanding to jump on launchpad and see that people have already hammered out workarounds *and* a fix seems to be in the works. Go community and thanks!

I wrote:
> Brian Rogers wrote:
> > Switching to the older driver is more of a workaround than a solution.
> > But anyone who wants working Bluetooth today can build a custom
> > kernel with hci_usb instead of btusb.
>
> Thanks for finding that, but it didn't help.
> I've tried hci_usb with Jaunty's 2.6.28-7, and it didn't solve my
> problem.
>
> My next attempt will be to try and build the entire Bluetooth stack
> from 2.6.24 grafted into the newer kernel, and see if that works...

Ok, success for me!

I forward-ported the Bluetooth protocol stack from 2.6.24 to 2.6.28, and now I'm able to connect to my Sony-Ericsson phone over Bluetooth, and using the BNEP protocol connect to the internet over 3G.

I'm using the connection to post this command, and have used it to fetch about 50 web pages.

Note I did *not* have to change the drivers, only the network protocol stack... I'm using the "btusb" driver module, which is the one Ubuntu enables.

It's hard to be sure, but for anyone wanting to reproduce this and see if it fixes their problem, I think the steps for the forward port are as follows:

    1. Fetch a linux-2.6.24 source tree from kernel.org, and unpack it.
        (http://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.24.tar.bz2).
    2. Install package kernel-source-2.6.28 (from Jaunty's repo).
        (Start from https://launchpad.net/ubuntu/+source/linux, I think you can
        download a package file and install it with dpkg).
    3. Unpack /usr/src/linux-source-2.6.28.tar.bz2 to somewhere handy.
    4. Enter the unpacked linux-source-2.6.28 directory.
    5. cp /boot/config-$(uname -r) .config
    6. mv net/bluetooth net/bluetooth.orig
    7. mv include/net/bluetooth include/net/bluetooth.orig
    8. Copy files from 2.6.24:
           cp -r ../linux-2.6.24/net/bluetooth net/
           cp -r ../linux-2.6.24/include/net/bluetooth include/net/
    9. Apply a tiny patch to make it compile (attached to this comment).
    10. make bzImage
    11. make modules
    12. make install modules_install
    13. update-initramfs -a
    14. grub-update
    15. Reboot with the new kernel...

It's a fairly trivial forward port.

Looking at the attachments in this bug report, I noticed that "diff" was not flagged as a patch. A patch contains changes to an Ubuntu package that will resolve a bug and this attachment is one! Subsequently, I've checked the patch flag for it. In the future when submitting patches please use the patch checkbox as there are some Launchpad searches that use this feature. Thanks for your contribution Jamie Lokier!

Today I'd tested bluetooth on 2.6.24-22-generic + bluez 4.30 and... it isn't work!

For whatever it's worth, when I bought a new BT 2.0 dongle it immediately worked flawlessly. It's the same generic chinese/taiwan brand (Billionton)as my first (which does not work) but it identifies completely different:

[code]Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)[/code]

In the forums, it seems people have had success with 2.0-compliant devices, while 1.1 and older suffer from whatever this is.

isecore wrote:
> For whatever it's worth, when I bought a new BT 2.0 dongle it
> immediately worked flawlessly. It's the same generic chinese/taiwan
> brand (Billionton)as my first (which does not work) but it identifies
> completely different:
>
> [code]Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd
> Bluetooth Dongle (HCI mode)[/code]
>
> In the forums, it seems people have had success with 2.0-compliant
> devices, while 1.1 and older suffer from whatever this is.

Mine has the same id as your new one and doesn't work:

Bus 004 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd
Bluetooth Dongle (HCI mode)

But then I've said my bug may be a different one.

-- Jamie

Jamie's patch doesn't work for me:

In file included from net/bluetooth/rfcomm/core.c:49:
include/net/bluetooth/rfcomm.h:255: error: expected ‘)’ before ‘(’ token
include/net/bluetooth/rfcomm.h:256: error: expected ‘)’ before ‘(’ token
include/net/bluetooth/rfcomm.h: In function ‘rfcomm_dlc_throttle’:
include/net/bluetooth/rfcomm.h:261: error: implicit declaration of function ‘__rfcomm_dlc_throttle’
include/net/bluetooth/rfcomm.h: In function ‘rfcomm_dlc_unthrottle’:
include/net/bluetooth/rfcomm.h:267: error: implicit declaration of function ‘__rfcomm_dlc_unthrottle’
net/bluetooth/rfcomm/core.c: At top level:
net/bluetooth/rfcomm/core.c:470: warning: conflicting types for ‘__rfcomm_dlc_throttle’
include/net/bluetooth/rfcomm.h:261: warning: previous implicit declaration of ‘__rfcomm_dlc_throttle’ was here
net/bluetooth/rfcomm/core.c:481: warning: conflicting types for ‘__rfcomm_dlc_unthrottle’
include/net/bluetooth/rfcomm.h:267: warning: previous implicit declaration of ‘__rfcomm_dlc_unthrottle’ was here
make[4]: *** [net/bluetooth/rfcomm/core.o] Error 1
make[3]: *** [net/bluetooth/rfcomm] Error 2
make[2]: *** [net/bluetooth] Error 2
make[1]: *** [net] Error 2
make[1]: Leaving directory `/home/nagper/src/linux-source-2.6.28'
make: *** [debian/stamp-build-kernel] Error 2

NagPer

Thanks for trying, NagPer. Yes, there's a small hunk missing from my "diff" - in include/net/bluetooth/rfcomm.h. Here's a new one, called
make_2.6.24_bluetooth_work_in_2.6.28.diff. You still apply it after copying over the bluetooth tree from 2.6.24 over 2.6.28, as per the instructions.

Here's an alternative patch which might be easier for some people to try.
Just apply this one to a linux-source-2.6.28-7 tree.

It's exactly the same as the previous small patch, but you don't have fetch a 2.6.24 tree yourself and copy bits over.

There's no point trying both patches, they're the same code.

@Jamie Lokier
Is your latest patch (114,8 KiB) needs copying files from kernel 2.6.24?

@Jamie Lokier

I have just taken the time to compile 2.6.28.6 with your 114kb patch and rebooted successfully.

I am now able to successfully pair with the mobile device (which i couldn't do previously) but I am unable to send a file from my phone to the laptop, after opening the gnome bluetooth file sharing application (which used to work)

I am unable to SEND files from the laptop to the mobile device (times out)

Browsing files on the mobile device from the bluetooth icon in the systray causes my phone to reboot....but this is likely my phone's problem and I recall it used to do that too. However, it did actually get as far as to connect, which is will not previously do on the buggy BT kernels.

I also tried multisync which also did not work and eventually timed out scanning for bluetooth devices to sync to.

Can you confirm that you can / cannot send a file from your mobile device to the laptop?

Jamie, please let me know your thoughts / test results.

For you guys who aren't able to get this test working here is the complete set of working commands I issued:

  514 tar -xjvpf linux-source-2.6.28.tar.bz2
  515 cd linux-source-2.6.28
  516 cp /boot/config-$(uname -r) .config
  517 patch -p1 < /home/rick/Desktop/put_old_working_bluetooth_into_2.6.28_7.diff
  518 make bzImage
  519 make modules
  520 make install modules_install
  527 update-initramfs -k 2.6.28.6 -c
  528 update-grub

@Ari no you don't need to copy the files with this patch. Jamie explains this to you in the message above!

Richard Hamnett wrote:
> Can you confirm that you can / cannot send a file from your mobile
> device to the laptop?

I never send files over Bluetooth between phone and laptop, and don't
know how to it.

I just tried it now, with the patched kernel, and these things happened:

   - When I asked the phone to "send by bluetooth" a picture file,
     it searched for devices and couldn't see my laptop, even though I
     set the laptop to be visible in the GNOME Bluetooth Preferences.

   - When in GNOME Bluetooth Preferences I told it to search for a new
     device to connect to, it couldn't see the phone even though I set the
     phone to be visible.

   - The laptop does have the phone in its list of known devices, so
     when I clicked button in GNOME Bluetooth Preferences to connect
     explicitly, the button grayed out, but the status icon still
     didn't show it connected after several seconds.

   - Despite the above "not connecting properly as shown by GNOME",
     when I ran pand on the laptop, it *was* able to make a 3G data
     connection to the internet through the phone!

   - Even though the phone was connected and had 3G networking going
     on, and the phone's screen showed a connected icon, the phone
     _still_ didn't show the laptop in the list of devices to send
     files to.

I'm guessing the laptop isn't advertising its ability to receive
files. Since I never use this part of Bluetooth, and there's no
option for it in GNOME Bluetooth Preferences (they removed it!),
I don't know if this has anything to do with the kernel changes.

All I know which works is 3g data networking - running "pand" on the
laptop, that pairing with the phone, and the resulting BNEP network
able to be used as an internet connection. (Btw, it's annoying that
"pand" isn't in the new bluez packages at all... and the scripts on
bluez.org using D-BUS to connect don't work with the new version
of bluez... a different bug).

It's possible that sending and receiving files is not connected with
the kernel change at all, since I noticed some people are reporting
bugs with that and responses say it's something to do with the OBEX
server, not pairing.

As I don't use this part of Bluetooth at all, I'm not interested in
fiddling about with OBEX except just trying it for you now :-)

-- Jamie

Thanks Jamie,

I'm not sure what we do now? This thread has gotten so long that you cannot even view these comments without clicking on "view all xxx comments" !

I am not having the success you had with bluetooth, because I am using some more advanced features....but this should not really be happening if the only problem was the kernel bluetooth upgrade.

We NEED the fix.

Richard Hamnett wrote:
> I am not having the success you had with bluetooth, because I am using
> some more advanced features....but this should not really be happening
> if the only problem was the kernel bluetooth upgrade.

I'm pretty sure there's at least 3 different bugs affecting you:

   1. One which is fixed by changing kernel USB bluetooth
      driver only.

   2. One which is fixed by changing kernel bluetooth network
      protocols only.

   3. One to do with OBEX and Gnome for file transfers.

-- Jamie

@Jamie Lokier

Thanks for the reply.

Can you kindly doa quick summary of what I need to do to remedy each point in your list?

Cheers
Rich

Kernel 2.6.28.7 patched = bluetooth still doesn't work. Can someone compile generic kernel for ubuntu and send .debs @launchpad?

I sent my proposed fix to the kernel team mailing list. It consists of three cherry-picks from upstream (though one hasn't merged into mainline yet), and some conflict resolution for the last patch.

For anyone that wants to build their own kernel and test it, I've rolled it all into a single patch, which I'm attaching.

Jamie's patch fixed the problem for me.

I used someone's patch on one of these email lists and it fixed the
problem. I can confirm it has not been fixed in Intrepid.

On 3/5/09, uboltun <email address hidden> wrote:
> Jamie's patch fixed the problem for me.
>
> --
> Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
> https://bugs.launchpad.net/bugs/268502
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
PGP Public Encryption Key:
http://johndoe32102002.blogspot.com/

I've kernel compiled from linux-source-2.6.28. I did choice in config:
Networking support
  Bluetooth subsystem support
and disabling HCI USB driver
enabling HCI USB driver (old version)
and compile it. First what I must do:
$ sudo /etc/init.d/bluetooth restart
then
Search new devices, add *** key - it works okay
then
Send files to device - it doesn't work
output message in red color:
org.openbox.Error.ConnectionRefused

Wow! I tried second test and I sent files on my phone! Without patch Jammy Lokier. BlueZ 4.32.
Linux -> Phone = OK
Phone -> Linux = doesn't work

It works just a view times with Integrated System Solution Corp.
Fully updated Jaunty 64
Bluetooth Laser Mouse

After reboot, there was no connection anymore. (the mouse was set to always trusted, the bluetooth stick is visible)

hci0: Type: USB
        BD Address: 00:11:67:C3:6B:70 ACL MTU: 1021:4 SCO MTU: 48:10
        UP RUNNING PSCAN ISCAN
        RX bytes:2066 acl:0 sco:0 events:70 errors:0
        TX bytes:820 acl:0 sco:0 commands:63 errors:0
        Features: 0xff 0xfe 0xff 0x7e 0x98 0x19 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'mellhen-home-bluetooth'
        Class: 0x1a2104
        Service Classes: Networking, Capturing, Object Transfer
        Device Class: Computer, Desktop workstation
        HCI Ver: 2.0 (0x3) HCI Rev: 0x302 LMP Ver: 2.0 (0x3) LMP Subver: 0x302
        Manufacturer: Integrated System Solution Corp. (57)

To get it work:
1 i deleted all paired devices manually
2 restarted bluetooth
3 restarted kbluetooth
4 paired the device

But after reboot no connection is possible anymore.
Dell Wirelleless (Broadcom) on my notebook works allways.

see attechment for detailes.

attechment is called "kbluetooth"

I guess that the first step to fix this bug is include command while booting Ubuntu
$ sudo /etc/init.d/bluetooth restart

Bluetooth doesn't work for me too (Ubuntu 8.10/9.04a5). I'm able to view another bluetooth devices, but sending or receiving files failed with the following errors.

lsusb -vvv:
Bus 006 Device 003: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize0 16
  idVendor 0x1131 Integrated System Solution Corp.
  idProduct 0x1004 Bluetooth Device
  bcdDevice 3.73
  iManufacturer 1 ISSC
  iProduct 2 ISSCEDRBTA
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 186
    bNumInterfaces 3
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
      Self Powered
    MaxPower 0mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 1
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 1
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x03 EP 3 OUT
        bmAttributes 1
          Transfer Type Isochronous
          Synch Type None
          Usage Type Data
        wMa...

As one step to get the proposed patches included I have prepared test kernels based on those patches. They can be found at http://people.ubuntu.com/~smb/bug268502/
Please verify whether this solves the issue. Thanks

I have same problem with bluetooth here, since Ubuntu 8.10 new (and fresh)
install until now, in sync with expeimental repositories
(for KDE 4.2, newest bt packs, etc, etc)...

I had changed my bt dongle (usb) thinking that are a problem with first, but
it was right and bt stack that wasn't (and sitll isn't) the problem...

I tried all kind of solutions, except kernel compile: 1. using experimental
repositories. 2. using alternative bueman reproitories, 3. downgrading
kdebluetooth4 to KDE 3.X, downgrading bt 4 stack to bt 3 stack, but noking
worked.

Curious, a cople of times, I get bt working for receiving/sending files from
other computer. Curious again, just for one or to times I get bt working for
sending files to mobeile (a1200), but not for receiving...

Oh, yes: Based on error message of obex-server, II had tried change
obex-server. I put obexd (work one time, neve more). Reinstalled
obex-server, or did a full remove of obex-server from my notebook fo them
install from source (manual compile and install)

But nothing! BT with a1200e still wont' work.

Any sugests that could I do?

2009/3/10 Stefan Bader <email address hidden>

> As one step to get the proposed patches included I have prepared test
> kernels based on those patches. They can be found at
> http://people.ubuntu.com/~smb/bug268502/<http://people.ubuntu.com/%7Esmb/bug268502/>
> Please verify whether this solves the issue. Thanks
>
> --
> Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
> https://bugs.launchpad.net/bugs/268502
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in The Linux Kernel: In Progress
> Status in “linux” source package in Ubuntu: In Progress
>
> Bug description:
> Bluetooth doesn't work for at least the following devices:
> 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
>
> They don't work properly with the newer btusb driver, which replaced
> hci_usb by default in 2.6.27. This hasn't been fixed upstream as of
> v2.6.29-rc3.
>
> Original message below:
>
> Association with Bluetooth works using kernel 2.6.26, since the updates to
> 2.6.27 (both -1 and -2) association fails. I can scan and see bluetooth
> devices but not pair.
>
> Using my phone, I start the association process, the phone asks for a
> passkey, and in 2.6.26 the popup window appears normally allowing me to
> enter the passkey. In 2.6.27 the dialog box never appears.
>
> If I use hcitool:
>
> :~$ sudo hcitool cc 00:1B:59:96:A6:DD
> :~$ sudo hcitool auth 00:1B:59:96:A6:DD
> HCI authentication request failed: Connection timed out
>
> the dialog box appears very very briefly then vanishes.
>
> dmesg shows a couple of problems:
>
> [25791.306170] btusb_intr_complete: hci0 urb ffff88004dd0fb40 failed to
> resubmit (19)
> [25791.315446] btusb_send_frame: hci0 urb ffff880048542840 submission
> failed
>
> and the syslog shows that there was an attempt to associate:
>
> Sep 23 08:16:59 charlie hcid[5903]: link_key_request
> (sb...

@Stefan Bader

This package 100% fixed the problem I have been trying to resolve for MONTHS, so I would like to thank you for your efforts.

Strangely, I'm unsure as to how you created the package ...does it differ to the method I described in my comment #101?

Thank you

That actually are not mine efforts but those of Brian (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502/comments/107). So the package was created by using the current intrepid kernel and then adding the three patches Brian found (which I added to the peoples page).

The packages from Stefan Bader fixed my problem too. The Bluetooth usb device works perfectly!

@Stefan Bader - ok great....well I appreciate you posting the link! :)

@Sebastian Riebel - great news !

I am hoping that this will be enough to get the fixes added into the repos!

Didn't solve my problem:

# hciconfig
hci0: Type: USB
 BD Address: 00:0A:3A:87:A5:8D ACL MTU: 1021:8 SCO MTU: 64:1
 UP RUNNING
 RX bytes:211 acl:0 sco:0 events:27 errors:0
 TX bytes:841 acl:0 sco:0 commands:27 errors:0

# hcitool inq
Inquiring ...
Inquiry failed.: Connection timed out

Stefan, any chance of getting a 2.6.28-9-generic AMD64 patched test kernel?

Just installed Jaunty alpha6, and just about everything works perfectly right out of the box, except for Bluetooth (DBT-122) which has the same problem as in Intrepid.

Hi Sami,

did you really intend to send this to me? I'm on this bug's watch list, but I
have not ever written a comment on this. And I do not use the AMD64 platform.
In the meantime I purchased a different bluetooth dongle that just works fine.

Regards,
Stefan

Am Sonntag, 15. März 2009 schrieb Sami Mäkinen:
> Stefan, any chance of getting a 2.6.28-9-generic AMD64 patched test
> kernel?
>
> Just installed Jaunty alpha6, and just about everything works perfectly
> right out of the box, except for Bluetooth (DBT-122) which has the same
> problem as in Intrepid.

Yep, Jamie Lokier's patch fixed this bug. But not enough...
The full description this bug fix:

1) Remove BT_HCIBTUSB driver and restore BT_HCIUSB (old version driver) - apply Jamie Lokier's patch
2) Write patch for bluez (?) - with old driver version Ubuntu needs a restart of bluetooth (sudo /etc/init.d/bluetooth restart) so this command must be execute while system's booting

For the future:
Add for bluez-gnome receiving files in the relation Phone -> Linux

This patch must be applied into jaunty! (of course including 2nd step)
Ubuntu's developers, please fix this bug.

Ari,

Have you tried my patch? Jamie Lokier's patch is useful for investigating the problem, but it's not the kind of thing that can be committed as a solution. For one, it involves undoing any bug fixes that occurred between 2.6.24 and 2.6.28. My patch just pulls the solution from upstream.

You can get a pre-built kernel at the link Stefan Bader posted: http://people.ubuntu.com/~smb/bug268502/

Also, it'd be nice if anyone reporting a success or failure with that kernel would mention which dongle they are using.

My comment was for Stefan Bader, who built the kernel based on Brian Roger's patch.

Since the patched kernel is for Intrepid, I can't test it in Jaunty, which also features this issue.

Brian,
Your patch worked with my bluetooth dongle and linux_2.6.28-8.26 custom build kernel:
Bus 003 Device 002: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
I was having problems connecting a GPS device before.

@Sami, Jaunty based kernels including the patch at the same place (http://people.ubuntu.com/~smb/bug268502/)

@Brian Rogers
https://bugs.launchpad.net/linux/+bug/268502/comments/110
I've got tested kernels from http://people.ubuntu.com/~smb/bug268502/ and both solutions fixing bug.

Thanks Stefan Bader!

Bus 002 Device 008: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

Booted back into Intrepid, and this kernel does not seem to affect the problem. I'm still getting hci0 timeouts. I'm not sure if I have the new kernel set up correctly though. I downloaded linux-image-2.6.27-11-generic_2.6.27-11.27b268502v1_amd64.deb and then did a dpkg -i for that file and rebooted. However after installation the timestamp for the kernel is 2009-03-11 rather than 2009-03-18 (=today) as I'd expect. aptitude shows two versions of that kernel available, and the installed one is 2.6.27-11b268502v1 so from that I would guess that the patched kernel is indeed in use. uname -a says:
Linux skybox 2.6.27-11-generic #1 SMP Tue Mar 10 21:51:11 UTC 2009 x86_64 GNU/Linux

So did I do something wrong, or does this patch not fix my problem?

Booting into Jaunty now.

In Jaunty now

Linux homeskybox 2.6.28-11-generic #34b268502v1 SMP Wed Mar 18 16:32:33 CET 2009 x86_64 GNU/Linux

This time I'm sure I have the right kernel.

No help - still getting hci0 command tx timeout

:(

Anything else I should do? This is a fresh alpha6 install of jaunty, just now updated to today's latest packages. No custom hacks or non-default settings, except for now this test kernel.

The problem with the D-Link Corp. DBT-122 Bluetooth adapter (ID 2001:f111) may not be a kernel problem. I once (7-3-2009) had it working (no timeout, could scan) with the btusb driver while the bluetoothd daemon was stopped (of was it mere chance?) This would indicate a Bluez bug, not a kernel bug (or a combination of two). I tried to file a separate bug on this (https://bugs.launchpad.net/bugs/329828) but I was maybe naive because nobody seems to mind.

@Sami Mäkinen
Did you put it into console?:
$ sudo /etc/init.d/bluetooth restart

Tried restarting bluetooth, no help. Also tried with bluetooth service stopped. Same thing, hci0 timeout.

Brian & Stefan,

Thanks for your work.

Brian's proposed patches and a test kernel based on them work well with my bluetooth dongle.

Details:
Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
OS Ubuntu 8.10 beta 64-bit (2.6.27-11-generic)
Patches from at http://people.ubuntu.com/~smb/bug268502/

Notes - what I did (I am not much experienced user ...):
1) Installed the right .deb of the patched Intrepid kernel.
2) rebooted
3) reinstalled all bluetooth related packages via Synaptic.
4) rebooted and profiled my kernel
5) rebooted

I have no problems with timeouts. Everything works as it used to in Hardy.
I have jused finished cleaning of 2 Nokia mobiles with Wammu.

lsusb: Bus 002 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

uname -a:Linux library 2.6.28-11-generic #34b268502v1 SMP Wed Mar 18 15:32:17 UTC 2009 i686 GNU/Linux (patched kernel)

I stop the daemon, take the dongle out and back in. Bingo:
sudo hciconfig hci0 up
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)

hcitool scan: Scanning ...
 00:13:70:0E:8A:77 Nokia 6021 (my phone is seen)

I start the daemon: sudo /etc/init.d/bluetooth start

hcitool scan: Scanning ...
Inquiry failed: Connection timed out

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:4866 acl:38 sco:0 events:187 errors:0
 TX bytes:1325 acl:34 sco:0 commands:44 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)

Conclusion: in my configuration the btusb kernel driver alone works, not with Bluez.

Abstract: so this patch is fixing bug. Problem with 2001:f111 D-Link Corp. [hex] DBT-122 is a separate bug, so developers - please include patch into linux-*-2.6.28-11-*, rebuild packages and upload into repos :) Who can talk to Canonical's/Ubuntu's developers?

You can try going to the #ubuntu-motu channel and asking them. Personally
though the success rate is low unless you give them a patch that they can
press the "approve" button on.

Booted 2.6.27.11 kernel (linked above) and could transfer files from phone to computer

bt dongle is Bus 004 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

Could not transfer from computer to phone but I have done some other stuff over the course of this bug and things could be broken.

If we have selected option "Show icon only, while adapter is connected", must execute command /etc/init.d/bluetooth restart so we must add this script to rc.local

DBT-122 is still a problem, procuding the command timeouts.

I borrowed a new device to test:
Bus 001 Device 003: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub [ednet]

This usb dongle works great, both on the patched kernel as well as the regular Ubuntu 2.6.28-10 kernel.

So for me this patched kernel does not make any difference, for better or worse.

Sending from Nokia N95 to computer failed, but sending from computer to N95 works. Also browsing works, although it is very slow and the browsing windows becomes grayed out for a while before later becoming active again, every time a directory or drive is changed. The sending from N95 to computer has once been fixed already, so this is another regression. I will try to locate that bug report and suggest reopening it.

disregard that last bit - sending from phone to computer works after manually installing and starting gnome-bluetooth. Odd that this is not automatically installed and started once bluetooth starts.

 tielie said earlier that ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle worked for them, but mine
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
does not work for me. Standard ubuntu 8.10 install, backports enabled.

I have tried to use the kernel
linux-image-2.6.28-11-generic_2.6.28-11.34b268502v1_i386.deb
from the link at http://people.ubuntu.com/~smb/bug268502/
but I then get "Error: Dependency not satisfiable: wireless-crda
screenshot attached. What should I do?
Sorry if this is a dumb question.

Ian

@Ian M. Stewart
You must download wireless-crda and install the package.
$ wget http://mirrors.kernel.org/ubuntu/pool/main/w/wireless-crda/wireless-crda_1.7_i386.deb
$ sudo dpkg -i wireless-crda_1.7_i386.deb

Or just use the 2.6.27 kernel at that same location instead.

Thank you to Ari, and to Brian. I tried the 2.6.28 kernel, and it's broken my nvidia drivers (and possibly other things?). However, with my USB dongles (as listed before), this has not fixed my bluetooth. The Bluetooth Device Wizard can still not see either dongle. Is there some other process I should be trying?

If you would be so kind, can you give me a quick lesson on how to get back to my original kernel? It might save me a lot of digging.

It was still worth trying :)

Ian

@Ian M. Stewart
type into console:

$ sudo /etc/init.d/bluetooth restart

Problem 2.6.28 with your nvidia - I guess this is configurable. If you want to config this, check dkms --help.

Some Bluetooth dongles may have a kernel problem but others not. People keep telling others to try new kernels and patch kernels. But for some dongles, there is no kernel problem but a Bluez daemon problem. See my test on 2009-03-18: with the daemon stopped, with btusb alone, my dongle scans my phone. With the daemon active, I get the hci0 timeout error message.

More people should do this test. Sudo etc/init.d/bluetooth stop and then try hciconfig -a and hcitool scan to see the result. (If hci0 is not recognized, it maybe efficient to take the dongle away and then back in and redo hciconfig-a and hcitool scan.) This way it is possible to separate btusb issues and bluetoothd issues.

I tried bluetooth/bluez/libbluetooth3 version 4.33+git20090327-0ubuntu1. There is no improvement. With a D-Link DBT-122, Bluez is still just as broken as five months ago.

Thanks for your help Ari. I don't see how the bluetooth restart would differ from a system restart - which is what I did to try the dongles. I also tried system restarts with the dongle in and with it out and put in later, but to no effect. The same tests with 2.6.27-11
I have since deleted the 2.6.28-11 and the 2.6.27-11 kernels from my menu.lst and reverted to 2.6.27-9, which I think must have been where I came from as the nvidia now works OK. I'd forgotten how horrible low graphics mode is!

It's getting very late here, and I have work tomorrow. I'll check back tomorrow night, but was only trying to give feedback on the use of those kernels as suggested.

People with the kernel problem can scan. It's just that nothing else works.

Stefan Bader,

The commit I took from bluetooth-next was merged upstream for 2.6.30 now that the merge window is open, so everything is officially upstream now. That means this is ready to go in the Jaunty kernel, right?

I subscribed Stefan. Stefan, can we cherrypick this?

@Martin, test kernels have been build with the expected patch. As the merge window is open now, it should get in and I will prepare a SRU.

Hello Stefan,

Stefan Bader [2009-03-30 8:36 -0000]:
> @Martin, test kernels have been build with the expected patch. As the
> merge window is open now, it should get in and I will prepare a SRU.

Thanks! I'm actually more concerned about Jaunty, but intrepid SRU is
okay if we can ensure that it doesn't cause regressions on other
hardware.

Stefan, Martin,

Where to get the kernel that includes the patch? I think I'm being bitten by this one in Jaunty.

> Where to get the kernel that includes the patch? I think I'm being
> bitten by this one in Jaunty.

Currently only as test kernels at (and the Jaunty version will be outdated by
the number of uploads in between):
http://people.ubuntu.com/~smb/bug268502/

No improvement with 4.34
---------------------------------------
uname -a : Linux library 2.6.28-11-generic #38-Ubuntu SMP Fri Mar 27 09:00:52 UTC 2009 i686 GNU/Linux
lsusb : Bus 002 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
dpkg -l | grep blue* : ii bluetooth 4.34-0ubuntu1
/etc/init.d/bluetooth status : * bluetooth is running
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:1340 acl:0 sco:0 events:39 errors:0
 TX bytes:1185 acl:0 sco:0 commands:49 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)

But as ususal, btusb alone works
------------------------------------------------
sudo /etc/init.d/bluetooth stop : * Stopping bluetooth
sudo hciconfig hci0 up
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:1688 acl:0 sco:0 events:50 errors:0
 TX bytes:1226 acl:0 sco:0 commands:61 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

Is it a other bug with DBT-122, right? So, please don't mark as a duplicate of bug #329828
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/329828

@Ari
I thought better to keep things separated and that's why I opened bug #329828
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/329828. At that time, this #268502 was registered as kernel bug only and I thought my problem was not kernel (my post 2009-02-07 above).
But is seems that Baptiste Mille-Mathias made the choice to group kernel and bluez problems (after all it may be an incompatibility between btsub and bluetoothd, revealed by DBT-122), to keep an eye on both I suppose. Therefore he wrote:
** Also affects: bluez (Ubuntu)
   Importance: Undecided
       Status: New
I am just a user. My concern is to see my problem solved. Thus my opening #329828. But of course Baptiste knows better and I am happy with #268502 as long as it concerns the bluez package also, and not only the kernel. (Anyway nobody worked on #329828.)

Dominique, I did finally get my DBT-122 to do as you described, i.e. I stop bluetooth, then pull the USB dongle out, put it back in, do hciconfig and then hcitool. I dunno what I messed up last time I tried it.

I can now scan for devices and connect to and query info from my N95 using hcitool, so at least some bits do indeed work even on my computer.

Same problem here with KY-BT100. I had problems with wiimote:
https://bugs.launchpad.net/bugs/291051

Long story short: Problems connecting the device,doing "hcitool cc MACaddress" at the same time that I try to connect make it to work in all machines. It has to be a simple thing.

Thanks for your work.

@Dominique Meeùs
I have tried what you suggested on 2009-03-29: The result was:

ian@******:~$ sudo hciconfig -a
hci0: Type: USB
 BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
 DOWN
 RX bytes:0 acl:0 sco:0 events:0 errors:0
 TX bytes:0 acl:0 sco:0 commands:0 errors:0

ian@******:~$ sudo hcitool scan
Device is not available: No such device

with both my USB dongles, either straight away or after unplugging and plugging back in.

@Stefan Bader
With this patch Ubuntu needs to be restarted after logging.
$ sudo /etc/init.d/bluetooth restart
Can you add to patch thing which can restart bluetooth while booting Ubuntu?

I have a dondle identified by device 1caa:0001 in lsusb... Just it. Vendor or Model are not identified.

Since Intrepid it is not working. Yesterday I upgraded to Jaunty and, after various other workarounds (sis671, no konsole [/dev/pts has not auto-mounting], slmodem... etc, that I could get work), bluetooth is just one that I couldn't!

Kdebluetooth starts. Other devices can see my notebook. But it can't see anybody.

In Intrepid, it at least see other devices (besides couldn't connect or paring). But now, nothing more...

This bug was fixed in the package linux - 2.6.28-11.39

---------------
linux (2.6.28-11.39) jaunty; urgency=low

  [ Alan Tull ]

  * SAUCE: mx51: fix to1.1 in mxc_iomux_set_input
    - LP: #348333

  [ Andy Whitcroft ]

  * SAUCE: acer: rfkill disable quirk for ACER Aspire One
    - LP: #319825

  [ Brad Figg ]

  * ARM: Increase CONFIG_BLK_DEV_RAM_SIZE for imx51 flavour.
    - LP: #349842
  * ARM: Enable rtl8187 for imx51
    - LP: #349526
  * ARM: Unset CONFIG_USB_STORAGE_DEBUG for imx51
    - LP: #348504

  [ Bryan Wu ]

  * build CRAMFS into kernel to support mounting CRAMFS initrd on iop32x
    machine
    - LP: #349104

  [ Michael Casadevall ]

  * [lpia] Change ATA, SCSI, SD, ext2-4 modules into compiled-in components
    - LP: #347458

  [ Rob Herring ]

  * SAUCE: imx51: fec: fix cache operations for receive
    - LP: #348333

  [ Sam Yang ]

  * SAUCE: Revert ENGR00103870 FEC reopening causes network wdog timeout
    - LP: #348333
  * SAUCE: imx51: fec cache flush functions are incorrect
    - LP: #348333

  [ Upstream Kernel Changes ]

  * Bluetooth: Add fine grained mem_flags usage to btusb driver
    - LP: #268502
  * Bluetooth: Handle bulk URBs in btusb driver from notify callback
    - LP: #268502
  * Bluetooth: Submit bulk URBs along with interrupt URBs
    - LP: #268502

 -- Tim Gardner <email address hidden> Wed, 01 Apr 2009 17:37:32 -0600

There should be no need to restart it and from the comments up to now I did not see that this was needed with the kernel patch. Can others comment on that?

Still no improvement. The bluetooth daemon seems to be incompatible with btusb.

lsusb | grep D-Link
Bus 002 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

uname -a
Linux library 2.6.28-11-generic #39-Ubuntu SMP Thu Apr 2 03:00:35 UTC 2009 i686 GNU/Linux

sudo /etc/init.d/bluetooth status
 * bluetooth is running

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)

sudo hcitool scan
Scanning ...
Inquiry failed: Connection timed out

sudo /etc/init.d/bluetooth stop
 * Stopping bluetooth

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)

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

No "timed out (110)" when bluetooth is not in the way.

Why this bug is affected by bluez [intrepid/jaunty] ?

I wonder why a functionality present in 8.04 and broken for the full duration of 8.10 (regression) can be still "Undecided" and not assigned three weeks before the launch of 9.04.
But I am not a developer and I do not know how such work is assigned in Canonical and in the community. Is there a resource (link) explaining the steps of preparation and launch of a new version?

@Dominique Meeùs

Thankyou!! ~7months later my bluetooth keyboard&mouse finnally works with latest kernel + your work around.

@ Ian M. Stewart

You might be missing a step or two. For reference my complete steps are:

1. sudo /etc/init.d/bluetooth stop
2. <unplug your bluetooth dongle and plug it back in now>
3. sudo hciconfig hci0 up
4. hciconfig -a
5. sudo hcitool scan
6. sudo hidd --search 00:07:61:9D:87:66

(Yes i'm using hidd from bluez-compat to connect, I don't know how else to connect)

For interest here's the full log:

$ lsusb | grep Blue
Bus 003 Device 004: ID 22b8:0850 Motorola PCS Bluetooth Device
leifer@leifer-desktop:~$ uname -a
Linux leifer-desktop 2.6.28-11-generic #40-Ubuntu SMP Fri Apr 3 17:39:51 UTC 2009 i686 GNU/Linux

leifer@leifer-desktop:~$ sudo /etc/init.d/bluetooth start
 * Starting bluetooth [ OK ]
leifer@leifer-desktop:~$ hciconfig -a
hci0: Type: USB
 BD Address: 00:0C:55:36:1E:56 ACL MTU: 377:10 SCO MTU: 16:0
 UP RUNNING
 RX bytes:667 acl:0 sco:0 events:19 errors:0
 TX bytes:578 acl:0 sco:0 commands:21 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)
leifer@leifer-desktop:~$ sudo hcitool scan
Scanning ...
Inquiry failed: Connection timed out

Ok lets try turning off bluetoothd.

$ sudo /etc/init.d/bluetooth stop
 * Stopping bluetooth [ OK ]
leifer@leifer-desktop:~$ sudo hciconfig hci0 up
leifer@leifer-desktop:~$ hciconfig -a
hci0: Type: USB
 BD Address: 00:0C:55:36:1E:56 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)

leifer@leifer-desktop:~$ sudo hcitool scan
Scanning ...
 00:07:61:9D:87:66 Logitech Cordless MediaBoard Pro(TM)
leifer@leifer-desktop:~$ sudo hidd --search 00:07:61:9D:87:66
Searching ...
 Connecting to device 00:07:61:9D:87:66

Success!

Just for your information about current situation in Intrepid:

I had installed the patched kernel for 64-bit Intrepid and my USB bluetooth started to work flawlessly. Today the update system offered newer kernel version. After I installed the update I am back in the situation before the patchech kernel - my USB bluetooth cannot pair phones etc. => Recommendation: Until the fix is committed do not install kernel updates or they will replace the patched kernel ...

Is it way to solve this problem in intrepid 32-bit?
my dongle is ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
do i need to patch a kernel or it should be fixed by update?

@ Stiff
As you may see at the top of the page, this is a two-sided bug, with a kernel side (btusb driver) and a Bluez side. The kernel side is said to be fixed. The Bluez side is qualified as New and Undecided. As a result nobody seems to be working on this any more (the Bluez side is not assigned, at least). Shall we see two successive version of Ubuntu (8.10 and 9.04) with the same regression from 8.04 going on for some rather popular hardware?
It may be an upstream bug. I wonder if Bluetooth is broken in all distributions using Bluez 4.xx or only in Ubuntu. I am not a developer and I do not feel like subscribing to a mailing list of Bluez developers to put the question.
Leif Gruenwoldt above (2009-04-05) says that I solved his problem with the hint of stopping bluetooth. Maybe an other software is used to connect keyboard and mouse. With bluetooth stopped, my phone is recognized, but I cannot do anything useful with it. Softwares as Wammu, or bluez-gnome, or blueman want bluetooth started.
In the meanwhile, I reinstalled 8.04 on an old laptop, moved the dongle to the laptop, and I sync my phone with this (mostly the agenda), and copy the files afterwards to other computers to read my agenda in Lightning (Thunderbird extension).

I tried to launch ubuntu intrepid with kernel 2.6.24 from hardy and my dongle was worked fine. Therefore, I would like to try fixing this bug in kernel.
status of bug in intrepid "Fix Committed", what does it mean? that i can download update from repository? or i must patch the kernel modules manually?

Fix committed means it is in our git repo (kernel.ubuntu.com). It has not been uploaded yet, but will first appear in the proposed updates and later in the normal updates.

Got Bluez 4.35 just now. Just as broken as always since 4.xx.

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:327 acl:0 sco:0 commands:21 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)

Confirming problems in current Jaunty Release Candidate with USB Bluetooth dongle that comes with the Logitech DiNovo Edge keyboard. It will initially work in HCI mode (i.e. pairing with keyboard works), but if left idle, the dongle will suddenly revert to HID-mode, and I lose the Bluetooth device.

Here's what appears in the kernel log when the dongle suddenly reverts itself to HID-mode:
[164344.428180] usb 2-3.1: reset low speed USB device using ehci_hcd and address 5
[191730.936976] usb 8-2: USB disconnect, address 6
[191730.936978] usb 8-2.1: USB disconnect, address 9
[191730.937941] btusb_intr_complete: hci0 urb ffff88020b2e8240 failed to resubmit (19)
[191730.937950] btusb_bulk_complete: hci0 urb ffff88020b2e83c0 failed to resubmit (19)
[191730.938939] btusb_bulk_complete: hci0 urb ffff88020b2e86c0 failed to resubmit (19)
[191730.939124] btusb_send_frame: hci0 urb ffff880135304f00 submission failed
[191731.188639] usb 8-2.2: USB disconnect, address 7
[191731.220736] usb 8-2.3: USB disconnect, address 8
[191731.920011] usb 8-2: new full speed USB device using uhci_hcd and address 10
[191732.101937] usb 8-2: configuration #1 chosen from 1 choice
[191732.104908] hub 8-2:1.0: USB hub found
[191732.106862] hub 8-2:1.0: 3 ports detected
[191732.389849] usb 8-2.2: new full speed USB device using uhci_hcd and address 11
[191732.542916] usb 8-2.2: configuration #1 chosen from 1 choice
[191732.554127] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2.2/8-2.2:1.0/input/input13
[191732.580592] generic-usb 0003:046D:C713.000A: input,hidraw2: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.2-2.2/input0
[191732.657823] usb 8-2.3: new full speed USB device using uhci_hcd and address 12
[191732.817074] usb 8-2.3: configuration #1 chosen from 1 choice
[191732.836757] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2.3/8-2.3:1.0/input/input14
[191732.885632] logitech 0003:046D:C714.000B: input,hiddev96,hidraw3: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.2-2.3/input0
[237346.101670] usb 2-3.1: reset low speed USB device using ehci_hcd and address 5

I can run:
$ sudo hid2hci

and the Bluetooth device comes back and works OK paired with the keyboard. Something is timing out somewhere. I would like the dongle to always stay in HCI mode.

This problem did not happen in Ubuntu Intrepid.

Here's the Bluetooth dongle ID:
Bus 008 Device 013: ID 046d:c709 Logitech, Inc. BT Mini-Receiver (HCI mode)

And some versions:
linux-image-2.6.28-11-generic (2.6.28-11.42)
bluez 4.32-0ubuntu4

My dongle (Integrated System Solution Corp. KY-BT100 Bluetooth Adapter) works in Jaunty :)

Mine still does not work. This is a regression form 8.04 over two releases 8.10 and 9.04. I wonder why the Bluez bug (filed more than six month ago) is still considered New (through two releases), importance undecided (decidedly important to me) and unassigned (I am not able to fix it myself!)

uname -a
Linux library 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux
dpkg -l | grep bluez
ii bluez 4.35-0ubuntu1
lsusb
Bus 003 Device 002: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
hciconfig -a
hci0: Type: USB
 ...UP RUNNING
 ...Can't read local name on hci0: Connection timed out (110)

Dominique Meeùs wrote:
> Mine still does not work. This is a regression form 8.04 over two
> releases 8.10 and 9.04. I wonder why the Bluez bug (filed more than six
> month ago) is still considered New (through two releases), importance
> undecided (decidedly important to me) and unassigned (I am not able to
> fix it myself!)

Ah well, mine doesn't work either - unless I apply my _kernel_ patch
which reverts _net/bluetooth_ back to the 2.6.24 Hardy kernel's
protocol stack. (Patch posted earlier to this long bug report).

The latest kernel fixes to make the USB Bluetooth driver better don't
make any difference on my system. Neither does running older Bluez
code. I see a protocol bug in the kernel. Fortunately for me, I have
a workaround, but unfortunately it's not suitable for general use as
it reverts the entire kernel bluetooth stack quite a long way.

-- Jamie

Using Jaunty with Blueman from the PPA - browsing, copying, pasting etc.
on a phone via Nautilus works just fine!

No more "Operation not supported by backend". Just works.

It did not work in Intrepid w/Blueman PPA.

Jamie Lokier wrote:
> Dominique Meeùs wrote:
>> Mine still does not work. This is a regression form 8.04 over two
>> releases 8.10 and 9.04. I wonder why the Bluez bug (filed more than six
>> month ago) is still considered New (through two releases), importance
>> undecided (decidedly important to me) and unassigned (I am not able to
>> fix it myself!)
>
> Ah well, mine doesn't work either - unless I apply my _kernel_ patch
> which reverts _net/bluetooth_ back to the 2.6.24 Hardy kernel's
> protocol stack. (Patch posted earlier to this long bug report).
>
> The latest kernel fixes to make the USB Bluetooth driver better don't
> make any difference on my system. Neither does running older Bluez
> code. I see a protocol bug in the kernel. Fortunately for me, I have
> a workaround, but unfortunately it's not suitable for general use as
> it reverts the entire kernel bluetooth stack quite a long way.
>
> -- Jamie
>

2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

Jaunty 64Bit - Dell E6500

Bluetooth behaviour has changed. Under 8.10 the Dell Bluetooth radio had to be off during the boot up and then turned on. From then on Bluetooth mostly worked. Under Jaunty its the exact opposite. The bluetooth radio MUST be on during the boot up phase.

I built a new Jaunty 64 and from alpha 6 it appeared that Bluetooth was fixed. However it has reverted to a new incantation over the various updates to Beta and then RC and Production.

Now bluetooth mostly only works (ie can send files or use Gnome Phone Manager) if I connect from the Phone to the Laptop via anyremote first. So what I have to do it start anyremote via ganyremote - then I start Anyremote on my Nokia 6233 and then I can disconnect if I want too (don't have to) and then the Laptop can successfully communicate with the phone.

I updated to latest Blues 4.36 from 4.32 no change

Re-booted and the updated to Blueman - Replaces Gnome Bluetooth Applet.

Seems to work properly - will reboot a few more times and advise if behaviour varies.

2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

Jaunty 64Bit - Dell E6500

Yes, Blueman is definitely the answer in Jaunty.

All things seem to work for me - browsing, transferring files to phone
and also Wamma/Gammu phone access works when paired by Blueman.

https://launchpad.net/blueman/

kylea wrote:
> Re-booted and the updated to Blueman - Replaces Gnome Bluetooth Applet.
>
> Seems to work properly - will reboot a few more times and advise if
> behaviour varies.
>
> 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64
> GNU/Linux
>
> Jaunty 64Bit - Dell E6500
>

Debian SID still the problem.

maximi89@Maximiliano:~/Descargas/Bárbara$ uname -a
Linux Maximiliano 2.6.29-1-686 #1 SMP Fri Apr 17 14:35:16 UTC 2009 i686 GNU/Linux

Bus 002 Device 006: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device

dmesg
[63401.520024] usb 2-7: reset low speed USB device using ohci_hcd and address 2
[71975.908248] usb 2-2: USB disconnect, address 5
[71975.908411] btusb_intr_complete: hci0 urb ef8e4bc0 failed to resubmit (19)
[71975.908647] btusb_send_frame: hci0 urb ef8e4bc0 submission failed
[71978.900030] usb 2-2: new full speed USB device using ohci_hcd and address 6
[71979.124225] usb 2-2: New USB device found, idVendor=1131, idProduct=1004
[71979.124229] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[71979.124233] usb 2-2: Product: ISSCEDRBTA
[71979.124235] usb 2-2: Manufacturer: ISSC
[71979.124321] usb 2-2: configuration #1 chosen from 1 choice
[71980.338422] hci_cmd_task: hci0 command tx timeout

So far with Blueman - I have to re-scan for devices and then I can Browse the phone. So its still not quite right.

Should just connect and work.

2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
Jaunty 64Bit - Dell E6500

Noticed in kernel log for Linux 2.6.30-rc4 something promising on the way for the dreaded "hci_cmd_task: hci0 command tx timeout" ??

 - Bluetooth: Add different pairing timeout for Legacy Pairing

http://lkml.org/lkml/2009/4/30/10

Note sure how to get and test with this latest kernel. If anyone knows or can test it would be great to hear from them.

Blueman 1.10 - seems to be working last few re-starts have ok , with bluetooth working immediately.

Will do some more re-starts and shutdowns to confirm

2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
Jaunty 64Bit - Dell E6500

Blueman 1.10 - behaviour is not consistent.

Last Restart I had to "Search" for devices (button on the Blueman Devices dialog window) - then Bluetooth started to work. Other times after a restart it just works straight away.

Might be a timing thing - Ill try again and wait a few minutes before trying to connect to the phone.

Note: Connecting from the phone to the PC nearly always works and then all is ok until the next restart.

2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
Jaunty 64Bit - Dell E6500

Another test shutdown then started again - same behaviour had to "Search" for devices (button on the Blueman Devices dialog window) - then Bluetooth started to work.

Noticed this is the syslog log

obex-data-server: sdp_extract_seqtype: Unexpected end of packet

2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
Jaunty 64Bit - Dell E6500

Kylea, Could you provide a list of steps you took to get blueman working? I
have not been able to get it to work at all on a fresh install of jaunty.
After I "enable bluetooth", all the options on the blueman menu are still
greyed out and I can't do anything at all. Thanks!

added the following to sources.list

http://ppa.launchpad.net/blueman/ppa/ubuntu jaunty main

Upgraded the following packages:
bluetooth (4.32-0ubuntu4) to 4.36-0ubuntu2
bluez (4.32-0ubuntu4) to 4.36-0ubuntu2
bluez-alsa (4.32-0ubuntu4) to 4.36-0ubuntu2
bluez-cups (4.32-0ubuntu4) to 4.36-0ubuntu2
bluez-gstreamer (4.32-0ubuntu4) to 4.36-0ubuntu2
bluez-utils (4.32-0ubuntu4) to 4.36-0ubuntu2
libbluetooth-dev (4.32-0ubuntu4) to 4.36-0ubuntu2
libbluetooth3 (4.32-0ubuntu4) to 4.36-0ubuntu2

Removed the following packages:
bluez-gnome

Installed the following packages:
blueman (1.10-1~ppa3j)

Thats all - beware it usually works - but sometimes it just wont and you have to re-boot

Thanks Kylea. Unfortunately that's exactly what I was doing. I installed
jaunty afresh and tried it again to be sure, but I get the same result (100%
reproducible). I have logged a separate bug against blueman (370389) for
this issue.

I have the problem reported by Jamie Lokier here: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/288613/comments/12 (can not connect to PAN service on Sony-Ericsson phone). The problem still exists in kernel 2.6.28-11.42 (up to date Jaunty) even though this bug is marked as "Fix released" for a month. I have a Thinkpad T61p with bluetooth controller 'Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller'. The problem with PAN on S-E phones (don't know about other phones...) is also reported separately as bug #336012, I have submitted some more details there. I can confirm applying the patch posted by Jamie Lokier in comment 99 (forward-porting the Bluetooth protocol stack from 2.6.24 to 2.6.28) makes the problem disappear. Is there any progress happening on solving this bug?

hi guys
i have the cambridge silicon dongle
it doesnt work
tielie has mentioned that it works nicely
any help would be appreciated
thanks!!

ok for my above comment
i can send files to some phones
i cant pair with my sony k600i ( can pair with my nokia n73)
but i cant receive any file
any help??

New flavor of the kernel this morning. The famous "more than six month regression" hci0 command tx timeout is still there.
~$ uname -a
Linux library 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:27:06 UTC 2009 i686 GNU/Linux

I insert my dongle
~$ lsusb | grep Blue
Bus 003 Device 002: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

No improvement:
May 7 05:09:04 library kernel: [ 236.152016] usb 3-1: new full speed USB device using uhci_hcd and address 2
May 7 05:09:04 library kernel: [ 236.344036] usb 3-1: configuration #1 chosen from 1 choice
May 7 05:09:04 library bluetoothd[2968]: HCI dev 0 registered
May 7 05:09:04 library kernel: [ 236.372633] Bluetooth: Generic Bluetooth USB driver ver 0.3
May 7 05:09:04 library kernel: [ 236.372758] usbcore: registered new interface driver btusb
May 7 05:09:04 library bluetoothd[2968]: HCI dev 0 up
May 7 05:09:04 library bluetoothd[2968]: Starting security manager 0
May 7 05:09:09 library kernel: [ 241.512969] hci_cmd_task: hci0 command tx timeout
May 7 05:09:14 library bluetoothd[2968]: Can't write class of device: Connection timed out (110)
May 7 05:09:14 library bluetoothd[2968]: Adapter /org/bluez/2968/hci0 has been enabled
May 7 05:09:14 library kernel: [ 246.519680] hci_cmd_task: hci0 command tx timeout
May 7 05:09:19 library bluetoothd[2968]: Sending getting name command failed: Connection timed out (110)
May 7 05:09:19 library kernel: [ 251.524851] hci_cmd_task: hci0 command tx timeout
May 7 05:09:24 library bluetoothd[2968]: Can't read class of device on hci0: Connection timed out (110)
May 7 05:09:24 library kernel: [ 256.530150] hci_cmd_task: hci0 command tx timeout

2009/5/6 Dominique Meeùs <email address hidden>

> New flavor of the kernel this morning. The famous "more than six month
> regression" hci0 command tx timeout is still there.
> ~$ uname -a
> Linux library 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:27:06 UTC 2009
> i686 GNU/Linux
>
> I insert my dongle
> ~$ lsusb | grep Blue
> Bus 003 Device 002: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth
> adapter
>
> No improvement:
> May 7 05:09:04 library kernel: [ 236.152016] usb 3-1: new full speed USB
> device using uhci_hcd and address 2
> May 7 05:09:04 library kernel: [ 236.344036] usb 3-1: configuration #1
> chosen from 1 choice
> May 7 05:09:04 library bluetoothd[2968]: HCI dev 0 registered
> May 7 05:09:04 library kernel: [ 236.372633] Bluetooth: Generic Bluetooth
> USB driver ver 0.3
> May 7 05:09:04 library kernel: [ 236.372758] usbcore: registered new
> interface driver btusb

You are using the module btusb 0.3 , in my case i'm using the 0.4 on

Linux Maximiliano 2.6.29-1-686 #1 SMP Fri Apr 17 14:35:16 UTC 2009 i686
GNU/Linux

But works fine my Bluetooth on old kernel 2.6.26, but i don't know what
module use...

> May 7 05:09:04 library bluetoothd[2968]: HCI dev 0 up
> May 7 05:09:04 library bluetoothd[2968]: Starting security manager 0
> May 7 05:09:09 library kernel: [ 241.512969] hci_cmd_task: hci0 command
> tx timeout
> May 7 05:09:14 library bluetoothd[2968]: Can't write class of device:
> Connection timed out (110)
> May 7 05:09:14 library bluetoothd[2968]: Adapter /org/bluez/2968/hci0 has
> been enabled
> May 7 05:09:14 library kernel: [ 246.519680] hci_cmd_task: hci0 command
> tx timeout
> May 7 05:09:19 library bluetoothd[2968]: Sending getting name command
> failed: Connection timed out (110)
> May 7 05:09:19 library kernel: [ 251.524851] hci_cmd_task: hci0 command
> tx timeout
> May 7 05:09:24 library bluetoothd[2968]: Can't read class of device on
> hci0: Connection timed out (110)
> May 7 05:09:24 library kernel: [ 256.530150] hci_cmd_task: hci0 command
> tx timeout
>
> --
> Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
> https://bugs.launchpad.net/bugs/268502
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Maximiliano Augusto Castañón Araneda
Santiago, Chile
Linux user # 394821

Hi Dominique - if you can try this.

If you have a Nokia phone, install anyremote and then set it up to use bluetooth channel 19. Install the java client on the phone - you might need to sms it to yourself. I can sms them to you - then it will install automatically on the phone.

I have to most often, link from the phone to the PC - I use anyremote. This seems to "wake up" the bluetooth service and then I can link from the PC to my phone.

here is the link details

http://anyremote.sf.net/

http://ppa.launchpad.net/anyremote/ppa/ubuntu jaunty main

erm hello
anyon can help?
i'm kinda new to linux

psychodude - might be helpful for you to have a long careful read of this bug :)

There are several hundred posts covering a multitude of issues and suggestions.

This is seemly a very complex bug to fix with several overlapping pieces of software pulling in different directions. as its not fixed for a lot of people.

After installing Jaunty (fresh install) everything works flawlessly.

USB bluetooth adapter:
Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

OS Ubuntu 9.04 64-bit (2.6.28-11-generic)
Motherboard Asus P5KPL (Intel chipset with Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GH)