Upgrade pppd to at least version 2.4.0 for service under 2.4.nn kernels!!

 The modem drivers are NOT loaded at boot up.
 Rather within /etc/modules.conf the lines:
 	alias char-major-62 lt_serial
 	alias /dev/tts/LT0  lt_serial
        alias /dev/modem    lt_serial
 enable loading of the drivers on demand, such as by ppp intiation.

 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     only if the System has modular isa-pnp.o 
 --------------------------------------------------------------------------------------

 Should driver loading or NO DIAL TONE problems be encountered,
 	read the guidance in DOCs/Insert-param.html.
 Related information is also contained in DOCs/Ltmodem.html,
   which relates problems encountered and overcome with particular PC hardware.


Run the following command sets to gain some understanding of functionality and components/
 
$  grep lt_ /etc/modules.conf 
display lines governing demand loading of the modem drivers,

$  grep LT0 /etc/devfs/conf.d/ltmodem 
OR for Mandrake 8.1 and later
$  grep LT0 /etc/devfsd.conf
displays lines maintaining a symbolic link under device file system usage:
   /dev/modem --> /dev/tts/LT0

$ ls -l /dev/modem 
should display
  /dev/modem --> /dev/ttyLT0
OR it the device file system is implemented
  /dev/modem --> /dev/tts/LT0

If all is OK, both lt_modem.o and lt_serial.o should be loaded by:
$ modprobe    lt_serial
Check with: 
$ lsmod 
and both drivers should removed by:
$ modprobe -r lt_serial 
$ lsmod 

With these tests successful, modem drivers should be autoloaded 
merely by initiating modem usage.

Use your Linux distributions utilities, to set up dialup scripts.
If using the device file system, /dev/modem MUST be specified as the port.
Minicomm is a good utility for testing modem functionality.
Remember that a response to AT
  OK
just comes from the driver, while successful ATI queries 
must actually access the modem firmware.

For a report of actions during initiation of ppp, first as Root:
$ tail -f /var/log/messages & 
The & allows continued access to the Command Line during the ensuing report.   
Do few ENTER, to clear space.
Then initiate a ppp session to see the actions culminating in an Internet
connection.  There should be a report of the successive actions. 
After a CONNECTtion has completed, tail can be stopped by:
$ fg tail
Ctrl-C

If you wish to use the smart utility wvdial.
First read wvdial,txt for instructions on the intitial 
$ wvdialconf

To automate some removal of modules after ppp termination,
install the following file:

#!/bin/sh
# file  /etc/ppp/ip-down.d/mod-down
# As Root: chmod +x v/etc/ppp/ip-down.d/mod-down
#   to make executable
#
# remove ppp related modules
sleep 20
/sbin/modprobe -r ppp_deflate
sleep 2
/sbin/rmmod -ars
sleep1
/sbin/rmmod -ars

Should complete removal of the ltmodem installation be desired, run
                    ./ltuninst2
                    ./cleanup 

The still in maturation utility
                    ./checkout
will display facets of your installation and run ./wvdialconf
if the wvdial package is installed.

It there are any problems getting online, use utils/unloading
to unload excess modules, particularly including ethernet drivers.

 		Get on line and Enjoy!!   
 Report Problems or Praise to discuss@linmodems.org. 



