From: "Mark S. Townsley" <mstownsley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>, seife@suse.de
Subject: Re: [Bluez-users] minicom over /dev/rfcomm0 failed
Date: Mon, 18 Dec 2006 08:43:58 -0800 [thread overview]
Message-ID: <be976db60612180843r5faa3f3bwcc8d46e0bea1d31f@mail.gmail.com> (raw)
In-Reply-To: <20061218090638.GB960@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 2229 bytes --]
Hi Stefan: Below are the various info that you asked for. Let me know if
you notice anything I did that is wrong.
linux-fqoe:~ # rfcomm
rfcomm0: 00:80:98:98:A2:28 channel 1 clean
linux-fqoe:~ #
linux-fqoe:~ # id
uid=0(root) gid=0(root) groups=0(root)
linux-fqoe:~ # cat /etc/bluetooth/rfcomm.conf
#
# RFCOMM configuration file.
#
rfcomm0 {
bind yes;
device 00:80:98:98:A2:28;
channel 1;
}
linux-fqoe:~ #
linux-fqoe:~ # ls -l /dev/rfcomm0
crw-rw---- 1 root root 216, 0 Dec 18 08:16 /dev/rfcomm0
linux-fqoe:~ #
linux-fqoe:~ #
linux-fqoe:~ # minicom
LANG/ja
LANG/ko
LANG/ru
minicom: cannot open /dev/rfcomm0: No such file or directory
Mark
On 12/18/06, Stefan Seyfried <seife@suse.de> wrote:
>
> 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
> the
> > BT_ADDR of that external device.
> > However, when I run minicom (with serial device set to /dev/rfcomm0), I
> got
> > 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ürnberg | "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=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
[-- Attachment #1.2: Type: text/html, Size: 3156 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
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 16:43 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
2006-12-18 16:43 ` Mark S. Townsley [this message]
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=be976db60612180843r5faa3f3bwcc8d46e0bea1d31f@mail.gmail.com \
--to=mstownsley@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=seife@suse.de \
/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