Bluetooth bug in TC-13.1

[AlejandroPadrino]

Hello,

I'm trying to load bluetooth software to link TC 13.1 with bluetooth devices.  Blueman.tcz fails to download startup-notification.tcz file.  What to do now?

Could be possible to load bluetooth and blueman with no *-gir.tcz extensions?

Thank you.  :-)

[Juanito]

There was an error in the blueman dep file, it should have read libstartup-notification - fixed now.

The blueman app needs the *gir extensions.

[AlejandroPadrino]

After downloaded updated Bluetooth, it can not start.  Error shows me Can not connect to BlueZ manager, BlueZ daemon is not loaded.  The bluetooth device is ath9k, dmesg shows calltrace error to device.  After running sudo depmod ath9k the device appears to be loaded, but shows same error: BlueZ daemon is not loaded.  The bluetooth device runs using other Linux distro.

[Paul_123]

What are the error messages

[AlejandroPadrino]

Can not connect to BlueZ manager, BlueZ daemon is not loaded.

[Paul_123]

You know it does not start automatically, right?  What happens when you try to load Bluetoothd?   There is an init.d script that will also start dbus if needed.

[AlejandroPadrino]

sudo dbus    ; appears to run.
sudo bluez start    ; appears to run.

but blueman-manager remains with error.  :-(

sudo bluetoothd -n    ; bluetoothd[4280]: src/adapter.c:adapter_init() Failed to access management interface.

:-(

[Paul_123]

You will have to research your adapter function in linux.  Does it need firmware?

[AlejandroPadrino]

yes, Atheros (ath9k) firmware loaded before loading bluez5.tcz & blueman.tcz

[Juanito]

Check the dbus and bluez daemons are running with:

Code: [Select]

/usr/local/etc/init.d/dbus status
/usr/local/etc/init.d/bluez status
..start the bluetooth daemon with:

Code: [Select]

sudo bluetoothd -nd
..start blueman in a separate terminal window with:

Code: [Select]

blueman-manager
..and look for error messages.

[AlejandroPadrino]

dbus service started.
bluez service NOT STARTED after bluez start, runned with and without sudo.

bluetoothd daemon (bluetoothd -nd): 
bluetoothd[3744]: src/adapter.c:adapter_init() Failed to access management interface.
bluetoothd[3744]: src/main.c:main() Adapter handling initialization failed.

:-(

[Paul_123]

Figure out why your adapter is not being recognized by the kernel.

I would guess that the driver is not really loaded, or there is missing firmware.  You need to look at dmesg.

[Juanito]

This is for intel hardware on Core-14.x, but you should see something analogous to this:

Code: [Select]

dmesg
...
Bluetooth: Core ver 2.22
NET: Registered PF_BLUETOOTH protocol family
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
usbcore: registered new interface driver btusb
Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 2 week 3 2013
bluetooth hci0: Direct firmware load for intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq failed with error -2
bluetooth hci0: Falling back to sysfs fallback for: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Bluetooth: hci0: Intel BT fw patch 0x37 completed & activated
Note the kernel initially tries to load firmware from the driver and then falls back to loading it from /usr/local/lib/firmware

[Juanito]

..and blueman works - although it sometimes does not start first time.