Re: ModemData.txt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Marvin!
First of all I tried to change provider, and that's what happened:

WvDial<*1>: WvDial: Internet dialer version 1.56
WvModem<*1>: Cannot set 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: ATM1L3DT7020001033
WvDial<*1>: Waiting for carrier.
WvDial Modem<*1>: ATM1L3DT7020001033
WvDial<Warn>: Timed out while dialing.  Trying again.
WvDial<Warn>: Maximum Attempts Exceeded..Aborting!!
WvDial<*1>: Disconnecting at Sat Dec 22 09:44:53 2007

If I change the Init2 as per your suggestion, the result is that the
Modem does nothing and writes:

WvDial<*1>: WvDial: Internet dialer version 1.56
WvModem<*1>: Cannot set 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 +MS=34
WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +MS=34
WvDial Modem<*1>: ERROR
WvDial Modem<*1>: ERROR
WvDial<Err>: Bad init string.
WvModem<*1>: Cannot set 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 +MS=34
WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +MS=34
WvDial Modem<*1>: ERROR
WvDial Modem<*1>: ERROR
WvDial<Err>: Bad init string.
WvModem<*1>: Cannot set 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 +MS=34
WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +MS=34
WvDial Modem<*1>: ERROR
WvDial Modem<*1>: ERROR
WvDial<Err>: Bad init string.

If I let the "old" Init2, and I add the Init3 (originally no Init3 was
in the wvdial.conf), that's what happens:

WvDial<*1>: WvDial: Internet dialer version 1.56
WvModem<*1>: Cannot set 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>: Sending: AT+CGI=59
WvDial Modem<*1>: AT+CGI=59
WvDial Modem<*1>: ERROR
WvDial<Err>: Bad init string.
WvModem<*1>: Cannot set 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>: Sending: AT+CGI=59
WvDial Modem<*1>: AT+CGI=59
WvDial Modem<*1>: ERROR
WvDial<Err>: Bad init string.
WvModem<*1>: Cannot set 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>: Sending: AT+CGI=59
WvDial Modem<*1>: AT+CGI=59
WvDial Modem<*1>: ERROR
WvDial<Err>: Bad init string.

I hope these cases could help you to check what's the problem... If I
knew how to do, I would probably set a longer waitingtime with the
"original" Init2 and Init3 and see what happens... but of course I am
not sure I am really well understanding which is the problem...

Thank you,
Matteo




