From: Beerman <beerman@piwo.ws>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] FC2+BT007SV+S55 - scanning works and that's it (l2ping, rfcomm, etc. don't)
Date: Wed, 9 Jun 2004 13:30:40 +0200 [thread overview]
Message-ID: <20040609133040.41a92af8@pytong> (raw)
Hi.
I am using Fedora Core 2 (2.6.5)
My bluez stuff is:
[root@pytong bluetooth]# rpm -qa|grep bluez
bluez-sdp-1.5-2.1
bluez-bluefw-1.0-2
bluez-libs-2.5-2.1
bluez-hcidump-1.5-4
bluez-pan-1.1-4
bluez-utils-2.4-3
Hardware is Bluetake BT007SV USB dongle and Siemens S55 mobile phone. I want to make rfcomm as serial link for talking with mobile modem.
Running BlueZ:
[root@pytong bluetooth]# service bluetooth start
Starting Bluetooth: [ OK ]
[root@pytong bluetooth]# lsmod
Module Size Used by
rfcomm 27164 1
l2cap 16004 5 rfcomm
hci_usb 9604 3
bluetooth 33636 11 rfcomm,l2cap,hci_usb
.
...........
Scanning finds my phone:
[root@pytong bluetooth]# hcitool scan
Scanning ...
00:01:E3:13:CD:DA S55
but cannot ping it:
[root@pytong bluetooth]# l2ping 00:01:E3:13:CD:DA
Can't connect.: Invalid exchange
I can(?) bind to rfcomm:
[root@pytong bluetooth]# rfcomm
rfcomm0: 00:01:E3:13:CD:DA channel 1 clean
but cannot connect:
[root@pytong bluetooth]# rfcomm connect 00:01:E3:13:CD:DA 1
Can't connect RFCOMM socket: Host is down
What can be wrong ?
Thank you very much for help.
What can be wrong ?
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-06-09 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 11:30 Beerman [this message]
2004-06-09 11:43 ` [Bluez-users] FC2+BT007SV+S55 - scanning works and that's it (l2ping, rfcomm, etc. don't) Marcel Holtmann
2004-06-09 12:03 ` Michal Semler
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=20040609133040.41a92af8@pytong \
--to=beerman@piwo.ws \
--cc=bluez-users@lists.sourceforge.net \
/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