Bluetooth does not work at Acer Aspire 7520

Bug #284982 reported by IUnknown
96
This bug affects 13 people
Affects Status Importance Assigned to Milestone
bluez-utils (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Hardy by Abelardo Jara-Berrocal
Nominated for Intrepid by IUnknown
Nominated for Jaunty by IUnknown
Nominated for Karmic by seanbw

Bug Description

Bluetooth does not work. dmesg says:
root@sasha-laptop:/etc/apt# dmesg | grep 'Bluetooth'
[ 22.160307] Bluetooth: Core ver 2.13
[ 22.160419] Bluetooth: HCI device and connection manager initialized
[ 22.160426] Bluetooth: HCI socket layer initialized
[ 22.164536] Bluetooth: L2CAP ver 2.11
[ 22.164540] Bluetooth: L2CAP socket layer initialized
[ 22.171108] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 115.563085] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 115.563104] Bluetooth: BNEP filters: protocol multicast
[ 115.621833] Bluetooth: RFCOMM socket layer initialized
[ 115.621875] Bluetooth: RFCOMM TTY layer initialized
[ 115.621879] Bluetooth: RFCOMM ver 1.10
[ 115.975984] Bluetooth: SCO (Voice Link) ver 0.6
[ 115.975986] Bluetooth: SCO socket layer initialized

hcitool says nothing:
root@sasha-laptop:/etc/apt# hcitool dev
Devices:

When I am trying to restart bluetooth:
root@sasha-laptop:/etc/apt# /etc/init.d/bluetooth restart
 * Stopping bluetooth [ OK ]
 * Starting bluetooth [ OK ]

I have these:
Oct 17 16:27:34 sasha-laptop bluetoothd[19851]: Bluetooth daemon
Oct 17 16:27:34 sasha-laptop bluetoothd[19851]: Starting SDP server
Oct 17 16:27:34 sasha-laptop bluetoothd[19851]: bridge pan0 created
Oct 17 16:27:34 sasha-laptop kernel: [29788.788077] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Oct 17 16:27:34 sasha-laptop bluetoothd[19851]: Starting experimental netlink support
Oct 17 16:27:34 sasha-laptop bluetoothd[19851]: Failed to find Bluetooth netlink family
Oct 17 16:27:34 sasha-laptop bluetoothd[19851]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so

What is wrong with my bluetooth?

Revision history for this message
Sameer Morar (smorar) wrote :

I can confirm that the exactly same problem happens on my laptop. I am currently using a Toshiba Tecra M4.

Revision history for this message
SabreWolfy (sabrewolfy) wrote :

Same output for me (just slightly newer version numbers) with Intrepid RC on an Acer Aspire 4710. Does that mean there is no way I can use bluetooth in Ubuntu on this laptop? :-( That would be sad.

Revision history for this message
Feanor (angelo-pantano) wrote :

same problem here, ubuntu intrepid and toshiba satellite laptop

my adapter worked fine in hardy

Revision history for this message
bluebook (sharpchick) wrote :

Same problem here as well. Lenovo Thinkpad X200 with Intrepid. It worked fine with Hardy Heron. Some more output that might help.

dmesg | grep 'Bluetooth'
[ 40.928567] Bluetooth: Core ver 2.11
[ 40.928720] Bluetooth: HCI device and connection manager initialized
[ 40.928726] Bluetooth: HCI socket layer initialized
[ 40.987001] Bluetooth: L2CAP ver 2.9
[ 40.987009] Bluetooth: L2CAP socket layer initialized
[ 41.048236] Bluetooth: BNEP (Ethernet Emulation) ver 1.2
[ 41.048246] Bluetooth: BNEP filters: protocol multicast
[ 41.108913] Bluetooth: RFCOMM socket layer initialized
[ 41.108935] Bluetooth: RFCOMM TTY layer initialized
[ 41.108939] Bluetooth: RFCOMM ver 1.8
[ 41.126689] Bluetooth: SCO (Voice Link) ver 0.6
[ 41.126696] Bluetooth: SCO socket layer initialized

 sudo hciconfig hci0 reset
Can't get device info: No such device

grep hcid /var/log/syslog
returns nothing

hcitool scan
Device is not available: No such device

 sudo /etc/init.d/bluetooth start stop restart
 * Starting bluetooth [ OK ]

grep blue /var/log/syslog
Nov 3 09:01:15 doublethink bluetoothd[5705]: Bluetooth daemon
Nov 3 09:01:15 doublethink bluetoothd[5705]: Starting SDP server
Nov 3 09:01:15 doublethink bluetoothd[5705]: Starting experimental netlink support
Nov 3 09:01:15 doublethink bluetoothd[5705]: Failed to find Bluetooth netlink family
Nov 3 09:01:15 doublethink bluetoothd[5705]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Nov 3 09:01:15 doublethink bluetoothd[5705]: bridge pan0 created

Revision history for this message
John Doe (johndoe32102002) wrote :

Same problem here as well. I have a Winbook V Series laptop. I upgraded from Hardy to Intrepid, and bluetooth now fails to work properly. Here are some hopefully helpful logs:

#dmesg | grep 'Bluetooth'
[ 36.432172] Bluetooth: Core ver 2.13
[ 36.436772] Bluetooth: HCI device and connection manager initialized
[ 36.436777] Bluetooth: HCI socket layer initialized
[ 36.466171] Bluetooth: L2CAP ver 2.11
[ 36.466176] Bluetooth: L2CAP socket layer initialized
[ 36.484050] Bluetooth: SCO (Voice Link) ver 0.6
[ 36.484054] Bluetooth: SCO socket layer initialized
[ 36.527797] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 36.527801] Bluetooth: BNEP filters: protocol multicast
[ 36.693036] Bluetooth: RFCOMM socket layer initialized
[ 36.693053] Bluetooth: RFCOMM TTY layer initialized
[ 36.693056] Bluetooth: RFCOMM ver 1.10
[ 6812.928554] Bluetooth: Generic Bluetooth USB driver ver 0.3

#sudo hciconfig hci0 reset
<nothing resulted>

#hcitool scan
Scanning ...
Inquiry failed: Connection timed out
<the bluetooth light was not blinking, no scanning was occuring>

#sudo /etc/init.d/bluetooth restart
 * Stopping bluetooth [ OK ]
 * Starting bluetooth [ OK ]

#hcitool dev
Devices:
 hci0 <mac here>

Installing these bluetooth programs, above the default installed programs for Intrepid, did not help:
Commit Log for Wed Nov 5 21:17:29 2008

Installed the following packages:
gnome-bluetooth (0.11.0-0ubuntu3)
gnome-vfs-obexftp (0.4-1build1)
libbtctl4 (0.10.0-1ubuntu1)
libgnomebt0 (0.11.0-0ubuntu3)
obexfs (0.10-3build1)
obexftp (0.19-7ubuntu2)
obexpushd (0.7-1ubuntu2)
ussp-push (0.9-2ubuntu1)

