Bluetooth dongle not working with 2.6.31 kernel in karmic

[SpmP]

Binary package hint: bluez

maybee already reported...
 Bluetooth device does not work with 2.6.31 family of kernels in karmic (9.10).
1) Karmic, amd64
2) linux-generic 2.6.31.4.15
    bluez 4.45-0ubuntu4

3) I expect the bluetooth device to be detected etc.
4) Bluetooth device is not available, manual module loading etc. does not help.

I have tried both ubuntu version of bluez, and vanilla from svn, no difference.

Bluetooth works fine with bluez from karmic (and svn) with linux-image-2.6.28-14 from jaunty.

lsusb|grep -i bluetooth
Bus 004 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

please let me know if theres anything else you need.

[Mario Limonciello (superm1)]

Is the btusb module getting loaded? Automatically?

[SpmP (scarletpimpernal)]

yes
...
 usbcore: registered new interface driver btusb
...

[Mario Limonciello (superm1)]

Ok, so is bluetoothd running automatically like it should then? There is a udev rule that should be spawning it.

If it is, running, check the output of hciconfig. Is it showing an hci0 device?

[SpmP (scarletpimpernal)]

ok boot with kernel ver. 2.6.31-4-generic

bluetoothd is running
ps aux|grep -i blue

root 254 0.0 0.0 0 0 ? S< 19:32 0:00 [bluetooth]
root 2552 0.0 0.1 28472 1860 ? S<s 19:34 0:00 /opt/bluetooth/sbin/bluetoothd --udev
<user> 3407 0.3 1.2 189584 12504 ? S 19:34 0:00 bluetooth-applet

so udev seems to be doing its job.

sudo hciconfig
hci0: Type: USB
 BD Address: 00:10:60:A5:4C:D1 ACL MTU: 192:8 SCO MTU: 64:8
 DOWN
 RX bytes:1109 acl:0 sco:0 events:47 errors:0
 TX bytes:688 acl:0 sco:0 commands:47 errors:0

and

sudo hciconfig hci0 up
Can't init device hci0: Unknown error 132 (132)

As you would expect, the bluetooth applet is showing (i. adapter present) but with the wee red x to indicate not something...

ok... so its still running bluetooth from svn... after reinstalling and upgrading bluez, so running from /usr/sbin its the same problem

