public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [Bluez-users] minicom over /dev/rfcomm0 failed
@ 2006-12-18  5:56 Mark S. Townsley
  2006-12-18  9:06 ` Stefan Seyfried
  0 siblings, 1 reply; 5+ messages in thread
From: Mark S. Townsley @ 2006-12-18  5:56 UTC (permalink / raw)
  To: BlueZ users


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

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.

Am I missing a step somewhere?
Any help much appreciated.


Mark

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bluez-users] minicom over /dev/rfcomm0 failed
  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
  0 siblings, 1 reply; 5+ messages in thread
From: Stefan Seyfried @ 2006-12-18  9:06 UTC (permalink / raw)
  To: bluez-users

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bluez-users] minicom over /dev/rfcomm0 failed
  2006-12-18  9:06 ` Stefan Seyfried
@ 2006-12-18 16:43   ` Mark S. Townsley
  2006-12-18 17:34     ` Stefan Seyfried
  0 siblings, 1 reply; 5+ messages in thread
From: Mark S. Townsley @ 2006-12-18 16:43 UTC (permalink / raw)
  To: BlueZ users, seife


[-- 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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bluez-users] minicom over /dev/rfcomm0 failed
  2006-12-18 16:43   ` Mark S. Townsley
@ 2006-12-18 17:34     ` Stefan Seyfried
  2006-12-18 18:06       ` Mark S. Townsley
  0 siblings, 1 reply; 5+ messages in thread
From: Stefan Seyfried @ 2006-12-18 17:34 UTC (permalink / raw)
  To: Mark S. Townsley; +Cc: BlueZ users

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=3D0(root) gid=3D0(root) groups=3D0(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 wro=
ng
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=FCrnberg \                    -- Leonard Cohen

-------------------------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bluez-users] minicom over /dev/rfcomm0 failed
  2006-12-18 17:34     ` Stefan Seyfried
@ 2006-12-18 18:06       ` Mark S. Townsley
  0 siblings, 0 replies; 5+ messages in thread
From: Mark S. Townsley @ 2006-12-18 18:06 UTC (permalink / raw)
  To: Stefan Seyfried; +Cc: BlueZ users


[-- 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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-12-18 18:06 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox