Bluetooth doesn't work in Ubuntu 11.04

[Paolo Rotolo]

Binary package hint: gnome-bluetooth

Bluetooth doesn't work in Ubuntu 11.04. When turning it on, it's shown as disabled.
Bluetooth model is: " ASUSTek Computer, Inc. BT-183 Bluetooth 2.0+EDR adapter "
This looks like a regression because the Bluetooth was working in Ubuntu 10.10.
See the video for more information...

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gnome-bluetooth 2.91.2.is.2.32.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sat Apr 16 17:11:13 2011
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=it_IT.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)

[Mathieu Trudel-Lapierre (cyphermox)]

Paolo, if this is a USB device can you please run 'lsusb' and tell us which device it is in the list? Thanks.

[Mathieu Trudel-Lapierre (cyphermox)]

Providing with the contents of /var/log/syslog would be good too, since it will contain at least some messages from bluez and the kernel bluetooth drivers.

[Paolo Rotolo (paolorotolo)]

Hi, Mathieu Trudel-Lapierre. Bluetooth is not a usb device. Bluetooth is built into the laptop...
The model is: ASUSTek Computer, Inc. BT-183 Bluetooth 2.0+EDR adapter

Here is / var / log / syslog:

Thanks

[Ian Santopietro (isantop)]

This is also affecting all bluetooth enabled System76 Laptops. Upon investigation of the issue, we found that enabling the bluetooth module (It is off at boot by default on our models), then running these commands allows bluetooth to function:

sudo killall bluetoothd
sudo bluetoothd

However, if the module is disabled then enabled, it will not work until the commands are run again.
This should suggest a problem with the bluez package (provider of /usr/sbin/bluetoothd), right?

[Paolo Rotolo (paolorotolo)]

He works, thanks!

[Ian Santopietro (isantop)]

Additionally, using a system with a bluetooth module powered on from the moment the system is booted allows bluetooth to function out of the box, without restarting bluetoothd. It looks like there is a bug that prevents bluetoothd from detecting a module activated after it's been started.

[Ian Santopietro (isantop)]

Installing the Maverick version of the bluez package solved the issue here as a workaround. We know it's a problem with the bluez package. I'll be looking at what specifically changed between the two versions. Dev help here would also be great.

[Ian Santopietro (isantop)]

Attaching hci.log as suggested by apport:

[Matt Grant (mattgrant)]

I will give the older bluez a try, and mark it 'hold' to stop updates from obliterating the older package. Dell Vostro 1510 on Natty.

[Brian Murray (brian-murray)]

Ian - could you elaborate on what you mean by "It is off at boot by default on our models". How exactly do you have it turned off on at boot? I was trying to recreate this issue on a Lenovo X201 Tablet and was unable to. Thanks in advance.

[Ian Santopietro (isantop)]

Our BIOSes are configured to turn off power to the modules when the system is booted or resumed from suspend. In Ubuntu, the modules don't appear to be installed, and lsusb does not echo the existence of the module until pressing Fn+F12 to turn the module on. It's analogous to booting the system with a physical killswitch in the off position.

[Denwerko (denwerko)]

same on asus m51sn, integrated bluetooth module wont work until sudo kill bluetoothd and then restarting bluetootd. When I borrowed other other usb bluetooth dongle from second computer, it worked out of box

[Platon Pukhlechev (ifalkorr-deactivatedaccount)]

natty amd64
in my laptop
Bus 008 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
bluetooth module wont work until sudo kill bluetoothd and then restarting bluetoothd
in 10.10 works fine

[Mauricio Farell Perezgrovas (mfarell)]

Same here with natty intel
Bus 001 Device 002: ID 174f:110b Syntek

[Ed Schouten (ed-80386)]

Same here with Natty, on an Apple MacBook:

Bus 003 Device 003: ID 05ac:8205 Apple, Inc. Bluetooth HCI

[Ed Schouten (ed-80386)]

Indeed; killling and restarting bluetoothd and reassociating with my Apple mouse works, but unfortunately I can now only use it as a pointing device -- not a clicking device.

[Pavol Klačanský (pavolzetor-deactivatedaccount)]

I added to rc.local file command "service bluetooth restart" and it "works"

[s0undt3ch (ufs)]

This is also present in kubuntu

[Ted Reed (treed)]

I'm experiencing similar problems where Bluetooth isn't working, but the workaround is not fixing it for me.

I don't know if it matters much, but the BT icon on the bar is grayed out, even when it says Bluetooth: On. (Clicking Preferences shows a window indicating that it's off, as well.)

Curiously, it worked fine after the first reboot after the upgrade, but not since.

[Seth Rosenblum (ricklerre)]

"sudo service bluetooth restart" also works as a workaround for me

[David Duffey (dduffey)]

I have a MacBook and an AMD based Toshiba Tecra R850. Restarting bluetooth on both of these laptops also worked for me.

[bilbo-le-hobbit (bilbohobbit)]

Same here on my asus m51sn
Ubuntu Natty 64bits
2.6.38-8-generic x86_64
lsusb : Bus 004 Device 002: ID 0b05:1712 ASUSTek Computer, Inc. BT-183 Bluetooth 2.0+EDR adapter

"sudo service bluetooth restart" or "sudo /etc/init.d/bluetooth restart" works
I have to make this each time i restart my pc

[Mats Karrman (mats-karrman)]

Same problem on My Acer Ferrari 3400.
Ubuntu Natty 64bits
2.6.38-8-generic x86_64
lsusb: Bus 004 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Above suggested workarounds works for me too.

[Arian van Dorsten (jwasys)]

"sudo service bluetooth restart" also works as a workaround for me

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

Ubuntu Natty 32bits

2.6.38-8-generic

Compaq NX9030

[s0undt3ch (ufs)]

The workarounds work for me too, although I have to manually connect my mouse every time.

[Paolo Rotolo (paolorotolo)]

Bluetooth works correctly in Ubuntu 11.04 (20110430).

Great job!

[Majdi zamim (majdi-1400)]

also , same issue has occurred in TOSHIBA Satellite M300
 it was working properly in the previous version but when i upgraded to the latest version the issue has appeared

[Stefan Nagy (stefan-nagy)]

I have the same problem with a Compaq Computer Corp. Bluetooth Device (USB ID 049f:0086) and a Microsoft Wireless Entertainment Keyboard 7000. In addition sometimes the keyboard layout changes to english (I have a german keyboard with ö, ü and all this stuff). I have to remove the keyboard and add it again to get the german layout back…

BTW, there's a related bugreport: bug 700292

[pionnier (v-pionnier)]

Bluetooth is enabled, I can even pair devices. But when I try to browse files on a device or to send file to a device it doesn't work at all, in both directions. I also cannot set up an internet connection via bluetooth with my cell phone.
lsusb: Bus 004 Device 004: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
All worked fine in 10.10

[Two Point Oh (twopt0)]

Same issue on a daru3. Fn+F12 keycombo to turn on Bluetooth: Bluetooth applet icon is grayed out, says bluetooth is turned on, but Bluetooth Preferences window has only a large button for turning on Bluetooth. Workaround of restarting bluetoothd works.

[VoLk (ivn-wd77)]

I have same problem with a laptop Toshiba L500-223.
Ubuntu 11.04, 64-bit, 2.6.38-8-generic.

[bilbo-le-hobbit (bilbohobbit)]

The patch from bug #700292 bug solved the problem for me. Patched kernel packages available into natty-proposed

[Maverick13 (mavervicandgus)]

I have same problem with a laptop Toshiba A305D-SP6801.
Ubuntu 11.04, 32 bit 2.6.38-8-generic.

[Johnny (johnny-free)]

I have the same problem with my notebook (clevo).
With the command : "service bluetooth restart" a can do work some device with bluetooth, but my bluetooth's mouse don't work.
She connect with notebook, but there aren't communication.

[3ntix (francesco-3ntini)]

I've a Santech notebook (a clevo based) with a fresh instal of K-ubuntu. With "service bluetooth restart" resolve the problem.

I've update the kernel from the natty-proposed repository and the systray icon work properly. I've not tried with any device yet.

Maybe add also the kde bluetooth software as affected from this bug?

[Emanuele Sagona (zago84)]

This is my lsusb command line:

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

This bug affects my two computers, one with Ubuntu 32 bit and the other one Ubuntu 64 bit

[Mark Ovens (parish)]

And another.

Edimax Bluetooth USB dongle

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

[Bart (dmitriy-murzin)]

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

not work bluetooth mouse

Ubuntu 11.04 amd64 update 04.04.2011

[Bart (dmitriy-murzin)]

sorry, update 2011-05-04

[pableu (ps-pableu)]

I'm also affected by this bug. I have a D-Link USB Dongle.

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

