Hi, this bluetooth config was working just fine until I installed bluez-libs 3.1-1 and bluez-utils-3.1-2.
I have a Kensington usb dongle type bluetooth adapter and its seen as:
Bus 002 Device 002: ID 0db0:697a Micro Star International
When I attempt to connect, I get:
Aug 21 09:28:02 lapzilla hcid: Bluetooth HCI daemon
Aug 21 09:28:02 lapzilla hcid: Register path:/org/bluez fallback:1
Aug 21 09:28:02 lapzilla hcid: Device hci0 has been added
Aug 21 09:28:02 lapzilla sdpd: Bluetooth SDP daemon
Aug 21 09:28:02 lapzilla hidd: Bluetooth HID daemon
Aug 21 09:28:02 lapzilla hcid: Can't write inquiry mode for hci0: Input/output error (5)
Aug 21 09:28:02 lapzilla hcid: Register path:/org/bluez/hci0 fallback:0
I tried doing some searching for this problem but can't find any references.
Any help is much appreciated.
The dbus daemon has to be started before bluetooth, it is required bei hcid.
EDIT: oops, seems you have it started already, so there is something else going on.
Well, the problems with the new versions of bluez-utils and bluez-libs have been discussed a couple of times in the forums, although a clear diagnosis is still missing. I was willing to post a bug concerning the issue, but I am really unable to identify the source of the problem so to produce a useful bug report.
I am actually anle to solve the problems you describe avoiding to launch the bluettoth service at boot. I launch dbus and bluetooth by hand and all goes smoothly. Otherwise I need to give a
hciconfig hci0 reset
Please also not that the pairing system and pin exchange method is changed: you need to define your pin directly in /etc/bluetooth/hcid.conf, without resorting anymore to a pin helper.
Mortuus in anima, curam gero cutis