Lucent DSP winmodem tracking page  August 15, 2002
    Updated at: http://linmodems.technion.ac.il/Ltmodem.html

Synopsis
A group of volunteer Maintainers and Testers receives linuxVER.zip compiler kits from the Lucent subsidiary Agere Systems, Inc,(AS)  .   Proprietary DSP (digital signal processor) code is contained in the kits,  with current core code version = 8.22,  together with Open Source serial code and code directing compilation and installation of a pair of modem drivers.  Beginning with the AS kits, volunteer Maintainers produce ltmodem-version.tar.gz kits with enhanced functionality, greater ease of usage, a substantial diagnostic suite linked to documentation.  Tester groups represent the major Linux distributions.  They use the ltmodem compiler  to generate Installer kits for the modem drivers, matched to the kernels of on-going Linux releases.   Installer kits do not require auxilliary resources, but must be carefully version and flavor matched with the running kernel. Documentation and utilities are installed to /usr/share/DOCs/ltmodem-version/.
 

Version number interpretation - Within a ltmodem-8.22a4.tar.gz designation, components of the version are the:
    8.22 designation of the AS core driver code.
    a1 , a2, ...,a7 are successive improvements in ONLY the installer codes, without changes to the AS core.
    8.22a will be the final designation of the "a" series, indicating that projected improvements are mature.
Thus  if your currrent modem service is fine, there is No Benefit in re-installing with a newer version of the installer kits, until there is a new release in the AS core code.

Both Compiler and Installer kits can be downloaded from Canada or Germany.
There is a  Polish Linux distribution, with a slightly modified compiler kit.
There is support in Portugese  and Italian.  Additional translations are welcomed.
Communications are through the more general Winmodem email list, discuss@linmodems.org, to which send:
   help queries - do include your Linux distribution and kernel-version;
   bug fixes;
   Gratitiude too.

General issues:
Statement of Purpose -  to Exist as little as possible.
Release news   -  What is new and Who (roughly current since VER=5.97)
The Configure implementation - easier for Newbies.
Garments around the Source - adaptiveness and added utility.
When to upgrade?  -  Wait until the AS core code changes, though drivers must be re-compiled with each Linux kernel change.

The utilities minicom and wvdial are useful for accessing the modem hardware and thus testing adequacy of the driver installation.
Setting up ppp and achieving Internet navigation are not integral to any modem driver installation.
There are excellent HowTOs on these separate tasks, and which may be provided as part of your Linux installation. Also see post install issues below.

The information below is fairly technical.  For Newbies, Daniel Rees' site is recommended for a first reading on ltmodem.



Modem, Chipset and driver information
     Documentation is available at Agere Systems, Inc.
     There are modemVER.pdf files in the DOCs/ folder of the ltmodem-VER kits, or copied into /usr/share/doc/ltmodem-ver/, or available within DOCs.tgz at http://www.heby.de/ltmodem
   The AMR soft modems are NOT supported by the ltmodem drivers,  Agere Systems is currently developing support support under Linux for the AMR modems
    Supported DSP chips as of modem600.pdf are:
        Apollo - This version of drivers will run on DSP1642-CC, DSP1641-CC, DSP1643-CH, DSP1644-CH, DSP1641B-CH
       Mars3.2, Mars3, Mars2, Mars1 - this version of drivers will run on DSP1645, DSP1646, DSP1648, DSP1648B.
       The Apollo3 (APL43) chipset is for Modem/LAN applications.
     Lucent HSP modem with an Agere 1646TOO chip - is an older chip.
For linux kernels in the 2.2.nn series, the ltmodem-6.00c2 and earlier resources provide serviceable drivers,  but 8.22 series drivers DO NOT serve 2.2.nn kernels.
The 8.22 series is providing support for the emerging 2.5 -> 2.6 kernels.

NOT supported include: Lucent Wildwire ADSL Client with PCI ids 11c1:0462  &  soft AMR/AC'97 modems.
     Venus chipset modems which have a more expensive controller, as contrasted to a DSP.

