Stuff You'll need:
The Kernel Source for your *INSTALLED* Kernel (kernel-source rpm)
isapnptools (isapnptools rpm)
The open source LT Winmodem drivers
A bit of luck
a Guinness

Setting up the Modem:
In order to install these modules, the documentation says you need to have the kernel headers installed.  This is not true for Redhat: You'll need the entire kernel source.  The source for the kernel is located (I think) on disc 2 of the installation cds, and will be under the Development/System menus in gnoRPM.  Install the kernels and then do:

$ ln -s /usr/src/linux /usr/src/linux-x.x.x

..where x.x.x is the kernel version you're running.  This creates a symbolic link to the linux-2.4.2 directory, which pretty much fools the system into thinking that /usr/src/linux is really /usr/src/linux-x.x.x. For example, my kernel version is 2.4.2 (stock kernel from Redhat 7.1 install) and when I installed the kernel-source RPM, it created a directory called /usr/scr/linux-2.4.2, so my line would read:

$ ln -s /usr/src/linux /usr/src/linux-2.4.2

Now, you've got the kernel sources installed, you need to type uname -r to make sure that the version of linux you are currently running (read the output of this command) matches the version of your installed kernel.  If it does not, you can get the proper version at www.kernel.org.

Ok, so now everything's cool, right? Right.  So now we need to compile the specific kernel headers we need to compile the Winmodem drivers, so we're going to do the following:

$ make dep

This'll take a while, about 5 or so minutes on my laptop, probably 15 or so on the stock 1410 (w/32mb ram).  Go get a cold Guinness while it compiles.  mm.. Guinness.

Now, let's look and make sure it got some headers. Type:

$ ls /usr/src/linux/include/linux

You should see exactly 1 assload of filename.h files.  These are your kernel headers.  To verify, let's type:

$ cat /usr/src/linux/include/linux/version.h | grep UTS

Which will return:In order to install these modules, the documentation says you need to have the kernel headers installed.  This is not true for
Redhat: You'll need the entire kernel source.  The source for the kernel is located (I think) on disc 2 of the installation cds, and will
be under the Development/System menus in gnoRPM.  Install the kernels and then do:

       $ ln -s /usr/src/linux /usr/src/linux-x.x.x

..where x.x.x is the kernel version you're running.  This creates a symbolic link to the linux-2.4.2 directory, which pretty much fools
the system into thinking that /usr/src/linux is really /usr/src/linux-x.x.x. For example, my kernel version is 2.4.2 (stock kernel from
Redhat 7.1 install) and when I installed the kernel-source RPM, it created a directory called /usr/scr/linux-2.4.2, so my line would
read:

       $ ln -s /usr/src/linux /usr/src/linux-2.4.2

Now, you've got the kernel sources installed, you need to type uname -r to make sure that the version of linux you are currently
running (read the output of this command) matches the version of your installed kernel.  If it does not, you can get the proper
version at www.kernel.org.

Ok, so now everything's cool, right? Right.  So now we need to compile the specific kernel headers we need to compile the
Winmodem drivers, so we're going to do the following:

       $ make dep

This'll take a while, about 5 or so minutes on my laptop, probably 15 or so on the stock 1410 (w/32mb ram).  Go get a cold
Guinness while it compiles.  mm.. Guinness.

Now, let's look and make sure it got some headers. Type:

       $ ls /usr/src/linux/include/linux

You should see exactly 1 assload of filename.h files.  These are your kernel headers.  To verify, let's type:

       $ cat /usr/src/linux/include/linux/version.h | grep UTS

Which will return:

       #define UTS_RELEASE "x.x.x"

..where x.x.x is your kernel version.

Finally, we can install the linmodem drivers.  To do this, type:

       $ cd /to_where_you_downloaded_the_drivers/ltmod*
       $ ./build_module

..and follow the directions.  Fair enough?  But you're not done yet.

build_module only compiles the drivers. Now you need to actually activate the puppies.  So you're going to do:

$ ./inst2
$ ./autoload

..but you're not done yet!  The drivers are installed and everything, but the modem is physically NOT active!  Install the isapnptools rpm. You need this to make the modem work.  You will  once that's installed you need to generate an isapnp.conf file which is what we'll use to activate the modem. to do this, you will type:

$ /sbin/pnpdump > /etc/isapnp.conf

This will generate a file in your /etc directory that contains config parameters for both the modem and the sound card. The sound card is listed first, so let's skip that bit.  We should see a part that says:

(CONFIGURE ACRd119/1 (LD 0

We want to trash all of the comment lines until it looks something like this (or you can just paste mine):

(CONFIGURE ACRd119/1 (LD 0
(IO 0 (SIZE 8) (BASE 0x02f8) (CHECK))
(INT 0 (IRQ 4 (MODE +E)))
(IO 1 (SIZE 8) (BASE 0x0130) (CHECK))
(NAME "ACRd119/1[0]{LT Win Modem        }")
(ACT Y) ))

Notice that I changed the "BASE" part on the second line to 0x02f8. You need to do that.

Now, (almost done) you need to type:

$ /sbin/isapnp /etc/isapnp.conf

This activates the modem. Yay!  Now, you can type:

$ cat /proc/isapnp | more

..and you'll see a couple lines that say something about the LT Win Modem "Device is active" and have a buncha 0xffff ports active, and have an IRQ of 255.  This is weird, but a good thing.

To make it activate on boot up, add:

/sbin/isapnp /etc/isapnp.conf

to your /etc/rc.d/rc.local file.

That's all you have to do! (whew!)

Problems/To Do List:
While I can get the modem to dial out, I can not keep a stable connection to my ISP, but this is *NOT* due to the modem installation.  This is due to my inability to set up pppd and wvdial properly.  Minicom works just peachy. :-)  ..I will publish my findings when I can figure out how to get the pppd to behave.

---

Original Sources:
Linux on the IBM Thinkpad i1410
A guide by Marvin (installing the drivers)
A guide by Jari (more install instructions + post install stuff)

About the Author:
I am not a linux expert. I don't pretend to be.  I have, however, been screwing around with computers since I was knee-high to a microchip (20 years ago! wow!).  This being said, I take no responsibility for anything my instructions do to your system.  I published this as a guide for those who need help getting this modem working on this particular laptop with this particular distribution.  Your milage may vary if you do not use exactly the same setup.