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