uname -a:
Linux ws36 2.6.38-8-generic-pae #42-Ubuntu SMP Mon Apr 11 05:17:09 UTC 2011 i686 i686 i386 GNU/Linux

I attached the (grepped) syslog-output. Around 07:42:50, I manually killed and restarted bluetoothd and then the bluetooth-applet worked as expected.

[Monitor_Inc (bobdharris)]

I have the same as pionnier (wrote on 2011-05-01:) but on a Samsung M50

Bluetooth is enabled, I can find and pair devices. But when I try to browse or send files to my phone in either direction it doesn't work. Also cannot set up DUN with my phone.
lsusb: Bus 004 Device 004: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
All worked fine in 10.10

Restart bluetooth work around does not appear to work for me.

[Alex (pokrovs)]

I have the same as poinnier and Monitor_Inc on HP Compaq 8240

Bluetooth is enabled and I can pair devices. But I can't send files and can't establish inet connection.

The same on 10.10 all worked fine

[Luis Mercado (arteminimal)]

Bluetooth was working for me just fine on Natty, theu it suddenly stops and now it does not even detects my internal Bluetooth device.

Macbook Pro 4,1

[3ntix (francesco-3ntini)]

Updating the kernel from natty-proposed (now I have 2.6.38-9-generic)
seem solving the problem.

[Peter Curtis (pdcurtis)]

Several of the comments (31 and 43) refer to mobile phones. I have found that the rfcomm bindings which create the bluetooth devices (/dev/rfcommx) are not taking place either in 11.04 and one also has to bind them manually by:

sudo rfcomm bind all

after the bluetooth restart

The combination of sudo bluetooth restart and sudo rfcomm bind all now allows me to use gnome-ppp to connect all my phones.

Bluetooth also needs to be restarted after a suspend or hibernate on my machine, a MSI Wind U100

Hopefully these are all going to be tested and sorted in the new kernel

[VoLk (ivn-wd77)]

3ntix, some people can't afford updating from natty-proposed, because updating from natty-proposed is risky :( For example, it's people who using laptop for work... (Sorry for my English, please)

[ChrisBE (cbe010)]

I have the same issue as described with the grayed-out applet. hp-g60t AMD64. I have a wireless switch that enables/disables bluetooth and wifi, after pressing it "off" then "on" the applet is white and I can connect to my phone. Thanks for working on this.

[Ron Laws (ron-laws86)]

Bluetooth is broken. Fail

[Miroslav (dzundam-deactivatedaccount)]

11.04 64-bit, Dell Vostro 1000 with USB bluetooth dongle

"sudo service bluetooth restart" works as a workaround for me

[Zilvinas Jonaitis (zjonaitis)]

I have the same issue with Bluetooth.

Notebook: DELL Vostro 1015 w/ Atheros Wifi+BT combo.

lsusb:
Bus 004 Device 002: ID 0cf3:3002 Atheros Communications, Inc.

uname -a:
2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 i686 i386 GNU/Linux

hciconfig:
hci0: Type: BR/EDR Bus: USB
 BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
 DOWN
 RX bytes:0 acl:0 sco:0 events:0 errors:0
 TX bytes:30 acl:0 sco:0 commands:10 errors:0

sudo hciconfig hci0 up:
Can't init device hci0: Connection timed out (110)

"sudo service bluetooth restart" does NOT work for me.

[Barry Warsaw (barry)]

Try this, which works reliably for me on a MacBook Pro 1,1:

$ sudo hciconfig hci0 reset

[Mike Demers (med11043)]

Same problem for me on a custom desktop using a USB bluetooth adapter as soon as I updated to 11.04 (worked fine in 10.10)....

The "sudo killall bluetoothd" "sudo bluetoothd" workaround works for me, but I have to do it every time I restart or boot the computer which is annoying!

Hopefully it is fixed and an update posted soon...

[MP (trelirodia)]

Same problem with integrated bluetooth after upgrade to Natty. Worked well on Meerkat.
Restarting bluetoothd solves it.

[Ryan Shaw (ryannathans)]

Broadcom corp. BCM2046B1 USB 2.0 HUB (part of BCM2046 bluetooth) is showing up is lsusb however it is an integrated on board chip.

NONE of the solutions posted fixes my issue.

11.04 64bit

[Ryan Shaw (ryannathans)]

Are there any known solutions for my above posted bluetooth adapter?

[Ryan Shaw (ryannathans)]

No bluetooth adapter is detected according to bluetooth app.

