Comment 344 for bug 268502

Revision history for this message
In , Marius (marius-redhat-bugs) wrote :

Hi, All

Here is my config (I have Debian Squeeze installed on a Dell D630):

$ uname -a
Linux mrneagu-ro 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux
cat /etc/debian_version
6.0.1

'hciconfig hci0' gave me null BT address (00:00:00:00:00:00) and I also could not bring up the Bluetooth module:

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

lsusb gave me someting like this:
Bus 002 Device 002: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth

My problem occurred when I started VMWare which stole the Bluetooth adapter (usb.autoConnect.device0 = "" and even if usb.generic.autoconnect = "FALSE" it stole my Bluetooth). Then the kernel (on the host) crashed and Gnome asked me to send a report to kernel.org.

As this happened really often, I usually had to reboot to solve the problem, so I was searching for a way to reset the Bluetooth module in place and restart Bluetooth services. I found this post: http://marc.info/?l=linux-usb&m=121459435621262&w=2 to reset the any usb device.

$ sudo usbreset /dev/bus/usb/002/002

After this, every restart would not resolve the problem. Address of the module still null and "Can't init device hci0: Connection timed out (110)". The Bluetooth icon in the upper-right corner of the screen had always a red x-mark on it.

Additionally the Bluetoth module changed from bus 2 to bus 3:
Bus 003 Device 002: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth

Now, I resolved the problem according to this forum: http://ubuntuforums.org/showpost.php?p=8306034&postcount=4 :

I restarted in Windows and used the Bluetooth mouse there and then rebooted back in Debian and it came back by itself. So it seems that Windows somehow knows how to reset the Bluetooth module and Linux doesn't. I don't know if it's a kernel or bluez bug, but I hope this gets resolved because it is very annoying.

Thank you.
Kind Regards.