From: Wouter Verhelst <wouter@grep.be>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Apple PowerBook and Nokia 6310i
Date: Thu, 21 Oct 2004 01:36:08 +0200 [thread overview]
Message-ID: <20041020233608.GA26457@grep.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 2748 bytes --]
Hi,
I recently (as in, two days ago) acquired a new laptop, a 12" Apple
PowerBook G4. This thing has bluetooth; so does my Nokia.
Right now, I'm trying to connect to the Internet using the laptop and
the Nokia, which doesn't seem to work. I did get it to work using IrDA
on my previous laptop, but a) that was an i386 laptop, b) it was over
IrDA instead of bluetooth, and c) the reason I bought this laptop is
because the previous one was stolen from me -- so I can't look up how I
did everything anymore.
After configuring everything, this is what appears in my syslog when I
try to connect:
|Oct 21 01:29:41 localhost pppd[10896]: pppd 2.4.2 started by wouter, uid 1000
|Oct 21 01:29:41 localhost hcid[3587]: link_key_request (sba=00:0D:93:10:92:B6, dba=00:60:57:30:38:D8)
|Oct 21 01:29:42 localhost chat[10897]: abort on (BUSY)
|Oct 21 01:29:42 localhost chat[10897]: abort on (NO CARRIER)
|Oct 21 01:29:42 localhost chat[10897]: abort on (VOICE)
|Oct 21 01:29:42 localhost chat[10897]: abort on (NO DIALTONE)
|Oct 21 01:29:42 localhost chat[10897]: send (AT&F^M)
|Oct 21 01:29:42 localhost chat[10897]: expect (OK)
|Oct 21 01:29:43 localhost chat[10897]: AT&F^M^M
|Oct 21 01:29:43 localhost chat[10897]: OK
|Oct 21 01:29:43 localhost chat[10897]: -- got it
|Oct 21 01:29:43 localhost chat[10897]: send (ATDT+3222750205^M)
|Oct 21 01:29:43 localhost chat[10897]: expect (CONNECT)
|Oct 21 01:29:43 localhost chat[10897]: ^M
|Oct 21 01:30:03 localhost chat[10897]: ATDT+3222750205^M^M
|Oct 21 01:30:03 localhost chat[10897]: CONNECT
|Oct 21 01:30:03 localhost chat[10897]: -- got it
|Oct 21 01:30:03 localhost pppd[10896]: Serial connection established.
|Oct 21 01:30:03 localhost kernel: divert: not allocating divert_blk for non-ethernet device ppp0
|Oct 21 01:30:03 localhost pppd[10896]: Using interface ppp0
|Oct 21 01:30:03 localhost pppd[10896]: Connect: ppp0 <--> /dev/rfcomm0
|Oct 21 01:30:16 localhost pppd[10896]: Serial line is looped back.
|Oct 21 01:30:16 localhost pppd[10896]: Connection terminated.
|Oct 21 01:30:16 localhost kernel: divert: no divert_blk to free, ppp0 not ethernet
|Oct 21 01:30:28 localhost pppd[10896]: Terminating on signal 15.
|Oct 21 01:30:28 localhost pppd[10896]: Exit.
While this happens, I can see the Nokia does set up the connection;
however, it drops the line somewhere between the "Connect: ppp0 <-->
/dev/rfcomm0" and te "Serial line is looped back" message. When that
happens, it appears as if pppd does not immediately notice.
I'm not sure why it doesn't work; Any hints would be greatly
appreciated.
--
EARTH
smog | bricks
AIR -- mud -- FIRE
soda water | tequila
WATER
-- with thanks to fortune
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-10-20 23:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 23:36 Wouter Verhelst [this message]
2004-10-21 17:48 ` [Bluez-users] Apple PowerBook and Nokia 6310i Marcel Holtmann
2004-10-21 18:03 ` Wouter Verhelst
2004-10-21 19:33 ` Wouter Verhelst
2004-10-21 22:49 ` Marcel Holtmann
2004-10-22 11:32 ` Wouter Verhelst
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=20041020233608.GA26457@grep.be \
--to=wouter@grep.be \
--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