Translations between IC Consumer and AS chipset names:
   1641 = Apollo ISA
   1642 = Apollo ISA
   1643 = Apollo ISA with enough RAM for V.90
   1644 = 1643 + integrated plug and play
   1645 = Mars1 PCI
   1646 = HV-90 = Mars2 PCI
   1648 = Mars3
   1648C = Mars3.2 with more RAM for V.92

Changes from AS core code in releases 5.95 --> 8.22
    Cures some prior cases of NODIALTONE & HANGUP on ppp initiation.
    Some higher CONNECT speeds have been reported.
    Support of 2.4.nn kernels ( though ltmodem-5.78 supported 2.4.nn), and experimental support of 2.5.nn has begun
    With release 6.00 K56Flex support has been removed, with beneficial decrease in driver size.
    For a very few systems,  there was a loss of dial up sounds in the 5.95 --> 5.99 transition.  For some of the adaptive history see reports from  Thorsten  and Dieter .
           There is a correction for this problem in the 8.22 Agere release.
   The 8.22 drivers do serve under Symmetric Multi Processor (SMP) kernels.

Faxing issues - Fax support is included in the drivers. The reports on faxing are quite mixed: 1 , 2, 3,  Using a recent efax update may help.



Components, structural and nomenclature issues:
    Drivers compiled using ltmodem-VER kits, are named lt_modem.o and lt_serial.o, use
a node /dev/ttyLT0 c 62 64  with a symbolic link to it from /dev/modem
or alternativlyunder  Device File System  usage (standard for Mandrake 8.1 and later), there are created upon demand:
a node /dev/tts/LT0  with  symbolic links  /dev/modem and /dev/ttySLT0

The usage permissions to the dialout group specified in /etc/group.  Drivers are installed by ./ltinst2 into the standard modules path:
     /lib/modules/2.4.nn/kernel/drivers/char/     for 2.4.nn kernels
     /lib/modules/2.2.nn/misc/                                for 2.2.nn kernels

The modem drivers are NOT loaded on boot up, but are loaded on demand (typically by ppp initiation), thanks to the  lines added  to /etc/modules.conf:
    # lt_drivers: autoloading and insertion parameter usage
    alias char-major-62 lt_serial
    alias /dev/modem lt_serial
    alias /dev/tts/LT0 lt_serial
    # The next line is a syntax example, rarely needed, to automate parameter usage during lt_drivers insertion.
    # options lt_modem vendor_id=0x115d device_id=0x0420 Forced=3,0x130,0x2f8
    # section for lt_drivers ends

Under the older implementation of device nodes, the two line:
    alias char-major-62 lt_serial
complemented by a symbolic link:
    /dev/modem --> /dev/ttyLT0
suffice to load the modem drivers on ppp initiiation.

For systems using the Device Fiile System (devfs) implemented under the 2.4.nn Linux kernels, the additional line:
     alias /dev/modem /dev/tts/LT0
is needed.  There are also a symbolic links:
    /dev/modem --> /dev/tts/LT0
    /dev/ttySLTO --> /dev/tts/LT0    (which services wvdialconf)
maintained through two lines in  /etc/devfsd.conf  (in many  RMP using Linuxes) or  /etc/devfs/conf.d/litmodem (in Debian Linux):
        REGISTER        ^tts/LT0$       CFUNCTION GLOBAL symlink $devname modem
   UNREGISTER        ^tts/LT0$       CFUNCTION GLOBAL unlink modem
which together serve for demand loading of the modem drivers and  creation of /dev/tts/LT0 upon a query to /dev/modem.

The symbolic link /dev/ttySLT0 is useful for the setup utility for wvdial
# wvdialconf
because wvdial scans only for ports with names /dev/ttyS*

An informative query is:
$ ls -l  /dev/tts/  /dev/ttyS*
before and after driver loading.