[Jeff Rash (jeffrash)]

I enabled pre-release updates and installed all them. Now bluetooth works for me. I know that's like using a hammer to fix a watch, but it worked.

[Ryan Shaw (ryannathans)]

Found what looks like a FIX.

Enabled the bluetooth in Windows 7.

Booted back to ubuntu and it was working!

:D

[Joakim B (superslickjay)]

I run a freshly installed 11.04 with Gnome desktop and experience that bluetooth fails on random occasions. My Logitech MX mouse that also connects with bluetooth (separate logitech adapter) works like a charm, but my Apple bluetooth keyboard with a generic bluetooth dongle just won't work every 2nd reboot or so.

I've solved this until today by rebooting as it magically starts working after reboot. However I made a fix today that doesn't require rebooting:

I put a shell file on my desk called restartbluetooth.sh looking like below:
    sudo service bluetooth restart

I then ran sudo visudo and added the below shown line to the end of visudo:
  myusername ALL = NOPASSWD: /home/myusername/Desktop/bluetoothrestart.sh

As I can use my mouse but not my keyboard, I can click the restartbluetooth.sh on my desktop and execute the command without having to write in my password as it's kind of tough to do without a keyboard.

Maybe not the cleanest solution to grant root permissions to the file, but hey, it works!

[Mathieu Trudel-Lapierre (cyphermox)]

The problem here is that there seems to me like quite a few reports of "bluetooth not working"; unfortunately many of them are for vastly different hardware devices.

Ideally people should file new, separate bugs for their hardware, using 'ubuntu-bug linux' and answering the questions, the providing a clear description of the symptoms. It seems like there has been many issues with bluetooth this cycle related to various drivers and race conditions in loading these drivers; making sure that easch of those are listed independently against linux with all the necessary information about the exact driver in use (and also including the relevant syslog, usb, etc. info; which using ubuntu-bug automates). As it is, it looks like this bug is fairly hard to work on.

FWIW, I've had issues too, with a different device as well. While everything initially appears to be caused by the gnome-bluetooth or bluez applications, it's really largely a kernel problem in most cases. In the chance that it's not the problem in your case and really introduced by bluez, then the developers looking at your bug can reassign it to the correct package.

[Łukasz Szeremeta (l-szeremeta)]

Bug also applies to:

Notebook: MSI PR400-016PL (Crystal)
Bluetooth model is: Intel® Wireless WiFi Link 4965AGN
Ubuntu 11.04 i386 Stable (v. Live and installed)

[Bence Lukács (lukacs-bence1)]

Also doesn't work Bus 005 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) in 11.04.
It works correctly in 10.10.

[nnutter (nnutter)]

I updated using the "proposed" sources and did a dist-upgrade. With the new kernel my Bluetooth keyboard now works (even on the login screen).

[jvon (d-admin-betajunk-com)]

im on a eeepc 1000he kernel 2.6.39-2-generic on oneric. no device adapter found. but my usb one works fine.

[Mike Yates (fonehelp)]

My dongle was never a problem with 10.10 but would not P&P at all in 11.04 for the first three days.
Now it "usually" works if I start up with it inserted but never if inserted live.

usb-devices:-
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a12 ProdID=0001 Rev=52.76
C: #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

On failure:-
[ 435.656168] usb 2-2: USB disconnect, address 2
[ 435.657041] btusb_intr_complete: hci0 urb f1429300 failed to resubmit (19)
[ 435.657071] btusb_bulk_complete: hci0 urb f1429200 failed to resubmit (19)
[ 435.658041] btusb_bulk_complete: hci0 urb f1429180 failed to resubmit (19)
[ 435.658134] btusb_send_frame: hci0 urb f1f64800 submission failed
[ 443.560181] usb 2-2: new full speed USB device using uhci_hcd and address 3
[ 1523.136185] usb 2-2: USB disconnect, address 3
[ 1540.576160] usb 2-2: new full speed USB device using uhci_hcd and address 4