2007/12/21, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> Matteo,
>
> Occassionally we do encounter IPs whose servers are Linux hostile.
> Perhaps you can find some local Linux users with a different IP, thus
> to borrow their User/Password, to check your modem System on.
>
> The NoEC problem typically has been encountered with Lucent DSP
> modems.  I don't recall a prior NoEC problem with an external serial
> modem.
>
> In case there is an underlying noisy line problem,
> try changing the Init2 line to:
> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +MS=34
> Also you should have a country specification.
> Init3  =  AT+CGI=59
> 59 is the modem code for Italy.
>
> MarvS
>
>
>
> On Dec 21, 2007 1:40 PM, Matteo Mambretti <teo2257@xxxxxxxxx> wrote:
> > Dear all,
> > I've been trying all the day to set up the connection in order to
> > avoid the NoEC problem. I Googled all the day but unfortunately with
> > really no result.
> > Would anybody of you be so kind to help me in any way...? I believe
> > that only a "setting" is currently missing, as everything goes
> > properly till the end... and only the NoEC command is currently
> > missing from the connection...
> >
> > Thank you,
> > Matteo
> >
> >
> >
> > 2007/12/21, Matteo Mambretti <teo2257@xxxxxxxxx>:
> >
> > > Thank you Marvin for the suggestion... now I am registered!
> > >
> > > I read the attached file but it was unsuccessful for me... I could not
> > > find in the
> > > $ sudo tail -f /var/log/messages &
> > > anything about the
> > > "NoEC"
> > > nor the series of
> > > ^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G
> > > ^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G
> > > ^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G^G
> > > ^G^G^G^
> > >
> > > I anyway tried to change the
> > >  /etc/ppp/options
> > > adding FFFFFFFF (instead of 0) to the command asyncmap, but unsuccessfully.
> > >
> > > The only difference is that the number that the modem shows after
> > > CONNECT (and before NoEC) is different from yesterday...
> > >
> > > Thank you!
> > > Matteo
> > >
> > > 2007/12/21, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> > > > Matteo,
> > > >
> > > > Please sign up for LIST membership at www.linmodems.org, so that your
> > > > messages don't have to be manually Moderated.
> > > >
> > > > WvDial Modem<*1>: CONNECT 42666 NoEC
> > > > reports that your modem and the servers are failing to establish the
> > > > common Error Correction agreement (NoEC)
> > > >
> > > > Can you relate what change made enabled recognition of the modem? That
> > > > may help with this residual NoEC problem.
> > > >
> > > > Read the attached, ancient info on the NoEC problem.
> > > >
> > > > MarvS
> > > >
> > > > On Dec 20, 2007 4:09 PM, Matteo Mambretti <teo2257@xxxxxxxxx> wrote:
> > > > > Dear all,
> > > > > thanks God something has been changed!!! :-)
> > > > > Now the PC recognises the modem, and is able to dial-up... the problem
> > > > > is actually that it dials, then the modem communicates with the
> > > > > server, then waits... and then disconnect, and I do not know why...
> > > > >
> > > > > WvDial<*1>: WvDial: Internet dialer version 1.56
> > > > > WvDial<*1>: Initializing modem.
> > > > > WvDial<*1>: Sending: ATX3
> > > > > WvDial Modem<*1>: ATX3
> > > > > 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: ATM1L3DT7027020000
> > > > > WvDial<*1>: Waiting for carrier.
> > > > > WvDial Modem<*1>: ATM1L3DT7027020000
> > > > > WvDial Modem<*1>: CONNECT 42666 NoEC
> > > > > WvDial<*1>: Carrier detected.  Waiting for prompt.
> > > > > WvDial<Err>: Connected, but carrier signal lost!  Retrying...
> > > > > WvDial<*1>: Sending: ATM1L3DT7027020000
> > > > > WvDial<*1>: Waiting for carrier.
> > > > > WvDial Modem<*1>: NO CARRIER
> > > > > WvDial Modem<*1>: ATM1L3DT7027020000
> > > > > WvDial<Warn>: No Carrier!  Trying again.
> > > > > WvDial<Warn>: Maximum Attempts Exceeded..Aborting!!
> > > > > WvDial<*1>: Disconnecting at Thu Dec 20 22:01:43 2007
> > > > >
> > > > > What shall I do in your opinion?
> > > > > Thank you,
> > > > > Matteo
> > > > >
> > > > >
> > > > > 2007/12/20, Oliver Gerlich <olig9@xxxxxx>:
> > > > >
> > > > > > Matteo,
> > > > > >
> > > > > > here is a help page for setting up a modem under Ubuntu:
> > > > > > https://help.ubuntu.com/community/DialupModemHowto
> > > > > >
> > > > > > It links to the various subpages where detailed installation and
> > > > > > configuration instructions are listed.
> > > > > >
> > > > > > In your case, you should probably first look at this:
> > > > > > https://help.ubuntu.com/community/DialupModemHowto/Lucent
> > > > > >
> > > > > > After that, you should have a look at the various ways to configure the
> > > > > > login information; I have no idea which is the best way, so maybe you
> > > > > > could just start from the top until you find a way that works and is
> > > > > > easy to use :-)
> > > > > >
> > > > > > Btw. I think the Ubuntu IRC channel is quite useful for getting direct
> > > > > > help (faster than by email, anyway). There might not always be real
> > > > > > "experts" online, but you can get answers for common questions really quick.
> > > > > >
> > > > > > Regards,
> > > > > > Oliver
> > > > > >
> > > > > >
> > > > > >
> > > > > > Matteo Mambretti schrieb:
> > > > > > > I tried an even different alternative. I found in a box a very old
> > > > > > > internal modem. I mounted it, and... the PC is showing it (see
> > > > > > > attached).
> > > > > > > But nothing to do: it is NOT anyway working, and wvdialconf does not
> > > > > > > find it anyway! :-(
> > > > > > >
> > > > > > > I am very unhappy with this so difficult software... what shall I do?
> > > > > > >
> > > > > > > Thank you,
> > > > > > > Matteo
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 2007/12/20, Matteo Mambretti <teo2257@xxxxxxxxx>:
> > > > > > >> Dear all,
> > > > > > >> I would try it, but the system does not allow me to save the modified
> > > > > > >> file, as it says that I do not have the relevant permissions. What do
> > > > > > >> I have to do?
> > > > > > >>
> > > > > > >> But do you think that I will definitively be able tu use such PC and
> > > > > > >> modem? It's something like 3 weeks that we are making trials, but it
> > > > > > >> does not seem to work...
> > > > > > >>
> > > > > > >> The PC is running, the modem runs, the port is working, in some
> > > > > > >> situations the lights of the modem are switching on and off... but the
> > > > > > >> communication between the modem and the PC does not seem to work. I
> > > > > > >> will unfortunately need to carry this pc away in short time (when the
> > > > > > >> modem is needed) and I am really in trouble with this situation... I
> > > > > > >> fear that the old windows system will be the only possibility to make
> > > > > > >> it work... am I wrong?
> > > > > > >>
> > > > > > >> Thank you,
> > > > > > >> Matteo
> > > > > > >>
> > > > > > >> 2007/12/18, Oliver Gerlich <olig9@xxxxxx>:
> > > > > > >>> Matteo,
> > > > > > >>>
> > > > > > >>> the default menu.lst doesn't contain any irqpoll or acpi=off lines; you
> > > > > > >>> have to add them yourself.
> > > > > > >>>
> > > > > > >>> Here's a howto document for the menu.lst (and GRUB, which uses the
> > > > > > >>> menu.lst):
> > > > > > >>> https://help.ubuntu.com/community/GrubHowto
> > > > > > >>>
> > > > > > >>> The section "Setting kernel parameters" explains how to add a boot
> > > > > > >>> parameter (like irqpoll).
> > > > > > >>>
> > > > > > >>> In short, you have to find a line starting with "# kopt=" and add the
> > > > > > >>> irqpoll parameter at the end of the line. Then save the menu.lst, run
> > > > > > >>> "sudo update-grub", and reboot.
> > > > > > >>> As Marvin wrote, you should try adding the pollirq option first, reboot,
> > > > > > >>> and check if it helped. If that option does not help, remove the irqpoll
> > > > > > >>> parameter again from that kopt line in menu.lst, and instead add the
> > > > > > >>> parameter acpi=off to that line. Reboot, and check if that parameter helps.
> > > > > > >>>
> > > > > > >>> Regards,
> > > > > > >>> Oliver
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> Matteo Mambretti schrieb:
> > > > > > >>>> Dear all,
> > > > > > >>>> if it could help you:
> > > > > > >>>> - in the boot menu the serials are enabled. I tried "Enable" and
> > > > > > >>>> "Auto", but nothing seems to change.
> > > > > > >>>> - in the file  /boot/grub/menu.lst I cannot find neither pollirq nor acpi...
> > > > > > >>>>
> > > > > > >>>> Thank you,
> > > > > > >>>> Matteo
> > > > > > >>>>
> > > > > > >>>> 2007/12/18, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
> > > > > > >>>>> Folks
> > > > > > >>>>>
> > > > > > >>>>> Would some one send Matteo an example kernel line with irqpoll or
> > > > > > >>>>> acpi=off per my suggestions below. Until Friday, I won't be under
> > > > > > >>>>> Linux and cannot check syntax validity
> > > > > > >>>>>
> > > > > > >>>>> Matteo,
> > > > > > >>>>>
> > > > > > >>>>> 1) If you can access the bootup BIOS, check that the serial ports are
> > > > > > >>>>> in fact activated,
> > > > > > >>>>> as shutting off this service is an option on some newer PCs, favoring USB ports.
> > > > > > >>>>> . From what you havve described thus far, I doubt this is the problem,
> > > > > > >>>>> but it will not hurt to check.
> > > > > > >>>>>
> > > > > > >>>>> 2) Within /boot/grub/menu.lst  , there are stansa specifying the boot
> > > > > > >>>>> up options, and within each a line specifying the kernel used and
> > > > > > >>>>> bootup options. In the options list following the kernel name, try the
> > > > > > >>>>> effects of successive (one at a time) the following options:
> > > > > > >>>>>  pollirq , acpi=off
> > > > > > >>>>> Each time save, reboot, and test
> > > > > > >>>>>
> > > > > > >>>>> These modifiers change the power/irq management of the System
> > > > > > >>>>>
> > > > > > >>>
> > > > > > >>
> > > > > > >> ------------------------------------------------------------------------
> > > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
>

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux