OESF Portables Forum
Everything Else => Sharp Zaurus => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => Cxx0 General discussions => Topic started by: Shadow on May 07, 2004, 07:55:28 am
-
Hi there!
I have just bought a used Zaurus SL-C700 from a friend including a network adaptor and a bluetooth CF Card... the network works fine, no problems there but I had to install the bluetooth first, so I consulted a manual on this page http://www.zaurususergroup.com/modules.php...ename=Bluetooth (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=Bluetooth).
The problem\'s this: I can browse for Bluetooth devices and I see my mobile (T610). I could even add my Zaurus to the mobile phone... but what I cannot do is connect from the Zaurus using the Dial-Up IrDA connection I\'ve set up. Since there is no error message beside \"Network Offline\" I have no idea where to look for the mistake...
Can someone help me out here?
-
Dial-Up IrDA connection
Note the word IrDA.
I don\'t know, but I expect that you can use exactly the same script but change the line that goes /dev/ircomm to /dev/ttyS3 (I think that\'s the CF card)
The script will (I guess) be in /etc/ppp/peers/
Simon
-
No, that\'s not it... with the actual settings the bluetooth card at least reacts... the lamp flashes. If I change that entry it won\'t budge anymore.
As I understand it I\'m like redirecting the IrDA scripts to the bluetooth device. So I guess it\'s all right to use that script... and since I receive info of my mobile fone on the Z I guess the CF Card is working all right as well... But perhaps there is a problem with authentication? I mean I have to enter a pin code but I haven\'t found a way to tell my phone to which pin it has to reply... could ot be that I have to use the pin as password in the Zs network connection?
-
Any connection errors should appear in the log /tmp/qpe-pppd-log
Have you actually paired your Zaurus and phone? The Bluetooth howto explains where the pins for initiating and accepting connections on the Zaurus are. The network connection password is not used as the Bluetooth pin for pairing.
If your Zaurus and phone are not automatically pairing when you try to establish a network connection, you could also try running the following on your Zaurus as also explaining in the howto:
dund -c 11:22:33:44:55 (replacing the MAC address with your phone\'s)
-
No they are not pairing... They only pair when I establish a connection with the phone. I have set the pin codes on the Zaurus correctly... at least I hope so...
I have used dund, received no error message and thought it worked... but it didn\'t help. Should there be an active LAP connection, when I type dund -l? because there is none.
The error log says that the scripts waited for one minute for a \"CONNECT\" and received none. I still think I have to set up something about the phone but I don\'t know what...
-
They only need to pair once and then you no longer need the PIN numbers. It sounds like you have got them paired and it\'s probably just a modem initialisation string or dialing string problem.
Could you post the contents of your /tmp/qpe-pppd-log ? There shouldn\'t be any sensitive details in it.
-
There aren\'t any problematic details... I\'ll just connect via LAN and post a cat. Just a sec (or two )
-
May 7 16:49:43 localhost pppd[3701]: pppd 2.4.0 started by root, uid 0
May 7 16:12:00 localhost chat[3703]: abort on (NO CARRIER)
May 7 16:12:00 localhost chat[3703]: abort on (NO DIALTONE)
May 7 16:12:00 localhost chat[3703]: abort on (BUSY)
May 7 16:12:00 localhost chat[3703]: send (ATDT107410844844222^M)
May 7 16:12:00 localhost chat[3703]: expect (CONNECT)
May 7 16:13:00 localhost chat[3703]: alarm
May 7 16:13:00 localhost chat[3703]: Failed
May 7 16:13:00 localhost pppd[3701]: Connect script failed
May 7 16:13:01 localhost pppd[3701]: Exit.
-
It still doesn\'t work. Isn\'t there anybody who had the same problem?
-
Hmm, you need to run pppd with debug to let us see a bit more of the problem. Put a line with \'debug\' (without the qutoes) in the /etc/ppp/peers file for the network connection and then show us that log file again after trying to connect.
-
May 10 16:49:43 localhost pppd[577]: pppd 2.4.0 started by root, uid 0
May 10 16:12:00 localhost chat[583]: abort on (NO CARRIER)
May 10 16:12:00 localhost chat[583]: abort on (NO DIALTONE)
May 10 16:12:00 localhost chat[583]: abort on (BUSY)
May 10 16:12:00 localhost chat[583]: send (ATDT107410844844222^M)
May 10 16:12:00 localhost chat[583]: expect (CONNECT)
May 10 16:12:00 localhost chat[583]: ATDT107410844844222^M^M
May 10 16:12:00 localhost chat[583]: NO CARRIER
May 10 16:12:00 localhost chat[583]: -- failed
May 10 16:12:00 localhost chat[583]: Failed (NO CARRIER)
May 10 16:13:00 localhost pppd[577]: Connect script failed
May 10 16:13:01 localhost pppd[577]: Exit.
Thats the new output.
-
Is your phone indicating that the Bluetooth connection has been established? I wouldn\'t expect it to get to the chatscript if the connection to your phone was not established, so it looks like it could be a phone initialisation/network account setup issue.
What is the modem init string that you are using?
The other output you can look at is from the command (run as root)
pppd call <your peers filename goes here> -detach
e.g. pppd call DialupIrDA547634967397 -detach
The entire pppd log will then be printed to the Zaurus screen.
-
I have a T608, which is similar to the 610, and to make it work I had to edit the chat string and get rid of the \"ATZ OK\" sequence before dialing, otherwise it didn\'t work. Don\'t know if that\'s your problem though...
-
Where would I find this modem init string?
-
Is your phone indicating that the Bluetooth connection has been established? I wouldn\'t expect it to get to the chatscript if the connection to your phone was not established, so it looks like it could be a phone initialisation/network account setup issue.
What is the modem init string that you are using?
The other output you can look at is from the command (run as root)
pppd call <your peers filename goes here> -detach
e.g. pppd call DialupIrDA547634967397 -detach
The entire pppd log will then be printed to the Zaurus screen.
BTW the only thing that is returned is ATZ.
-
The modem setup scripts should be in /etc/ppp/peers. Each file in there corresponds to a connection.
-
Well the whole file lloks as follows:
/dev/rfcomm0
debug
noipdefault
115200
connect \'/usr/sbin/chat -s -v -t 60 ABORT \"NO CARRIER\" ABORT \"NO DIALTONE\" ABORT \"BUSY\" \"\" \"ATQ0V1S100=1\" OK \"ATDT0844844222\" CONNECT \"¥¥d¥¥d\"\'
crtscts
lock
modem
user \"xxxxxxxx\"
usepeerdns
defaultroute
mtu 576
mru 576
connect -delay 1000
remotename IRDA1084202939
That\'s it... the connect string looked like this before:
connect \'/usr/sbin/chat -s -v -t 60 ABORT \"NO CARRIER\" ABORT \"NO DIALTONE\" ABORT \"BUSY\" \"\" \"ATZ\" OK \"ATQ0V1S100=1\" OK \"ATDT0844844222\" CONNECT \"¥¥d¥¥d\"\'
Oh yeah BTW I\'m having the problem that this file is always reset, when I go in suspend mode... at least that seems to be the cause... how can I permanently change that file?
-
It should only be getting reset when you change something in the Network app.
What you need to do is find the modem initialisation string for the T610 as what you have is definitely incorrect. You can edit the modem init string in the Network app (It\'s on the 2nd tab of the connection editing screen), but then you\'ll have to put /dev/rfcomm0 back into that file.
-
OK so that means some googling for that init string, right?
-
If you can\'t find it on the forums then yes. I have a Nokia which is different so I don\'t know what it should be.
-
I found the string for a T68 but since the other phones all use the same strings I thought I\'d just try it... but now my battery is low... cool... I\'ve been charging it for about a day and all I get is 30 to 60 minutes battery life... is that normal?
-
The T68 string may well work.
The C700 has a small battery and a large bright screen, so using it constantly will drain the battery rather quickly. You might want to try turning the brightness down. It\'s also possible the battery is on its way out as that still sounds a little on the low side. All lithium batteries have a limited lifespan.
-
On mt T608, I use no modem init string. The ATD is 1st command.
-
Brightness, good idea... the battery should be new though... I\'ll try it.
I\'ll give you an update as soon as I have the power supply handy.
-
OK we don\'t have to worry about Bluetooth anymore... I just killed my little Zaurus after just one week... how that god damned power cord managed to sling itself around my foot I\'ll never know... What I do know is is that the ppor thing flew across the room and crashed against floor and wall.
Interesting about it though is that it still worked fine than... but today I tried to turn it on... nothing. It\'s just that... I curse my luck...
OK forget about that, now it works again.... I just don\'t know why.
-
Heureka I say! The Phone tried to connect! Well, only for half a second but it tried! I\'ll post the log
May 12 08:55:47 localhost pppd[453]: pppd 2.4.0 started by root, uid 0
May 12 08:55:51 localhost chat[464]: abort on (NO CARRIER)
May 12 08:55:51 localhost chat[464]: abort on (NO DIALTONE)
May 12 08:55:51 localhost chat[464]: abort on (BUSY)
May 12 08:55:51 localhost chat[464]: send (AT+CBST=80,0,1;+CHSN=4,2,0,12^M)
May 12 08:55:51 localhost chat[464]: expect (OK)
May 12 08:55:52 localhost chat[464]: AT+CBST=80,0,1;+CHSN=4,2,0,12^M^M
May 12 08:55:52 localhost chat[464]: OK
May 12 08:55:52 localhost chat[464]: -- got it
May 12 08:55:52 localhost chat[464]: send (ATDT107410840840222^M)
May 12 08:55:52 localhost chat[464]: expect (CONNECT)
May 12 08:55:52 localhost chat[464]: ^M
May 12 08:55:56 localhost chat[464]: ATDT107410840840222^M^M
May 12 08:55:56 localhost chat[464]: NO CARRIER
May 12 08:55:56 localhost chat[464]: -- failed
May 12 08:55:56 localhost chat[464]: Failed (NO CARRIER)
May 12 08:55:56 localhost pppd[453]: Connect script failed
May 12 08:55:57 localhost pppd[453]: Exit.
This is the actal log file though I have to say I couldn\'t connect a second time yet.
-
May 12 08:55:56 localhost chat[464]: ATDT107410840840222^M^M
May 12 08:55:56 localhost chat[464]: NO CARRIER
May 12 08:55:56 localhost chat[464]: -- failed
May 12 08:55:56 localhost chat[464]: Failed (NO CARRIER)
Looks like you\'ve got the number wrong or you couldn\'t get through to the number via your phone. NO CARRIER basically means it didn\'t get an answer or could not establish a connection with the modem at the other end.
-
OK I\'ll look into that... even though it should be the right number... anyway what I don\'t quite understand is why it worked only once. All I get now is an
alarm
and a
-- write timed out
-
tumnus: You were right one zero was missing in my number... so as soon as I can start another try we\'ll see if it works... I\'d just like to know why it only worked once.
-
Heureka it works! I\'ve got Internet! The only strange thing is that over Bluetooth I cannot reach google... it always redirects me to the zaurus homepage. Is that probably a wrong hosts entry? Which would be strange since it works normally over LAN.