On success:-
[ 25.177801] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 25.231100] usbcore: registered new interface driver btusb
[ 25.644274] Bluetooth: L2CAP ver 2.15
[ 25.644284] Bluetooth: L2CAP socket layer initialized
[ 25.678833] cfg80211: World regulatory domain updated:
[ 25.678844] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 25.678855] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 25.678865] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 25.678875] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 25.678884] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 25.678894] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 25.701647] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 25.701656] Bluetooth: BNEP filters: protocol multicast
[ 25.734683] Bluetooth: SCO (Voice Link) ver 0.6
[ 25.734693] Bluetooth: SCO socket layer initialized
[ 25.924624] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 25.924640] i915 0000:00:02.0: setting latency timer to 64
[ 25.998449] Bluetooth: RFCOMM TTY layer initialized
[ 25.998464] Bluetooth: RFCOMM socket layer initialized
[ 25.998471] Bluetooth: RFCOMM ver 1.11
[ 26.087690] i915 0000:00:02.0: irq 44 for MSI/MSI-X
[ 26.087707] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 26.087714] [drm] Driver supports precise vblank timestamp query.
[ 26.200936] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 26.202981] [drm] initialized overlay support
[ 26.400079] ath9k 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 26.400103] ath9k 0000:02:00.0: setting latency timer to 64
[ 26.452504] ath: EEPROM regdomain: 0x65
[ 26.452513] ath: EEPROM indicates we should expect a direct regpair map
[ 26.452524] ath: Country alpha2 being used: 00
[ 26.452529] ath: Regpair used: 0x65
[ 26.452720] cfg80211:...

[teamkde (teamkde-gmail)]

I have this same problem on two machines running 11.04.

Machine #1 Dell Duo built in Bluetooth Adapter
Machine #2 Dell Vostro 1520 Laptop using a Kensington bluetooth adapter that worked perfectly in previous versions of Ubuntu

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev=02.06
S: Manufacturer=Linux 2.6.38-8-generic ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:1a.7
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev=02.06
S: Manufacturer=Linux 2.6.38-8-generic ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:1d.7
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev=02.06
S: Manufacturer=Linux 2.6.38-8-generic uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1a.0
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev=02.06
S: Manufacturer=Linux 2.6.38-8-generic uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1a.1
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a12 ProdID=0001 Rev=31.64
C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev=02.06
S: Manufacturer=Linux 2.6.38-8-generic uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1a.2
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev=02.06
S: Manufacturer=Linux 2.6.38-8-generic uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.0
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=07 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev=02.06
S: Manufacturer=Linux 2.6.38-8-generic uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.1
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls...

[Gunne Steen (gunne)]

Hi,

Just want to give the information that this bug mentioned not is present if using Linux kernel package 2.6.38-9 (present in natty proposed repository). As also mentioned earlier in this thread.

So something have been changed in the kernel packages following updates 2.6.35.x (maverick) - 2.6.38-8 to 2.6.38-9 causing the differencies in behaviour. Have not gone deeper into it for to see exactly whats changed :-)

[JoaoH (joao-machado-family)]

Same issue on HPmini and HP G60 notebook with usb dongle:
Bus 003 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Worked fine in 10.10...

For me, if I boot from a cold boot, the bluetooth dongle will not work, dongle doen't blink and Gnome applet icon is greyed out. If I unplug it the icon goes away, if I plug it back in the icon comes back but it is still greyed out.

Restarting the laptop will cause the bluetooth dongle to work normally , if I shutdown and restart it will not work, a soft restart will make it work again.

hope this helps...

[Btg (bjorn-t-gustafsson)]

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

Refused to work with 2.6.38-8, updated to 2.6.38-9 and now it works like a charm.

Well done.

[Apteryx (maxco)]

I have the same hardware as post #52 (ID 0cf3:3002 Atheros Communications, Inc.), and bluetooth hardware device is not recognized (it times out):

hciconfig
hci0: Type: BR/EDR Bus: USB
 BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
 DOWN
 RX bytes:0 acl:0 sco:0 events:0 errors:0
 TX bytes:9 acl:0 sco:0 commands:3 errors:0

sudo hciconfig hci0 reset
Can't init device hci0: Connection timed out (110)

uname -a
Linux Vostro-V130 2.6.38-9-generic #43-Ubuntu SMP Thu Apr 28 15:23:06 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

[szbab (szbab-club)]

same problem with a laptop Clevo W270HUQ
Refused to work with 2.6.38-8, updated to 2.6.38-9 and now it works like a charm.

[Mike Yates (fonehelp)]

So, do we have an expected date when 2.6.38-9 will be on the "normal" updates?

Or is it harmless to install it now? Where from?

[Paolo Rotolo (paolorotolo)]

Yes, the bug is fixed in the update of 30/05/2011

Thanks all!

[rb.eng (rb-engch)]

Works with 11.04 Kernel 2.6.38-8 after installing updates 5/30/2011

>>>THANK YOU <<< to all those involved in this fix. You've made my day a lot brighter!

Upgraded packages 5/30/2011:
bind9-host to 1:9.7.3.dfsg-1ubuntu2.1;dnsutils to 1:9.7.3.dfsg-1ubuntu2.1; gnome-nettool to 2.32.0-0ubuntu1.1;
libbind9-60 to 1:9.7.3.dfsg-1ubuntu2.1; libdns69 to 1:9.7.3.dfsg-1ubuntu2.1; libisc62 to 1:9.7.3.dfsg-1ubuntu2.1; libisccc60 to 1:9.7.3.dfsg-1ubuntu2.1; libisccfg62 to 1:9.7.3.dfsg-1ubuntu2.1; liblwres60 to 1:9.7.3.dfsg-1ubuntu2.1; libpam-modules to 1.1.2-2ubuntu8.2; libpam-modules-bin to 1.1.2-2ubuntu8.2; libpam-runtime to 1.1.2-2ubuntu8.2; libpam0g to 1.1.2-2ubuntu8.2; phonon-backend-gstreamer to 4:4.7.0really4.5.0-0ubuntu2.1; xserver-common to 2:1.10.1-1ubuntu1.1; xserver-xephyr to 2:1.10.1-1ubuntu1.1; xserver-xorg-core to 2:1.10.1-1ubuntu1.1

Hardware: Dell Mini 9; Dlink DBT-120 dongle through a Kensington SD-100 docking station.
Bus 001 Device 015: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

[rb.eng (rb-engch)]

Premature Assessment: > Worked for one reboot <> with 11.04 Kernel 2.6.38-8 after installing updates 5/30/2011.

It turns out the fix for me is not complete. Following a restart This Morning: I still need to use "sudo service bluetooth restart" to get bluetooth working. I will test it again after I see 2.6.38-9 released and will report again. I'll be more thorough in my assessments next time.

Nonetheless I appreciate the efforts being made to fix the bug by Ian et al.

[VoLk (ivn-wd77)]

I still need use "sudo service bluetooth restart" too. The bug isn't fixed in the update of 30/05/2011 for me :-(

I have a laptop Toshiba L500-223.
Ubuntu 11.04, 64-bit, 2.6.38-8-generic.

[ChrisBE (cbe010)]

updates and natty-proposed kernel 2.6.38-9 did not work for me.
ubuntu 11.04 64-bit

[John Pugh (jpugh)]

This seems to be a duplicate of bug 700292 however some state the fix in 700292 does not fix their issue.

https://bugs.launchpad.net/bugs/700292

[Jeanfrancoissven (s-beddeleem)]

"updates and natty-proposed kernel 2.6.38-9 did not work for me.
ubuntu 11.04 64-bit"

Same here!
My bluetooth applet stays grey all the time...

[Jeanfrancoissven (s-beddeleem)]

Solved, I had to enable my bluetooth adapter in the windows partition...

[Mike Yates (fonehelp)]

Surely you mean it's solved in Windows, not Ubuntu !!

Anyone tried reverting to 2.6.38-7 ?

Any advice on doing that ?

I've been without a mouse for a month now - almost going back to 10.10 or a tangly USB cable...

Well, I can start it by "sudo service bluetooth restart" then delete and rediscover mouse, but...

[Niko (niko2f)]

With my notebook Asus M51Sn the bluetooth not working...
Bus 004 Device 002: ID 0b05:1712 ASUSTek Computer, Inc. BT-183 Bluetooth 2.0+EDR adapter
but if I do:
sudo service bluetooth restart
then it's allright!!

[axelsvag (darinsson)]

Still problem with acer d255 with "ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
" even when using 2.6.38-9. Sudo service bluetooth restart works though

[tkoun (tkoun)]

hello,

here is my workaround that consistently works not only at boot or reboot but also after suspend/hibernate...

--> just install using synaptic the bluez package from blueman ppa (ppa:blueman/ppa); it only exists for maverick but it installs ok in natty.

before I tried
1) kernel upgrade from natty proposed
2) /etc/init.d/ bluetooth restart in /etc/rc.local

1) did not work and 2) does not work after suspend/resume

hope this will help someone trapped in natty and lazy as myself to downgrade to the good old maverick...

