From: Stefan Seyfried <seife@suse.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] minicom over /dev/rfcomm0 failed
Date: Mon, 18 Dec 2006 10:06:38 +0100 [thread overview]
Message-ID: <20061218090638.GB960@suse.de> (raw)
In-Reply-To: <be976db60612172156l60a7124bsc9a02b4d1a68c455@mail.gmail.com>
On Sun, Dec 17, 2006 at 09:56:40PM -0800, Mark S. Townsley wrote:
> Hi:
> I am trying to use minicom on my SuSE box to receive connections from an
> external device that connect, via Bluetooth, and handshake with the AT
> command set.
> I have /dev/rfcomm0. I also have entries in /dev/rfcomm0 that binds to t=
he
> BT_ADDR of that external device.
> However, when I run minicom (with serial device set to /dev/rfcomm0), I g=
ot
> back:
> =
> minicom: cannot open /dev/rfcomm0: No such file or directory.
> =
> I do have /dev/rfcomm0 and the permission on it looks correct.
Please show us your /etc/bluetooth/rfcomm.conf, the output of "rfcomm" as
root, "ls -l /dev/rfcomm0" and "id" as your user.
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-12-18 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 5:56 [Bluez-users] minicom over /dev/rfcomm0 failed Mark S. Townsley
2006-12-18 9:06 ` Stefan Seyfried [this message]
2006-12-18 16:43 ` Mark S. Townsley
2006-12-18 17:34 ` Stefan Seyfried
2006-12-18 18:06 ` Mark S. Townsley
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=20061218090638.GB960@suse.de \
--to=seife@suse.de \
--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