public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Rui Pedro Lopes <rlopes@ipb.pt>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Totally confused
Date: Wed, 16 Aug 2006 09:18:28 +0100	[thread overview]
Message-ID: <44E2D4D4.6030304@ipb.pt> (raw)
In-Reply-To: <20060815222203.GI15576@refinery.twat.com.ar>

-----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-----


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-08-16  8:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15  0:42 [Bluez-users] Totally confused Terry Mackintosh
2006-08-15  1:23 ` redondos
2006-08-15 10:31   ` Rui Pedro Lopes
2006-08-15 22:22     ` redondos
2006-08-16  8:18       ` Rui Pedro Lopes [this message]
2006-08-16 13:39         ` redondos
2006-08-16 13:38           ` Rui Pedro Lopes
2006-08-16 15:16             ` redondos
2006-08-17  8:30               ` Rui Pedro Lopes
2006-08-16 14:27           ` manojt ambe
2006-08-16 15:13             ` Rui Pedro Lopes
2006-08-15 15:39   ` Terry Mackintosh
2006-08-15 22:33     ` redondos
2006-08-16  8:32       ` Rui Pedro Lopes
2006-08-15 21:29 ` digitalfredy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44E2D4D4.6030304@ipb.pt \
    --to=rlopes@ipb.pt \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox