Return-Path: Message-ID: Date: Mon, 18 Dec 2006 08:43:58 -0800 From: "Mark S. Townsley" To: "BlueZ users" , seife@suse.de In-Reply-To: <20061218090638.GB960@suse.de> MIME-Version: 1.0 References: <20061218090638.GB960@suse.de> Subject: Re: [Bluez-users] minicom over /dev/rfcomm0 failed Reply-To: BlueZ users List-Id: BlueZ users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1921177131==" Sender: bluez-users-bounces@lists.sourceforge.net Errors-To: bluez-users-bounces@lists.sourceforge.net --===============1921177131== Content-Type: multipart/alternative; boundary="----=_Part_23860_5245409.1166460238117" ------=_Part_23860_5245409.1166460238117 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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; 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 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 a= n > > 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=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=3D= DEVDEV > _______________________________________________ > Bluez-users mailing list > Bluez-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluez-users > ------=_Part_23860_5245409.1166460238117 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Stefan: Below are the various info that you asked for. Let m= e 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:~ # <= br>linux-fqoe:~ # id
uid=3D0(root) gid=3D0(root) groups=3D0(root)
linux-fqoe:~ # cat /etc= /bluetooth/rfcomm.conf
#
# RFCOMM configuration file.
#

rf= comm0 {
        bind yes;
&n= bsp;      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

Mar= k

On 12/18/06, Stefan Seyfried < seife@suse.de> wrote:

On Sun, Dec 17, 2006 at 09:56:40PM -0800, Mark S. Townsl= ey wrote:
> Hi:
> I am trying to use minicom on my SuSE box to receive c= onnections from an
> external device that connect, via Bluetooth, and= handshake with the AT
> command set.
> I have /dev/rfcomm0.&nb= sp; I also have entries in /dev/rfcomm0 that binds to the
> BT_ADDR of that external device.
> However, when I run minic= om (with serial device set to /dev/rfcomm0), I got
> back:
>> minicom: cannot open /dev/rfcomm0: No such file or directo= ry.
>
> 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 &n= bsp; | &nbs= p; "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=3DDEVDEV
_______________________________________________
Blue= z-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

------=_Part_23860_5245409.1166460238117-- --===============1921177131== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- 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 --===============1921177131== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users --===============1921177131==--