Re: [Bluez-users] Totally confused

Rui Pedro Lopes
2006-08-16T08:18:28Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

redondos wrote:
> Have you tried following the Gentoo wiki? You're probably not using
> Gentoo, but they are well-known for providing pretty good documentation
> to the open source community.
>
> http://www.gentoo-wiki.com/HOWTO_use_a_bluetooth_headset
Yap. Actually, I'm using debian...
>
> About the PIN code: have you configured a pin helper correctly in
> hcid.conf? It's pretty simple, you can just write a shell script:
>
> #!/bin/sh
> echo "PIN:1234
>
> Make it executable, then edit hcid.conf with the line:
>
> pin_helper /path/to/the/script
Yes, I have tried that. Here is the syslog messages:

Aug 16 09:13:20 tash hcid[7714]: Bluetooth HCI daemon
Aug 16 09:13:20 tash hcid[7714]: Unknown option 'pin_helper' line 27
Aug 16 09:13:20 tash hcid[7714]: syntax error line 27
Aug 16 09:13:20 tash sdpd[7716]: Bluetooth SDP daemon
Aug 16 09:13:20 tash hidd[7718]: Bluetooth HID daemon
Aug 16 09:13:20 tash hcid[7714]: Register path:/org/bluez fallback:1
Aug 16 09:13:20 tash hcid[7714]: Device hci0 has been added
Aug 16 09:13:21 tash hcid[7714]: Starting security manager 0
Aug 16 09:13:21 tash hcid[7714]: Can't write inquiry mode for hci0:
Input/output error (5)
Aug 16 09:13:21 tash hcid[7714]: Register path:/org/bluez/hci0 fallback:0

Apparently, pin_helper is not available...
Here is what the Debian maintainer added to the documentation:

PIN (or passkey) management
- ---------------------------
since bluez 3.0 the old pin_helper script has been replaced by
the dbus interface. To add a default passkey for every outgoing
request (e.g. the old /etc/bluetooth/pin file) drop it into
/etc/bluetooth/passkeys/default. (e.g. echo "1234" >
/etc/bluetooth/passkeys/default )
To add a passkey for a specific outgoing connection replace default
with the device's address. ( /etc/default/passkeys/aa:bb:cc:dd:ee:ff
will contain passkey for aa:bb:cc:dd:ee:ff ).
After adding a passkey you should restart bluetooth with

/etc/init.d/bluetooth restart

and the new passkeys will be registered.

I have also tried that and it is not working... do you think it is a
Debian problem?

Cheers,

/rp
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE4tTUAhGrHSs5PNIRAnwmAKDG2ImeO5udqunoscaUL/Py4U8XvwCeJb3C
H7/lfRt/4s8zpcaCtlUnl0c=
=0Z90
-----END PGP SIGNATURE-----