LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 12-13-2010, 06:01 PM   #1
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 12.04LTS, Debian 7.5
Posts: 61

Rep: Reputation: 2
Problem with Sierra Wirelss AC850 under Ubuntu 10.04 (addendum)


I'm starting a new thread, because the one I started a few months ago does not appear to be getting any repeonses.

To see the previous thread:
http://www.linuxquestions.org/questi...-koala-804371/

I've come a bit further than then. The chat script now has the AT_OPSYS command removed as a result of my experiments talking to the card directly with screen /dev/umts.

The script /etc/ppp/peers/eplus now looks like this:
Quote:
-detach
/dev/umts
460800
debug
defaultroute
usepeerdns
user wapuser1
show-password
crtscts
lock
##
## the eplus version with symlinkk /dev/umts...
##
#/dev/ttyUSB0
#/dev/umts
#460800
#crtscts
#lock
#defaultroute
#mtu 1500
#mru 1500
#debug
#idle 300
idle 30
##
## some other options (including compression protocol stuff)
##
noccp
noauth
noipdefault
novj
nomagic
maxfail 40
persist
##
## Specify user and call chat script
##
#user umts
user eplus
connect '/usr/sbin/chat -v -f /etc/chatscripts/eplus'
The persist and maxfail 40 options only serve to allow the chatscript to try again every 30 seconds or so. Occassionaly I also get a "NO CARRIER" reasponse, which I guess is to be expected.

The chat script looks like this:
Quote:
TIMEOUT 240
ABORT "NO CARRIER"
ABORT "NO DIALTONE"
ABORT "ERROR"
ABORT "NO ANSWER"
ABORT "BUSY"
#"" "+++atz"
"" "ATZ"
OK "ATE0V1"
#OK "AT_OPSYS=3,2"
#OK "AT_OPSYS=1,2"
OK AT+CGDCONT=1,"IP","internet.eplus.de","",0,0
OK "ATD*99***1#"
"CONNECT" ""
The command "AT_OPSYS=3,2" (or whatever) are not recognised by the air card. That is somethibg I discovered by talking to the card directly wit the screeen command.

The result as shown by /var/log/syslog:
Quote:
Dec 7 19:50:07 achim-laptop chat[2540]: CONNECT
Dec 7 19:50:07 achim-laptop chat[2540]: -- got it
Dec 7 19:50:07 achim-laptop chat[2540]: send (^M)
Dec 7 19:50:07 achim-laptop pppd[2536]: Script /usr/sbin/chat -v -f /etc/chatscripts/eplus finished (pid 2539), status = 0x0
Dec 7 19:50:07 achim-laptop pppd[2536]: Serial connection established.
Dec 7 19:50:07 achim-laptop pppd[2536]: using channel 3
Dec 7 19:50:07 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Dec 7 19:50:07 achim-laptop NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Dec 7 19:50:07 achim-laptop pppd[2536]: Using interface ppp0
Dec 7 19:50:07 achim-laptop pppd[2536]: Connect: ppp0 <--> /dev/umts
Dec 7 19:50:08 achim-laptop pppd[2536]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <pcomp> <accomp>]
Dec 7 19:50:08 achim-laptop pppd[2536]: rcvd [LCP ConfReq id=0x3 <asyncmap 0x0> <auth chap MD5> <magic 0x8228888> <pcomp> <accomp>]
Dec 7 19:50:08 achim-laptop pppd[2536]: sent [LCP ConfRej id=0x3 <magic 0x8228888>]
Dec 7 19:50:08 achim-laptop pppd[2536]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <pcomp> <accomp>]
Dec 7 19:50:08 achim-laptop pppd[2536]: rcvd [LCP ConfReq id=0x4 <asyncmap 0x0> <auth chap MD5> <pcomp> <accomp>]
Dec 7 19:50:08 achim-laptop pppd[2536]: sent [LCP ConfAck id=0x4 <asyncmap 0x0> <auth chap MD5> <pcomp> <accomp>]
Dec 7 19:50:08 achim-laptop pppd[2536]: sent [LCP EchoReq id=0x0 magic=0x0]
Dec 7 19:50:08 achim-laptop pppd[2536]: rcvd [LCP DiscReq id=0x5 magic=0x8228888]
Dec 7 19:50:08 achim-laptop pppd[2536]: rcvd [CHAP Challenge id=0x1 <0c5dd2dd9a30db1dc6dd532142030509>, name = "UMTS_CHAP_SRVR"]
Dec 7 19:50:08 achim-laptop pppd[2536]: sent [CHAP Response id=0x1 <a00984bbaeab0a552df8b36a82e29237>, name = "eplus"]
Dec 7 19:50:08 achim-laptop pppd[2536]: rcvd [LCP EchoRep id=0x0 magic=0x8228888 00 00 00 00]
Dec 7 19:50:08 achim-laptop pppd[2536]: rcvd [CHAP Success id=0x1 ""]
Dec 7 19:50:08 achim-laptop pppd[2536]: CHAP authentication succeeded
Dec 7 19:50:08 achim-laptop pppd[2536]: CHAP authentication succeeded
Dec 7 19:50:08 achim-laptop pppd[2536]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
Dec 7 19:50:08 achim-laptop pppd[2536]: Modem hangup
Dec 7 19:50:08 achim-laptop pppd[2536]: Connection terminated.
Doe anybody have any idea what so ever what in the blue blazes causes my card to hang up as soon as a connection is made?

Help please! Somebody must have a clue...

Thanks

Achim
 
Old 12-18-2010, 02:18 AM   #2
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,441
Blog Entries: 3

Rep: Reputation: 182Reputation: 182
I have looked at all your post from all the other sites. and seems you just need to make sure you have not messed up anything. Put everything back to the way the distro comes all configurations. Start from square one. Think wifi that uses pppd. Now read this real good. and then we will let the operating system run the protocols.
Quote:
Connect using KPPP (Recommended).
Ok now I find kpppd works much better than gnome-pppd.
kubuntu 9.04 supports that old device out of the box. Thats if you want to run UBUNTU.

Last edited by Drakeo; 12-18-2010 at 02:28 AM.
 
Old 12-20-2010, 04:24 AM   #3
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 12.04LTS, Debian 7.5
Posts: 61

Original Poster
Rep: Reputation: 2
Thanks very much for the response, Drakeo.

I don't think I've messed anything up, but to be absolutely sure, I will do as you suggest. I have tried the Sierra Wireless site before (something over a year ago) and the instructions were incomplete (in some aspects just plain wrong). I note that there was a problem with Ubuntu 9.10 that should've been fixed in 10.4. If It hasn't been fixed, then that might be the cause of my problem... there isn't any further detail on that page, but maybe I can find something elsewhere on the SW site.

I'll have a go at reinstalling drivers and scripts from scratch after work. I'll let you know what happened.

Thanks again

Achim
 
Old 12-20-2010, 02:26 PM   #4
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 12.04LTS, Debian 7.5
Posts: 61

Original Poster
Rep: Reputation: 2
Hi again Drakeo,

I just finished reading through the instructions on the SW site. It would seem, from the table in section 1 (Supported modems), that the AC850 is not supported. Not discouraged (yet) I read on.

Now I have to take a deep breath and plow on, because everything I've set up to date will have to be scrapped. It means removing a whole set of files and commenting out a lot of code...

Here goes nothin'... I'll keep you posted.

Achim
 
Old 12-20-2010, 02:40 PM   #5
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,441
Blog Entries: 3

Rep: Reputation: 182Reputation: 182
did you read this
 
Old 12-22-2010, 03:28 PM   #6
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 12.04LTS, Debian 7.5
Posts: 61

Original Poster
Rep: Reputation: 2
Some more interesting info

Hi again Drakeo,

Firstly, in response to your last post: Yes, I have been aware of the card identification problem for some time. In any event, the firmware is definitely being found and aparently works. Here is an extract out of dmesg from an earlier attempt:

Quote:
[ 795.208086] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 795.208100] pcmcia_socket pcmcia_socket0: cs: memory probe 0xd0000000-0xd7ffffff: excluding 0xd0000000-0xd7ffffff
[ 795.208143] pcmcia_socket pcmcia_socket0: cs: memory probe 0xb4000000-0xbfffffff: excluding 0xb4000000-0xb47fffff 0xb8000000-0xbbffffff
[ 795.214081] pcmcia 0.0: pcmcia: registering new device pcmcia0.0
[ 795.258108] pcmcia 0.0: firmware: requesting SW_8xx_SER.cis
[ 795.326704] 0.0: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
In the end I did not use the instructions on the site you suggested, because my card is not in the list of supported cards (old or not, it works well under Windoze). Instead I found the following info, also at sierra wireless:
http://sierrawireless.custhelp.com/a...-850%2F860,-ac

It is interesting to note that this and other sites always state that the firmware should be in /lib/firmware but ubuntu 10.4 already has it in /lib/firmware/cis. I have it in both locations, just to be on the safe side.

The problem occurs when my modem requests IP and DNS addresses:

Quote:
Dec 7 19:50:08 achim-laptop pppd[2536]: CHAP authentication succeeded
Dec 7 19:50:08 achim-laptop pppd[2536]: CHAP authentication succeeded
Dec 7 19:50:08 achim-laptop pppd[2536]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
Dec 7 19:50:08 achim-laptop pppd[2536]: Modem hangup
Dec 7 19:50:08 achim-laptop pppd[2536]: Connection terminated.
I found the following gem of information at http://osr507doc.sco.com/en/NetAdminG/pppT.tsneg.html:

Quote:
Authentication stage
As mentioned above, this stage is optional and only occurs if either the local or remote system requires authentication for this connection. Lines 57-70 in ``Sample logfile of PPP negotiation'' show a typical authentication negotiation.

If IPCP entries appear for your interface, then the authentication stage was successful. If no IPCP entries appear and LCP appears to have completed successfully (no NAKs or Rejects on LCP stage packets), then a problem is likely with authentication. Look for an authentication entry with a PAP or CHAP failure indicated. Typical problems here are the sending of an incorrect password or incorrect packet ID. See the pppauth(SFF) manual page for more information on authentication entries and exchanges.

IPCP stage
If all of the preceding stages appear successful but the connection still fails, the problem is in the IPCP negotiation stage. The following parameters are negotiated at this stage: IP addresses and Van Jacobson TCP/IP header compression. The typical problem at this stage is a disagreement about these parameters between the local and remote systems. If this occurs, you will see a NAK or Reject entry for a particular parameter. Try changing the value/state of the parameter causing the NAK or rejection.
Since, in my case, the problem occurs in the IPCP negotiation, it would appear that there are no authentication problems. So where does that leave me? There are huge numbers of posts about IPCP negotiation, so others have obviously had similar problems.

Kppp is not an option (yet), because to install it you need a package manager and, hence, an internet connection. I tried downloading the individual packages (when they were not already installed) but ended up with 3 tiers of dependancies and decided to wait until I get home and can use Synaptic to handle it.

The season of good cheer is upon us and there are other things taking up our time. I will have a go at installing kppp between Christmas and the new year and I will keep on trawling through the many posts on various forums.

If, or rather when I find the solution, I will post it. As always any, and I do mean ANY, suggestions are more than welcome.

A merry Christmas to all reading this forum.

Achim
 
Old 12-23-2010, 11:14 AM   #7
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,441
Blog Entries: 3

Rep: Reputation: 182Reputation: 182
seems KDE kppd will configure this for you. In gnome Ubuntu you can still install kppd
 
Old 01-02-2011, 11:21 AM   #8
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 12.04LTS, Debian 7.5
Posts: 61

Original Poster
Rep: Reputation: 2
Hi again,

I spent some time trying various things. Firstly I installed kppp and wvdial. I therefore have everything needed to apply the instructions on the aforementioned Sierra Wireless page.