For most sytems, both modem drivers will load upon demand, or through:
$ modprobe lt_serial
Sequential loading if desired can be achieved by:
$ modprobe lt_modem
$ modprobe lt_serial
If  lt_modem but NOT lt_serial loads, remedial procedures are described in DOCs/Insert-parameters, or the modem hardware may not be fully served by the ltmodem drivers.   Some ESS and AMR modems can achieve dialout with the ltmodem drivers, but fail at the ppp initiation step.

For a minority of ISA card modems, modem functiionality may require a lt_modem.o insertion by:
$  insmod lt_modem Forced=irq,BaseAddress,PortAddress,0
   of which Forced=3,0x130,0x2f8,0  is just a particular syntax sample.
   Once found effective, these type of specification can be automated by a line like the following in /etc/modules.conf
   options lt_modem Forced=3,0x130,0x2f8,0
   The forth parameter needn't be entered as 0 is the default.  Enter 1 for to promote scanning for the modem.
An "options lt_modem vendor_id=0x115d device_id=0x0420"  type of usage is only relevant to a very few PCI card modems, and not ISA card modems.
Note that this is a syntax ONLY example, and necessary for a small minority of installations.
For details read within DOCs/, Insert-param.html and Insert-param4.txt .

Modem and ppp modules loaded during a ppp session for 2.4.nn kernels typically are:
---------------------------------------------------------------------------------------
Module                  Size                           Used by
ppp_deflate           39584   0  (autoclean)
bsd_comp                4176   0  (autoclean)
ppp_async               6224   0  (autoclean)
lt_serial                 20944   0  (autoclean)
lt_modem            314592   0  (autoclean) [lt_serial]
ppp_generic           13152   0  (autoclean) [ppp_deflate bsd_comp ppp_async]
isa-pnp                                may be required by lt_serial if the System has modular isa-pnp.o
-----------------------------------------------------------------------------------------

Upon  loading of lt_modem and lt_serial, io space usage will be shown by:
    cat /procs/ioports
Interrupt assignments will be given only during modem hardware usage, as displayed by:
    cat /procs/interrupts

After an online session is concluded, these drivers can be unloaded by Root, through
 $  rmmod -a
 $  rmmod -a
if indeed loaded autoclean. Or the modem drivers can be unloaded by the single command:
$   modprobe -r lt_serial
or sequentially by
$  rmmod lt_serial lt_modem

It is instructive to (as Root) give these insertion and removal commands after:
$ tail -f /var/log/messages &
to see the reports of kernel actions.
--------------------------------------------------------------------------------------

Odds and ends:

Compiler gcc with version 3 or later do NOT  yet output functional drivers.

Only one Lucent DSP modem is supported on a single PC, though as of September 2001 work is in progress to achieve multiple modem support.

SMP (symmetric multi processor) kernels are now standard for some Linux distros including Slackware.
Until SMP support is enabled in the modem drivers (anticipated), kernels was be recompiled for single processor service to achieve modem functionality.

Modem profiles can be stored by the AT&W command, but EEPROM service is NOT yet enabled for Linux.

In the prior 5.78 releases, functionality was combined a single ltmodem.o driver, which  was installed with ./ltinst only.

Drivers compiled from the AS linuxVER.zip are named ltmodem.oand ltserial.o and use node:  /dev/ttyS14 c 62 78.
They lack support for the driver loading parameters and other enhancements crucial to some of successes described below.  Drivers from linuxVER.zip ltmodem-VER.tar.gz kits should NOT be mixed  Each driver pair will only be functional with its own /dev/Node.

The following file will direct unloading of drivers upon ppp shutdown:
----------------------------------------------------------------------------
#!/bin/sh
#  Copy out to /etc/ppp/ip-down.d/mod-down
#     and to make executable :
# chmod +x  /etc/ppp/ip-down.d/mod-down
#   The modem drivers are removed by
modprobe -r lt_serial

#   The ppp drivers by:
/sbin/modprobe -r ppp_deflate
sleep 1
/sbin/rmmod -as
sleep1
/sbin/rmmod -as
--------------------------------------------------------------------------------



CASE HISTORIES - easy installations are most common.
     Mandrake 8.0 --
     Acer laptop 514TE ---
     Suse with 2.4.7-4GB

BIOS changes from PNP --> Other are sometimes necessary.  See DOCs/BIOSaccess.txt
Port specifications within the bootup BIOS have proven necessary in some Dell laptops.

Some diligence effort is needed with particular hardware or Linux distributions.
 A 3rd Forcing parameter is needed, as in 5.78e and 5.78f releases.
    See DOCs/Insert-param.html for details and history.
For PCI card modems ONLY irq changes in the Forced parameters should be attempted if necessary.
    The defaults of the PCI card should be utilized for the ioport and BaseAddress parameters.
Two very useful developmentat reports were:
        Gaël Delalleau's  comparison of 2 parameter 5.99a and 3 parameter 5.78e with Toshiba laptop
        Bernard Holzmayer's   Acer Extensa 500T (=Travelmate 500T) laptop.
For ISA card modems, /etc/pnp.gone can hinder function, the problem of NO DIALTONE .
   Release 5.99b  --  Implementation of the 3rd parameter for Forcing resource choices.
     Dell Inspiron 7000 report from Denis Auroux  and with much more detail for Redhat 7.1.
                  options lt_modem Forced=3,0x130,0x2F8   set in /etc/modules.conf  for automation.
           Inspiron 2500 with combo NIC & modem.
           Dell L400
           Dell 17k   -  options lt_modem Forced=3,0x130,0x2f8,0
     Acer Extensa 501 laptop  - Forced=3,0x108,0x2e8    with details for RedHat 7.1.
                          500T            Forced=3,0x108,0x2e8  , also available in Italian
                  100T            Forced=3,0x108,0x2e8
           Travelmate 600TER  though with irda conflict

     Toshiba 530CDT            Forced=3,0x130,0x2f 8
           Tecra 8000             Forced=3,0x1c00,0x2f8

     Some IBM Thinkpads have Lucent modems -  but the drivers  provided are the now dated release 5.95.
           Thinkpad i1410 --  Thinkpad i1411
                  T20, with Debian 2.2.r2
                  A22p under Red Hat 7.1  & Mandrake 8.1
                          A22m

      Compaq  Armada E500 , M700
                     Presario 336     Forced=3,0x2ff,0x2f8   , from  peter.stromberg AT dynamics.saab.se
                     Presario 800 T1220 1238 1245, Evo N400c, 220, 1690 1800
                                  800 T FAILURE despite extended knowledgeable efforts, with Askey build modem.
     HP Pavilion 6736 KR --  in the BIOS settings, turn off the (Win98) setting for the OS
                      7861

            Siemens laptop (lifeserie c) with ltmodem/intel_ethernet express combination.
    Fujitsu-Siemens Lifebook E-6560  - use in /etc/modules.conf
options lt_modem vendor_id=0x11c1 device_id=0x0440
                       Amilo D  B142, complete report

PCMCIA  modem guidance:
 32 bit  Cardbus, recognized as anamalous memory.
 There are now three types of bridges for PCMCIA support.
To achieve support through Texas Instruments PCMCIA sockets, a modified driver kit may be necessary, and is available at:  http://www.heby.de/ltmodem/pcmcia
Managing PCMCIA  and PCI modems on the same PC.



Post install issues - there is much useful information in DOCs.

Ethernet function will commonly interfere with modem usage, unless the System is set up by an expert.  The simplest avoidance is to shut ethernet down with:
# ifdown eth0
or
# ifconfig eth0  down

Adapting to the device file system used in Mandrake 8.1 is described in DOCs/DeviceFileSystem.txt

For the 2.4..nn kernel series, verify that the ppp utilities are at least version 2.4.0

Using the Microsoft Network under Linux is possible.

Infrared communications are compromnised by modem usage.

To get on the Internet, Root must set up a DialOut script. To setup the utility wvdial  with ltmodem drivers, a temporary symbolic link  /dev/modem --> /dev/ttyLT0  is necessary. It is not ncessary for Systems using the Device File System.  Read DOCs/wvdial.txt for guidance.   There is a wvdial FAQ.

General guidance on many other post install issues  is provided by Jacques Goldberg.
If you have ppp problems under 2.4.nn kernels, upgrade ppp and module utilities.
It  is good to have a copy of the modem command set .

While many Systems easily achieve CONNECT speeds near the 56 mH maximum, others benefit from the proper use of Country Codes (see DOCs/CountryCodes) and special Init strings.  There are Local phone company issues and consequences to avoid.



Problem avoiding and solving

Linux User Groups in many countries can be found through http://www.linux.org/users/index.html.  If you are a Linux Newbie, locating an experienced User nearby could greatly aid your problem solving.  There is a dedicated Help Site for common Newbie issues.   While discuss@linmodems.org aspires to provide some help beyond bare driver functionality, there is a Linux Documentation Project with help on many related topics.

Conservatively upgrading kernels and modules.
Generally new modules/drivers must be recompiled with each kernel upgrade.   It is wise to maintain the prior functioning kernel+modules set, while installing an upgrade.  In particular, the prior communications capabilities should not be be removed, until verifying that the new communications  are functional, whether by modem, ethernet or whatever.  Otherwise an annoying necessity of being off line under Linux may be incurred, when further Linux files/sources are needed to get back on line.  Here is a particular report of a 2.2 --> 2.4 upgrade problem.

Whenever the kernels and/or modules are changed, dependency files must be rebuilt.
On Debian related systems with a folder   /etc/modutils/,
    Root /Superuser should run the command: update-modules, which includes depmod -a.
For other Linux distributions, the relevant command is just: depmod -a.
There is a searchable archive on Linux upgrading issues.

Here are Information gathering instructions to follow, before querying discuss@linmodems.org on Winmodem isses.

Lockup troubleshooting -  Run diagnositics and report to the List if necessary.

A tool for displaying PCI IDs generally, in addition to the utils/scanPCI for ltmodems specifically.

Driver compilation failures are Most Commonly due to inadequate kernel-header resources.  Read revelant sections of 1ST-READ and  DOCs/compile_failures. A "make dep" is essential.  Directions for Suse 2.4.0  and 2.4.4 - 4GB.

Failure of lt_serial to insert (insmod lt_serial) can be due to improper Flavor matching of a kernel and modem drivers.

"Unresolved symbols" complaints during the "depmod -e" test may only reflect trivial sub-version differences between your running kernel and that of the kernel headers used in compiling the modem drivers.  Their are the following solution routes:
1)  Use fixscript V1.8 after reading the explanations towards the end of 1ST-READ, in DOCs/  and utils/  . The most recent version can always be downloaded from http;//www.heby.de/ltmodem.  The downloaded fixscript.gz MUST only be unpacked (gunzip fixscript.gz) under Linux
2)  Use Kees Vonk strategem  of renaming the kernel-headers version: change the first line of
    /usr/src/linux-2.4.2.SuSE/include/linux/version.h from:
    #define UTS_RELEASE "2.4.2"    to    #define UTS_RELEASE "2.4.2-4GB"
3) Flavor match versions of binary installers carefully, the Debian example.
4) Most laboriously, install and use if necessary full kernel-sources, as described in DOCs/Compile_failure.

DOCs/Insert-param.html directs the checks to do if modem drivers do not initially load, for example,
      the init_module complaint:      lt_serial.o: init_module: No such  device
This open source ltmodem-0.9.9.tgz may be useful for defining resources, to aid specification of Forced parameters, but  before running the tests First:  rmmod lt_serial lt_modem

Resolution of audio card conflict. -- case report
Audio card resource conflicts can be a cause of NO DIALTONE.
Crash upon disconnect was solved by compiling ALSA sound support into a 2.4.9 kernel

