Using winmodems under Knoppix.
Just worked this out for the Lucent ltmodem code supporting the DIgital Signal Processing chipset (DSP) using the ltmodem-8.26a.tar.gz supplied at http://ltmodem.heby.de. For 2.6 kernels use the ltmodem-8.31a8 or subsequent updates. More general issues are also addressed below

Problem 1) on the Knoppix CD there is specified something like (I'm not under Knoppix now, rather a standard Debian)
$ ls -l /usr/bin/gcc*
lrwxr-xr-x 1 root root 7 May 30 09:15 /usr/bin/gcc -> gcc-3.3
-rwxr-xr-x 1 root root 69960 Mar 10 2004 /usr/bin/gcc-2.95
-rwxr-xr-x 1 root root 85740 Apr 1 19:43 /usr/bin/gcc-3.3
That is, the default gcc is gcc-3.3. BUT the the 2.4.26? Knoppix kernel was compiled with gcc-2.95, and the modem drives MUST be also.
Get your Knoppix compiler version from within:
~$ cat /proc/version
Linux version 2.4.27-1-686 (joshk@trollwife) (gcc version 3.3.4 (Debian 1:3.3.4-7)) #1 Sun Aug 15 01:13:41 UTC 2004
which on my current boot shows: gcc version 3.3.4 was used to compile the boot kernel.
The modem driver package will generally try to use the default gcc--> gcc-whatever burnt into the CD. If you have done a KNOPPIX hardisk install, you need only change the symbolic link to the correct one and the standard driver compile will probably be OK.

2. ltmodem fix) The ltmodem compile sanely aborts when a compile is attempted, because of the gcc problem. Being co-maintainer of the ltmodem package, I knew who to do a modification of the Makefile, to specify usage of the required gcc-2.95. Then the driver compile went to completion.

3) The set up was continuned with
# su root
Manual creation of the driver port:
# mknod /dev/ttyLT0 c 62 64
and a symbolic link
# ln -s /dev/ttyLT0 /dev/modem
the drivers were inserted
# insmod ./lt_modem.o
# insmod ./lt_serial.o

Harder + driver sanity was checked with:
# wvdialconf /etc/wvdial.conf
during which the symbolic link /dev/modem --> ./dev/ttyLT0 was followed.
an alternative link for this test could have been made with
# ln -s /dev/ttyLT0 /dev/ttyS14
as S14 iand S15 are reserved for experimental usage.

If successful, there is generated /etc/wvdial.conf
which must be completed by editiing in your dialup Name, Password, and Phone# . Here is a smaple wvdial.conf:

[Dialer Defaults]
Modem = /dev/modem
# if the port does not have a name style /dev/ttyS*
# if will not be tested by wvdialconf, so there is necessary either
# /dev/modem --> /dev/TrueModemPort
# or /dev/ttyS14 symbolic link to the /dev/TrueModemPort
Baud = 115200
Init1 = ATZ
# An Init2 like the following is necessary if not in the USA
# Init2 = AT+GCI=< hexadecimal country code>
# in which case make the following Init3
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
Phone = 3019178111
Username = marvstod
# For MSN.NET/COM users, specify your Username as:
# Username = MSN/Username
Password = MyPassword
# if using SmartLink slmodem drivers uncomment the next linet:
# Carrier Check = no

A dialout was then successfull with:
# wvdial

Most generally for setting up a modem, start with my diagnostic tool:
http://linmodems.technion.ac.il/#scanmodem
and more generally browse http://linmodems.technion.ac.il/ which does have a search engine to the [email protected] archives.
Please post modem questions to [email protected]
If you have done a Knoppix hard disk install the guidance from these sources should suffice for all winmodems, except the non-supported 3COM winmodems.

For CDROM Knoppix boot users, you will want to save newly compiled drivers
and the wvdial.conf
to some storage media, where you can access them on the next bootup,
You will need to:
a) make the modem ports
b) insmod PathtoStored/ModemDrivers.o
c) cp Stored/wvdial.conf /etc/wvdial
d) wvdial
and that should get you on line. There will be special cases, as both driver styles and modem port creation methods are diverse. Time permitting I will progressively work through these problems for the several winmodem types and post to this List and [email protected] Look at http://linmodems.technion.ac.il/, where I'll have a Knoppix section setup

Therein there should be around Monday, Sept 28 a setup package for the
ltmodem-2.4.26 case, as only code experiences Users will be able to modify the ltmodem Makefile as I did.

MarvS
scanModem maintainer
ltmodem co-maintainer