(Note: the dates on the outputs below should be ignored. I had to redo some stuff, because I didn't save the output at the first attempt.)

In accordance with the instructions I tried wvdialconf create. The first time it failed. I figured I would try configuring kppp anyway and quickly discovered that my device symlink (/dev/umts) is not available in kppp, but /dev/modem is in the list. Hence I changed my udev rule as follows:

Quote:
BUS=="pcmcia", SYSFS{card_id}=="0x0710", NAME="modem", SYMLINK="tts/modem"
Restarting udev gave the following result in /var/log/syslog:

Quote:
Jan 2 16:47:46 achim-laptop udevd[302]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /lib/udev/rules.d/99-aircard.rules:6
Jan 2 16:47:46 achim-laptop udevd[302]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /lib/udev/rules.d/99-aircard.rules:6
Jan 2 16:47:46 achim-laptop udevd[302]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /lib/udev/rules.d/99-aircard.rules:6
Jan 2 16:47:46 achim-laptop udevd[302]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /lib/udev/rules.d/99-aircard.rules:6
Jan 2 16:47:52 achim-laptop udevd[2524]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /lib/udev/rules.d/99-aircard.rules:6
Jan 2 16:47:52 achim-laptop udevd[2524]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /lib/udev/rules.d/99-aircard.rules:6
Jan 2 16:47:52 achim-laptop kernel: [20820.119922] udev: starting version 151
So at some future stage I'm going to have to change the udev rule, I suppose. None-the-less the device was mapped to /dev/modem and I could continue. Before I did anything else, I tried wvdialconf create again and got the following response:

Quote:
Editing `create'.

Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1
ttyS2<*1>: ATQ0 V1 E1 -- OK
ttyS2<*1>: ATQ0 V1 E1 Z -- OK
ttyS2<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyS2<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyS2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyS2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyS2<*1>: Modem Identifier: ATI -- Manufacturer: Sierra Wireless, Inc.
ttyS2<*1>: Speed 4800: AT -- OK
ttyS2<*1>: Speed 9600: AT -- OK
ttyS2<*1>: Speed 19200: AT -- OK
ttyS2<*1>: Speed 38400: AT -- OK
ttyS2<*1>: Speed 57600: AT -- OK
ttyS2<*1>: Speed 115200: AT -- OK
ttyS2<*1>: Max speed is 115200; that should be safe.
ttyS2<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found a modem on /dev/ttyS2.
create<Warn>: Can't open 'create' for reading: No such file or directory
create<Warn>: ...starting with blank configuration.
Modem configuration written to create.
ttyS2<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
At this point the light on the card is flashing orange, not green, so something isn't quite right. Hence, I also tried the following:

Quote:
achim@achim-laptop:/var/log$ pccardctl ident
Socket 0:
product info: "Sierra Wireless", "AC850", "3G Network Adapter", "R1"
manfid: 0x0192, 0x0710
function: 2 (serial)
This is as expected, so I plowed on regardless. Next step was to try configuring kppp. I selected /dev/modem as the device. I then went to the "Modem" tab and clicked the button "Query Modem...". The modem was found and determined to be ready. Kppp then issued 7 ATI-comands. the response from each one looked something like this:

Quote:
Manufacturer: Sierra Wireless, Inc. Model: AC850 Revision: U1_2_34ACAP G:/WS/FW/U1_2_34ACAP/MSM6275/SRC 2006/07/14 13:51:14 IMEI: 357807000599131 IMEI SV: 17 FSN: X161116164211 3GPP Release 5 +GCAP: +CGSM,+DS,+ES 1980/01/06 00:13:40
Next I set up the account. I know from earlier experimentation that both PAP and CHAP work with eplus as ISP, so I initially left the PAP/CHAP authentication setting. This got me an immediate "ERROR". So I tried just PAP as suggested by Sierra Wireless. This gave the following response in the log window:

Quote:
AT+CGDCONT=1,"IP","internet.eplus.de","",0,0
OK
ATM1L1
OK
ATX3
OK
ATDT*99#
CONNECT
Since I set the option to auto redial when disconnected and similar stuff, this response comes up again and again. Note that my card was still flashing orange!

I'd really like to know what is happening but /var/log/syslog only gives the following information:

Quote:
Jan 2 17:42:35 achim-laptop pppd[2782]: Using interface ppp0
Jan 2 17:42:35 achim-laptop pppd[2782]: Connect: ppp0 <--> /dev/modem
Jan 2 17:42:35 achim-laptop kernel: [24103.516772] PPP BSD Compression module registered
Jan 2 17:42:35 achim-laptop kernel: [24103.584985] PPP Deflate Compression module registered
Jan 2 17:43:05 achim-laptop pppd[2782]: Terminating on signal 15
Jan 2 17:43:05 achim-laptop pppd[2782]: Connection terminated.
Jan 2 17:43:05 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 2 17:43:05 achim-laptop pppd[2782]: Exit.
Jan 2 17:43:10 achim-laptop pppd[2805]: pppd 2.4.5 started by achim, uid 1000
Jan 2 17:43:10 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 2 17:43:10 achim-laptop NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Jan 2 17:43:10 achim-laptop pppd[2805]: Using interface ppp0
Jan 2 17:43:10 achim-laptop pppd[2805]: Connect: ppp0 <--> /dev/modem
Jan 2 17:43:40 achim-laptop pppd[2805]: Terminating on signal 15
Jan 2 17:43:40 achim-laptop pppd[2805]: Connection terminated.
Jan 2 17:43:40 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
That last bit just kept repeating. Then I tried just CHAP authentication and got the following in /var/log/syslog:

Quote:
Jan 2 17:58:39 achim-laptop pppd[3290]: Using interface ppp0
Jan 2 17:58:39 achim-laptop pppd[3290]: Connect: ppp0 <--> /dev/modem
Jan 2 17:58:39 achim-laptop pppd[3290]: CHAP authentication succeeded
Jan 2 17:58:39 achim-laptop pppd[3290]: CHAP authentication succeeded
Jan 2 17:58:47 achim-laptop pppd[3290]: Hangup (SIGHUP)
Jan 2 17:58:47 achim-laptop pppd[3290]: Modem hangup
Jan 2 17:58:47 achim-laptop pppd[3290]: Connection terminated.
Jan 2 17:58:47 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 2 17:58:47 achim-laptop pppd[3290]: Exit.
Jan 2 17:58:52 achim-laptop pppd[3302]: pppd 2.4.5 started by achim, uid 1000
Jan 2 17:58:52 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 2 17:58:52 achim-laptop NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Jan 2 17:58:52 achim-laptop pppd[3302]: Using interface ppp0
Jan 2 17:58:52 achim-laptop pppd[3302]: Connect: ppp0 <--> /dev/modem
Jan 2 17:58:52 achim-laptop pppd[3302]: CHAP authentication succeeded
Jan 2 17:58:52 achim-laptop pppd[3302]: CHAP authentication succeeded
Jan 2 17:58:52 achim-laptop pppd[3302]: Hangup (SIGHUP)
Jan 2 17:58:52 achim-laptop pppd[3302]: Modem hangup
Jan 2 17:58:52 achim-laptop pppd[3302]: Connection terminated.
Jan 2 17:58:52 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 2 17:58:52 achim-laptop pppd[3302]: Exit.
Jan 2 17:58:57 achim-laptop pppd[3318]: pppd 2.4.5 started by achim, uid 1000
Jan 2 17:58:57 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 2 17:58:57 achim-laptop NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Jan 2 17:58:57 achim-laptop pppd[3318]: Using interface ppp0
Jan 2 17:58:57 achim-laptop pppd[3318]: Connect: ppp0 <--> /dev/modem
Jan 2 17:58:57 achim-laptop pppd[3318]: CHAP authentication succeeded
Jan 2 17:58:57 achim-laptop pppd[3318]: CHAP authentication succeeded
Jan 2 17:59:27 achim-laptop pppd[3318]: Terminating on signal 15
Jan 2 17:59:27 achim-laptop pppd[3318]: Connection terminated.
Jan 2 17:59:27 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 2 17:59:28 achim-laptop pppd[3318]: Exit.
Jan 2 17:59:33 achim-laptop pppd[3335]: pppd 2.4.5 started by achim, uid 1000
Jan 2 17:59:33 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 2 17:59:33 achim-laptop NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Jan 2 17:59:33 achim-laptop pppd[3335]: Using interface ppp0
Jan 2 17:59:33 achim-laptop pppd[3335]: Connect: ppp0 <--> /dev/modem
Jan 2 17:59:33 achim-laptop pppd[3335]: CHAP authentication succeeded
Once again I either get the "modem hangup" problem or I get the "Terminating on signal 15". Oddly enough when I first did this, the LED on my card went green!! Now it is back to orange.

With all the experimentation I haven't come any further than with the command pon eplus that I was using earlier. For anyone not familiar with this command, it is just shorthand for pppd call eplus where %eplus" is the pppd script in /etc/ppp/peers.

Soooo... has anyone got any other ideas? This is really getting me down. I seem to be close to a solution but just can't quite nail it down. All suggestions welcome.

Cheers

Achim
 
Old 01-03-2011, 07:07 AM   #9
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,441
Blog Entries: 3

Rep: Reputation: 182Reputation: 182
you did follow this link right write looks like the modem side is working is the firmware installed for the radio side.

Last edited by Drakeo; 01-03-2011 at 07:29 AM.
 
Old 01-04-2011, 04:59 AM   #10
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 12.04LTS, Debian 7.5
Posts: 61

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Drakeo View Post
you did follow this link right write looks like the modem side is working is the firmware installed for the radio side.
The link you refer to is in fact the very first one I used to try to get the card working back in August 2006. I had the same problem back then. I have fiddled with options, changed laptops, upgraded the operating system (all many times over) and am now back approximately where I started. The information on that page doesn't appear to have changed much since 2006, though I note it was last edited in July 2008.

The only thing I haven't tried is changing the card. Reason... it works under Win 2000 and Win XP using 3G-Watcher. This was achieved on an old ACER Aspire as well as my HP nx6325. I previously had both these machines set up as dual boot Linux/Windoze and the card did not work under Linux. It now continues not to work with Linux on an IBM T43. I know others have had success with the same card (check the links in my earlier posts... especially the ubuntu Forum) but I'm ready to give up.

The new standard is USB these days. Newer laptops don't have a PCMCIA slot anymore. Does anyone know of a USB modem card that will work under Linux?

BTW... what do you mean with "radio side" firmware? Nobody has ever mentioned such a thing before and I've seen no references to such a beast in any other forum nor in any of the stuff from Sierra Wireless.

Achim

P.S. It is often mentioned in various posts concerning the AC850 that it identifies itself as an AC750. I have seen no evidence of this at all... see responses to pccardctl ident and the responses to the ATI commands issued by kppp. Never-the-less I note that the firmware for the AC750 has changed in recent times (now 140 bytes instead of 132) whilst the firmware, labeled SW_8xx_SER.cis, for the AC850 has not. Maybe I'll try using the AC750 firmware and see if that works.
 
Old 01-06-2011, 06:19 AM   #11
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,441
Blog Entries: 3

Rep: Reputation: 182Reputation: 182
The only reason I asked was to find a base foundation of your work. I believe you have a couple threads here and a couple threads in som other forums. In that link was one thing out of all those forums you have been posting to I did not see you write about. as your device is no longer in the Sierra Wireless data but the next card up is. It uses the same protocol.
Quote:
'' AT
TIMEOUT 5
OK ATD*99#
CONNECT ''
the time out is a big thing it allows the server to search and send for your account next make sure you speed is correct because it will also drop you.
please read this link here you will find that unfortunately your 850 is not supported. but from the looks of this it may be. but the firmware could be different. You will see that in 10.04 Sierra Wireless modem is supported through network manager. it shows usb for instructions but your device if the kernel module is loaded should be seen.
those directions are for 10.04. you will note the kppp setup also has changed for 10.04.
Quote:
# chmod a+x ip-up.local ip-down.local
this is a big deal.
why
Quote:
Found a modem on /dev/ttyS2.
create<Warn>: Can't open 'create' for reading: No such file or directory
create<Warn>: ...starting with blank configuration.
Modem configuration written to create.
ttyS2<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
that file must be executable. hang in there. do not let the usb direction confuse you it is all a com connection. tty*
Hang in there.
Please read this for 10.04

Last edited by Drakeo; 01-06-2011 at 06:23 AM.
 
Old 01-09-2011, 04:36 PM   #12
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 12.04LTS, Debian 7.5
Posts: 61

Original Poster
Rep: Reputation: 2
Hi Drakeo,

about 24 hours before your reply-post I bought a Nokia CS-15 from Amazon. Why? Because the blurb assured me that it has support for Linux. The documentation confirms this BUT (there's always a "but", isn't there) the installation did not work as specified. Why am I not surprised?

Apparently the device registers itself as a CD-ROM initially. One then installs a .deb package on the CD-ROM and:
1. the CD-ROM becomes a modem.
2. new modem management and dial up software is installed.
Sounds like just the ticket for a jaded aging hacker who's looking for an easy way out.

BUT: The device did not register itself at all. Using lsusb revealed that the device had been recognised as a usb device. The log in /var/log/syslog gave a dizzying list of errors which I couldn't even begin to understand. I then got on the net and started looking for information. The following post gave me a vital clue:
http://www.petrilopia.net/wordpress/...-15-and-linux/
I used the suggested usb_modeswitch (er... after I had installed it, that is). The result was that the CS15 now flashed green.

In accordance with the information from the Nokia site (http://mea.nokia.com/support/product...cs-15/software), I downloaded and installed the package which should have been on the pseudo-CD-ROM. This resulted in a new rule: /etc/udev/rules.d/25-nokia-zerocd.rules.

In /var/log/syslog I then found:
Quote:
Jan 9 22:17:26 achim-laptop udevd[294]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/rules.d/25-nokia-zerocd.rules:1
Jan 9 22:17:26 achim-laptop udevd[294]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/25-nokia-zerocd.rules:1
Jan 9 22:17:27 achim-laptop udevd[294]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/rules.d/25-nokia-zerocd.rules:1
Jan 9 22:17:27 achim-laptop udevd[294]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/25-nokia-zerocd.rules:1
Jan 9 22:17:27 achim-laptop udevd[294]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/rules.d/25-nokia-zerocd.rules:1
Jan 9 22:17:27 achim-laptop udevd[294]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/25-nokia-zerocd.rules:1
Jan 9 22:17:27 achim-laptop udevadm[4657]: unrecognized command
Jan 9 22:17:27 achim-laptop udevadm[4659]: unrecognized command
Jan 9 22:17:27 achim-laptop udevd[294]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/rules.d/25-nokia-zerocd.rules:1
Jan 9 22:17:27 achim-laptop udevd[294]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/25-nokia-zerocd.rules:1
Jan 9 22:17:27 achim-laptop udevadm[4661]: unrecognized command
I basically ignored this and plowed on.

OK. Next step was to configure kppp. The main thing here was to select the correct device. From /var/log/syslog I could see that there were now 4 new devices: ttyACM0, 1, 2 & 3. Again with help from the Nokia site I selected ttyACM0 which showed up in the list of devices for the modem configuration.

My first attempt to connect gave (in the kppp terminal):
Quote:
~}#@!}!)} }<}!}$}&@}#}$@#}%}&0b}"}&} } } } }'}"}(}"]Y~
NO CARRIER
Up to that point everything was fine. Here's the output from /var/log/syslog:
Quote:
Jan 9 16:16:00 achim-laptop pppd[3781]: pppd 2.4.5 started by achim, uid 1000
Jan 9 16:16:00 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 9 16:16:00 achim-laptop NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Jan 9 16:16:00 achim-laptop pppd[3781]: Using interface ppp0
Jan 9 16:16:00 achim-laptop pppd[3781]: Connect: ppp0 <--> /dev/ttyACM0
Jan 9 16:16:00 achim-laptop pppd[3781]: Remote message: TTP Com PPP - Password Verified OK
Jan 9 16:16:00 achim-laptop pppd[3781]: PAP authentication succeeded
Jan 9 16:16:01 achim-laptop pppd[3781]: LCP terminated by peer (0021: Normal Termination by NCP)
Jan 9 16:16:01 achim-laptop pppd[3781]: Hangup (SIGHUP)
Jan 9 16:16:01 achim-laptop pppd[3781]: Modem hangup
Jan 9 16:16:01 achim-laptop pppd[3781]: Connection terminated.
Jan 9 16:16:01 achim-laptop NetworkManager: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 9 16:16:02 achim-laptop pppd[3781]: Exit.
I tried various changes and options and always got this result or (last time) "Terminating on signal 15". In desperation I tried changing the script in /etc/ppp/peers (created cs-15). You can pretty much guess what it looks like (i.e. not much different from the original eplus script). Then I entered pon cs-15 and got:
Quote:
Jan 9 22:10:28 achim-laptop pppd[4592]: pppd 2.4.5 started by achim, uid 0
Jan 9 22:10:28 achim-laptop pppd[4592]: Failed to open /dev/ttyACM0: Input/output error
Jan 9 22:10:28 achim-laptop pppd[4592]: Exit.
Of course I tried heaps more than just that. I've really only shown the brightest low-lights in this dismal failure.

Sorry if this seems disappointing to you given the time you have spent on the problem with the AC850, but consider how disappointing this all is for me. I'm going to keep trying with the CS-15 for this week. After that I will send the CS-15 back. There is some hope, after all, that I'll get this USB-stick working. Whether or not I get it working I will make another attempt at getting the AC850 to work. The trouble is that the instructions from Sierra Wireless are not straight forward and they are sometimes ambiguous (e.g. "Prior to installing the driver, the kernel source code must be downloaded into /usr/src/linux." The package manager - synaptic - suggests the headers are sufficient. What about a link to the source, do I really need to copy it all to /usr/src/linux?) For this and similar reasons I haven't tried it this weekend.

Once again I've used up my only free day (Sunday) with hacking around on my laptop.... One of these days my wife is going to kill me!

Cheers

Achim

P.S. My reflections on USB sticks and modern PCs had nothing to do with the different protocols. I know that given the right driver, the PCMCIA and USB devices look the same to the OS. However, newer machines are not equipped with a PCMCIA slot and some day I will need a new laptop... get my drift?

Last edited by achim_59; 01-09-2011 at 04:41 PM. Reason: Syntax corrections
 
Old 01-20-2011, 02:14 PM   #13
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 12.04LTS, Debian 7.5
Posts: 61

Original Poster
Rep: Reputation: 2
CS-15 working

My efforts to get the CS-15 working have been successful. You can see what happened on this other forum:

http://www.linuxforums.org/forum/log...088fb2f3eab721

I now have another problem and I'm not sure if it was a result of installing the card or a glitch from my upgrade to ubuntu 10.10. If I knew how to uninstall a package that has dependency problems, I could have saved myself a lot of trouble. I'll have to look into it.

If anyone else has a CS-15 that they want to get running, I would strongly advise against installing the zero_cd package from Nokia. If you have Ubuntu 10.10, then you don't need to do anything special. The link above has a wvdial.conf that works without any other changes required (no mode_switch, no udev rules). If you're really lucky, the graphical install might even work... apparently it has for some people.

I hope to get back to the AC850 problem soon... honestly!

Achim
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Cannot get AC850 working under Ubuntu (Karmic Koala) achim_59 Linux - Wireless Networking 15 12-07-2010 04:55 PM
Sierra wireless AC850 not functioning on nx6325 with Ubuntu 8.04 achim_59 Linux - Networking 0 01-27-2009 05:35 PM
LXer: Addendum Ubuntu 8.04 - Pseudo Root User - III LXer Syndicated Linux News 0 01-11-2009 01:00 PM
LXer: Addendum Ubuntu 8.04 - Pseudo Root User - II LXer Syndicated Linux News 0 11-18-2008 10:50 AM
LXer: Addendum Ubuntu 8.04 - Pseudo Root User LXer Syndicated Linux News 0 10-20-2008 05:50 PM


All times are GMT -5. The time now is 12:58 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration