Linux bluetooth development
 help / color / mirror / Atom feed
* [Bluez-users] rfcomm failing after PIN is entered on nokia 6310i
@ 2003-12-17  9:19 Jiri Kaderavek
  0 siblings, 0 replies; 2+ messages in thread
From: Jiri Kaderavek @ 2003-12-17  9:19 UTC (permalink / raw)
  To: bluez-users

Hi all.

I'm setting up a bluetooth connection between
my server and Nokia 6310i phone. This connection
was working (phone and server was paired), but now
I'm asked by phone for entering a PIN (maybe i've
changed USB bluetooth dongle, because i have
2 units).

After typing

# rfcomm connect rfcomm0

(i'm sure that rfcomm0 is well configured in a rfcomm.conf)
i must confirm the conection on the phone and then
i'm asked by the phone for a PIN number. After inserting 
the same PIN as in /etc/bluetooth/pin i see:

uran:/home/kodoub# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Resource temporarily unavailable

My pin_helper is a bash script with echo "PIN:XXXXX".
The same problem i have also on my second computer.
I'm using Debian with different kernels on these
computers (patched Linux version 2.4.20-k7-mh8 and
Linux version 2.4.22). I'm sure that i solved this
problem in the past after a days, but i've forget
the solution. Please, can anybody help me remember
what is bad?

Thanx, Jirka.


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 2+ messages in thread
* [Bluez-users] rfcomm failing after PIN is entered on nokia 6310i
@ 2003-12-17  9:20 jirka
  0 siblings, 0 replies; 2+ messages in thread
From: jirka @ 2003-12-17  9:20 UTC (permalink / raw)
  To: bluez-users

Hi all.

I'm setting up a bluetooth connection between
my server and Nokia 6310i phone. This connection
was working (phone and server was paired), but now
I'm asked by phone for entering a PIN (maybe i've
changed USB bluetooth dongle, because i have
2 units).

After typing

# rfcomm connect rfcomm0

(i'm sure that rfcomm0 is well configured in a rfcomm.conf)
i must confirm the conection on the phone and then
i'm asked by the phone for a PIN number. After inserting 
the same PIN as in /etc/bluetooth/pin i see:

uran:/home/kodoub# rfcomm connect rfcomm0
Can't connect RFCOMM socket: Resource temporarily unavailable

My pin_helper is a bash script with echo "PIN:XXXXX".
The same problem i have also on my second computer.
I'm using Debian with different kernels on these
computers (patched Linux version 2.4.20-k7-mh8 and
Linux version 2.4.22). I'm sure that i solved this
problem in the past after a days, but i've forget
the solution. Please, can anybody help me remember
what is bad?

Thanx, Jirka.


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-12-17  9:20 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-12-17  9:19 [Bluez-users] rfcomm failing after PIN is entered on nokia 6310i Jiri Kaderavek
  -- strict thread matches above, loose matches on Subject: below --
2003-12-17  9:20 jirka

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox