John CANADA Kernel 2.6.22-14-generic

Syntactics <Syntactics@xxxxxxxxxxx> · Fri, 07 Mar 2008 22:32:42 -0700

Hi, I need help with wvdial and/or pppd.  I previously sent this message
to wvdial@xxxxxx but that site is no longer up.  I also tried
discuss-get.123_145@xxxxxxxxxxxxx but received no reply.

I am trying to locate someone from wvdial that could help as I think
this is the proper starting point.

If someone who can help with wvdial is available:

Please read the 'forwarded message' attachment to start.

Jacques Goldberg provided me with a debug script.  Its output contains
most of what should be needed to get an idea of the problem.  Attached
are a few attempts to connect, some succeeded, some failed after
succeeding, some never connected at all, some even cause slmodemd to fail.

We can start wherever you like.  I am a newbie in linux.

Thanks for your help.

John.
--- Begin Message ---

Subject: Re: John CANADA Kernel 2.6.22-14-generic
From: Jacques Goldberg <Jacques.Goldberg@xxxxxxx>
Date: Sat, 01 Mar 2008 21:31:16 +0200
In-reply-to: <000001c87b07$869c31f0$2496cecd@AcerAspire3000>
References: <000001c87746$55931de0$8496cecd@AcerAspire3000>	 <47C2608C.8080601@xxxxxxx> <000001c877de$43d00350$3996cecd@AcerAspire3000>	 <47C314F0.7080109@xxxxxxx> <000001c877fc$5eaa6b70$4496cecd@AcerAspire3000>	 <47C44A85.5080809@xxxxxxx> <000001c879b2$3bcb2dd0$bc97cecd@AcerAspire3000>	 <47C66798.2000301@xxxxxxx> <000001c87b07$869c31f0$2496cecd@AcerAspire3000>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12)	Gecko/20080211 Red Hat/1.5.0.12-8.el4 Thunderbird/1.5.0.12 Mnenhy/0.7.5.666

John,
This has reached a level too difficult for me.
Transmitting to the list.
Please reply to "Reply-to".discuss-get.123_145@xxxxxxxxxxxxx

LIST: I have made my best, with no success, to try to find why his 
slmodemd compatible modem fails under Ubuntu 7.10 2.6.22-24.generic.
The communication behaves erratically at random, sometimes connect, 
sometimes not, sometimes hangs while connected, sometimes not.

PLEASE TAKE OVER ....

John Gammon wrote:
Jacques, 

when the 'sudo wvdial' command fails while trying to connect:

smaknj@Smaknj-Laptop:~$ sudo wvdial
WvDial<*1>: WvDial: Internet dialer version 1.56
WvModem<*1>: Cannot get information for serial port.
WvDial<*1>: Initializing modem.
WvDial<*1>: Sending: ATZ
WvDial Modem<*1>: ATZ
WvDial Modem<*1>: OK
WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
WvDial Modem<*1>: OK
WvDial<*1>: Modem initialized.
WvDial<*1>: Sending: ATDT7804218500
WvDial<*1>: Waiting for carrier.
WvDial Modem<*1>: ATDT7804218500
WvDial Modem<*1>: NO CARRIER
WvDial<Warn>: No Carrier!  Trying again.
WvDial<*1>: Disconnecting at Fri Feb 29 11:19:57 2008
smaknj@Smaknj-Laptop:~$ 

It causes the slmodemd to fail

smaknj@Smaknj-Laptop:~$ sudo slmodemd -c CANADA --alsa hw:0,6
SmartLink Soft Modem: version 2.9.11 Feb 17 2008 09:31:10
symbolic link `/dev/ttySL0' -> `/dev/pts/1' created.
modem `hw:0,6' created. TTY is `/dev/pts/1'
Use `/dev/ttySL0' as modem device, Ctrl+C for termination.
error: cannot update delay: 0 instead of 384.				
smaknj@Smaknj-Laptop:~$

My understanding... (which may be false) is that slmodemd dynamically
creates a symbolic link to the modem hardware, and remains alive
to perform certain duties unknown to me.

Wvdial is then executed, which (via its wvdial.conf entry 'modem =
ttysL0') points to the modem and talks to the codec running on the
modem, telling it to dial out to the designated phone number.

Wvdial will try to negotiate the connection and (if successful) 
startup pppd (which has its own 'provider' file, with connection 
settings that match the wvdial.conf file).  pppd will then take 
over as the primary communication and packet handler, talking with
the peer ppp software.

If wvdial cannot negotiate a connection, it quits.
End My understanding....

does this 'slmodemd' error:

error: cannot update delay: 0 instead of 384.

possibly indicate what kind of problem wvdial is having?

Since pppd is not launched, I conclude that wvdial is the 
component that is failing.  However, what I do in the wvdial.conf
file either prevents connecting entirely, or allows connecting, but
not every time.  The default settings work the best.

I realize I am grasping at straws now.  So I am trying to understand 
the 'behind the scenes' activity, to try to isolate which component
is the one failing.... slmodemd or wvdial or pppd or ?

I picked up a phone line splitter and I'm able to listen on the phone
to the protocols.  I notice that the protocol sequence starts out
normal (like my other pc), but within a few seconds the chatter becomes
very high pitched and "sparky" or "chirpy", not the usual lower tones
I'm used to hearing.

Is the modem itself the problem?

On my desktop panel, I can select 'dialup connections' from the network 
icon, and launch 'Connect to ppp0 via modem.  I thought it should have 
said 'Connect to modem via ppp0', but it doesn't work anyway.

Since the /etc/ppp/options file contains 'redial' capabilities, it seems
that pppd is also capable of dialling out on its own.

Any ideas?

thanks 

John.

--- End Message ---
Attachment:
bad.gz

Description: GNU Zip compressed data
Attachment:
ConnectandFailed.gz

Description: GNU Zip compressed data
Attachment:
LackofLCPEchoResponses.gz

Description: GNU Zip compressed data
Attachment:
VeryGoodConnection.gz

Description: GNU Zip compressed data
smaknj@Smaknj-Laptop:~$ sudo wvdial
WvDial<*1>: WvDial: Internet dialer version 1.56
WvModem<*1>: Cannot get information for serial port.
WvDial<*1>: Initializing modem.
WvDial<*1>: Sending: ATZ
WvDial Modem<*1>: ATZ
WvDial Modem<*1>: OK
WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
WvDial Modem<*1>: OK
WvDial<*1>: Modem initialized.
WvDial<*1>: Sending: ATDT7804218500
WvDial<*1>: Waiting for carrier.
WvDial Modem<*1>: ATDT7804218500
WvDial Modem<*1>: CONNECT 38667
WvDial<*1>: Carrier detected.  Starting PPP immediately.
WvDial<Notice>: Starting pppd at Fri Feb 29 22:29:16 2008
WvDial<Notice>: Pid of pppd: 21833
WvDial<*1>: Using interface ppp0
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: local  IP address 205.206.150.167
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: remote IP address 205.206.120.50
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: primary   DNS address 209.115.142.9
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: secondary DNS address 209.115.142.132
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: Connect time 15.0 minutes.
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: pppd: ��[06][08]�蝝6][08]
WvDial<*1>: Disconnecting at Fri Feb 29 22:44:20 2008
WvDial<*1>: The PPP daemon has died: Lack of LCP echo responses (exit code = 15)
WvDial<*1>: man pppd explains pppd error codes in more detail.
WvDial<Notice>: I guess that's it for now, exiting
WvDial<*1>: Provider is overloaded(often the case) or line problem.
WvDial<Notice>: The PPP daemon has died. (exit code = 15)