This modem enjoys the most support under Linux, in that there exist three different
There exists a manufacturer-unsupported, half-binary/half-open-sourced
kernel module, originally designed for Red Hat 6.2's 2.2.14-5 kernel,
but substantially reworked by Mark Spieth and others to function
with 2.2.x and 2.4.x kernels. This is driver version 5.78(c,d,e,...), and
is the driver you are most likely to have success using.
There exists a manufacturer-unsupported, binary-only
kernel module, compiled under Red Hat 6.0's 2.2.12-20 kernel.
This is driver version 5.68.
Some open source tools for use with Lucent modems are
Pavel Machek writes that "It is not too useful,
however: it is a hardware driver, and without a v.34 protocol stack, you
can't connect to your ISP. It is enough to turn your Lucent winmodem
into an answering machine, however."
It should be noted that the binary-only driver module (from "linux568.zip")
contains code from the GPL'ed Linux serial.c driver, so, since
the source code for the
modem driver is not available, trafficking in this driver is apparently
in violation of the GPL. Distributing the partially open source driver
("i56lvp578.zip") may or may not be technically legal, since the GPL'ed
code, though not yet linked with the closed-source code, is certainly intended
to be so. See
this Kernel Traffic issue
and a Linux-Kernel mailing list archive for the week including Dec. 3rd, 2000,
for more details.
Binary-only drivers for ES56T-PI (PCI) and ES56V-I (ISA), compiled under RedHat 6.0's kernel
2.2.12-20, are available. The driver has been used via forced insertion up through kernel 2.2.15,
and up through 2.2.17 using the "tty.h" patch described in the "Tips and Tricks..." section, above.
There are apparently two types of PCTel module package around.
A package (rpm or deb) which installs
two module files, pctel_hsp.o and pctel_pci.o, in /lib/modules/2.2.16.
With such a package, if you are running a kernel more recent than 2.2.16, you
will need to use forced insertion (insmod -f), and if you are not successful, might
try the "fixscript" method used with the Lucent 5.68 and ESS modules above - but, note
that this has not, to my knowledge, been tried out yet. If you are running a kernel
older than 2.2.16, you should consider upgrading your kernel, or else try the
fixscripting as well (this is also not guaranteed to work).
Please send me a report if you get these to work.
A package which, when unpacked, gives a set of libraries (hsp.a, etc...)
and a small C source file (ptmodule.c), which should be in directories like lib/
and src/module/. If there are no directories, create them and arrange the files with:
Now go to the directory src/module and type make. This should generate the module
file pctel.o, which will appear back up in the directory lib.
(The driver module is not the object file ptmodule.o in src/module!)
The apparent version of the module generated in this way will match your current kernel version.
With the modules in hand, proceed to install as follows:
Change to the root user: su (enter root password when prompted)
Create the device file: mknod /dev/pctel c 62 79
Make convenience device: ln -s /dev/pctel /dev/modem
Make convenience device: ln -s /dev/pctel /dev/ttyS15
Set device ownership: chgrp uucp /dev/pctel
Set device permissions: chmod 666 /dev/pctel
Install module file (only for package type 2, above): cp pctel.o /lib/modules/`uname -r`/misc/
Insert module(s) in kernel with insmod -fmodulename
There exist drivers for kernels 2.2.14, 2.2.16, and 2.2.17 at
The page is in French,
but the installation commands are given on the page in boldface red text
(you can also use the
Essentially, download the appropriate package, unpack it with tar -zxvf,
and run the installation script ins_all.
This driver is a bit finicky (with the most common symptom of failure being
the "NO DIALTONE" response), but a number of people have been able to get
it to work, usually by inserting their modem's vendor ID in the modem's
.inf file, perhaps along with a change of the device major number from 254 to 253.
See the Linmodems.org mailing list archives for details; one example of many is given
Mikhail Moreyra has written a GPL'ed driver for the CL-MD5620DT chipset
which can do up to 33.6 kbps; however, this is alpha software
and should be treated with due care. The driver can be obtained at
Gabriel Gambetta (ggambett(at)internet.com.uy) issued a patched
version of the driver to allow standard AT modem commands;
you can get this version at Rob Clark's site
A driver for the HaM modem was beta-tested in early 2001 and is
expected to be released quite soon.
An rpm package with a driver for the 3Com MDP3900V-U modem
(apparently found in the Dell Dimension L733r) was
posted to the Linmodems.org mailing list
click here for more information), and is mirrored
A request for comments was posted by a 3Com official
about the possible demand for a binary-only driver for their miniPCI combination
here on the Linodems.org mailing list; please respond to the address
given, firstname.lastname@example.org, and not to the mailing list.
Though to my knowledge no driver has yet been
released, Werner Heuser's
miniPCI page has more information and links.