From: Gregory Gulik <greg@gulik.org>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Trouble with D-LINK adapter w/Treo 650 and FC4
Date: Wed, 24 Aug 2005 23:18:09 -0500 [thread overview]
Message-ID: <430D4681.80609@gulik.org> (raw)
I've been trying to follow the instructions to get a D-LINK DBT-120
Bluetooth adapter to work with Fedora Core 4 using a Treo 650 PalmOS
phone on the Sprint network.
I've been battling it for a while and since I'll be traveling a lot very
soon (the reason I'm trying to get this working) and I'm running out of
time so I'm asking for help.
Basically, the instructions I'm following are these:
http://www.gurulabs.com/goodies/Using_Linux_and_Bluetooth_DUN_with_the_Treo650.php
Everything went fairly well except when I finally try to bring up the
PPP connection I get an error:
[root@dell8100 bluetooth]# ifup treo
Failed to activate treo with error 7
/var/log/messages reports the following details:
Aug 24 23:13:16 dell8100 ifup-ppp: pppd started for treo on /dev/rfcomm0
at 115200
Aug 24 23:13:16 dell8100 pppd[30712]: pppd 2.4.2 started by root, uid 0
Aug 24 23:13:17 dell8100 hcid[30014]: link_key_request
(sba=00:13:46:47:64:27, dba=00:07:E0:03:D3:99)
Aug 24 23:13:18 dell8100 pppd[30712]: Failed to open /dev/rfcomm0:
Connection reset by peer
Aug 24 23:13:18 dell8100 pppd[30712]: Exit.
FYI:
00:13:46:47:64:27 is my D-Link Bluetooth adapter
00:07:E0:03:D3:99 is my Treo 650
I tried to follow some of the other diagnostics I found on the list to
no avail:
# l2ping 00:07:E0:03:D3:99
Ping: 00:07:E0:03:D3:99 from 00:13:46:47:64:27 (data size 20) ...
Recv failed: Connection reset by peer
During that time /var/log/messages reported the following:
Aug 24 23:14:14 dell8100 hcid[30014]: link_key_request
(sba=00:13:46:47:64:27, dba=00:07:E0:03:D3:99)
If I try to scan for the phone it DOES appear to be found:
# hcitool scan
Scanning ...
00:07:E0:03:D3:99 MYTREO
One thing I noticed is that when I remove the /etc/bluetooth/link_key
and then try to start PPP the phone asks me for my PIN again. I put it
in and that time it seems to open the /dev/rfcomm0 port. It then tries
to send AT commands which don't respond so it times out and fails.
Help!
--
Greg Gulik http://www.gulik.org/greg/
greg @ gulik.org
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-08-25 4:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 4:18 Gregory Gulik [this message]
2005-08-25 19:03 ` [Bluez-users] Trouble with D-LINK adapter w/Treo 650 and FC4 Marcel Holtmann
2005-08-26 14:51 ` Gregory Gulik
2005-09-09 20:35 ` Gregory Gulik
2005-09-09 21:04 ` Marcel Holtmann
2005-09-09 21:46 ` Gregory Gulik
2005-09-09 23:02 ` Marcel Holtmann
2005-09-09 23:06 ` Gregory Gulik
2005-09-09 23:16 ` Marcel Holtmann
2005-09-10 2:15 ` Gregory Gulik
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=430D4681.80609@gulik.org \
--to=greg@gulik.org \
--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;
as well as URLs for NNTP newsgroup(s).