Revision history for this message
mklebel (mklebel) wrote :

same exact issue with me also.

Laptop - HP Compaq nc6230

Revision history for this message
Damien Wendlinger (d-wendlinger) wrote :

I also got the same problems, with the integrated bluetooth device.
my configuration is a Dell Vostro 1510, where 'firmware-addon-dell' has been installed.
ubuntu 8.10 Intrepid Ibex
packages installed, related to bluetooth features :
bluetooth
bluez
bluez-alsa
bluez-cups
bluez-gnome
bluez-gstreamer
bluez-pcmcia-support
gnome-bluetooth
gnome-vfs-obexftp
libbluetooth3
libbtctl4
libgnomebt0
obex-data-server

Revision history for this message
Olivier Guéry (nemolivier) wrote :

Bluetooth problems here to. Don’t know if it’s exactly the same.

I’m using a usb bluetooth key. Worked well in hardy.

lsusb give me this : Bus 002 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
dmesg this : [28710.504058] usb 2-3: new full speed USB device using ohci_hcd and address 4
                    [28710.721927] usb 2-3: configuration #1 chosen from 1 choice
                    [28710.974113] Bluetooth: Generic Bluetooth USB driver ver 0.3
                    [28710.976044] usbcore: registered new interface driver btusb

When I plugged it, the applet appear.
The applet can « find » my phone (nokia e71) but when I select it and choose « next » the too can’t « connect » (don’t know how to say that in english).
From the phone, I can find and « connect » my phone and computer. It seem’s that action from phone to computer worked, but not the other way.
Blueproximity, for exemple failed, gammu too.

Olivier.

Revision history for this message
herve34fr (hgotty) wrote :

I have also the same problem.
With intrepid Bluetooth doesn't work.
I'm using an USB Bluetoth key well recognized.
I can see other BT devices with the Gnome-applet but I can't pair them.
I think it's a bug of Intrepid. . . .

Hervé

Stiff (stiff.ru)
Changed in bluez-utils:
assignee: nobody → stiff11
status: New → Confirmed
Revision history for this message
Damien Wendlinger (d-wendlinger) wrote :
Download full text (4.0 KiB)

I bought an USB Bluetooth key (Belkin - F8T013), which works fine, immediately after connexion.
Nothing to do, really, not even a "bluetooth restart"...

Here some clues, maybe !
damien@vostro:~$ lsmod | grep bluetooth
bluetooth 61924 23 btusb,sco,bnep,rfcomm,l2cap
             ==> before having that key, I had no 'btusb'
damien@vostro:~$ dmesg | grep 'Bluetooth'
[ 32.211975] Bluetooth: Core ver 2.13
[ 32.214162] Bluetooth: HCI device and connection manager initialized
[ 32.214169] Bluetooth: HCI socket layer initialized
[ 32.264247] Bluetooth: L2CAP ver 2.11
[ 32.264260] Bluetooth: L2CAP socket layer initialized
[ 32.331217] Bluetooth: RFCOMM socket layer initialized
[ 32.331243] Bluetooth: RFCOMM TTY layer initialized
[ 32.331248] Bluetooth: RFCOMM ver 1.10
[ 32.365798] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 32.365813] Bluetooth: BNEP filters: protocol multicast
[ 32.637959] Bluetooth: SCO (Voice Link) ver 0.6
[ 32.637974] Bluetooth: SCO socket layer initialized
[ 302.061098] Bluetooth: Generic Bluetooth USB driver ver 0.3
             ==> before having that key, I had not this Generic BT USB driver

before having the key, daemon.log said :
Nov 5 07:20:23 vostro bluetoothd[6656]: Bluetooth daemon
Nov 5 07:20:23 vostro bluetoothd[6656]: Starting SDP server
Nov 5 07:20:23 vostro bluetoothd[6656]: Starting experimental netlink support
Nov 5 07:20:23 vostro bluetoothd[6656]: Failed to find Bluetooth netlink family
Nov 5 07:20:23 vostro bluetoothd[6656]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Nov 5 07:20:23 vostro bluetoothd[6656]: bridge pan0 created
Nov 5 23:51:06 vostro bluetoothd[6656]: bridge pan0 removed
Nov 5 23:51:06 vostro bluetoothd[6656]: Stopping SDP server
Nov 5 23:51:06 vostro bluetoothd[6656]: Exit
Nov 5 23:51:06 vostro bluetoothd[19503]: Bluetooth daemon
Nov 5 23:51:06 vostro bluetoothd[19503]: Starting SDP server
Nov 5 23:51:06 vostro bluetoothd[19503]: Starting experimental netlink support
Nov 5 23:51:06 vostro bluetoothd[19503]: Failed to find Bluetooth netlink family
Nov 5 23:51:06 vostro bluetoothd[19503]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Nov 5 23:51:06 vostro bluetoothd[19503]: bridge pan0 created

Now, it says :
Nov 9 00:44:10 vostro bluetoothd[8416]: HCI dev 0 registered
Nov 9 00:44:10 vostro bluetoothd[8416]: HCI dev 0 up
Nov 9 00:44:10 vostro bluetoothd[8416]: Failed to listen on control channel
Nov 9 00:44:10 vostro bluetoothd[8416]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Nov 9 00:44:10 vostro bluetoothd[8416]: Registered interface org.bluez.Service on path /org/bluez/hci0
Nov 9 00:44:10 vostro bluetoothd[8416]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 9 00:44:10 vostro bluetoothd[8416]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 9 00:44:10 vostro bluetoothd[8416]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 9 00:44:10 vostro bluetoothd[8416]: Registered interface org.bluez.Serial on path /org/bluez/hci0/dev_MAC_ADRESS1
Nov 9 00:44:10 vostro bluetoothd[8416]: Registered interface org.bluez....

Read more...

Revision history for this message
chaanakya (chiraag) wrote :

I have similar lines in my daemon.log, but my bluetooth is not working. By that, I mean that it can find others, but cannot pair with them. Very frustrating. DEVS: PLEASE FIX THIS ASAP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Relevant lines from daemon.log:

Nov 11 17:46:12 chiraag-laptop bluetoothd[5225]: HCI dev 0 registered
Nov 11 17:46:12 chiraag-laptop bluetoothd[5225]: HCI dev 0 up
Nov 11 17:46:12 chiraag-laptop bluetoothd[5225]: Registered interface org.bluez.Service on path /org/bluez/hci0
Nov 11 17:46:12 chiraag-laptop bluetoothd[5225]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Nov 11 17:46:12 chiraag-laptop bluetoothd[5225]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 11 17:46:12 chiraag-laptop bluetoothd[5225]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 11 17:46:12 chiraag-laptop bluetoothd[5225]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 11 17:46:12 chiraag-laptop bluetoothd[5225]: Adapter /org/bluez/hci0 has been enabled
Nov 11 17:46:12 chiraag-laptop bluetoothd[5225]: Starting security manager 0

Any ideas would be helpful.

Revision history for this message
chaanakya (chiraag) wrote :

Edit: It "successfully connected" with my bluetooth mouse, but it just doens't work. I'm sure the mouse isn't a problem because it works fine on my dad's laptop running vista (ugh!) Anyway, I'll try connecting my Lego Mindstorms NXT and see how that goes.

Revision history for this message
chaanakya (chiraag) wrote :

Edit: OK. The pairing with the NXT failed, probably because it required a pin. Does anyone know how to send a certain pin from the computer to the other device, whatever that may be? Thanks.

Revision history for this message
Alexey Govorov (zlogr5) wrote :

Same problem for me..

1. dmesg | grep 'Bluetooth'
[ 17.780769] Bluetooth: Core ver 2.13
[ 17.782668] Bluetooth: HCI device and connection manager initialized
[ 17.782674] Bluetooth: HCI socket layer initialized
[ 17.867079] Bluetooth: L2CAP ver 2.11
[ 17.867089] Bluetooth: L2CAP socket layer initialized
[ 17.893351] Bluetooth: RFCOMM socket layer initialized
[ 17.894359] Bluetooth: RFCOMM TTY layer initialized
[ 17.894368] Bluetooth: RFCOMM ver 1.10
[ 17.920952] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 17.920961] Bluetooth: BNEP filters: protocol multicast
[ 18.049778] Bluetooth: SCO (Voice Link) ver 0.6
[ 18.049786] Bluetooth: SCO socket layer initialized
[88530.085339] Bluetooth: Generic Bluetooth USB driver ver 0.3

2. root@adm:/# hcitool dev
Devices:
 hci0 00:02:72:05:F1:24

3. And then i trying to setup new device via bt applet it displays clear list of devices (you can see it on screenshot..)

Revision history for this message
drewp (drewp) wrote :

Same on hp pavilion dv9000 with Actiontec BTM200B usb bluetooth. It used to work in hardy.

plus(pts/0):/# uname -a
Linux plus 2.6.24-21-generic #1 SMP Tue Oct 21 23:09:30 UTC 2008 x86_64 GNU/Linux

plus(pts/0):/# lsusb | grep -i blue
Bus 003 Device 002: ID 1668:0500 Actiontec Electronics, Inc. [hex] BTM200B BlueTooth Adapter

plus(pts/0):/# dmesg | grep -i blue
[ 41.722719] Bluetooth: Core ver 2.11
[ 41.723865] Bluetooth: HCI device and connection manager initialized
[ 41.723869] Bluetooth: HCI socket layer initialized
[ 42.302901] Bluetooth: HCI USB driver ver 2.9

plus(pts/0):/# hcitool dev
Devices:

plus(pts/0):/# hcitool scan
Device is not available: No such device

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

Hey, I'm not alone!!!

I can't make my acer aspire 5610 with USB bluetooth to work with the wiimote, I can see the wiimotes, but I can't connect.

It worked fine in Hardy.

Revision history for this message
Ash (ashish-g8) wrote :

same as above all... my machine Toshiba Satellite M200....
have not tried previous version, but inbuilt bluetooth not working in 8.10

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

Please...
Could you the Ubuntu guys tell in a detailed list what changes have you done in bluethooth so we the users that have problems now (a lot of people) can help you squash the bugs?.

All bug reports I see have been unusually mute on the ubuntu devs side.

A little communication will help to overcome the frustration that people have when things that worked, don't work anymore. It will add more eyes to find the problem too.

Revision history for this message
Rafael (infornography) wrote :

Also experiencing this problem in a Sony Vaio NR330AE, Ubuntu 8.10.

This line shows in dmesg everytime I try to restart the "bluetooth" service:
[ 5867.790329] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.

Revision history for this message
chaanakya (chiraag) wrote :

Yes! I finally got Bluetooth working ( kind of). I added blueman's repo and updated the bluez 4 stack ( I think it is version 20), and presto! Bluetooth works for the first time on my laptop in intrepid! There are a few problems, however. For one, the statusbar icon disappears after my first connection. To solve this problem, restart the Bluetooth service, and you should be good to go. I figured out how to make intrepid ask for a passkey. I'm not at my ubuntu box right now, but you have to edit the hcid.conf and remove 1234 from the "default passkey for incoming connections" section (you should leave the quotes there). Bluetooth should work at this point!

Revision history for this message
peddy (peddy22) wrote :

chaanakya, could you please post the output of

dpkg -l | grep blue

to help others match your configuration?

Thanks :)

Revision history for this message
drewp (drewp) wrote :

My device detection also improved when I added the blueman repo. I haven't tried all the dialup/etc functions, but this fixes my "No such device" problem.

web page:
https://launchpad.net/~blueman/+archive

add these to /etc/apt/sources.list:
deb http://ppa.launchpad.net/blueman/ubuntu intrepid main
deb-src http://ppa.launchpad.net/blueman/ubuntu intrepid main

dpkg -l | grep blue
ii blueman 0.6-r121-0ubuntu3~ppa1i A graphical bluetooth manager
rc bluetooth-alsa 0.5cvs20070908-1 Bluetooth audio for Linux
ii bluetooth3 3.26-0ubuntu14 Bluetooth stack utilities
rc bluez 4.12-0ubuntu5 Bluetooth tools and daemons
rc bluez-audio 3.26-0ubuntu6 Bluetooth audio support
ii bluez-gnome 1.8-0ubuntu1 Bluetooth utilities for GNOME
rc bluez-utils 4.12-0ubuntu5 Transitional package
ii bluez3-audio 3.26-0ubuntu14 Bluetooth audio support
ii bluez3-utils 3.26-0ubuntu14 Bluetooth tools and daemons
ii gnome-bluetooth 0.11.0-0ubuntu3 GNOME Bluetooth tools.
ii libbluetooth-dev 4.19-1ubuntu2 Development files for using the BlueZ Linux Bluetooth library
ii libbluetooth2 3.29-0ubuntu1 Library to use the BlueZ Linux Bluetooth stack
ii libbluetooth3 4.19-1ubuntu2 Library to use the BlueZ Linux Bluetooth stack
ii python-bluez 0.15-1build1 Python wrappers around BlueZ for rapid bluetooth development

Stiff (stiff.ru)
Changed in bluez-utils:
assignee: stiff11 → nobody
Revision history for this message
Ash (ashish-g8) wrote :

added repo - it updated bluez to 4.20 but still no help.... Satellite M200

Revision history for this message
John Doe (johndoe32102002) wrote : Re: [Bug 284982] Re: Bluetooth does not work at Acer Aspire 7520

I tried to update bluez to 4.20 from the source, and that did not help
either... Winbook V350

On 12/1/08, Ash <email address hidden> wrote:
> added repo - it updated bluez to 4.20 but still no help.... Satellite
> M200
>
> --
> Bluetooth does not work at Acer Aspire 7520
> https://bugs.launchpad.net/bugs/284982
> You received this bug notification because you are a direct subscriber
> of the bug.
>

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

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

I tried installing blueman from drewp suggestions.

I updated bluez to 4.20 like Ash did...

...my bluetooth is not working.Detection but no connect.

My wiimotes are used as paperweight. :-(

Acer Aspire 5610

Revision history for this message
Rafael (infornography) wrote :

Are the errors in dmesg the same, even after the update?

On Tue, Dec 2, 2008 at 4:55 PM, Jose Hevia
<email address hidden> wrote:
> I tried installing blueman from drewp suggestions.
>
> I updated bluez to 4.20 like Ash did...
>
> ...my bluetooth is not working.Detection but no connect.
>
> My wiimotes are used as paperweight. :-(
>
> Acer Aspire 5610
>
> --
> Bluetooth does not work at Acer Aspire 7520
> https://bugs.launchpad.net/bugs/284982
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

The problem everybody is having seems a software thing, a lot of people is having problems with connections.

I think I never had errors on dmesg. I removed the blueman repository and reverted to standard ubuntu config.

If I put now the usb bluetooth dongle and click setup new device->Forward the detection of the nintendo wiimote is instantaneus the problem is connecting, if I click forward:

Pairing wih Nintendo RVL-CNT-01 failed

Looking at dsmesg:

[ 121.654024] Bluetooth: L2CAP ver 2.11
[ 121.654034] Bluetooth: L2CAP socket layer initialized
[ 121.677795] Bluetooth: SCO (Voice Link) ver 0.6
[ 121.677806] Bluetooth: SCO socket layer initialized
[ 121.702842] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 121.702853] Bluetooth: BNEP filters: protocol multicast
[ 121.720389] Bluetooth: RFCOMM socket layer initialized
[ 121.720676] Bluetooth: RFCOMM TTY layer initialized
[ 121.720684] Bluetooth: RFCOMM ver 1.10
[ 121.758876] Bridge firewalling registered
[ 121.759112] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
[ 172.856849] CPU0 attaching NULL sched-domain.
[ 172.856860] CPU1 attaching NULL sched-domain.
[ 172.857834] CPU0 attaching sched-domain:
[ 172.857839] domain 0: span 0-1 level MC
[ 172.857843] groups: 0 1
[ 172.857850] CPU1 attaching sched-domain:
[ 172.857852] domain 0: span 0-1 level MC
[ 172.857855] groups: 1 0
[ 245.576132] hci_cmd_task: hci0 command tx timeout

The program lswm detects the device without problems, wmgui gives:
Socket connect error (control channel)

I have used my wiimotes with same hardware with former ubuntu versions, and it just worked. Something has been broken in the software side.

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

John Doe: If you install bluez from source and don't wok, remove it because it could conflict when versions you install. Also, if you compile bluez you need to remove the previous versions(that's why I don't do that).

When nothing worked I installed lswm wmgui... and libs from source, and I noticed they were interfering with the libwii... I had installed. It was giving me (more)problems. Everything in /usr/local is user generated(compiled), not ubuntu created.

Revision history for this message
chaanakya (chiraag) wrote :

Edit: OK. I was mistaken. I have two dongles: one that is very old and can only pair with one device at a time (This one doesn't even work in Windows). The other is quite new, and works on Vista perfectly. On my Ubuntu laptop, the old one works perfectly, but the other doesn't work AT ALL!!!! I still get the bluetooth icon, but I can't find a single device!!!!! When I had said that bluetooth was finally working, I hadn't tested the new one. However, on a positive note, I did just update my bluetooth packages through Update Manager and haven't tested either dongle since. I shall test shortly, as I am still in school :( To recap, the old dongle works, but the new one doesn't. PLEASE FIX THIS DEVS!!!!! I know you are getting emails from Launchpad from this thread. Please, please at least tell us a workaround for this problem, even if it is extremely dirty!!! I need the new one to work!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Revision history for this message
kylea (kylea) wrote :

Intrepid 8.10 64bit

Getting these errors:

Dec 7 22:24:33 kylea-e6500 bluetoothd[13095]: Failed to find Bluetooth netlink family
Dec 7 22:01:53 kylea-e6500 bluetoothd[10423]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Dec 7 22:24:33 kylea-e6500 kernel: [ 2620.764695] usb 1-1.2: usbfs: process 13098 (hid2hci) did not claim interface 0 before use

Have had a pattern of having Bluetooth radio turned off during boot and until gnome desktop is fully loaded - this has worked fine for 1 week.

This weekend load this stopped "working"

Tried repeated switch off and on after approx 10 attempts Bluetooth would start.

Sunday evening nothing was working...

So followed this suggestion...

****************************************************

"My device detection also improved when I added the blueman repo. I haven't tried all the dialup/etc functions, but this fixes my "No such device" problem.

web page:
https://launchpad.net/~blueman/+archive

add these to /etc/apt/sources.list:
deb http://ppa.launchpad.net/blueman/ubuntu intrepid main
deb-src http://ppa.launchpad.net/blueman/ubuntu intrepid main"

****************************************************

Re-paired from the Phone to laptop

Shutdown phone - restarted then Bluetooth worked.

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

If I do
sudo /etc/init.d/bluetooth start stop restart

as bluebook, I get the same messages:
* Starting bluetooth [ OK ]

grep blue /var/log/syslog
Dec 7 10:41:41 xirio bluetoothd[6382]: Bluetooth daemon
Dec 7 10:41:41 xirio bluetoothd[6382]: Starting SDP server
Dec 7 10:41:41 xirio bluetoothd[6382]: Starting experimental netlink support
Dec 7 10:41:41 xirio bluetoothd[6382]: Failed to find Bluetooth netlink family
Dec 7 10:41:41 xirio bluetoothd[6382]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Dec 7 10:41:41 xirio bluetoothd[6382]: bridge pan0 created
Dec 7 14:21:59 xirio bluetoothd[6390]: Bluetooth daemon
Dec 7 14:21:59 xirio bluetoothd[6390]: Starting SDP server
Dec 7 14:21:59 xirio bluetoothd[6390]: Starting experimental netlink support
Dec 7 14:21:59 xirio bluetoothd[6390]: Failed to find Bluetooth netlink family
Dec 7 14:21:59 xirio bluetoothd[6390]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Dec 7 14:21:59 xirio bluetoothd[6390]: bridge pan0 created
Dec 7 17:08:47 xirio bluetoothd[6395]: Bluetooth daemon
Dec 7 17:08:47 xirio bluetoothd[6395]: Starting SDP server
Dec 7 17:08:48 xirio bluetoothd[6395]: Starting experimental netlink support
Dec 7 17:08:48 xirio bluetoothd[6395]: Failed to find Bluetooth netlink family
Dec 7 17:08:48 xirio bluetoothd[6395]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Dec 7 17:08:48 xirio bluetoothd[6395]: bridge pan0 created
Dec 7 21:18:50 xirio bluetoothd[6373]: Bluetooth daemon
Dec 7 21:18:50 xirio bluetoothd[6373]: Starting SDP server
Dec 7 21:18:51 xirio bluetoothd[6373]: Starting experimental netlink support
Dec 7 21:18:51 xirio bluetoothd[6373]: Failed to find Bluetooth netlink family
Dec 7 21:18:51 xirio bluetoothd[6373]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Dec 7 21:18:51 xirio bluetoothd[6373]: bridge pan0 created
Dec 7 21:55:29 xirio bluetoothd[6373]: HCI dev 0 registered
Dec 7 21:55:29 xirio bluetoothd[6373]: HCI dev 0 up
Dec 7 21:55:29 xirio bluetoothd[6373]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Dec 7 21:55:29 xirio bluetoothd[6373]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Dec 7 21:55:29 xirio bluetoothd[6373]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Dec 7 21:55:29 xirio bluetoothd[6373]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Dec 7 21:55:29 xirio bluetoothd[6373]: Registered interface org.bluez.Service on path /org/bluez/hci0
Dec 7 21:55:29 xirio bluetoothd[6373]: Adapter /org/bluez/hci0 has been enabled
Dec 7 21:55:29 xirio bluetoothd[6373]: Starting security manager 0

I don't like the netlink thing.

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

No such netlink errors in Hardy(I have it on another machine, with bluetooth working). There it is much more "Registering" things.

Revision history for this message
kylea (kylea) wrote :

After adding these to /etc/apt/sources.list:

deb http://ppa.launchpad.net/blueman/ubuntu intrepid main
deb-src http://ppa.launchpad.net/blueman/ubuntu intrepid main"

I noticed some "New in repository" items via Synaptic Package Manager.

Ran those - had to uninstall "bluez-compat"

This installed libbluetooth3 and blueman (0.5) and some other items.

Now I start blueman after PC boots to gnome and its all working. blueman also has a much better interface

Here is an extract from my Commit Log for Sun Dec 7 2008

Reinstalled the following packages:
bluetooth (4.12-0ubuntu5)
bluez (4.12-0ubuntu5)
bluez-alsa (4.12-0ubuntu5)
bluez-cups (4.12-0ubuntu5)
bluez-gnome (1.8-0ubuntu1)
bluez-gstreamer (4.12-0ubuntu5)
bluez-utils (4.12-0ubuntu5)
gnome-bluetooth (0.11.0-0ubuntu3)
libbluetooth3 (4.12-0ubuntu5)
libbtctl4 (0.10.0-1ubuntu1)
libgnomebt0 (0.11.0-0ubuntu3)
obex-data-server (0.3.4+svn1951-0ubuntu1)

Reinstalled the following packages:
bluez (4.12-0ubuntu5)

Upgraded the following packages:
bluetooth (4.12-0ubuntu5) to 4.23-0ubuntu2~git20081206
bluez (4.12-0ubuntu5) to 4.23-0ubuntu2~git20081206
bluez-alsa (4.12-0ubuntu5) to 4.23-0ubuntu2~git20081206
bluez-compat (4.12-0ubuntu5) to 4.23-0ubuntu2~git20081206
bluez-cups (4.12-0ubuntu5) to 4.23-0ubuntu2~git20081206
bluez-gstreamer (4.12-0ubuntu5) to 4.23-0ubuntu2~git20081206
bluez-utils (4.12-0ubuntu5) to 4.23-0ubuntu2~git20081206
libbluetooth3 (4.12-0ubuntu5) to 4.23-0ubuntu2~git20081206
obex-data-server (0.3.4+svn1951-0ubuntu1) to 0.4.3~svn081116-2

Removed the following packages:
bluetooth
bluez
bluez-alsa
bluez-audio
bluez-gstreamer
bluez-utils
gnome-phone-manager

Installed the following packages:
blueman (0.6-r121-0ubuntu3~ppa1i)
bluetooth3 (3.26-0ubuntu14)
bluez3-audio (3.26-0ubuntu14)
bluez3-utils (3.26-0ubuntu14) > this failed, conflict with bluez-compat
dnsmasq (2.45-1ubuntu1)
dnsmasq-base (2.45-1ubuntu1)

1. Removed the following packages:
bluez-compat

2 .Installed the following packages:
bluez3-utils (3.26-0ubuntu14) --> this worked

3. Removed the following packages:
blueman
bluetooth3
bluez-compat
bluez3-audio

4. Installed the following packages:
blueman (0.6-r121-0ubuntu3~ppa1i)
bluetooth3 (3.26-0ubuntu14)
bluez3-audio (3.26-0ubuntu14)
bluez3-utils (3.26-0ubuntu14)

Hope this helps someone

Revision history for this message
herve34fr (hgotty) wrote :

I tried your tip: adding new repositories and I get the message :
Impossible de récupérer http://ppa.launchpad.net/blueman/ubuntu/dists/intrepid/blueman/binary-amd64/Packages.gz 404 Not Found
Impossible de récupérer http://ppa.launchpad.net/blueman/ubuntu/dists/intrepid/blueman/source/Sources.gz 404 Not Found
I have 8.10 64 bits.
It seems that the modification is wrong for 64 bits.

Revision history for this message
chaanakya (chiraag) wrote :

Did you try adding the sources exactly as described above? If you missed the deb or intrepid or main or something, the source will not add correctly. If you are unsure of anything in that line, just copy that line into the "Add a source" dialog box.

Revision history for this message
Ash (ashish-g8) wrote :

i'm on 4.23 ver Bleuz using above repos....
still my built-in bluetooth adapter isn't working.....

@ubuntu:~$ grep blue /var/log/syslog
Dec 5 22:48:58 ubuntu bluetoothd[5254]: bridge pan0 removed
Dec 5 22:48:58 ubuntu bluetoothd[5254]: Stopping SDP server
Dec 5 22:48:58 ubuntu bluetoothd[5254]: Exit
Dec 9 02:35:57 ubuntu bluetoothd[5101]: Bluetooth daemon
Dec 9 02:35:57 ubuntu bluetoothd[5101]: Starting SDP server
Dec 9 02:35:57 ubuntu bluetoothd[5101]: Registered interface org.bluez.Service on path /org/bluez/5101/any
Dec 9 02:35:57 ubuntu bluetoothd[5101]: Starting experimental netlink support
Dec 9 02:35:57 ubuntu bluetoothd[5101]: Failed to find Bluetooth netlink family
Dec 9 02:35:58 ubuntu bluetoothd[5101]: bridge pan0 created
Dec 9 02:36:31 ubuntu x-session-manager[5417]: WARNING: Could not launch application 'blueproximity-autostart.desktop': Unable to start application: Failed to execute child process "blueproximity" (No such file or directory)
Dec 9 02:38:06 ubuntu bluetoothd[5101]: bridge pan0 removed
Dec 9 02:38:06 ubuntu bluetoothd[5101]: Stopping SDP server
Dec 9 02:38:06 ubuntu bluetoothd[5101]: Exit
Dec 9 02:38:15 ubuntu bluetoothd[7128]: Bluetooth daemon
Dec 9 02:38:15 ubuntu bluetoothd[7128]: Starting SDP server
Dec 9 02:38:15 ubuntu bluetoothd[7128]: Registered interface org.bluez.Service on path /org/bluez/7128/any
Dec 9 02:38:15 ubuntu bluetoothd[7128]: Starting experimental netlink support
Dec 9 02:38:15 ubuntu bluetoothd[7128]: Failed to find Bluetooth netlink family
Dec 9 02:38:15 ubuntu bluetoothd[7128]: bridge pan0 created

Can anybody sense somethin.....

Revision history for this message
Ash (ashish-g8) wrote :

in-addition to above dmesg says:-

 37.125353] ACPI: WMI: Mapper loaded
[ 38.039640] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use)
[ 38.106253] apm: BIOS not found.
[ 38.294332] ppdev: user-space parallel port driver
[ 40.142403] Bluetooth: Core ver 2.13
[ 40.142573] NET: Registered protocol family 31
[ 40.142583] Bluetooth: HCI device and connection manager initialized
[ 40.142597] Bluetooth: HCI socket layer initialized
[ 40.167706] Bluetooth: L2CAP ver 2.11
[ 40.167723] Bluetooth: L2CAP socket layer initialized
[ 40.190194] Bluetooth: SCO (Voice Link) ver 0.6
[ 40.190212] Bluetooth: SCO socket layer initialized
[ 40.214391] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 40.214408] Bluetooth: BNEP filters: protocol multicast
[ 40.249694] Bridge firewalling registered
[ 40.251854] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
[ 40.278052] Bluetooth: RFCOMM socket layer initialized
[ 40.278086] Bluetooth: RFCOMM TTY layer initialized
[ 40.278092] Bluetooth: RFCOMM ver 1.10
[ 43.912514] [drm] Initialized drm 1.1.0 20060810
[ 43.919718] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 43.919735] pci 0000:00:02.0: setting latency timer to 64
[ 43.919971] [drm] Initialized i915 1.6.0 20060119 on minor 0
[ 44.429410] sky2 eth0: enabling interface
[ 44.452644] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 44.452806] iwl3945 0000:03:00.0: restoring config space at offset 0x1 (was 0x100002, writing 0x100006)
[ 44.455650] firmware: requesting iwlwifi-3945-1.ucode
[ 44.581738] Registered led device: iwl-phy0:radio
[ 44.581765] Registered led device: iwl-phy0:assoc
[ 44.581830] Registered led device: iwl-phy0:RX
[ 44.581847] Registered led device: iwl-phy0:TX
[ 44.661167] NET: Registered protocol family 17

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

