I am trying to connect to wind network, using the internal HDSPA modem. My ppp client terminates with "IPCP: timeout sending Config-Requests". Disabling compression eliminates the error "Protocol-Reject for 'Compression Control Protocol' (0x80fd) received", but it don't resolve the problem. Using pap or chap don't resolve the problem. Any hint on how to resolve the problem?
alex
output of lsusb Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 0930:1302 Toshiba Corp. Wireless Broadband (3G HSDPA) SM-Bus Minicard Status Port Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c045 Logitech, Inc. Optical Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 004: ID 08ff:1600 AuthenTec, Inc. AES1600 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
---------- output of pppd call gprs pppd options in effect: debug # (from /etc/ppp/peers/gprs) kdebug 7 # (from /etc/ppp/options) nodetach # (from /etc/ppp/peers/gprs) dump # (from /etc/ppp/peers/gprs) noauth # (from /etc/ppp/peers/gprs) refuse-chap # (from /etc/ppp/peers/gprs) refuse-mschap # (from /etc/ppp/peers/gprs) refuse-mschap-v2 # (from /etc/ppp/peers/gprs) refuse-eap # (from /etc/ppp/peers/gprs) name Wind # (from /etc/ppp/peers/gprs) remotename Wind # (from /etc/ppp/peers/gprs) /dev/ttyUSB0 # (from /etc/ppp/peers/gprs) 9600 # (from /etc/ppp/peers/gprs) lock # (from /etc/ppp/options) connect /etc/ppp/peers/gprs-connect-chat # (from /etc/ppp/peers/ gprs) disconnect /etc/ppp/peers/gprs-disconnect-chat # (from /etc/ppp/peers/ gprs) crtscts # (from /etc/ppp/peers/gprs) local # (from /etc/ppp/peers/gprs) show-password # (from /etc/ppp/peers/gprs) ipcp-accept-local # (from /etc/ppp/peers/gprs) ipcp-accept-remote # (from /etc/ppp/peers/gprs) noipdefault # (from /etc/ppp/peers/gprs) ipcp-restart 100 # (from /etc/ppp/peers/gprs) ipcp-max-configure 2 # (from /etc/ppp/peers/gprs) defaultroute # (from /etc/ppp/peers/gprs) usepeerdns # (from /etc/ppp/peers/gprs) deflate 15 # (from /etc/ppp/peers/gprs) Press CTRL-C to close the connection at any stage! defining PDP context... AT OK ATH OK ATE1 OK ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK AT+CGDCONT=1,"IP","internet.wind","0.0.0.0",0,0 OK waiting for connect...
ATD*99***1# CONNECT Connected. If the following ppp negotiations fail, try restarting the phone.
Serial connection established. using channel 23 Using interface ppp0 Connect: ppp0 <--> /dev/ttyUSB0 sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x36ab7f47> <pcomp> <accomp>] rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth chap MD5> <magic 0x12a313b> <pcomp> <accomp>] sent [LCP ConfNak id=0x0 <auth pap>] rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x36ab7f47> <pcomp> <accomp>] rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <auth pap> <magic 0x12a313b> <pcomp> <accomp>] sent [LCP ConfAck id=0x1 <asyncmap 0x0> <auth pap> <magic 0x12a313b> <pcomp> <accomp>] sent [PAP AuthReq id=0x1 user="Wind" password="Wind"] rcvd [LCP DiscReq id=0x2 magic=0x12a313b] rcvd [PAP AuthAck id=0x1 ""] PAP authentication succeeded sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>] sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>] rcvd [LCP ProtRej id=0x3 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f] Protocol-Reject for 'Compression Control Protocol' (0x80fd) received sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>] IPCP: timeout sending Config-Requests sent [LCP TermReq id=0x2 "No network protocols running"] sent [LCP TermReq id=0x3 "No network protocols running"] Connection terminated. Serial link disconnected. connection at any stage! Modem hangup
file /etc/ppp/peers/gprs-connect-chat #!/bin/sh exec chat \ TIMEOUT 5 \ ECHO ON \ ABORT '\nBUSY\r' \ ABORT '\nERROR\r' \ ABORT '\nNO ANSWER\r' \ ABORT '\nNO CARRIER\r' \ ABORT '\nNO DIALTONE\r' \ ABORT '\nRINGING\r\n\r\nRINGING\r' \ '' '\rAT' \ TIMEOUT 12 \ SAY "Press CTRL-C to close the connection at any stage!" \ SAY "\ndefining PDP context...\n" \ OK 'ATH' \ OK 'ATE1' \ OK 'ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0' \ OK 'AT+CGDCONT=1,"IP","internet.wind","0.0.0.0",0,0'\ OK 'ATD*99***1#' \ TIMEOUT 22 \ SAY "\nwaiting for connect...\n" \ CONNECT '\d\c' \ SAY "\nConnected." \ SAY "\nIf the following ppp negotiations fail,\n" \ SAY "try restarting the phone.\n" #EOF
cla t <c.tamburr...@sns.it> wrote: > pppd version 2.4.4 > kernel Linux 2.6.27-11-generic > I am trying to connect to wind network, using the internal HDSPA modem. > My ppp client terminates with "IPCP: timeout sending Config-Requests". > Disabling compression eliminates the error "Protocol-Reject for > 'Compression Control Protocol' (0x80fd) received", but it don't resolve > the problem. Using pap or chap don't resolve the problem. > Any hint on how to resolve the problem?
I've not used GPRS but have seen enough posts to think PPP implementations for cell phones are often marginal.
Try adding the pppd option novj. If that doesn't work try removing the usepeerdns option and/or specifying a bogus local IP, e.g., "10.0.0.2:" If it still doesn't work try commenting out "ipcp-max-configure 2" and "ipcp-restart 100" (100 seconds is a _long_ time between IPCP requests and the limit of 2 such requests seems a little severe).
Modifying ipcp-max-configure and ipcp-restart does not resolve. With noccp i get ---------- sent [PAP AuthReq id=0x1 user="anon" password="anon"] rcvd [LCP DiscReq id=0xa magic=0xe2e628] rcvd [PAP AuthAck id=0x1 ""] PAP authentication succeeded sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>] sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>] IPCP: timeout sending Config-Requests sent [LCP TermReq id=0x2 "No network protocols running"] sent [LCP TermReq id=0x3 "No network protocols running"] Connection terminated. Serial link disconnected. connection at any stage! Modem hangup ---------- so the "Protocol-Reject" is not the problem. I think it is a driver problem. My modem is Manufacturer: Novatel Wireless Incorporated Model: Expedite EU870D MiniCard Revision: 10.9.0802.01-12 [2007-08-10 13:10:18] IMEI: <hidden> +GCAP: +CGSM,+DS It seems that it is a driver problem and that my modem will never work on linux (2.6.27-11), as read from http://ubuntuforums.org/showthread.php?t=740888 http://ubuntuforums.org/showthread.php?t=1059605
alex
Il Thu, 26 Mar 2009 14:20:21 -0500, Clifford Kite ha scritto:
> cla t <c.tamburr...@sns.it> wrote: >> pppd version 2.4.4 >> kernel Linux 2.6.27-11-generic
>> I am trying to connect to wind network, using the internal HDSPA modem. >> My ppp client terminates with "IPCP: timeout sending Config-Requests". >> Disabling compression eliminates the error "Protocol-Reject for >> 'Compression Control Protocol' (0x80fd) received", but it don't resolve >> the problem. Using pap or chap don't resolve the problem. Any hint on >> how to resolve the problem?
> I've not used GPRS but have seen enough posts to think PPP > implementations for cell phones are often marginal.
> Try adding the pppd option novj. If that doesn't work try removing the > usepeerdns option and/or specifying a bogus local IP, e.g., "10.0.0.2:" > If it still doesn't work try commenting out "ipcp-max-configure 2" and > "ipcp-restart 100" (100 seconds is a _long_ time between IPCP requests > and the limit of 2 such requests seems a little severe).
>> sent [LCP TermReq id=0x2 "No network protocols running"] sent [LCP >> TermReq id=0x3 "No network protocols running"] Connection terminated. >> Serial link disconnected. connection at any stage! Modem hangup
cla t <c.tamburr...@sns.it> wrote: > Modifying ipcp-max-configure and ipcp-restart does not resolve. > With noccp i get > ---------- > sent [PAP AuthReq id=0x1 user="anon" password="anon"] > rcvd [LCP DiscReq id=0xa magic=0xe2e628] > rcvd [PAP AuthAck id=0x1 ""] > PAP authentication succeeded > sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 > 0.0.0.0> <ms-dns2 0.0.0.0>] > sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 > 0.0.0.0> <ms-dns2 0.0.0.0>] > IPCP: timeout sending Config-Requests
This shows only 2 IPCP requests, the same as before. There should be 10 requests before a "timeout" occurs since the default ipcp-max-configure is 10. ??
> sent [LCP TermReq id=0x2 "No network protocols running"] > sent [LCP TermReq id=0x3 "No network protocols running"] > Connection terminated. > Serial link disconnected. connection at any stage! > Modem hangup > ---------- > so the "Protocol-Reject" is not the problem.
Agreed.
> I think it is a driver problem. > My modem is > Manufacturer: Novatel Wireless Incorporated > Model: Expedite EU870D MiniCard > Revision: 10.9.0802.01-12 [2007-08-10 13:10:18] > IMEI: <hidden> > +GCAP: +CGSM,+DS > It seems that it is a driver problem and that my modem will never work on > linux (2.6.27-11), as read from > http://ubuntuforums.org/showthread.php?t=740888 > http://ubuntuforums.org/showthread.php?t=1059605
Well, I saw no symptoms there that are comparable to yours. The fact that you get PPP negotiations started and some of which succeed makes me believe the "modem" is mostly doing it's job right.
Sometimes there can be some subtle thing that will cause a problem in some phase of PPP negotiations. You might try "nocrtscts" and see what happens. Since the PPP peer initially asked for CHAP it may not like PAP even though it asked for and got it after pppd NAKed CHAP and suggested PAP. Configuring /etc/ppp/chap-secrets is usually simple:
username * chap_secret
With appropriate substitutions for username and chap_secret of course.
Or the real authentication, which with PPP/GPRS takes place outside the purview of PPP, may be failing. AIUI (poorly) you usually won't get an IP address until that succeeds.
Finally, there was, and probably still is, a Linux PPP email group you can try, linux-...@vger.kernel.org.
-- Clifford Kite /* There are 10 types of people, those who can think in binary and those who can't */
> cla t <c.tamburr...@sns.it> wrote: >> Modifying ipcp-max-configure and ipcp-restart does not resolve. With >> noccp i get >> ---------- >> sent [PAP AuthReq id=0x1 user="anon" password="anon"] rcvd [LCP DiscReq >> id=0xa magic=0xe2e628] rcvd [PAP AuthAck id=0x1 ""] >> PAP authentication succeeded >> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 >> 0.0.0.0> <ms-dns2 0.0.0.0>] >> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 >> 0.0.0.0> <ms-dns2 0.0.0.0>] >> IPCP: timeout sending Config-Requests
> This shows only 2 IPCP requests, the same as before. There should be 10 > requests before a "timeout" occurs since the default ipcp-max-configure > is 10. ??
>> sent [LCP TermReq id=0x2 "No network protocols running"] sent [LCP >> TermReq id=0x3 "No network protocols running"] Connection terminated. >> Serial link disconnected. connection at any stage! Modem hangup >> ---------- >> so the "Protocol-Reject" is not the problem.
> Agreed.
>> I think it is a driver problem. >> My modem is >> Manufacturer: Novatel Wireless Incorporated Model: Expedite EU870D >> MiniCard >> Revision: 10.9.0802.01-12 [2007-08-10 13:10:18] IMEI: <hidden> >> +GCAP: +CGSM,+DS >> It seems that it is a driver problem and that my modem will never work >> on linux (2.6.27-11), as read from >> http://ubuntuforums.org/showthread.php?t=740888 >> http://ubuntuforums.org/showthread.php?t=1059605
> Well, I saw no symptoms there that are comparable to yours. The fact > that you get PPP negotiations started and some of which succeed makes me > believe the "modem" is mostly doing it's job right.
> Sometimes there can be some subtle thing that will cause a problem in > some phase of PPP negotiations. You might try "nocrtscts" and see what > happens. Since the PPP peer initially asked for CHAP it may not like > PAP even though it asked for and got it after pppd NAKed CHAP and > suggested PAP. Configuring /etc/ppp/chap-secrets is usually simple:
> username * chap_secret
> With appropriate substitutions for username and chap_secret of course.
> Or the real authentication, which with PPP/GPRS takes place outside the > purview of PPP, may be failing. AIUI (poorly) you usually won't get an > IP address until that succeeds.
> Finally, there was, and probably still is, a Linux PPP email group you > can try, linux-...@vger.kernel.org.
cla t <c.tamburr...@sns.it> wrote: > The datasheet http://www.novatelwireless.com/pdf/ > EU870D_Datasheet_0909.pdf includes linux 2.6.16 in the supported OS > list :o.
And it appears to be supported in your kernel version as well.
> I tried your parameters without success > output of ./gprs.sh > pppd options in effect: > debug # (from /etc/ppp/peers/gprs) > kdebug 7 # (from /etc/ppp/options) > nodetach # (from /etc/ppp/peers/gprs) > dump # (from /etc/ppp/peers/gprs) > noauth # (from /etc/ppp/peers/gprs) > refuse-pap # (from /etc/ppp/peers/gprs) > refuse-mschap # (from /etc/ppp/peers/gprs) > refuse-mschap-v2 # (from /etc/ppp/peers/gprs) > refuse-eap # (from /etc/ppp/peers/gprs) > name anon # (from /etc/ppp/peers/gprs) > remotename anon # (from /etc/ppp/peers/gprs) > /dev/ttyUSB0 # (from /etc/ppp/peers/gprs) > 9600 # (from /etc/ppp/peers/gprs) > lock # (from /etc/ppp/options) > connect /etc/ppp/peers/gprs-connect-chat # (from /etc/ppp/ > peers/gprs) > disconnect /etc/ppp/peers/gprs-disconnect-chat # (from /etc/ppp/ > peers/gprs) > nocrtscts # (from /etc/ppp/peers/gprs) > local # (from /etc/ppp/peers/gprs) > show-password # (from /etc/ppp/peers/gprs) > ipcp-accept-local # (from /etc/ppp/peers/gprs) > ipcp-accept-remote # (from /etc/ppp/peers/gprs) > noipdefault # (from /etc/ppp/options) > defaultroute # (from /etc/ppp/peers/gprs) > usepeerdns # (from /etc/ppp/options) > 10.0.0.2: # (from /etc/ppp/peers/gprs) > deflate 15 # (from /etc/ppp/peers/gprs) > Press CTRL-C to close the connection at any stage! > defining PDP context... > AT > OK > ATH > OK > ATE1 > OK > ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > OK > AT+CGDCONT=1,"IP","internet.wind","0.0.0.0",0,0 > OK > waiting for connect... > ATD*99***1# > CONNECT > Connected. > If the following ppp negotiations fail, > try restarting the phone. > Serial connection established. > using channel 1 > Using interface ppp0 > Connect: ppp0 <--> /dev/ttyUSB0 > sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x83571034> <pcomp> > <accomp>] > rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth chap MD5> <magic 0x155577f> > <pcomp> <accomp>] > sent [LCP ConfAck id=0x0 <asyncmap 0x0> <auth chap MD5> <magic 0x155577f> > <pcomp> <accomp>] > rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x83571034> <pcomp> > <accomp>] > rcvd [LCP DiscReq id=0x1 magic=0x155577f]
This is something I've never seen. It seems to be a "Discard Request." According to RFC 1661 it is used in debugging, testing and "numerous other functions." Most likely not related to your problem.
> rcvd [CHAP Challenge id=0x1 <8034f39d8210fcc9662ea0c3e08e4649>, name = > "UMTS_CHAP_SRVR"] > sent [CHAP Response id=0x1 <150ec4939de507c09b9feea5d832cd75>, name = > "anon"] > rcvd [CHAP Success id=0x1 ""] > CHAP authentication succeeded > CHAP authentication succeeded > sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>] > sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 > 0.0.0.0> <ms-dns2 0.0.0.0>] > rcvd [LCP ProtRej id=0x2 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 > 2f] > Protocol-Reject for 'Compression Control Protocol' (0x80fd) received > sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 > 0.0.0.0> <ms-dns2 0.0.0.0>]
<and 8 more IPCP ConfReqs>
Well you can stop using nocrtscts and "10.0.0.2:" since neither helped. :(
One last thing I can think of is to try the pppd "noccp" option which will disable the CCP ConfReq above. The pppd man pages say
noccp Disable CCP (Compression Control Protocol) negotia- tion. This option should only be required if the peer is buggy and gets confused by requests from pppd for CCP negotiation.
but since the peer sent a Protocol-Reject for CCP the chance of noccp helping seems slight.
As noted earlier GPRS level authentication (where the real authentication is done) failure could be the problem but I'm not able to help with that.
<...>
Good Luck!
-- Clifford Kite /* I gave up on politics when no matter who I voted for, I regretted it. * -- Pepper...and Salt, WSJ */
It may be that the modem is taking a while to register to the GSM/3G network, and it doesn't have an IP address to give.
If this is a plugin modem, try adding a delay for a minute or two, or ten, before calling and setting up the GPRS/3G data connections with pppd. Increasing pppd option ipcp-max-configure might also help.
> On 2009-03-30, cla t <c.tamburr...@sns.it> wrote: >> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 >> 0.0.0.0> <ms-dns2 0.0.0.0>] >> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 >> 0.0.0.0> <ms-dns2 0.0.0.0>] >> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 >> 0.0.0.0> <ms-dns2 0.0.0.0>] >> sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 10.0.0.2> <ms-dns1 >> 0.0.0.0> <ms-dns2 0.0.0.0>] >> IPCP: timeout sending Config-Requests sent [LCP TermReq id=0x2 "No >> network protocols running"] sent [LCP TermReq id=0x3 "No network >> protocols running"] Connection terminated.
> It may be that the modem is taking a while to register to the GSM/3G > network, and it doesn't have an IP address to give.
> If this is a plugin modem, try adding a delay for a minute or two, or > ten, before calling and setting up the GPRS/3G data connections with > pppd. Increasing pppd option ipcp-max-configure might also help.
> -Mikko
with ipcp-max-configure 30 140 secs before ATD 140 secs after CONNECT the situation is the same.
> with > ipcp-max-configure 30 > 140 secs before ATD > 140 secs after CONNECT > the situation is the same.
Has PIN query been disabled from SIM? Have you double checked APN, usernames and passwords for the data connection? Does the device have leds to indicate network registration status (off, GSM, UMTS etc)?
Perhaps the device is just waiting for you to enter the PIN number for the SIM card. An AT command reference for the modem would help in this and other status checks. Or rely on the standard GSM AT commands.
> On 2009-04-01, cla t <c.tamburr...@sns.it> wrote: >> with >> ipcp-max-configure 30 >> 140 secs before ATD >> 140 secs after CONNECT >> the situation is the same.
> Has PIN query been disabled from SIM? Have you double checked APN, > usernames and passwords for the data connection? Does the device have > leds to indicate network registration status (off, GSM, UMTS etc)?
> Perhaps the device is just waiting for you to enter the PIN number for > the SIM card. An AT command reference for the modem would help in this > and other status checks. Or rely on the standard GSM AT commands.
> -Mikko
PIN query has been disabled with a mobile. The SIM works fine for making calls (with a mobile) and for connecting to internet with windows vista (same hardware). There are no modem leds (laptop toshiba portege r500-12r). APN (internet.wind) is correct (anyway, also internet.wind.biz has been tested). I found almost no reference on google of people making this hardware (novatel eu870d) work with linux. Only a line on https:// wiki.edubuntu.org/NetworkManager/Hardware/3G says that "Dell 5520 Mobile Broadband" aka "Novatel Wireless Expedite EU870D MiniCard" works, in a very particular situation (in australia, with linux kernel older than 2.6.22).
> PIN query has been disabled with a mobile. The SIM works fine for making > calls (with a mobile) and for connecting to internet with windows vista > (same hardware). There are no modem leds (laptop toshiba portege > r500-12r). APN (internet.wind) is correct (anyway, also internet.wind.biz > has been tested). I found almost no reference on google of people making > this hardware (novatel eu870d) work with linux. Only a line on https:// > wiki.edubuntu.org/NetworkManager/Hardware/3G says that "Dell 5520 Mobile > Broadband" aka "Novatel Wireless Expedite EU870D MiniCard" works, in a > very particular situation (in australia, with linux kernel older than > 2.6.22).
You could take an AT command log from Vista to see if there's something different compared to your Linux setup. I don't think this is a pppd or Linux kernel related problem anymore. AT command reference for the modem could help too.
> On 2009-04-01, cla t <c.tamburr...@sns.it> wrote: >> PIN query has been disabled with a mobile. The SIM works fine for >> making calls (with a mobile) and for connecting to internet with >> windows vista (same hardware). There are no modem leds (laptop toshiba >> portege r500-12r). APN (internet.wind) is correct (anyway, also >> internet.wind.biz has been tested). I found almost no reference on >> google of people making this hardware (novatel eu870d) work with linux. >> Only a line on https:// wiki.edubuntu.org/NetworkManager/Hardware/3G >> says that "Dell 5520 Mobile Broadband" aka "Novatel Wireless Expedite >> EU870D MiniCard" works, in a very particular situation (in australia, >> with linux kernel older than 2.6.22).
> You could take an AT command log from Vista to see if there's something > different compared to your Linux setup. I don't think this is a pppd or > Linux kernel related problem anymore. AT command reference for the modem > could help too.
> -Mikko
Vista logs are too long, so i send them via link. http://k2.sns.it/~alex/modem_vista.log http://k2.sns.it/~alex/ppp_vista.log I translated some lines in modem_vista.log. I made my chat script look very similar to vista result. Seems that vista calls ATD*##***##, but if I try to call that number, I get NO CARRIER, so I am still calling ATD*99***1#. Seems that vista uses very strange ppp authentication, I really don't know how to make it similar in linux. Till now, the situation is the same (ten [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>] sent, zero reply rcvd).
> I made my chat script look very similar to vista result.
Vista is not setting up the APN with AT+CGDCONT and it's relying on the phone/SIM to know it. Perhaps removing the APN name setting from Linux side helps.
On Apr 1, 3:53 pm, cla t <c.tamburr...@sns.it> wrote:
> PIN query has been disabled with a mobile. The SIM works fine for making > calls (with a mobile) and for connecting to internet with windows vista > (same hardware). There are no modem leds (laptop toshiba portege > r500-12r). APN (internet.wind) is correct (anyway, also internet.wind.biz > has been tested). I found almost no reference on google of people making > this hardware (novatel eu870d) work with linux. Only a line on https:// > wiki.edubuntu.org/NetworkManager/Hardware/3G says that "Dell 5520 Mobile > Broadband" aka "Novatel Wireless Expedite EU870D MiniCard" works, in a > very particular situation (in australia, with linux kernel older than > 2.6.22).
Hi,
I have your same laptop and your same problems in getting the hardware to work. Here's what i was able to do until today:
* Patched the option kernel driver to detect this device (it's just a matter of adding the usb id to the code). This results in a better error handling of the ppp session, no more hanging for some seconds, but a clear hangup from the modem. * I subscribed to the novatel developer's lounge and downloaded their Linux SDK, this allows me to talk to the modem on the status port using novatel's propietary protocol. * With this SDK I discovered that the device is in Low Power Mode, and needs to be turnd on in order to work correctly. Unfortunately the SDK command to do this fails for me. * Novatel is investigating on the case and tryng to help me out on this issue.
spleen.level...@gmail.com writes: > * With this SDK I discovered that the device is in Low Power Mode, and > needs to be turnd on in order to work correctly. Unfortunately the SDK > command to do this fails for me.
It's been a while, have you had any further progress on this? I got so far today as to installing the Novatel SDK and compiling your (I suppose?) example code from the forum, but then I realized I didn't have a patched option driver handy and as I was running Ubuntu 8.10 live from a USB stick, I decided I'll save that exercise for another day...
> PIN query has been disabled with a mobile. The SIM works fine for making > calls (with a mobile) and for connecting to internet with windows vista > (same hardware). There are no modem leds (laptop toshiba portege > r500-12r). APN (internet.wind) is correct (anyway, also internet.wind.biz > has been tested). I found almost no reference on google of people making > this hardware (novatel eu870d) work with linux. Only a line on https:// > wiki.edubuntu.org/NetworkManager/Hardware/3G says that "Dell 5520 Mobile > Broadband" aka "Novatel Wireless Expedite EU870D MiniCard" works, in a > very particular situation (in australia, with linux kernel older than > 2.6.22).
I get a similar behaviour on a Toshiba Portege R600 but with a different 3g module. The problem is the rfkill switch of the Toshiba laptop, which turns the device off by default. The solution is to patch the toshiba_acpi module and enable the device, see this Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/359474
Martin <martin.schlaef...@gmail.com> writes: > I get a similar behaviour on a Toshiba Portege R600 but with a > different 3g module. The problem is the rfkill switch of the Toshiba > laptop, which turns the device off by default. The solution is to > patch the toshiba_acpi module and enable the device, see this Ubuntu > bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/359474 > Maybe this also solves your problem...
The real solution for us is using toshset 1.75 which added support for enabling 3G in Linux and the R500. One still needs the toshiba_acpi patch from http://memebeam.org/toys/ExperimentalToshibaAcpiDriver and also the Option driver needs to be patched so that it has Toshiba's vendor and product ID's. Alternatively, usbserial driver works too, at least for lower speeds.
The patch for the option driver will probably be included in kernel 2.6.31 but toshiba_acpi is orphaned so the need to patch probably remains indefinitely...
> Martin <martin.schlaef...@gmail.com> writes: > > I get a similar behaviour on a Toshiba Portege R600 but with a > > different 3g module. The problem is the rfkill switch of the Toshiba > > laptop, which turns the device off by default. The solution is to > > patch the toshiba_acpi module and enable the device, see this Ubuntu > > bug report:https://bugs.launchpad.net/ubuntu/+source/linux/+bug/359474 > > Maybe this also solves your problem...
> The real solution for us is using toshset 1.75 which added support for > enabling 3G in Linux and the R500. One still needs the toshiba_acpi > patch fromhttp://memebeam.org/toys/ExperimentalToshibaAcpiDriverand > also the Option driver needs to be patched so that it has Toshiba's > vendor and product ID's. Alternatively, usbserial driver works too, at > least for lower speeds.
> The patch for the option driver will probably be included in kernel > 2.6.31 but toshiba_acpi is orphaned so the need to patch probably > remains indefinitely...
Can you please explain in a step by step guide how to fix this for a freshly installed linux (e.g. ubuntu 9.04). How to install/compile toshset, do the patch...etc. You would be doing all built-in 3G modems owners a big favor!
> On Jun 22, 11:58 pm, Anssi Saari <a...@sci.fi> wrote:
> > Martin <martin.schlaef...@gmail.com> writes: > > > I get a similar behaviour on a Toshiba Portege R600 but with a > > > different 3g module. The problem is the rfkill switch of the Toshiba > > > laptop, which turns the device off by default. The solution is to > > > patch the toshiba_acpi module and enable the device, see this Ubuntu > > > bug report:https://bugs.launchpad.net/ubuntu/+source/linux/+bug/359474 > > > Maybe this also solves your problem...
> > The real solution for us is using toshset 1.75 which added support for > > enabling 3G in Linux and the R500. One still needs the toshiba_acpi > > patch fromhttp://memebeam.org/toys/ExperimentalToshibaAcpiDriverand > > also the Option driver needs to be patched so that it has Toshiba's > > vendor and product ID's. Alternatively, usbserial driver works too, at > > least for lower speeds.
> > The patch for the option driver will probably be included in kernel > > 2.6.31 but toshiba_acpi is orphaned so the need to patch probably > > remains indefinitely...
> Can you please explain in a step by step guide how to fix this for a > freshly installed linux (e.g. ubuntu 9.04). How to install/compile > toshset, do the patch...etc. You would be doing all built-in 3G modems > owners a big favor!
> Thanks in advance...
> Yahya
Thanks guys, I was able to manage. It is now working with only one problem in Gnome's nm-applet. The applet detects two 3g modems instead of one. This results in a very wide list because it displays the full name of the device:
Mobile Broadband (Toshiba Wireless Broadband (3G HSDPA) SM-Bus Minicard Status Port).
I am going to go through the process again then writeup the step by step guide for others.
