From: andreas knuth <andreas.knuth@daimlerchrysler.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: Connecting to a Nokia 6021
Date: Fri, 24 Jun 2005 15:50:22 +0000 (UTC) [thread overview]
Message-ID: <loom.20050624T174404-129@post.gmane.org> (raw)
In-Reply-To: 1119525688.17872.4.camel@sliver.usr.dsi.unimi.it
Hi Sebastian,
Sebastiano Vigna <vigna <at> dsi.unimi.it> writes:
>
...
> L2CAP(d): cid 0x0040 len 4 [psm 3]
> RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> > HCI Event: Number of Completed Packets (0x13) plen 5
> 0000: 01 28 00 01 00 .(...
> > HCI Event: PIN Code Request (0x16) plen 6
> 0000: 10 26 00 70 13 00 .&.p..
>
> And them the phone times out. The interesting point is that if you look at
the included hcid.conf,
> I have a pin helper of my own, containing:
>
> #!/bin/bash
> echo "Request $(date)" >>/tmp/req
> echo "PIN:112358"
>
> This is never called by the stack.
>
> I couldn't find any log anywhere to find out what's happening, so I'm
> really stuck.
In your hcid.conf there are two "PIN-HELPER"s active at the same time! You
should have active only one at the same time. Try it out (deactivate
dbus_pin_helper -> #dbus_pin_helper.
regards,
Andreas
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-06-24 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 11:21 [Bluez-users] Connecting to a Nokia 6021 Sebastiano Vigna
2005-06-24 15:50 ` andreas knuth [this message]
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=loom.20050624T174404-129@post.gmane.org \
--to=andreas.knuth@daimlerchrysler.com \
--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