[Solved] Toshiba Satellite L550: bluetooth not working

ReaphSharc · 2009-12-01 08:59:44

Bluetooth on my Toshiba Satellite L550 does not seem to be working. I went through the wiki page on bluetooth, but could not get it to work, but also have noticed some errors. I've installed blueman, at boot bluetoothd is started and when I start XCFE4, I autostart blueman-applet. Is there supposed to be a tray-icon when using the applet by the way, because I'm not seeing one on my desktop).
I have tried to figure out what bluetooth hardware is in my laptop, but I've noticed nothing that looked like a bluetooth device with lspci en lsusb.
Syslog:

Dec  1 10:32:33 archy bluetoothd[2080]: Bluetooth daemon 4.58
Dec  1 10:32:33 archy kernel: Bluetooth: Core ver 2.15
Dec  1 10:32:33 archy kernel: Bluetooth: HCI device and connection manager initialized
Dec  1 10:32:33 archy kernel: Bluetooth: HCI socket layer initialized
Dec  1 10:32:33 archy kernel: Bluetooth: L2CAP ver 2.13
Dec  1 10:32:33 archy kernel: Bluetooth: L2CAP socket layer initialized
Dec  1 10:32:33 archy bluetoothd[2080]: Failed to find Bluetooth netlink family
Dec  1 10:32:33 archy kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Dec  1 10:32:33 archy kernel: Bluetooth: SCO (Voice Link) ver 0.6
Dec  1 10:32:33 archy kernel: Bluetooth: SCO socket layer initialized
Dec  1 10:33:13 archy kernel: Bluetooth: RFCOMM TTY layer initialized
Dec  1 10:33:13 archy kernel: Bluetooth: RFCOMM socket layer initialized
Dec  1 10:33:13 archy kernel: Bluetooth: RFCOMM ver 1.11

Dmesg:

Bluetooth: Core ver 2.15
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.13
Bluetooth: L2CAP socket layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11

Now, when I start blueman...

$ blueman-manager 
Loading configuration plugins
_________
<module> (/usr/lib/python2.6/site-packages/blueman/main/Config.py:20)
Skipping plugin Gconf
No module named gconf 
_________

