From: Marcel Holtmann <marcel@holtmann.org>
To: Steven Yap <syap@shaw.ca>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] /dev/rfcommX device not created in time
Date: Sun, 16 May 2004 14:00:20 +0200 [thread overview]
Message-ID: <1084708820.4184.9.camel@pegasus> (raw)
In-Reply-To: <1084674433.3927.14.camel@obsolescence>
Hi Steven,
> I'm using Debian unstable with kernel 2.6.5, udev 0.024, bluez-pan
> 1.1rel-3 and I'm observing a timing problem with udev and the rfcommX
> device.
>
> I'm trying to network my Palm Tungsten T3 with my computer but pppd
> never gets call. When I click on the Network Services' "Connect" button
> on the T3, I see from the log that dund complains about the failure to
> create /dev/rfcommX device:
>
> May 15 18:12:34 obsolescence hcid[2886]: link_key_request
> (sba=00:02:72:B1:45:02, dba=00:07:E0:2E:28:9C)
> May 15 18:12:35 obsolescence dund[7424]: RFCOMM TTY creation failed. No
> such file or directory(2)
> May 15 18:12:36 obsolescence udev[7431]: creating device node
> '/dev/rfcomm0'
> May 15 18:13:07 obsolescence udev[7442]: removing device node
> '/dev/rfcomm0'
>
> However, udev does create the /dev/rfcomm0, just not fast enough
> apparently. In a little experiment, as soon as I see the line:
>
> udev[7431]: creating device node '/dev/rfcomm0'
>
> I run "sudo pppd /dev/rfcomm0 call btpalm" and this allows the T3
> to grab an IP address and setup IP networking between the T3 and my
> computer. From that point on, I can surf the Web from the T3 without
> any problems.
>
> Are there other Bluez users out there who are using udev who has
> managed to workaround/fix this problem?
the bluez-utils-2.7 contains the pand and the dund and I already fixed
that problem there.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-05-16 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-16 2:27 [Bluez-users] /dev/rfcommX device not created in time Steven Yap
2004-05-16 12:00 ` Marcel Holtmann [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=1084708820.4184.9.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=syap@shaw.ca \
/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