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

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

If you have been directed to this file after a successful run of
build_module, CONGRATULATIONS on achieving a non-trivial compile process. 
particularly if you are a Linux Newbie!

There are two alternative routes to proceed, both reversible.
The current route can be continued:
  build_module > ltinst2 > autoload > checkout
It is recommended for the experience if these modem drivers have not been
previously installed, with benefits of diagnostics within the scripts.
The installation can be completely reversed by:
  ./ltuninst2 > ./cleanup
And please do this if you wish to try the alternative route.

If your Linux distribution has a software/dependency system that installs FileNames.rpm
(prototype RedHat) then the alternative is to use:	 ./build_rpm
If your Linux distribution has a software/dependency system that installs FileNames.deb        
(prototype Debian) then the alternative is to use:	 ./build_deb
If either case, auxilliary software is Essential for to support assembly of
the modem drivers into Installer packages such as:
    ltmodem-SomeVersion.rpm
    ltmodem-SomeVersion.deb
Your Distribution will have information on the needed Packaging software.

Installing with the following commands directly or through "front end" utilities:
   rpm -i ltmodem-SomeVersion.rpm
  dpkg -i ltmodem-SomeVersion.deb
installs the precompiled drivers and runs autoload.
Autoload making the modem device nodes and providing for autoloading of the drivers 
through lines appended to: /etc/modules.conf
If your System uses devfs (Device File System), a file
  /etc/devfs/conf.d/ltmodem
will be written or lines written to:
  /etc/devfsd.conf
depending on the devfs style of your Linux Distro.

So why bother with the Installers, when the first route works?
There are two reasons.
It is all too easy to introduce software incompatibities or break software
inter-dependencies of a computer system.  The rpm or Debian packae
maintenance systems provide Considerable Protection agains such faults.
They also provide for complete removal of all installed components through
commands such as:
   rpm -e ltmodem-SomeVersion.rpm
  dpkg -r ltmodem-SomeVersion.deb
This should be done for exmaple, as you progress to newer kernels.

The second reason is that the Installer packages are Portable.
In your Home/Institution they can be carried by floppy disk or through LAN
to other PCs.  Thus all the PCs do not have to have the 20 some MB of kernel
sources installed.  Or alternative, the Installers can be sent as email
Attachments to your grandparents or friend in the "Third World", who don't have
capabilities for compiling.

Lastly, please note that each of:
  build_module
  build_rpm
  build_deb
do support compiling of drivers with versions different from that of a
current kernel.  If suffices that the kernel headers for the target drivers
be resident.  For example, while your current kernel is say 2.4.8, drivers
could be compiled and packaged for say a kernel version 2.4.18. The command 
is of style:
  build_module 2.4.18

This capability enables availability of the modem drivers, BEFORE abandoning
your current kernel with its Internet connectivity. Please do remember that
it is not necessary to delete older kernel+modules+drivers when you do an
upgrade.  This can be done AFTER confirming all essential functions are served under
the kernel. It is Most Embarrasing if there is a failure of communications
under a new kernel, and its predecessor with modem drivers have been
removed!