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