1. AGERE_MODEM_Chip_1648c-tv5_Model_No._IC56A_made_by_Stratitec.zip Driver
2. NoEC.txt File Contents

NoEC.txt Driver File Contents (AGERE_MODEM_Chip_1648c-tv5_Model_No._IC56A_made_by_Stratitec.zip)

If a ppp connection if not sustained,
and the output from 
# tail -f /var/log/messages &
includes  "NoEC"  and/or a block like:
^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^
   
then try adding this line to /etc/ppp/options

asyncmap FFFFFFFF

======================
Subject:          Re: CONNECT NoEC [was: LT WinModem Problems]
     Date:         Wed, 17 Jul 2002 07:47:19 -0700
     From:          Bob Arendt <rda@rincon.com>
      To:          Darren Gould <darren_gould@linuxmail.org>
      CC:          Jacques.Goldberg@cern.ch, stodolsk@rcn.com, discuss@linmodems.org
 References: 
         1

Darren,

I believe the "NoEC" refers to "No Error Correction", one of modem protocol
options. This isn't necessarily a bad thing - the ISP side may not support
EC. The good news is that it looks like the ppp core is working and
communicating, based on the LCP messages from the pppd session.  You're
actually assigned an IP address. It seems strange that it doesn't also pass DNS hosts
-
but perhaps these are static in your case.  Also a default route should be set;
Once pppd is connected and up, try "netstat -rn" and see if there's an
entry:

Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
0.0.0.0         <the_ip_addr>   0.0.0.0         UG       40 0          0
ppp0

Destination 0.0.0.0 indicates this is the default route.  There should also
be entries for the interface and local transport (127.0.0.1).  If you don't
have a default route set, networking won't work.  DNS is also necessary for normal
access to the net.  My LCP exchange also has some lines that look like:
rcvd [IPCP ConfAck id=0x2 <addr 65.177.232.134> <compress VJ 0f 01> <ms-dns1
206.134.133.10> <ms-dns3 206.134.224.5>]

where 65.177.232.134 is my assigned local IP addr, and the dns1 & dns3
entries are the DNS nameservers from my ISP.  The "ifup ppp0" writes these addresses
into /etc/resolv.conf.  In your case, you may have to set up /etc/resolv.conf by
hand using IP addresses supplied, and a default route to set by hand as well.

Hope this helps.

Cheers,
-Bob Arendt

========================================
Subject:        Re: CONNECT NoEC [was: LT WinModem Problems]
   Date:        Wed, 17 Jul 2002 12:37:55 -0400 (EDT)
  From:        christoph hebeisen <heby@heby.de>
    To:        "stodolsk@rcn.com" <stodolsk@rcn.com>

The ec protocol is negotiated before the isp has any chance to notice what
operating system is running on the client machine - this is purely a
modem-to-modem issue. Some modems may have interoperability problems,
though.

Although in principle, communication is possible without error correction,
it turns out that at least for me connections without ec normally drop
after a few minutes and are not very reliable before (lots of resending of
packages on the ppp layer).

heby

On Wed, 17 Jul 2002, stodolsk@rcn.com wrote:

> Darren,
>    There have been a few cases in which IPs have "Linux hostile" protocols
> on their servers: borrowing a local friend's IP obviated the problem.  You
> might try such a test. Using Linux OS for their servers, RCN.COM is one
> Linux compatible IPs, serving California and the East coast north of the
> Carolinas.
>
> MarvS
>
=====================================
Subject:        Re: CONNECT NoEC [was: LT WinModem Problems]
   Date:        Wed, 17 Jul 2002 22:48:01 -0400 (EDT)
  From:        christoph hebeisen <heby@heby.de>
    To:        Darren Gould <darren_gould@linuxmail.org>
    CC:        <discuss@linmodems.org>

> Remember, I'm on a dual boot machine and the modem works in Windooze.

But the dsp code included in the windows driver might differ slightly
from the code used in the linux driver.  That's especially true if they're
different driver versions on the two systems.

> What about using the \N error control options available to the LT
> Winmodem, might this be a solution.  Is there a chance that the modem
> in Windooze is configured via this command (although it doesn't appear
> in the log file).

The modem will by default try to connect with error correction.  I get noec
connections sometimes when I'm on a bad line or the modem on the other
side has trouble (e.g. long distance connections with phone cards).
Hanging up and calling again normally solves the problem for me but I
guess you tried that.

heby

==========
Earlier discussion:

http://linmodems.technion.ac.il/archive/msg03315.html