menu options Adapter and Device are greyed out (and can't be clicked on) and so are all the icons.

If i start bluez-simple-agent:

$ bluez-simple-agent
Traceback (most recent call last):
  File "/usr/bin/bluez-simple-agent", line 90, in <module>
    path = manager.DefaultAdapter()
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter

And...

$ hciconfig dev
Can't get device info: No such device

I'm probably missing something here, so any help will truly be appreciated...

Last edited by ReaphSharc (2009-12-05 07:37:10)

MadCat_X · 2009-12-01 20:08:17

Maybe should take a look at omnibook-svn package in AUR. It provides a module which can do few tricks with notebooks that use certain hardware. Once you get it working, you can enable bluetooth radio by following command.

echo 1 > /proc/omnibook/bluetooth

BTW, I had to specify "ectype" parameter for the omnibook module manually, but that's how I got BT working on my Qosmio X300...

ReaphSharc · 2009-12-03 07:29:15

No Bluetooth file shows up in /proc/omnibook, but I haven't been able to load the module with parameters either.
(tried insmod <module> <parameter> syntax).

MadCat_X · 2009-12-03 10:59:44

I use

modprobe omnibook ectype=12 userset=1

to load mine. Maybe you could play around with the ectype value to see which one gives you the correct behaviour. I think the allowed values are from 0 to 13, though I'm not sure.

Last edited by MadCat_X (2009-12-03 11:01:14)

ReaphSharc · 2009-12-04 09:43:51

Awesome, thanks!
Unloaded the omnibook module and loaded it with those settings and BAM:

Dec  4 10:32:04 archy kernel: Bluetooth: Generic Bluetooth USB driver ver 0.5
Dec  4 10:32:04 archy kernel: usbcore: registered new interface driver btusb
Dec  4 10:32:04 archy bluetoothd[2093]: HCI dev 0 registered
Dec  4 10:32:04 archy bluetoothd[2093]: HCI dev 0 up
Dec  4 10:32:04 archy bluetoothd[2093]: Starting security manager 0
Dec  4 10:32:04 archy bluetoothd[2093]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Dec  4 10:32:04 archy bluetoothd[2093]: Adapter /org/bluez/2093/hci0 has been enabled
Dec  4 10:32:04 archy kernel: omnibook: get_wireless raw_state: 1f
Dec  4 10:32:04 archy kernel: omnibook: Begin table match of throttling feature.
Dec  4 10:32:04 archy kernel: omnibook: ACPI backend has already been initialized
Dec  4 10:32:04 archy kernel: omnibook: Returning table entry nr 0.
Dec  4 10:32:04 archy kernel: omnibook: Enabled features: ac battery blank bluetooth display dmi version lcd temperature wifi throttling.

I also suddenly noticed the appearance of a Bluetooth icon on my desktop (the applet came to life).

So I executed

echo "omnibook ectype=12 userset=1" > /etc/modprobe.d/bluetooth.conf

and removed the omnibook module from /etc/rc.conf.... but that did not work. At least, that did not make my kernel load up this module with these settings at boot.
If I load them manually, Bluetooth works and I can easily exchange files with my LG phone.

Only thing to solve now is how to make Arch load the module with the proper settings at boot, but I'm sure I'm only doing something very small wrong, and it is probably easily solvable.

Thanks for the help MadCat_X! You wouldn't happen to know how to load that module with those settings at boot, now do you?

Last edited by ReaphSharc (2009-12-04 10:21:38)

MadCat_X · 2009-12-04 15:49:55

I use a script to load the module and enable the BT on boot

#!/bin/bash

. /etc/rc.conf
. /etc/rc.d/functions
case "$1" in
  start)
    stat_busy "Starting omnibook module"
    modprobe omnibook ectype=12 userset=1
    sleep 2
    echo 1 > /proc/omnibook/bluetooth    
    stat_done
    ;;
  stop)
    stat_busy "Stopping omnibook module"
    echo 0 >/proc/omnibook/bluetooth
    rmmod omnibook
    stat_done
    ;;
  restart)
    $0 stop
    sleep 1
    $0 start
    ;;
  *)
    echo "usage: $0 {start|stop|restart}"
esac
exit 0

The "sleep 2" has proven to be necessary to enable BT right after loading the omnibook module (it probably takes some time to initialize the module), but it might not be necessary on your notebook. I have this script saved as"omnibook" in "/etc/rc.d/" and after adding "omnibook" entry to DAEMONS section in rc.conf I have BT up and running when my system finishes booting. Note that you have to add "omnibook" before "bluetooth" daemon in rc.conf. Not a really crystal clean solution, but it works like a charm:)

EDIT:
Now when I think about it, adding "omnibook" to MODULES in rc.conf and having

options omnibook ectype=12 userset=1

in modprobe.conf is a much cleaner solution and it works as well...

Last edited by MadCat_X (2009-12-04 16:41:01)

ReaphSharc · 2009-12-05 07:34:55

MadCat_X wrote:

EDIT:
Now when I think about it, adding "omnibook" to MODULES in rc.conf and having
options omnibook ectype=12 userset=1
in modprobe.conf is a much cleaner solution and it works as well...

"options"... I knew I was forgetting something silly.

Turns out we've helped each other out with this issue, haven't we?
I love the Linux community

Arch Linux

#1 2009-12-01 08:59:44

[Solved] Toshiba Satellite L550: bluetooth not working

#2 2009-12-01 20:08:17

Re: [Solved] Toshiba Satellite L550: bluetooth not working

#3 2009-12-03 07:29:15

Re: [Solved] Toshiba Satellite L550: bluetooth not working

#4 2009-12-03 10:59:44

Re: [Solved] Toshiba Satellite L550: bluetooth not working

#5 2009-12-04 09:43:51

Re: [Solved] Toshiba Satellite L550: bluetooth not working

#6 2009-12-04 15:49:55

Re: [Solved] Toshiba Satellite L550: bluetooth not working

#7 2009-12-05 07:34:55

Re: [Solved] Toshiba Satellite L550: bluetooth not working

Board footer