OESF Portables Forum
Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Accessories => Topic started by: markb on March 26, 2004, 08:49:35 pm
-
I\'ve had a Bluemonkey Bluetooth card for over a week, but haven\'t had any luck getting on the net through my mobile, using GPRS.
I don\'t think it\'s a hardware or driver problem.
I\'m pretty sure it\'s to do with my config files and/or dialup scripts.
I haven\'t played with ppp before, so I could be doing something obviously wrong, but don\'t realise it.
I\'m using a Sony Ericsson P800 phone, on the UK Orange network.
C860 with standard Sharp ROM.
I can pair up the devices OK. My c860 shows up as \"Zaurus\" on my phone. The phone asks me for the PIN that I set up. After I enter it it says \"Bonding complete\". So I think that part is working OK.
I can run sdptool browse on my Z and it discovers my phone:
(Part of MAC address replaced by XX - just to be on the safe side)
# sdptool browse
Inquiring ...
Browsing 00:XX:XX:XX:9A:12 ...
Service Name: Voice gateway
Service Description: Voice gateway
Service Provider: Sony Ericsson
Service RecHandle: 0x10000
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 8
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
Service Name: Dial-up Networking
Service Description: Dial-up Networking
Service Provider: Sony Ericsson
Service RecHandle: 0x10008
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Service Name: OBEX Object Push
Service RecHandle: 0x10009
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
Service Name: Bluetooth Serial Port
Service Description: Bluetooth Serial Port
Service Provider: Symbian Ltd.
Service RecHandle: 0x1000a
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
My /etc/bluetooth/rfcomm.conf file looks like this:
rfcomm0 {
# Automatically bind the device at startup
bind yes;
# Bluetooth address of the device
device 00:XX:XX:XX:9A:12;
# RFCOMM channel for the connection
channel 1;
# Description of the connection
comment "P800 DUN";
}
In /etc/ppp/peers I have a file called IRDA1079225237
(The file was originally named & created by the Network app on the Z, but I\'ve edited the contents.)
# cat IRDA1079225237
debug debug debug
/dev/rfcomm0
noipdefault
115200
connect \'/usr/sbin/chat -s -v -t 60 ABORT "NO CARRIER" ABORT "NO DIALTONE" ABORT "BUSY" "" "AT+CGDCONT=1,"IP","orangeinternet"" OK "ATDT*99#" CONNECT "dd"\'
crtscts
lock
modem
usepeerdns
defaultroute
mtu 576
mru 576
connect-delay 1000
remotename IRDA1079225237
I then try to connect using
pppd call IRDA1079225237
My phone then asks me if I want to accept or reject the connection. I accept! :-)
But I don\'t seem to have a network connection on my Z. :-(
If I look at my /var/log/messages file I get this:
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo #[device name] keyword=value,keyword=value,... > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo # > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo #Keywords > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo #BaudRate^I:max baud rate(- 115200bps) > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo #MaxTurn^I:max turn time(- 500ms) > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo #MinTurn^I:min turn time(- 10000us) > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo #DataSize^I:max data size(- 2048bytes) > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost pppd[3158]: pppd 2.4.0 started by root, uid 0
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo #WindowSize^I:max window size(- 7) > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo #BOFS^I^I:additional bofs(- 48bytes) > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo #DiscTime^I:disconnect time(- 40secs) > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: +
Mar 21 23:46:37 localhost irattach: executing: \'echo [NM207] BaudRate=57600 > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: executing: \'echo [sharp pdaMI-500] BaudRate=57600 > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:37 localhost irattach: executing: \'echo [sharp pdaMI-100] BaudRate=57600 > /proc/sys/net/irda/specific_dev\'
Mar 21 23:46:45 localhost chat[3169]: abort on (NO CARRIER)
Mar 21 23:46:45 localhost chat[3169]: abort on (NO DIALTONE)
Mar 21 23:46:45 localhost chat[3169]: abort on (BUSY)
Mar 21 23:46:45 localhost chat[3169]: send (AT+CGDCONT=1,IP,orangeinternet^M)
Mar 21 23:46:45 localhost pppd[3158]: Hangup (SIGHUP)
Mar 21 23:46:45 localhost pppd[3158]: Connect script failed
Mar 21 23:46:45 localhost chat[3169]: SIGHUP
Mar 21 23:46:45 localhost chat[3169]: Can\'t restore terminal parameters: Input/output error
Mar 21 23:46:46 localhost pppd[3158]: Exit.
Mar 21 23:46:47 localhost exiting on signal 15
I feel that I\'m close to getting it working, and it might just need a bit of tweaking.
I\'m hoping someone here can tell me what I\'m doing wrong.
Thanks in advance for any help.
Sorry for the long post, but I wanted to provide as much info as possible.
- Mark
-
There\'s 2 reasons for that, either you\'re using the wrong init string or you\'re connected to the wrong channel. Try using Channel 2 and the init string AT&FE0V1&D2S0=0S7=10
When my Zaurus was working (it\'s currently bricked) that worked fine for me with Orange GPRS and my Nokia 6310i
-
Thanks for the suggestion foxdie.
I tried changing channel to 2 first.
No luck.
Then I changed the init string.
I\'m not familiar with these chat script and modem commands.
I hope I changed the right thing.
I created a new script as follows:
# cat foxdie
debug debug debug
/dev/rfcomm0
noipdefault
115200
connect \'/usr/sbin/chat -s -v -t 60 ABORT "NO CARRIER" ABORT "NO DIALTONE" ABORT "BUSY" "" "AT&FE0V1&D2S0=0S7=10" OK "ATDT*99#" CONNECT "dd"\'
crtscts
lock
modem
usepeerdns
defaultroute
mtu 576
mru 576
connect-delay 1000
remotename zaurus
Then I did \"pppd call foxdie\".
I had to do a few restarts, and fix a typo.
But it now seems to be getting further, but still no net connection:
The log gives me this:
Mar 27 16:01:44 localhost pppd[7503]: pppd 2.4.0 started by root, uid 0
Mar 27 16:01:47 localhost hcid[7476]: link_key_request (sba=D8:0B:05:02:90:00, dba=12:9A:14:D9:0A:00)
Mar 27 16:01:48 localhost chat[7505]: abort on (NO CARRIER)
Mar 27 16:01:48 localhost chat[7505]: abort on (NO DIALTONE)
Mar 27 16:01:48 localhost chat[7505]: abort on (BUSY)
Mar 27 16:01:48 localhost chat[7505]: send (AT&FE0V1&D2S0=0S7=10^M)
Mar 27 16:01:48 localhost chat[7505]: expect (OK)
Mar 27 16:01:48 localhost chat[7505]: AT&FE0V1&D2S0=0S7=10^M^M
Mar 27 16:01:48 localhost chat[7505]: OK
Mar 27 16:01:48 localhost chat[7505]: -- got it
Mar 27 16:01:48 localhost chat[7505]: send (ATDT*99#^M)
Mar 27 16:01:49 localhost chat[7505]: expect (CONNECT)
Mar 27 16:01:49 localhost chat[7505]: ^M
Mar 27 16:01:50 localhost chat[7505]: ^M
Mar 27 16:01:50 localhost chat[7505]: CONNECT
Mar 27 16:01:50 localhost chat[7505]: -- got it
Mar 27 16:01:50 localhost chat[7505]: send (dd^M)
Mar 27 16:01:52 localhost pppd[7503]: Serial connection established.
Mar 27 16:01:52 localhost pppd[7503]: Using interface ppp0
Mar 27 16:01:52 localhost pppd[7503]: Connect: ppp0 <--> /dev/rfcomm0
Mar 27 16:01:54 localhost modprobe: modprobe: Can\'t locate module ppp-compress-26
Mar 27 16:01:54 localhost modprobe: modprobe: Can\'t locate module ppp-compress-24
Mar 27 16:01:54 localhost modprobe: modprobe: Can\'t locate module ppp-compress-26
Mar 27 16:01:54 localhost modprobe: modprobe: Can\'t locate module ppp-compress-24
Mar 27 16:01:54 localhost pppd[7503]: Could not determine local IP address
Mar 27 16:02:06 localhost pppd[7503]: Connection terminated.
To test to see if I get a net connection I just try pinging a known IP address. That fails. If I try to view a web page in NetFront it says there\'s no connection.
Thanks again for your help.
I think I\'m definitely getting closer!
- Mark
-
It looks like the ROM you have doesn\'t support Orange GPRS\'s compression. I recommend you try the latest Cacko Qtopia ROM, it should increase your chances for a successful connect. It\'s the one I use and it was the simplest to set up to dial up with bluetooth / orange gprs.
-
Thanks for the info Foxdie.
Not the news I was hoping for though :-(
Looks I\'ll have to try a new ROM.
- Mark
-
The Cacko Qtopia ROM is near-identical to the old ROM, it\'s got a few interface tweaks and updates, you won\'t really notice the difference (unless you want to keep the japanese elements, in which case you shouldn\'t change the ROM).
-
I don\'t think it\'s the ROM. I connect to Orange UK GPRS via a Nokia 6600 using the standard Sharp ROM on a 5600 and get the same messages about the compression modules. I wouldn\'t have thought that the 5600 and C860 ROMs were all that different anyway.
All I have in my peers file is this:
/dev/rfcomm0
115200
connect \'/usr/sbin/chat -s -v -t 60 ABORT "NO CARRIER" ABORT "NO DIALTONE" ABORT "BUSY" "" "ATZ" OK "ATDT*99#" CONNECT\'
crtscts
noipdefault
modem
user "user"
usepeerdns
defaultroute
connect-delay 5000
remotename DialupBluetooth1067815189
(The Nokia phones don\'t require anything other than ATZ for the initialisation string when you set the default GPRS access point on the phone itself)
Try it without the mru and mtu settings.
-
Thanks for the reply Tumnus.
I gave that a go as well. Unfortunately I get the same results. :-(
This is what I get in my log file:
Mar 28 17:38:01 localhost pppd[8152]: pppd 2.4.0 started by root, uid 0
Mar 28 17:38:01 localhost hcid[8111]: link_key_request (sba=D8:0B:05:02:90:00, dba=12:9A:14:D9:0A:00)
Mar 28 17:38:02 localhost chat[8154]: abort on (NO CARRIER)
Mar 28 17:38:02 localhost chat[8154]: abort on (NO DIALTONE)
Mar 28 17:38:02 localhost chat[8154]: abort on (BUSY)
Mar 28 17:38:02 localhost chat[8154]: send (ATZ^M)
Mar 28 17:38:03 localhost chat[8154]: expect (OK)
Mar 28 17:38:03 localhost chat[8154]: ATZ^M^M
Mar 28 17:38:03 localhost chat[8154]: OK
Mar 28 17:38:03 localhost chat[8154]: -- got it
Mar 28 17:38:03 localhost chat[8154]: send (ATDT*99#^M)
Mar 28 17:38:03 localhost chat[8154]: expect (CONNECT)
Mar 28 17:38:03 localhost chat[8154]: ^M
Mar 28 17:38:05 localhost chat[8154]: ATDT*99#^M^M
Mar 28 17:38:05 localhost chat[8154]: CONNECT
Mar 28 17:38:05 localhost chat[8154]: -- got it
Mar 28 17:38:05 localhost pppd[8152]: Serial connection established.
Mar 28 17:38:05 localhost pppd[8152]: Using interface ppp0
Mar 28 17:38:05 localhost pppd[8152]: Connect: ppp0 <--> /dev/rfcomm0
Mar 28 17:38:10 localhost modprobe: modprobe: Can\'t locate module ppp-compress-26
Mar 28 17:38:10 localhost modprobe: modprobe: Can\'t locate module ppp-compress-24
Mar 28 17:38:10 localhost modprobe: modprobe: Can\'t locate module ppp-compress-26
Mar 28 17:38:10 localhost modprobe: modprobe: Can\'t locate module ppp-compress-24
Mar 28 17:38:11 localhost pppd[8152]: Could not determine local IP address
Mar 28 17:38:14 localhost pppd[8152]: Connection terminated.
Mar 28 17:38:14 localhost pppd[8152]: Connect time 0.1 minutes.
Mar 28 17:38:14 localhost pppd[8152]: Sent 77 bytes, received 64 bytes.
Mar 28 17:38:15 localhost pppd[8152]: Exit.
- Mark
-
The ATZ initialisation string will almost definitely not work with the Sony P800 given all other Sony Ericsons require a different initialisation string. It\'s possible that your problem is that you didn\'t get the initialisation string quite right in the first place.
Are you sure you have GPRS enabled on your Orange account for internet access as well as WAP? Can you browse the web (not WAP) directly via GPRS on your phone?
You might want to contact Orange Support. If you are persistent enough you may get through to second level support. When I last got through to them over a year ago they had a linux expert who was getting a Zaurus. He could still be there.
-
Yep, my p800 has been happily surfing the web and handling email for the past year (almost time to upgrade to a P900!).
Maybe I should upgrade to a Nokia instead.
I wouldn\'t be surprised if I got the initialisation string wrong, as I don\'t really know what I\'m doing. :-)
I\'ve tried different scripts that I\'ve found on the web.
Lots of people have got bluetooth working, and have published their config files. But they don\'t seem to work for me.
I\'ll try talking to Orange and see if I can get through to a linux expert.
Thanks for your help.
- Mark
-
Now that I re-read your post, I\'m guessing the init string is wrong, both those init strings (your original one and the one I specified) were for Nokia\'s with GPRS.
Try dialling up the old fashioned way to a regular POP, try the following:
username: uk2
password: uk2
telephone: 0845 6653000
That\'s a free ISP that\'s charged at local rate and you don\'t require an account with them.
If that works then it\'s the init string that\'s incorrect, else it\'s a PPPD or kernel/module problem.
Ps. Orange don\'t have linux experts on their staff, they only cater for windoze users. They could have changed that policy since I last asked them for linux support 6 months ago but I very much doubt it
-
Hi markb,
My guess about your problem, is that when you are connecting to the internet through your phone, the ppp script is selecting a WAP access point (with an access point name \'orangewap\') rather than a general-purpose GPRS one (with the access point name \'orangeinternet\'). Presumbably, the phone\'s built-in web browser is choosing the correct access point, but the Z isn\'t when you dial in. (A well-maintained list of Internet APN\'s is here (http://www.taniwha.org.uk/gprs.html))
There are normally two ways to select the correct access point. Your phone may have a setting to specify the default access point. Or, your phone may assign CID numbers to the access points. These are just numbers from 1 upwards in which case you should use the dialling code *99***x#, where x is the CID.
There is a third way, which I have read about at a few places (for example here (http://www.nowsms.com/discus/messages/1/369.html)) where you can specify the service name directly. In your case, you would dial like this: *99*orangeinternet# . I have never tried this, though.
I may have a chance to have a look at a friend\'s P800 in a day or two. If I can be more specific, and you haven\'t cracked it by then, I\'ll post again.
Good luck,
P.
-
Ps. Orange don\'t have linux experts on their staff, they only cater for windoze users. They could have changed that policy since I last asked them for linux support 6 months ago but I very much doubt it
They don\'t officially support it, but they do have quite a few geeks/techies at 2nd level support and so you could be lucky and get to speak to one who uses Linux themselves, like I did.
-
I haven\'t had much of a chance to play with bluetooth, but I wanted to thank everyone for their suggestions.
I\'ll post back if I make any progress.
Hopefully I\'ll have time to play tomorrow evening.
As far as tech support goes I think it just depends on who you\'re lucky (or unlucky) enough to get through to.
I had a problem with my broadband connection ages ago and phoned up blueyonder tech support. When he asked about my setup I was reluctant to say I was using Linux.
I expected him to say \"Sorry we only do windows\". But he said he used linux himself, and he was able to investigate my problem through the linux command line.
But that was \"unofficial & unsupported\". I was just lucky.
Sometimes we\'re unlucky. I\'m sure we\'ve all experienced bad tech support.
I won\'t mention any names. But if I give a hint you could probably fill in the blank: DE_L :-)
- Mark
-
Hi again,
Followup to my previous post:
(1) The *99*orangeinternet# form will not work - in my enthusiasm I hadn\'t read to the bottom of the post that I quoted above, where the original poster explaind that he mis-understood the syntax of the GPRS diallup string. There is a way of associating \"orangeinternet\" with a CID using modem commands something like AT +CGDCONT=1, \"IP\", \"orangeinternet\"; followed by ATD*99***1# . I won\'t quote a single reference, but if you Google on \"AT+CGDCONT\" APN (http://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=%22AT%2BCGDCONT%22+APN&btnG=Search) you will find lots of hints.
(2) Probably simpler, is to figure out the CID for the correct GPRS connection that is already set up and working on your phone, and use ATD*99***x#. You could try the brute force approach, and just try 1,2,3,4 ... for x until you find one that works, or get fed up. However, I have found a hint here (http://www.woggledog.com/index.asp?subject=GPRS) that you can query the phone to find out the CID numbers of the GPRS connections that are set up on it, by sending AT+CGDCONT? to the phone. I\'m not sure how to do this from the console, but presumably if you put this string in the correct file in /etc/ppp/peers instead of ATD*99# and then use it to pretend to dial up, the phone\'s response will appear in a file like /var/log/messages or /tmp/qpe-pppd-log (depending on your ROM).
(3) The P800 (unlike my own Nokia 7650) does not have a way of specifying the default GPRS APN to be used when dialling in with *99# - it looks like you have to get the CID right.
My gut feeling is that since you got as far as
Mar 27 16:01:49 localhost chat[7505]: expect (CONNECT)
Mar 27 16:01:49 localhost chat[7505]: ^M
Mar 27 16:01:50 localhost chat[7505]: ^M
Mar 27 16:01:50 localhost chat[7505]: CONNECT
Mar 27 16:01:50 localhost chat[7505]: -- got it
Mar 27 16:01:50 localhost chat[7505]: send (dd^M)
Mar 27 16:01:52 localhost pppd[7503]: Serial connection established.
Mar 27 16:01:52 localhost pppd[7503]: Using interface ppp0
Mar 27 16:01:52 localhost pppd[7503]: Connect: ppp0 <--> /dev/rfcomm0
and that you have been accessing the full internet from applications on your phone already, the only issue is making sure that the ppp connection from your Z is picking the correct GPRS connection on your phone.
Good luck,
P.
-
I have a SL5500, Bluemonkey BT card and Orange GPRS working with my Siemens S55. I used the Bluez Dial-up Applet (http://www.killefiz.de/zaurus/showdetail.php?app=1243).
My file in /etc/ppp/peers looks like this:
/dev/rfcomm0
115200
connect \'/usr/sbin/chat -s -v -t 60 ABORT "NO CARRIER" ABORT "NO DIALTONE" ABORT "BUSY" "" "AT+CGDCONT=1,"ip","orangeinternet","",0,0" OK "ATDT*99***1#" CONNECT\'
crtscts
noipdefault
modem
usepeerdns
defaultroute
connect-delay 5000
remotename DialupBluetooth107754387
-
Thanks everybody!
I finally got it working.
I now have a permanent grin on my face, and will soon run up a huge phone bill. :-)
This seems to be quite tricky to set up.
Even though the example scripts work for the people that posted them, they still didn\'t work for me. I ended up taking a bit of each.
I used the dial-up applet to start with then edited the file it created.
The init string that finally worked was just \"ATZ\".
I used the suggestion from pakman to find out what number I should be using for GPRS.
Mar 31 16:04:06 localhost chat[11409]: send (AT+CGDCONT?^M)
Mar 31 16:04:07 localhost chat[11409]: expect (OK)
Mar 31 16:04:07 localhost chat[11409]: AT+CGDCONT?^M^M
Mar 31 16:04:08 localhost chat[11409]: +CGDCONT: 1,"IP","","",0,0^M
Mar 31 16:04:08 localhost chat[11409]: +CGDCONT: 2,"IP","orangemms","",0,0^M
Mar 31 16:04:08 localhost chat[11409]: +CGDCONT: 3,"IP","orangeinternet","",0,0^M
Mar 31 16:04:08 localhost chat[11409]: ^M
Mar 31 16:04:08 localhost chat[11409]: OK
After that I gave \"ATD*99***3#\" a try and it worked!
I\'ve been through so many permutations that I\'ve lost track of which suggestions I\'ve been following. But you\'ve all been a big help. Thanks!
My final working script is:
/dev/rfcomm0
115200
connect \'/usr/sbin/chat -s -v -t 60 ABORT "NO CARRIER" ABORT "NO DIALTONE" ABORT "BUSY" "" "ATZ" OK "ATD*99***3#" CONNECT\'
crtscts
noipdefault
modem
usepeerdns
defaultroute
connect-delay 5000
remotename BLUETOOTH1080801963
By the way, I still get these messages, even though it works:
Mar 31 16:34:19 localhost modprobe: modprobe: Can\'t locate module ppp-compress-26
Mar 31 16:34:19 localhost modprobe: modprobe: Can\'t locate module ppp-compress-24
Mar 31 16:34:19 localhost modprobe: modprobe: Can\'t locate module ppp-compress-26
Mar 31 16:34:19 localhost modprobe: modprobe: Can\'t locate module ppp-compress-24
- Mark (A happy bunny)
p.s.
It worked once. But I can\'t get it to work again. :-(
Oh well, at least I know it CAN work with my C860 & P800. So I\'m still happy. :-)
-
Hi markb,
Good to hear that you got this far. I have the same problem with not being able to re-connect. I get a NO CARRIER error in the log file. If I try again I then get a \"serial line is looped back\" message, which AFAIK indicates some kind of timeout. I think that the problem is that the phone is not disconnecting cleanly from the Orange network at the end of the previous session, and it can take a long time before it can connect again. I have not got around to investigating this properly, but I have got into the habit of switching the phone off and on again after a GPRS session from the Z, which usually seems to fix the problem. Sometimes I think the Orange network is simply busy and doesn\'t accept new connections.
I believe that the modprobe kernel messages are part of the ppp negotiation over compression levels, and are nothing to worry about as such. It would be nice to know more about this - obviously with GPRS using the best compression can make a big difference to your bill . I\'ll get around to investigating this some day as well, I guess.
Regards,
P.
-
I get something like this
Connection: ppp0 <---> /dev/rfcomm0
lcp: timeout sending config-request
Connection terminated
Exit
I dont how to fix it ?
-
I get something like this
Connection: ppp0 <---> /dev/rfcomm0
lcp: timeout sending config-request
Connection terminated
Exit
If you see a line like ppp0 <---> /dev/rfcomm0 then the Bluetooth connection has been established, so your problem is with your ppp/carrier configuration.
To debug it more, you need to run pppd from the command line like this:
pppd call <peers_file> debug -detach
Where <peers_file> is the name of the file under /etc/ppp/peers that the network connection uses. To see which file is being used by a network connection, look in the files under /home/zaurus/Applications/Network/modules for the name of the network connection. The peers filename is the ID value in the matching .conf file.
-
Thanks
LCP said something about chanell 18
So i changed it to 18
Now i have some problem with bluetooth
Can't get terminal parameters: Input/output error
i change pin to 9999
Every time i try to connect i have to get pin on my siemens ?
What's wrong now
I change value in pin and givepin
I can connect thru irda with smaller problem (sometimes zaurus dosent see siemens)
-
Like I said, your bluetooth connection looks fine so there was no need to change anything to do with bluetooth. The LCP stuff has nothing to do with bluetooth, but if you copy the output from PPP here then someone might be able to help (might be best to start another thread though with the appropriate topic title)