I cannot get the bluetooth daemon on my laptop to start - it is not running by default and running
does nothing.

Running Ubuntu 9.10 64bit on a Sager NP8662 laptop. Suggestions?

~Jeff

Look at 'dmesg' after you started the machine to see if the kernel recognizes the internal Bluetooth chipset, then check if all related kernel modules got loaded, then check Syslog after you started the service. If there's any error messages post them here in full and preferably in BB code tags.

It does in fact appear to be loading the bluetooth with out error. dmesg output

The syslog also does not report any bluetooth failure (it reports the gnome bluetooth does not start however blueman is starting just fine)

Suggestions/ideas?

Regards,
~Jeff

IIGC the Sager NP8662 basically is a Clevo, the M860ETU (review: http://www.notebookforums.com/thread228495.html). It's got an Intel PM45 chipset (http://www.intel.com/Products/Notebo...ldocuments.htm). On a laptop with an equivalent chipset (Dell Latitude E6400 / E6500) http://www.gentoo-wiki.info/Dell_Latitude_E6400_/_E6500 says Bluetooth should be working with hci_usb but you need to switch the bluetooth-device with 'hid2hci'. http://en.gentoo-wiki.com/wiki/Dell_Latitude_E6x00 however says Bluetooth requires hci_usb for kernel < 2.6.27 and btusb for kernel >= 2.6.27 and your dmesg says you're running a 2.6.31 kernel. If checking and changing modules doesn't work for you I suggest you check the http://www.linuxquestions.org/hcl/ (maybe there's something there) and post full specs (hwinfo, lshw, etc) in the hope somebody can add pointers. That's about all the suggestions I have right now...

Jump back a step - is this a case of not detecting the hardware or not starting the daemon?

On my laptop the BT appears on the USB bus thus:
lsusb
...
Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Is yours seen anywhere at all with lsusb / lspci commands? Do you physically need to turn it on with a FN key combo or switch?

Regarding the daemon - are you sure it's not running? If you issue 'ps aux | grep blue' you don't see and entry for: bluetoothd ?

ps aux | grep blue
user 7615 0.0 0.1 14728 5820 ? S 10:47 0:00 bluetooth-applet
root 13596 0.0 0.0 3488 1536 ? Ss 12:35 0:00 /usr/sbin/bluetoothd
root 13604 0.0 0.0 3240 788 pts/2 R+ 12:35 0:00 grep blue

Does init.d give any messages like:
* Stoppin bluetooth
* Starting bluetooth
?

Does running this do anything:
'hcitool scan'

There were some major issues with BT on Ubuntu 8.10 - but they are alleged to have been fixed - but I've always found Ubuntu 8+ -v- Bluetooth to be a bit of a bitch.

1 members found this post helpful.