PS: after having to deal with this and the infamous 1-pixel tray icons bug (https://bugs.launchpad.net/ubuntu/natty/+source/unity/+bug/767095) I wonder how it is possible that natty ever came out of the beta (not to say alpha) status

[rb.eng (rb-engch)]

Bluetooth now working!
After installing updates 6/4/2011 to kernel 2.6.38-9.43 et al my bluetooth keyboard is now working.
No more "sudo service bluetooth restart" required to get things working!

Thanks again to all those who worked to get this working.

Hardware:
Dell Mini 9; Dlink DBT-120 dongle through a Kensington SD-100 docking station.
Bus 001 Device 015: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Software (Synaptic quick filter "Blue"):
gnome-bluetooth 2.91.2.is.2.32.0-0ubuntu3
bluez-gstreamer 4.91-0ubuntu1
bluez 4.91-0ubuntu1
libgnome-bluetooth8 2.91.2.is.2.32.0-0ubuntu3
libbluetooth3 4.91-0ubuntu1
gtk2-engines 1:2.20.2-0ubuntu1
obex-data-server 0.4.6-0ubuntu1
rfkill 0.4-1
totem-plugins 2.32.0-0ubuntu10

[tkoun (tkoun)]

workaround described in #86 does not work consistently.
please disregard.
any news on this? does a kernel upgrade really work?

[ubuntic (ubuntic)]

Using Mainline Kernel: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v2.6.37.6-natty/
works for me.

You have to choose this kernel on booting the pc (after download and
install).

cheers
ubuntic

PS: We have to wait for a stable kernel, the kernels 2.6.38 and 2.6.39 are
little bit buggy i think.

[Mike Yates (fonehelp)]

I mentioned "reverting" to an older kernel or even 10.10 above.
I have found that if, on booting, I choose "Older Versions of Linux" and then the only non-recovery kernel offered,
my bluetooth mouse works consistently, even before logging in

$ uname -a
Linux mynetbook 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 01:41:57 UTC 2010 i686 i686 i386 GNU/Linux

When are we going to get a new kernel as good (for bluetooth) as that one?

[Mathieu Trudel-Lapierre (cyphermox)]

Since there are multiple reports about bluetooth working with a different kernel version, I'll reassign this to the linux package so there are more chances of someone actually fixing this as an update ;)

Has it been ascertained yet *which* kernel version consistently works for this? Is 2.6.38-9.43 working properly for everyone (you need to enable natty-proposed to get that version)?

[Mathieu Trudel-Lapierre (cyphermox)]

Actually, turns out that should be 2.6.38-10.44 in natty-proposed now, it should contain roughly the same patches.

[Xandru (xandruarmesto)]

Bluetooth works correctly with 2.6.38.10-44 (natty-proposed) in Toshiba Satellite U300 (bug #751208).

[Mike Yates (fonehelp)]

My bluetooth mouse also works consistently with natty-proposed, too, in my Packard Bell DOT_S2 netbook (Atom N450)

Linux mynetbook 2.6.38-10-generic #44-Ubuntu SMP Thu Jun 2 21:32:54 UTC 2011 i686 i686 i386 GNU/Linux

[Mike Yates (fonehelp)]

Strangely, though, after installing 2.6.38-10, if I select 2.6.38-8 (11.04 original) in GRUB, the mouse works OK !
mike@mynetbook:~$ uname -a
Linux mynetbook 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 i686 i386 GNU/Linux

Surely the modules etc. linked to the older kernel should not have been changed by the natty-proposed kernel (only) install?

[Marcos (deflagmator)]

Bluetooth now works perfect with 2.6.38.10 (natty-proposed) in HP dm1 (amd fusion laptop).

[[e-mail] (zubairw)]

Same problem. solved by killin bluetooth and restarting. waiting for a fix

[wnutt (wnutt998)]

I apologize if this should have been another in another bug/thread.

I have been having various problems with what lsusb shows to be "ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)" after much digging and frustration I found that there are "fake"(not Cambridge Silicon Radio hardware) dongles.

https://bugzilla.redhat.com/show_bug.cgi?id=519176#c37

After opening the dongle, I found almost exactly what was described. The only difference is that the number on my device was "AS3610QA C0912CAT", AS361 instead of the mentioned AS362. You may not need to open your dongle to find this out. The hardware address range for Accel is 00:1F:81 or 00:1F:81:00:00:00 - 00:1F:81:FF:FF:FF.

lots more info on this issue here: http://www.linux-archive.org/debian-kernel/542442-bug-525220-bluetooth-problem-caused-fake-dongles.html

uname -a : Linux StarBug1 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
And the current state of operation is that I can get as far as pairing after running "sudo service bluetooth stop" then "sudo service bluetooth start", restart does not seem to change anything.

I am willing to do testing but don't know more than a little bash.

[Geert (geert-x)]

I also have the Bluetooth disabled issue. When running the command '/etc/init.d/bluetooth start' I always get an error that the version of hci0 can't be read because the adapter is down. After bringing it up with 'hciconfig hci0 up' I can execute '/etc/init.d/bluetooth start' without error and bluetooth is working again.

Based on this observation I added the command 'hciconfig hci0 up' to the script '/etc/init.d/bluetooth'. I placed it in the beginning of the script, just before the 'Test' commands. Now bluetooth starts automatically after booting. (Kernel 2.6.38-8).

[Nikola Snele (n-schnelle)]

2.6.38-10-generic fixes bluetooth problem for me.

[Håvar (havar)]

Making /usr/sbin/bluetoothd suid root, solves this problem, but might pose some security issues.

sudo chmod +s /usr/sbin/bluetoothd

[Håvar (havar)]

Had this problem for this device: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth
The suid root fix above solved this problem on the release version of Ubuntu 11.04.

[Łukasz Szeremeta (l-szeremeta)]

Latest updates Ubuntu (including new kernel) solves this problem.

[Łukasz Szeremeta (l-szeremeta)]

*** Latest Ubuntu updates (including new kernel) solves this problem. ***

[Paolo Rotolo (paolorotolo)]

ok, good :)
Thanks all for the time to helping to make Ubuntu better :)

