From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Pairing a keyboard
Date: Thu, 25 Nov 2004 08:16:49 +0100 [thread overview]
Message-ID: <1101367010.7538.78.camel@pegasus> (raw)
In-Reply-To: <20041125064110.GA2505@frostnet.net>
Hi Chris,
> When trying to pair with an apple wireless keyboard, hcitool cc errors
> "Can't create connection: Input/output error". I was hoping someone
> might have a suggestion on what to look into.
who said that pairing works by calling "hcitool cc ..."? You should use
the "hidd --connect ..." command instead.
> I'm kernel 2.6.9-mh4 and bluez 2.11 on an x86 with a D-Link DBT-120.
> After starting hcid I run "hcitool cc <addr>" and get the error above.
> I've included "hcidump -x"'s transcript at the bottom of this email.
> bluepin does not work on my installation (pygtk seems broken), so I wrote
> a script to echo "0000" to stdout. This may well be my problem? I do not know
> if this is the format hcid is expecting or if it is the initial pin apple
> sets. I did read that the mouse uses this pin, this is the only reason for
> my choice. For my hcid.conf file, security is auto, pin_helper is set to this
> script, and auth and encrypt are commented out.
The bluepin script must echo "PIN:0000".
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-11-25 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 6:41 [Bluez-users] Pairing a keyboard Chris Frost
2004-11-25 7:16 ` Marcel Holtmann [this message]
2004-11-25 7:57 ` Chris Frost
2004-11-25 8:33 ` Marcel Holtmann
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=1101367010.7538.78.camel@pegasus \
--to=marcel@holtmann.org \
--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