Detection of the modem in the presence of a PCMCIA ethernet card may be aided by use of the forth insertion parameter.
id=0x420 Xircom/Lucent modems  have an optico-electronic coupling needing additional treatment beyond that in the core AS drivers.  A solution was requested from Xircom (now an Intel subsidiary). Use of the 4th insertion parameter may help. see DOCs/Insert-param4.txt , also available on-line, thanks to Jeffrey Phillips.

Modem sounds are not produced in a Small Minority of the 5.99 installations, in which functionality is otherwise fine. For one such system, use of the older archived 5.95 release did Restore sound.

A modem string with X2  only increases modem to CPU speed, not necesssarily CONNECT speed.

Co-existence of ethernet and ppp - Jacques Golderg comments.

The kppp configuration file may be different for each user.  Thus if dialup works for Root, but fails for a User, try resetting the script of User.

If ppp CONNECT is achieved, but  Internet navigation  fails, compare PING tests with IP NumericAddress and the corresponding NameAddress.  If there is a successfull "ping" of  a numeric IP address, such as the nameserver specified in /etc/resolv.conf
    ping 207.172.3.8
    PING 207.172.3.8 (207.172.3.8): 56 data bytes
    64 bytes from 207.172.3.8: icmp_seq=0 ttl=253 time=168.2 ms
while there is failure using a named address, such as "corel.com", then only NameServer function requires configuration.

Loading of ppp modules may fail due to inadequate aliases lists.

Check for proper country codes if there are dial sounds but no carrier.
      Country code lists are in the DOCs/ folder.

TAM functionality? Ed Schulz at AS reports that the current Linux ltmodem code does NOT include voice functionality.



Most entries above are from the Linmodem Archives,

Next entry???
Please add useful new Links/URLs with good Descriptive titles Herein.
Then send your update to:
     Jacques Goldberg <goldberg@phep2.technion.ac.il>
      MarvS <stodolsk@rcn.com>

Periodically, it may become appropriate to compact some of these contents into a HowTo.
Pages such as this can be hosted for general access, for example on the server
    which Jacques Goldberg has prepared for seaching the archives.
They could be announced through:  announce@linmodems.org
Such postings and access will greatly diminish the frequency of Newbie Repeater Questions.



List issues
Anti-SPAM measures are implemented, though occassional, there is a leak through.

To Unsubscribe, send an email from your initial subscription address to:
           announce-unsubscribe@linmodems.org
List founder Russell Nelson <nelson@crynwr.com> comments in response to:
         > so im asking, no im begging please remove me from THE LIST.
"It's quite possible that occasionally there is a problem.
But I need you to send me a copy of all the mail you sent to the list server,
and a copy of all the mail it returned.  Otherwise I cannot diagnose the problem."



Other Winmodem Chipset support.

Compiler kits available:
       Intel HaM driver, with a current beta download site.
       IBM's Mwave modem driver for Thinkpad 600E and newer laptops.  The source code is now part of the regular kernel-sources release.  This is new modem type, neither ISA or PCI. Rather it is similar to ethernet cards with respect to kernel access.
       for PCTEL, there is a resource site
Binaries only:
       For Conexant HSF modems, only binary drivers are supplied through Olitec.
             A HOWTO is available, and more here.
            ONLY the HSF is supported now with HCF support projected in May2002, see question 11.
       Driver for ESS ISA modems are only for earlier 2.2 kernel versions.

Some combination ethernet-modem cards have a supported chipset as in the
 Siemens laptop (lifeserie c) as in the ltmodem/intel_ethernet express combination.

No support:
       for 3COM/US Robotics Inc. winmodems,
           though Contrioller based modems are supported through the standard serial.o  drivers.
       Lucent AMR soft modems (without DSPs, digital signal processors).
       Motorola SM56 driver support began with the 2.4.5 kernel code, with relevant info gathered at:
       http://linmodems.technion.ac.il/Motorola.html  but support has terminated.