Ash:

Doesn't it sound strange?
Starting EXPERIMENTAL netlink support

with:
Failed to find Bluetooth netlink family

Revision history for this message
nkri (nkri) wrote :

I've had the same problem on a Toshiba Portege M400...same outputs from the logs, etc.

I tried installing Blueman from the above repo, but it didn't do much...it just says that it can't detect the device:
"Can't get device list. Reason: 'module' object has no attribute 'adapter'"

We really need to get this fixed...it's a major problem when something as common as bluetooth doesn't work, especially in an upgrade from a version which worked fine. Are there any developers around who could at least diagnose the problem?

Revision history for this message
kylea (kylea) wrote :

Can you disable the Bluetooth Radio until the PC boots - I get the same error if the Bluetooth radio is active during the boot process?

Its totally repeatable. There are some times function keys - (on laptops) that will toggle switch the radio on and off.

Revision history for this message
nkri (nkri) wrote :

Okay, so after installing Blueman with the older version of Bluez, then the newest version, 4.22, I believe this is a problem with the kernel not loading the bluetooth module properly; we need a kernel developer who can look through the code for bluetooth and hopefully find the problem...anyone know of a good dev who could help?

@kylea-the function keys on my laptop don't do anything in Intrepid, but they worked fine in Hardy. During boot, it says "Loading Bluetooth [OK]" and then proceeds.

Revision history for this message
az (xfjwrtserytsdty-deactivatedaccount) wrote :

Hi everyone.

I'm trying to use a Wiimote. It worked fine on Hardy, but stopped working after a clean install of Intrepid. Now it can still find the Wiimote, but pairing always fails. I'm using a generic "just made in china" dongle. lsusb gives me this:

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

After updating BlueZ to 4.21, the gui wizard behaves slightly different. Instead of acting like the wiimote wasn't there when trying to pair with it (as it did before), it immediately tells me the pairing has failed, and the wiimote stops blinking.

I've tried installing Blueman along with the old BlueZ, but it still won't work.

This seems to be a major problem in Intrepid.
Still no clue about the causes/solutions?

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

Hi mbonci

I have the same problem that you have (I have three wiimotes so I can use them as a giroscope). IMHO bluetooth support in intrepid is really broken. Two machines with intrepid, it doesn't work, it worked when it had Hardy(and former ubuntu versions).

I had tried everything I could, installing Blueman, updating BlueZ, removing them and compiling from source...

Usually you find a lot of help with solving problems in linux looking at mail lists, now you see a lot of people with this problem, but no solutions.

It would be great that the people that modified Hardy for Intrepid could give the people clues about what could be the problem. The more eyes that look at it the better options to solve the problem.

Revision history for this message
az (xfjwrtserytsdty-deactivatedaccount) wrote :

Hi José,

I just gave it up and downgraded to kernel 2.6.24 manually, now it all works fine. Works perfect, but it's definitely not a good solution.

After all, it doesn't seem to be exactly about Intrepid, but actually about the kernel itself (as nkri has already pointed out). So how do we make sure this problem won't pass unnoticed by kernel developers?

Revision history for this message
nkri (nkri) wrote :

mbonci-
    May I ask where you got the old kernel? I've seen more than one person say that old kernels work fine, so this may be the way to go until the bug gets fixed.

Thanks!
-nkri

PS: to make sure this gets noticed, maybe we should assign it to someone who is or knows a kernel developer? That way, someone would start taking the steps to really fixing it:)

Revision history for this message
az (xfjwrtserytsdty-deactivatedaccount) wrote :

nkri:

I just got the debs from the Hardy repository.
It's so obvious that it's even surprising - but it works! :)

