From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Can't connect RFCOMM socket: resource temporarily unavailable
Date: Fri, 28 Jan 2005 20:19:25 +0100 [thread overview]
Message-ID: <1106939965.10580.0.camel@pegasus> (raw)
In-Reply-To: <20050128172646.695.qmail@web53205.mail.yahoo.com>
Hi Filipa,
> I am have Linux 2.6.9 in my laptop and an Conceptronic
> CBT 100U USB adapter. I installed bluez-utils-2.14 and
> bluez-libs-2.14.
>
> 'hciconfig -a' shows me my device and 'hcitool scan'
> show me the computer of a friend (a windows pc). I can
> do an 'l2ping' and an 'rfcomm bind' to this computer
> without any problem.
>
> The problems arrive when I try to do 'rfcomm connect'.
> The answer is: "Can't connect RFCOMM socket: resource
> temporarily unavailable".
you can't use bind and connect together. Choose one.
> I saw on the web and on the mailling lists that there
> is a problem with the 'bluepin'. I checked mine and it
> didn't work. So, I created a new file (called pin in
> /usr/bin/) with:
>
> #!bin/sh
> # file: /usr/bin/pin
> echo -n "PIN: "
> cat /etc/bluetooth/pin
>
> and created a file in /etc/bluetooth/ also called pin
> with a numerical the PIN code.
>
> Still I could not make the 'rfcomm connect' work! It
> appears a window asking for the PIN in my friend's
> computer, but in my computer I still have the same
> answer.
Check with "hcidump -x" as root if it is really a PIN helper problem.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-28 19:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 17:26 [Bluez-users] Can't connect RFCOMM socket: resource temporarily unavailable Filipa Duarte
2005-01-28 19:19 ` Marcel Holtmann [this message]
2005-01-31 16:36 ` [Bluez-users] Can't connect RFCOMM socket Filipa Duarte
2005-01-31 17:07 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2005-05-01 17:22 [Bluez-users] Can't connect RFCOMM socket: Resource temporarily unavailable Szilágyi Szilveszter
2005-05-01 17:31 ` Marcel Holtmann
2005-05-01 19:27 ` Szilágyi Szilveszter
2005-06-23 10:49 [Bluez-users] Can"t connect RFCOMM socket: resource " Esther Lopez
2005-06-23 12:26 ` Luiz Fernando Capitulino
2005-06-23 13:51 ` Esther Lopez
2007-08-21 15:25 [Bluez-users] Can't connect RFCOMM socket: Resource " Hamid MENOUAR
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=1106939965.10580.0.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