public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mark S. Townsley" <mstownsley@gmail.com>
To: "Stefan Seyfried" <seife@suse.de>
Cc: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] minicom over /dev/rfcomm0 failed
Date: Mon, 18 Dec 2006 10:06:09 -0800	[thread overview]
Message-ID: <be976db60612181006p70bc77ceq1c0bb7c113c9d3d8@mail.gmail.com> (raw)
In-Reply-To: <20061218173426.GC13541@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 1687 bytes --]

Yes, that is the correct BT addr of the BT module that is trying to connect
to my SuSE box.
And I am running SuSE 10.1

thanks


On 12/18/06, Stefan Seyfried <seife@suse.de> wrote:
>
> On Mon, Dec 18, 2006 at 08:43:58AM -0800, Mark S. Townsley wrote:
> > 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;
>
> is this the correct BDADDR?
> Did you already pair the devices?
>
> What SUSE version are you using?
>
> >        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
>
> This works for me, i only get "No such file or directory if i enter the
> wrong
> BDADDR in the rfcomm.conf file or if i wait too long during the "do you
> want
> to allow device foobar to access the internet via the phone" dialog with
> confirming (on the phone).
> --
> Stefan Seyfried                  \ "I didn't want to write for pay. I
> QA / R&D Team Mobile Devices      \ wanted to be paid for what I write."
> SUSE LINUX Products GmbH, Nürnberg \                    -- Leonard Cohen
>

[-- Attachment #1.2: Type: text/html, Size: 2446 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

      reply	other threads:[~2006-12-18 18: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
2006-12-18 16:43   ` Mark S. Townsley
2006-12-18 17:34     ` Stefan Seyfried
2006-12-18 18:06       ` Mark S. Townsley [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=be976db60612181006p70bc77ceq1c0bb7c113c9d3d8@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