From: Robert L Waldrop <bob.waldrop@motorola.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] BlueZ stack failure
Date: Mon, 1 Aug 2005 14:01:10 -0500 [thread overview]
Message-ID: <20050801190110.GC11317@urbana.css.mot.com> (raw)
Hi,
I'm having a problem with the rfcomm utility and linux select().
The symptoms are that if I CTRL-C after incomming connection is heard,
when using "rfcomm listen ... /dev/rfcomm10", /dev/rfcomm10 is deleted.
More importantly, a select call on the device blocks except for the
first try. Also, when my machine boots, you have to run
"/etc/init.d/bluetooth restart" for some reason, otherwise; bluetooth
doesn't work, it's like there is something stuck at boot up.
I created the /dev/rfcomm10 using .../bluz-utils-2.18/scripts/create_dev
and am using a clean copy of "rfcomm." I've also tried rebooting bluetooth
between each calls rfcomm and that doesn't work.
I reinstalled libs and utils. I had been using the patch on 2.6.11 from
bluez.org. I'm initially had an install of Fedora Core three based on
2.6.9.
Thanks!
--bob w.
--
Robert Waldrop Motorola Personal Communications Sector
rwaldrop@urbana.css.mot.com Urbana-Champaign Design Center
voice 217-384-8719 1800 South Oak Street
Champaign IL 61820
[X] Motorola General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary
-------------------------------------------------------
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
reply other threads:[~2005-08-01 19:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050801190110.GC11317@urbana.css.mot.com \
--to=bob.waldrop@motorola.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