Bluetooth Dongle No Longer Active [Solved]

[Martin Goose]

I have been successfully using Bluetooth dongles with PCLOS for some time. Recently the dongle on my Acer Ultrabook no longer started up (flashing) when booting, although one continues to work on my desktop PC. Both are running fully updated PCLOS KDE. Kernel 3.2.18-pclos2.bfs.

The Control Centre - Browse and Configure Hardware identifies the dongle correctly as follows:

Identification
Vendor: ‎Cambridge Silicon Radio, Ltd
Description: ‎Bluetooth Dongle (HCI mode)
Media class: ‎Wireless|Radio Frequency|Bluetooth

Connection
Bus: ‎USB
Bus PCI #: ‎2
PCI device #: ‎3
Vendor ID: ‎0x0a12
Device ID: ‎0x0001

Misc
Module: ‎hci_usb

The KDE 'Configure Your Desktop' Bluetooth item reports:
"No Bluetooth adapters have been found"

Should the output of 'lsmod' list hci_usb somewhere?

Booting a live USB of the latest PCLOS does not bring the dongle to life. Booting a live USB of 'another popular distro' finds and activates the dongle thus proving the hardware.

Any suggestions, please, as to what I should try next?

[Just17]

have a look at the dmesg output after inserting the dongle ......  there might be some indication there ....

[zerocool]

The PCLOS team has recently updated many bluetooth and pulse audio files.
After these updates I lost my bluetooth connection to my headset (Motorola S10).
The first time I installed gnome bluetooh manager and that fixed the connection.
The next time, I had to uninstall pulse audio, reboot, reinstall pulse audio,
activate it in PCC, reboot, and everything works again...

Not very scientific (just guesses) but it worked.

 

[Martin Goose]

have a look at the dmesg output after inserting the dongle ......  there might be some indication there ....

Last few lines before inserting dongle

wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
usb 1-1.4: USB disconnect, device number 3
usbcore: registered new interface driver snd-usb-audio
wlan0: no IPv6 routers present

additional lines after inserting dongle

usb 2-1.2: new full-speed USB device number 4 using ehci_hcd
usb 2-1.2: New USB device found, idVendor=0a12, idProduct=0001
usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0

This is consistent with the Control Centre output after detecting the hardware.

Unless there are further ideas I may have to try zerocool's suggestion.

[coffeetime]

You can also try:
As su

Code: [Select]

bluetoothd -u
Reboot...

[Martin Goose]

You can also try:
As su

Code: [Select]

bluetoothd -u
Reboot...

Thanks for the suggestion. Tried it. No luck.

[coffeetime]

Please post back lsusb, lspci -vv and lsmod

[ff103]

Well I don't know if this was karma or what, but I just tried to connect my wife's tablet to transfer a photo a couple of hours ago and couldn't get my blue tooth dongle to work either. I just forgot about it and emailed the photo. After supper I decided to check out the forum and read the posts since my last visit like I always do and what do I see as the second post? This thread about a blue tooth dongle not working. After trying all the lsmod and lspci and dmesg, I try the "bluetoothd -u" and the blue tooth icon pops up in the task bar. Is this a great forum or what !! you guys are the best. Thanks for your suggestion coffeetime.

[nixus]

coffeetimes suggestion did the trick for me.

thanks,
nixus

[Martin Goose]

Please post back lsusb, lspci -vv and lsmod

Update from Desktop PC

1. Found that it was not up-to-date (only megagames repository selected) so updated with synaptic. Bluetooth died.

2. Tried bluetoothd -u <reboot>. No change

3. Removed Pulseaudio using task-pulse-audio-remove <reboot> and then reinstalled all bluetooth packages listed in synaptic. Reboot. No change.

4. Then tried bluetoothd -u <reboot>. Bluetooth returned.

I still have working sound so leaving pulseaudio to one side for now!

PS the updates that killed Bluetooth included:

libpulseaudio0 (2.0-1pclos2012) to 3.0-1pclos2013
libpulseglib20 (2.0-1pclos2012) to 3.0-1pclos2013

Perhaps these are causing the problem.

Update from Laptop PC

1. Removed Pulseaudio using task-pulse-audio-remove <reboot>

2. Then tried bluetoothd -u <reboot>. Bluetooth returned.

For both PCs a reboot kills Bluetooth again, but now bluetoothd -u brings it back without a reboot. Does this mean that bluetoothd -u now needs to be executed at each boot? If so to which startup file should it be appended?

PS for Coffeetime: I still have the output from lsusb, lspci -vv and lsmod before the fix if that would help for diagnostic purposes.

[Just17]

For both PCs a reboot kills Bluetooth again, but now bluetoothd -u brings it back without a reboot. Does this mean that bluetoothd -u now needs to be executed at each boot? If so to which startup file should it be appended?

http://www.pclinuxos.com/forum/index.php/topic,79157.msg653604.html#msg653604

[Martin Goose]

http://www.pclinuxos.com/forum/index.php/topic,79157.msg653604.html#msg653604

Thanks.  Is this a work-around or should there be a service or daemon in the list that you see in the PCLOS Control Centre after Bluetooth is installed?

[Just17]

For whatever reason bluetoothd does not appear to be launching automatically in your case, so this is the fix to get it launched during boot.

[Martin Goose]

For whatever reason bluetoothd does not appear to be launching automatically in your case, so this is the fix to get it launched during boot.

OK, that's fine. I will mark the thread as 'Solved'.