The files are below listed in order of their functionality, for the ltmodem-Version.tar.gz package.
FileList.txt - this file
scanPCI a symbolic link to utils/scanPCI
Tests for the presence of Lucent DSP modem hardware, with command line:
./scanPCI
1ST-READ - General instructions, particularly for Newbies.
utils/ksp.sh - Bob Arendt's script to aid setup of kernel sources and
headers. Prototyped for Red Hat 2.4.nn sources.
build_module - will compile modem drivers, IF the complementary kernel headers are present.
BLDrecord.txt with diagnostic information and advice is concurrently generated.
In case of failures, advice is copied into BLDrecod.txt
conf-report.txt - example of a successful report from the "configure" step of build_module
BLDrecord.txt is generated during build_module and contains diagnostic outputs and advice.
Options.txt - Dicusses build_rpm or build_deb alternatives to proceeding
with ltinst2 and autoload.
ltinst2 - will appear if build_module is successfull,
and copies the modem drivers into the kernel modules search PATH.
autoload - will appear if build_module is successfull,
Creates the modem device node and useful symbolic links to it,
Adds lines to /etc/modules.conf enabling autoloading of the modem drivers,
If the device file system (devfs) adds support lines to /etc/devfsd.conf or /etc/devfs/con.d/ltmodem
checkout - Resides in utils/. A link to it will appear if autoload is successfull.
Runs functionality tests on the installation, still under development in March 2002
Pre-installation of ppp dialer utility "wvdial" is needed to test the modem hardware.
build_rpm - Used to package the modem drivers into an installer: ltmodem-Version.rpm
Requires prior success with build_module
Requires the additional software for rpm package making. A subsequent
rpm -i ltmodem-Version.rpm
will perform steps of ltinst2 and autoload AND
Bring the Benefits of properly registering the modem software with your Distributions maintenance system.
As yet, checkout is not incorporated
build_deb - Used to package the modem drivers into a Debian style installer: ltmodem-Version.deb
Requires prior success with build_module
Requires the additional software for Debian package making. A subsequent
dpkg -i ltmodem-Version.deb
will perform steps of ltinst2 and autoload AND
Bring the Benefits of properly registering the modem software with your Distributions maintenance system.
As yet, checkout is not incorporated
NoEC.txt - Potential solution and discussion on No Error Control issues.
Tainted.txt - Info on Tainited kernel warnings
utils/ folder contents
----------------------
scanPCI - Tests for the presence of Lucent DSP modem hardware
ksp.sh - Robert Arendt's script for setting up sources for compiling,
prototyped for Red Hat
fixscript - a purely cosmetic tool which may be called during build_module, see DOCs/fixscript.txt
unloading - a utility unloading unused kernel modules, to obviate resource conflicts during modem tests.
CountryCode.tcl - atool for determining country codes
ltremane - for Expert use ONLY, in experiemnts to achieve multiple Lucent modem support.
DOCs/ folder contents
------------------------------
CREDITS - brief explanation of the history and Many Contributions to this volunteer package.
Ltmodem.html - Multiuse document including URLs to related information on line.
Copy to your Microsoft partition in not yet on-line.
ForNewbies - entry level explanation of sLanguage like kernel-headers and similar monsters.
Compile_properly.txt - How to setup the kernel headers needed for build_module.
Flavor.txt - Compiling properly won't be adequate unless the Flavor is correctly specified.
SMP.txt - Compiling properly won't be adequate if your kernel supports SMP.
conf-report.txt - a success example with added comments.
slackware - Guide to updating Slackware kernel+modules
Examples - What build_module outputs during a successful run.
build_rpm.txt What build_rpm outputs during a successful run.
LastAdvice - Read when the drivers were successfully installed, with autoload too.
Tainted.txt - Explains warning during insmod: taint the kernel-
modem600.txt - some technical info from Agere Inc,
modem822.txt - New features of the 8.22 source code release.
DeviceFileSystem.txt - Explanation of how device nodes and drives behave under the devfs,
which is standard for Mandrake 8.1
The manual step described is not necessary for post 6.00b15 installers.
Insert-param.html - Read if the drivers fail to load: parameters needed for some laptops mostly.
with interesting history of the parameter implementation.
andreas.txt - With internation intrigue, exciting history of the implementing the first insertion parameters.
Insert-param4.txt - Rarely needed usage in the presence of Xircom PCMCIA LAN cards.
/home/marv/ltmodem/DOCs/modem600.txt
wvdail.txt - How to run the utility: wvdialconf
chatscript.txt - What is reported during a successful dialup
post-install.html - if you have problems getting online
Country_codes - important if the modem default is not set to the country you are in.
LAN_ppp_DNS - If you really must use LAN and ppp simultaneously
Good primer on DNS (domain name service) too,
No_DialTone - What to do if
BIOSaccess.txt - may be necessary.
Suse_permissions - If you can dialout as root but not as a User
Server_issues - Problems with certain Internet providers.
linmodem-howto-all.html - needs an update.
==============
YOUR IMPROVEMENTS, foreign translation or addition to these documents will be appreciated.
MarvS - 5March2002
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.