I used this search as a starting point (linux-386, in my case):
http://packages.ubuntu.com/search?suite=hardy-updates&arch=any&searchon=names&keywords=linux
And then I just downloaded its dependencies (and their dependencies and so on). I don't know which debs are really needed, but this was the full list I had in the end:

linux-386_2.6.24.22.24_i386.deb
linux-image-2.6.24-22-386_2.6.24-22.45_i386.deb
linux-image-386_2.6.24.22.24_i386.deb
linux-restricted-modules-2.6.24-22-386_2.6.24.14-22.53_i386.deb
linux-restricted-modules-386_2.6.24.22.24_i386.deb
linux-restricted-modules-common_2.6.24.14-22.53_all.deb
linux-ubuntu-modules-2.6.24-22-386_2.6.24-22.35_i386.deb
module-init-tools_3.3-pre11-4ubuntu5.8.04.1_i386.deb
nvidia-kernel-common_20051028+1ubuntu8_all.deb

Just run the debs in the right order (dependencies first) and voilà! :)

Don't forget that your newly installed kernel won't be the default option, so you'll have to choose it manually at boot time, or edit /boot/grub/menu.lst.
(Or just uninstall the default kernel using synaptic - that's what I did).

In case you too have an eee, grab your kernel debs here:
http://www.array.org/ubuntu/dists/hardy/eeepc/binary-i386/

Good luck!

(But again... How/where do we talk to kernel developers? I really don't know. I'm new here.)

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

mbonci, nkri: mmmmm, very interesting!

I will do a diff between the kernels in bluetooth area and see if I could find something useful. I'm not an expert but better than nothing is anything.

Revision history for this message
Ash (ashish-g8) wrote :

I'll like to update on it:- i bought cheap chinese bluetooth adapter, n guess what , it was instantaneously recognized and it even searched my headset and get paired with it (using blueman) BUT i was unable to use them and I've nothing else to test it....

Revision history for this message
earthmeLon (earthmelon) wrote :

I am having trouble getting my bluetooth device working.

I am using an HP Pavillion DV9000

dmesg | grep Bluetooth
[ 27.685501] Bluetooth: Core ver 2.13
[ 27.686022] Bluetooth: HCI device and connection manager initialized
[ 27.686029] Bluetooth: HCI socket layer initialized
[ 27.717324] Bluetooth: L2CAP ver 2.11
[ 27.717334] Bluetooth: L2CAP socket layer initialized
[ 27.736989] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 27.737008] Bluetooth: BNEP filters: protocol multicast
[ 27.788186] Bluetooth: SCO (Voice Link) ver 0.6
[ 27.788196] Bluetooth: SCO socket layer initialized
[ 27.807803] Bluetooth: RFCOMM socket layer initialized
[ 27.810179] Bluetooth: RFCOMM TTY layer initialized
[ 27.810191] Bluetooth: RFCOMM ver 1.10

 hcitool dev
Devices:

Hope this gets resolved sometime soon :D

Revision history for this message
Ben King (black-rider-web) wrote :

Hi, I'm using a Thinkpad T61 with integrated Bluetooth and I'm having the same problems. I'm using ubuntu my kernel-version: 2.6.27.2

dmesg | grep Bluetooth
[ 242.830909] Bluetooth: Core ver 2.13
[ 242.832975] Bluetooth: HCI device and connection manager initialized
[ 242.832982] Bluetooth: HCI socket layer initialized
[ 242.911578] Bluetooth: L2CAP ver 2.11
[ 242.911596] Bluetooth: L2CAP socket layer initialized
[ 242.943613] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 242.943626] Bluetooth: BNEP filters: protocol multicast
[ 243.075099] Bluetooth: RFCOMM socket layer initialized
[ 243.077202] Bluetooth: RFCOMM TTY layer initialized
[ 243.077217] Bluetooth: RFCOMM ver 1.10
[ 243.126925] Bluetooth: SCO (Voice Link) ver 0.6
[ 243.126940] Bluetooth: SCO socket layer initialized

hcitool dev
Devices:

nothing helped till know. Hope somebody can resolved this soon.

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

Bug 291051: Meist3r shows us a trick that makes the wiimote bluethooth works on intrepid:

https://bugs.launchpad.net/ubuntu/+bug/291051

This is very important, because it makes the general bluethooth bug easily traceable.

Revision history for this message
afriseun (carel-kenweb) wrote :

Same problem here as described in initial bug description.

Bluetooth were working fine with Hardy, no Bluetooth after fresh install of Intrepid - NEC Versa 7200 laptop.

Revision history for this message
IUnknown (sasha-kpi) wrote :

I've just installed Ubuntu 9.04 beta1. Bluetooth still doesn't work for me :(

tags: added: jaunty
Revision history for this message
Miroslav Ďurian (aasami) wrote :

SOLVED

Open a terminal and issue:

hcitool dev
sudo hciconfig <hci0> reset
hcitool scan
sudo hcitool cc <MACaddres>

On my machine it looks like this:

aas@acutake:~$ hcitool dev
Devices:
 hci0 00:0A:3A:88:3A:0E
aas@acutake:~$ sudo hciconfig hci0 reset
aas@acutake:~$ hcitool scan
Scanning ...
 00:0F:DE:87:9F:EA Aas-P910i
aas@acutake:~$ sudo hcitool cc 00:0F:DE:87:9F:EA
aas@acutake:~$

Then you simply add new bluetooth device via bluetooth aplet on the panel.
The device should be discovered now. A least, it worked for me. :-)
Enjoy!

Revision history for this message
IUnknown (sasha-kpi) wrote :

Miroslav Ďurian, what laptop model do you have? Your method doesn't work for me too :(
My system doesn't see bluetooth adapter. hcitool dev shows nothing:

# sasha@sasha-laptop:~$ hcitool dev
Devices:

# sasha@sasha-laptop:~$ sudo hciconfig hci0 reset
Can't get device info: No such device

Very strange, because laptop has bluetooth adapter.

sasha@sasha-laptop:~$ dmesg | grep Bluetooth
[ 1.100011] Bluetooth: Core ver 2.13
[ 1.104015] Bluetooth: HCI device and connection manager initialized
[ 1.104018] Bluetooth: HCI socket layer initialized
[ 5.566907] Bluetooth: L2CAP ver 2.11
[ 5.566908] Bluetooth: L2CAP socket layer initialized
[ 5.566911] Bluetooth: SCO (Voice Link) ver 0.6
[ 5.566912] Bluetooth: SCO socket layer initialized
[ 5.566966] Bluetooth: RFCOMM socket layer initialized
[ 5.566973] Bluetooth: RFCOMM TTY layer initialized
[ 5.566974] Bluetooth: RFCOMM ver 1.10
[ 20.082986] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 20.082989] Bluetooth: BNEP filters: protocol multicast