[Mark Ovens (parish)]

Everything working again now, except that my Kensington BT mouse doesn't seem to reconnect automatically when the computer comes out of sleep which it used to in 10.10.

Thanks to those who fixed this :)

[Nick (soapduk)]

New kernel hasn't fixed it for me.

Ubuntu 11.04 - 32bit.

uname -a:
Linux scooby 2.6.38-10-generic-pae #46-Ubuntu SMP Tue Jun 28 16:54:49 UTC 2011 i686 athlon i386 GNU/Linux

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

I have a greyed out bluetooth icon. I can change the settings but setting BT to on doesn't activate it.

'sudo service bluetooth restart' makes the bluetooth software work, but I have to do it each time I boot, and my device does not find my BT mobile phone.

Also:

sudo killall /usr/sbin/bluetoothd
/usr/sbin/bluetoothd: no process found

sudo hciconfig hci0 reset - did nothing.

Bluetooth worked for me on 10.10 with this device.

[Nick (soapduk)]

Actually (see above comment) I've got it working now with the phone. It just seems sometimes after booting I have to do the 'sudo service bluetooth restart' to get BT working.

[Nick (soapduk)]

Bluetooth still only works after 'sudo service bluetooth restart' and, I have found -- oddly -- after resuming from hibernate. It's greyed out generally on booting. though.

[Mike Yates (fonehelp)]

Works perfectly for me again (as 10.10) since the new kernel arrived in the regular updates in June.
No-bluetooth was intermittent with the advance-realease of that kernel, though.
Ensure you have reverted your update-sources to normal, Nick.

[Karel Kozlik (karel.kozlik)]

new kernel does not fixed this for me as well

kk@kk-nb:~$ uname -a
Linux kk-nb 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

lsusb:
Bus 006 Device 003: ID 0c24:0021 Taiyo Yuden

[Seth Forshee (sforshee)]

All: this bug is fixed, as the problem is fixed for the individual who reported the problem. If your bluetooth still isn't working then you have a different problem, and you should open a new bug by running 'ubuntu-bug linux' from a terminal. Thanks!

[Nick (soapduk)]

yes it's working for me now. I found the program was related to an 11.04 install that crashed on 99%, affecting some of the start-up services or programs, but I've reinstalled those.

[Karlox (teknikalrepair)]

killall bluetoothd
Bluetoothd
Those simple commands made it up and runing!
Thanx!
Satellite pro A100
Device 002: ID 0930:0508 Toshiba Corp. Integrated Bluetooth HCI

[Karel Kozlik (karel.kozlik)]

Karlox and others who still have to restart bluetooth to make it working, please report to bug 830446. There is still some problem in the BT.
Tnx

[Mani Sabri (mani-sabri)]

This:
 http://askubuntu.com/questions/645/how-do-you-reset-a-usb-device-from-the-command-line
worked like a magic for me!

[yahya gm (yuhanna-yz)]

0000002B