Skip to contentSkip to conversation

Apple PowerBook and Nokia 6310i

Bluez-users Wouter Verhelst 2 participants 6 messages Oct 20, 2004 – Oct 22, 2004 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

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.

Signature · 6 lines
         EARTH
     smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
         WATER
 -- with thanks to fortune
maintainer
#1 lore raw

Hi Wouter,

Quoted 40 lines

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.
Quoted 4 lines

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.

what kernel version is this? Maybe it is a kernel bug in the PPP code or your settings for pppd are simply wrong. Try other dialers like wvdial.

Regards

Marcel

-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#2 lore raw
Quoted 1 line · Marcel Holtmann

Hi Wouter,

[...]

Quoted 6 lines
Quoted 4 lines

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.

what kernel version is this?

2.6.8, the one distributed with Debian Sarge (package kernel-image-2.6.8-powerpc version 2.6.8-6). Note, they have a few Debian-specific patches; I'll try with vanilla 2.6.9 and see whether that works.

Quoted 2 lines

Maybe it is a kernel bug in the PPP code or your settings for pppd are simply wrong.

That's most certainly possible, since I'm not a PPP guru; however, the following doesn't look incorrect to me:

|wouter@country:/etc/ppp/peers$ egrep -v '(^#|^$)' provider
|noauth
|connect "/usr/sbin/chat -v -f /etc/chatscripts/provider"
|defaultroute
|/dev/rfcomm0
|115200
|persist

/etc/chatscripts/provider:

|ABORT        BUSY
|ABORT        "NO CARRIER"
|ABORT        VOICE
|ABORT        "NO DIALTONE"
|""           AT&F
|OK           ATDT+3222750205
|CONNECT

which, I think, should work, no?

Quoted 1 line

Try other dialers like wvdial.

Hmm, I could try that, but I'd rather explore some other possibilities before I go that route. If there are any, that is ;-)

Thanks,

Signature · 6 lines
         EARTH
     smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
         WATER
 -- with thanks to fortune
#3 lore raw
Quoted 2 lines · On Thu, Oct 21, 2004 at 08:03:35PM +0200, wrote:

Debian-specific patches; I'll try with vanilla 2.6.9 and see whether that works.

Tried that; it didn't, same problem.

Signature · 6 lines
         EARTH
     smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
         WATER
 -- with thanks to fortune
maintainer
#4 lore raw
In reply to Wouter Verhelst

Hi Wouter,

Quoted 4 lines
Quoted 1 line

Try other dialers like wvdial.

Hmm, I could try that, but I'd rather explore some other possibilities before I go that route. If there are any, that is ;-)

you should really try the wvdial program, because it always did the right job for me.

Regards

Marcel

-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#5 lore raw
Quoted 9 lines · Marcel Holtmann

Hi Wouter,

Quoted 4 lines
Quoted 1 line

Try other dialers like wvdial.

Hmm, I could try that, but I'd rather explore some other possibilities before I go that route. If there are any, that is ;-)

you should really try the wvdial program, because it always did the right job for me.

I looked at it a few times in the past, and it never worked with the particular quirks of my provider.

In the mean time, though, I found out what the problem was. I had to add "user <username>" and "usepeerdns" directives to the peers/provider file; now everything works smoothly.

Next, try and get GPRS working. But to do that, I shouldn't need your help anymore. Thanks!

Signature · 6 lines
         EARTH
     smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
         WATER
 -- with thanks to fortune