So, Ubuntu 9.04 beta1 with latest updates can't see adapter too.

Revision history for this message
IUnknown (sasha-kpi) wrote :

When I am trying to restart bluetooth:
root@sasha-laptop:~# /etc/init.d/bluetooth restart
 * Stopping bluetooth [ OK ]
 * Starting bluetooth [ OK ]

I have these in my logs:
Apr 6 23:41:27 sasha-laptop bluetoothd[2670]: bridge pan0 removed
Apr 6 23:41:27 sasha-laptop bluetoothd[2670]: Stopping SDP server
Apr 6 23:41:27 sasha-laptop bluetoothd[2670]: Exit
Apr 6 23:41:27 sasha-laptop bluetoothd[5233]: Bluetooth daemon
Apr 6 23:41:27 sasha-laptop bluetoothd[5233]: Starting SDP server
Apr 6 23:41:27 sasha-laptop bluetoothd[5233]: Starting experimental netlink support
Apr 6 23:41:27 sasha-laptop bluetoothd[5233]: Failed to find Bluetooth netlink family
Apr 6 23:41:27 sasha-laptop bluetoothd[5233]: bridge pan0 created
Apr 6 23:41:27 sasha-laptop bluetoothd[5233]: Registered interface org.bluez.Service on path /org/bluez/5233/any

Revision history for this message
Jose Hevia (jose-francisco-hevia) wrote :

Hello everybody!!

Thanks to the ubuntu people I know what is my specific problem. The usb dongles I use don't work because they changed the drivers in the linux kernel.

Typing "lsusb" in the terminal, you will see if it is that the problem, here is mine:

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

As you can see, KY-BT100 doesn't work well, here is the blacklist if you want to compare with yours:

https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/268502?comments=all

Revision history for this message
Dread Knight (dread.knight) wrote :

Not working for me as well on Toshiba Portege M400 (tablet pc).

I bought bt audio headset and I can't use it, so not cool...

Changed in bluez-utils (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
bobnogueira (bobnogueira) wrote :

Same problem in acer 5720 on Ubuntu 9.04

roberto@roberto-laptop:~$ lsusb
Bus 002 Device 002: ID 5986:0102 Acer, Inc Crystal Eye webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 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 15d9:0a37
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Revision history for this message
levicivita (tullio-levi-civita) wrote :

This problem still exists on Mythbuntu 9.10:

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION="Ubuntu 9.10"

seanbw (seanbw)
tags: added: karmic
Revision history for this message
seanbw (seanbw) wrote :

I am on Ubuntu Karmic using Acer Laptop Aspire 5720.
The inbuilt bluetooth button is dead, there is no bluetooth/deafult file and although blueZ and bluetooth Manager have been installed via Synaptic, boot up does not load blueZ resulting in Bluettoth Manager reporting that : Bluez daemon is not running, blueman-manager cannot continue.
grep gives me:
root@acer-laptop:/home/seanbw# dmesg | grep 'Bluetooth'
[ 0.284010] Bluetooth: Core ver 2.15
[ 0.284018] Bluetooth: HCI device and connection manager initialized
[ 0.284022] Bluetooth: HCI socket layer initialized
[ 1.237941] Bluetooth: L2CAP ver 2.13
[ 1.237943] Bluetooth: L2CAP socket layer initialized
[ 1.237947] Bluetooth: SCO (Voice Link) ver 0.6
[ 1.237949] Bluetooth: SCO socket layer initialized
[ 1.237999] Bluetooth: RFCOMM TTY layer initialized
[ 1.238003] Bluetooth: RFCOMM socket layer initialized
[ 1.238005] Bluetooth: RFCOMM ver 1.11

hcitool dev gives nothing as follows:
root@acer-laptop:/home/seanbw# hcitool dev
Devices:
sudo /etc/init.d/bluetooth start results in: nothing whilst status just states:
root@acer-laptop:/home/seanbw# sudo /etc/init.d/bluetooth start
root@acer-laptop:/home/seanbw# sudo /etc/init.d/bluetooth status
 * bluetooth is not running
Finally in an attempt to put bluetooth in services that start at bootup, I did the following:
sudo update-rc.d -f bluetooth enable S and got:
root@acer-laptop:/home/seanbw# sudo update-rc.d -f bluetooth enable S
update-rc.d: warning: bluetooth start runlevel arguments (none) do not match LSB Default-Start values (2 3 4 5)
update-rc.d: warning: bluetooth stop runlevel arguments (none) do not match LSB Default-Stop values (0 1 6)
 Enabling system startup links for /etc/init.d/bluetooth ...
 Removing any system startup links for /etc/init.d/bluetooth ...
   /etc/rc0.d/K74bluetooth
   /etc/rc1.d/K74bluetooth
   /etc/rc2.d/S25bluetooth
   /etc/rc3.d/S25bluetooth
   /etc/rc4.d/S25bluetooth
   /etc/rc5.d/S25bluetooth
   /etc/rc6.d/K74bluetooth
 Adding system startup for /etc/init.d/bluetooth ...
   /etc/rc0.d/K74bluetooth -> ../init.d/bluetooth
   /etc/rc1.d/K74bluetooth -> ../init.d/bluetooth
   /etc/rc6.d/K74bluetooth -> ../init.d/bluetooth
   /etc/rc2.d/S25bluetooth -> ../init.d/bluetooth
   /etc/rc3.d/S25bluetooth -> ../init.d/bluetooth
   /etc/rc4.d/S25bluetooth -> ../init.d/bluetooth
   /etc/rc5.d/S25bluetooth -> ../init.d/bluetooth
After which a status enquiry still gave me:
root@acer-laptop:/home/seanbw# sudo /etc/init.d/bluetooth status
 * bluetooth is not running

Rumen Staykov (rstaykov)
Changed in bluez-utils (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
zid1988 (zid1988) wrote :

Im having the same problem with bluetooh on my HP 630 Notebook PC.
Im using Ubuntu 10.10 with kernel version- 2.6.35-31-generic

and, this the output of ..... dmesg | grep Bluetooth

[ 13.604408] Bluetooth: Core ver 2.15
[ 13.604425] Bluetooth: HCI device and connection manager initialized
[ 13.604439] Bluetooth: HCI socket layer initialized
[ 13.648692] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 15.046873] Bluetooth: L2CAP ver 2.14
[ 15.046876] Bluetooth: L2CAP socket layer initialized
[ 15.051712] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 15.051715] Bluetooth: BNEP filters: protocol multicast
[ 15.057243] Bluetooth: SCO (Voice Link) ver 0.6
[ 15.057246] Bluetooth: SCO socket layer initialized
[25298.953987] Bluetooth: RFCOMM TTY layer initialized
[25298.953993] Bluetooth: RFCOMM socket layer initialized
[25298.953995] Bluetooth: RFCOMM ver 1.11

Kindly fix it soon, Thanks :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.