heres the output of:
/usr/sbin/bluetoothd -d -n
bluetoothd[4261]: Bluetooth daemon 4.47
bluetoothd[4261]: Enabling debug information
bluetoothd[4261]: parsing main.conf
bluetoothd[4261]: discovto=0
bluetoothd[4261]: pairto=0
bluetoothd[4261]: pageto=8192
bluetoothd[4261]: name=%h-%d
bluetoothd[4261]: class=0x000100
bluetoothd[4261]: discov_interval=0
bluetoothd[4261]: Key file does not have key 'DeviceID'
bluetoothd[4261]: Starting SDP server
bluetoothd[4261]: Loading builtin plugins
bluetoothd[4261]: Loading service plugin
bluetoothd[4261]: Loading hciops plugin
bluetoothd[4261]: Loading hal plugin
bluetoothd[4261]: Loading storage plugin
bluetoothd[4261]: Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[4261]: Loading audio plugin
bluetoothd[4261]: Loading netlink plugin
bluetoothd[4261]: Loading serial plugin
bluetoothd[4261]: Loading network plugin
bluetoothd[4261]: Loading input plugin
bluetoothd[4261]: register_interface: path /org/bluez/4261/any
bluetoothd[4261]: Registered interface org.bluez.Service on path /org/bluez/4261/any
bluetoothd[4261]: input.conf: Key file does not have key 'IdleTimeout'
bluetoothd[4261]: /etc/bluetooth/network.conf: Key file does not have key 'Disable'
bluetoothd[4261]: /etc/bluetooth/network.conf: Key file does not have key 'DisableSecurity'
bluetoothd[4261]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[4261]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[4261]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[4261]: Config options: InterfacePrefix=bnep%d, PANU_Script=(null), GN_Script=(null), NAP_Script=(null), GN_Interface=pan0, NAP_Interface=pan1, Security=true
bluetoothd[4261]: Can't create GN bridge
bluetoothd[4261]: Starting experimental netlink support
bluetoothd[4261]: Failed to find Bluetooth netlink family
bluetoothd[4261]: Unix socket created: 9
bluetoothd[4261]: audio.conf: Key file does not have key 'AutoConnect'
bluetoothd[4261]: audio.conf: Key file does not have key 'MaxConnected'
bluetoothd[4261]: Telephony plugin initialized
bluetoothd[4261]: HFP AG features: "Ability to reject a call" "Enhanced call status" "Extended Error Result Codes"
bluetoothd[4261]: HCI dev 0 registered
bluetoothd[...

[SpmP (scarletpimpernal)]

and just to prove it works on 2.6.28...

11/08/09 19:51:27 foundation bluetoothd[1859] Bluetooth daemon 4.47
11/08/09 19:51:27 foundation bluetoothd[1860] Starting SDP server
11/08/09 19:51:27 foundation bluetoothd[1860] bridge pan0 created
11/08/09 19:51:27 foundation bluetoothd[1860] Starting experimental netlink support
11/08/09 19:51:27 foundation bluetoothd[1860] Failed to find Bluetooth netlink family
11/08/09 19:51:27 foundation bluetoothd[1860] HCI dev 0 registered
11/08/09 19:51:27 foundation bluetoothd[1860] Failed to open RFKILL control device
11/08/09 19:51:27 foundation bluetoothd[1860] HCI dev 0 up
11/08/09 19:51:27 foundation bluetoothd[1860] Starting security manager 0
11/08/09 19:51:27 foundation bluetoothd[1860] Parsing /etc/bluetooth/serial.conf failed: No such file or directory
11/08/09 19:51:27 foundation bluetoothd[1860] probe failed with driver input-headset for device /org/bluez/1859/hci0/dev_00_12_D2_6A_3E_D2
11/08/09 19:51:27 foundation bluetoothd[1860] Adapter /org/bluez/1859/hci0 has been enabled

[Mario Limonciello (superm1)]

Then lets get the kernel guys in here on this to start looking for where the regression developed. Considering the last thing happening during that run of bluetoothd where it failed was rfkill stuff, can you check the status of the rfkill interface too?

$ rfkill

You'll see if hci0 is ending up blocked for some reason (which would explain why you weren't able to run hciconfig hci0 up)

[Leann Ogasawara (leannogasawara)]

Can you test and confirm with the newer 2.6.31-5 kernel? The reason I ask is I thought some rfkill related work went into 2.6.31-5. Thanks.

[SpmP (scarletpimpernal)]

Thanks for keeping onto this one.
 I can confirm that
rfkill unblock blutooth
 allows the device to be 'brought up'
2.6.31-1-rt and 2.6.31-5 both seem to work without needing this.
 Strangely tho, the device is down by default and must be 'turned on' by gnome-bluetooth (or hciconfig hci0 up)
So half solved 8)

[Jens B. (jens-bavendiek)]

Hi,

I have a similar problem though im running: 2.6.31-13
I also can confirm that rfkill unblock blutooth and then a hciconfig hci0 up
brings the decive up withouth an error.
I now can scan for devices and find my cell-phone though i cannot connect to it.

jab@kiki:~$ sudo hcitool cc 00:23:F1:B3:C5:7C
jab@kiki:~$

i get no feedback.
If you can help Id really appreciate it!

Thanks in advance
Jens

[Jeremy Foshee (jeremyfoshee)]

Hi SpmP,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

apport-collect -p linux 411362

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jens B. (jens-bavendiek)]

I just tested my bluetooth with the new Ubutun Beta2 Released Apr 8th, 2010 and had no problem connecting to my phone.
So Id assume that this issue got fixed.

Thanks!

[penalvch (penalvch)]

SpmP, thank you for reporting this and helping make Ubuntu better. Karmic reached EOL on April 30, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

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

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

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

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

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

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

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

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

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

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

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]