See also the Linux survey of laptop with internal modems .
For a general survey see the Modem Chipsets Index(http://www.modem-help.co.uk/chips/)
Recently a binary driver for the devices based on the Lucent chipset became available, see Linmodems.Org(http://www.linmodems.org)
This is a set of Linux drivers for the ACP modem (Mwave)(http://www-124.ibm.com/acpmodem/) , a WinModem. It is composed of a loadable kernel module and a user level application. Together these components support direct attachment to public switched telephone networks (PSTNs) and support selected world wide countries. This driver provides support for the IBM ThinkPad 600E (600, 770). The modem also supports the standard communications port interface (ttySx) and is compatible with the Hayes AT Command Set.
This modem (aka Rockwell modem) is used in e.g. some models of the SONY VAIO series. You may get a binary driver from MBSI(http://www.mbsi.ca/cnxtlindrv/).
Conexant/Rockwell modem HOWTO(http://www.tldp.org/HOWTO/Conexant+Rockwell-modem-HOWTO/index.html)
For the modem made by Ambient(http://www.ambient.com/), you may find a binary driver from Intel(http://developer.intel.com/design/modems/index.htm) .
This Linux driver. supports all laptops, using the SIS630(S) chipset: Gericom Overdose (Webboy), Baycom Worldbook II, Sager ... (in fact these are laptops manufactured by Clevo(KAPOK) Modell 2200C/2700C).
See ESS Modem Mini FAQ(http://wettstein.homelinux.org/ess/).
Internal PCMCIA modems usually work with Linux. But there are no guarantees. And some are so called PCMCIA WinModems. Look here(http://www.heby.de/ltmodem) for a driver of Lucent based WinModems.
On this page(http://www.sfu.ca/~cth/ltmodem/) you'll find Linux drivers and documentation for so called Winmodems with Lucent Apollo (ISA) and Mars (PCI) chipsets. Lucent AMR modems are not supported by this driver. The core communications code of these kits is the property of Agere Systems, Inc. (formerly known as Microelectronics Group of Lucent Technologies). The open source parts were modified to implement some additional features. [I didn't investigate the difference to the above mentioned site, yet WH]
Some internal modems will NOT work with Linux , if the laptop has an unsupported WinModem or SoftModem . This is caused by non-standard hardware.
Quotation from the Kernel-FAQ: 'Why aren't WinModems supported? (REG, quoting Edward S. Marshall) The problem is the lack of specifications for this hardware. Most companies producing so-called WinModems refuse to provide specifications which would allow non-Microsoft operating systems to use them. The basic issue is that they don't work like a traditional modem; they don't have a DSP, and make the CPU do all the work. Hence, you can't talk to them like a traditional modem, and you -need- to run the modem driver as a realtime task, or you'll have serious data loss issues under any kind of load. They're simply a poor design."'
A quotation from WinModem are not Modems(http://www.xmodem.org/) :'It has been pointed out to me that the name "Winmodem" is a registered trademark of U.S. Robotics and, subsequent to their merger, 3Com. I'm sure that they are proud of this fact ;) In any case, when I refer to Winmodems, please read it as "Winmodems(TM), host-based modems, HCF-modems, HSP-modems, [soft-modems] and all similar modem-like hardware." '.
From <discuss_at_linmodems.org>, <LeRoutier_at_wanadoo.fr> wrote: "While surfing, i found a site where we can download a DDK for WinModems(http://www.krftech.com/windrv/index.html) . It's available under Win32 and Linux (yes, you read well). . Look carefully at it, it should contain great info about WinModem internals I hope it helped. If not, sorry ."
As a last resort you may use an external modem.
What Kind of Modem Is Used In My Laptop? How to check it.
Bus 0, device 16, function 0: Communication controller: Lucent (ex-AT&T) Microelectronics L [..] Medium devsel. Fast back-to-back capable. IRQ 11. [..] Non-prefetchable 32 bit memory at 0xfedffc00 [0xfedffc00]. I/O at 0xf4e8 [0xf4e9]. I/O at 0xf000 [0xf001].
ATI3 LT V.90 Data+Fax Modem Version 5.54
If you have an internal PCMCIA modem check the output of
There might be other ways to get information about the internal modem.
If you need to get information about an unknown device you may look up the mapping of FCC IDs(http://www.fcc.gov/oet/fccid/) by the U.S. government. In the database of PCI manufacturer and device IDs (
lspci) or in the database of PnP device IDs (
I purchased a refurbished Compaq Armada SB (AR SB 5233/32/4.0/DMT), and it came with an internal modem. Compaq calls it a "Compaq Armada 1500 Series 560CL Telephony Modem". The Compaq software that claims to upgrade it to V.90 calls it a "Compaq Armada Controllerless Integrated Modem Deliverable". After the upgrade, the modem firmware is version 1.6.19, and the Compaq Diagnostics displays "UNIMODEM1D905A3B". The word WinModem did not show up anywhere. Of course, RedHat 6.0 will not recognize it.
On the bottom of the computer, there was a sticker added with:
COMPAQ COMPUTER CORPORATION MODEM MANUFACTURED IN TAIWAN SERIES NC1000 COMPLIES WITH PART 68.FCC RULES. FCC REGISTRATION NUMBER: CNTTAI-32206-DT-E REN: 0.6 LOAD NUMBER: 0.6 JTM APPROVAL NUMBER: DAFH/36A/1097/S 307363-001 CY S59
on that sticker was a Industry Canada sticker with:
780 8534 A
I purchased a T-8 Torx screw driver to look at the board, and I hope to find a replacement modem that I can use with Linux.
Here is info that was on the modem.
A sticker had:
Compaq Series NC1000 See Manual Complies with Canadian ICES-003 Class B. FCC UL Tested To Comply With FCC Standards FOR HOME OR OFFICE USES 307362-002 S59
Another sticker with a barcode of:
below an etched:
A bigger barcode sticker on the Lucent chip had:
REPLACE WITH COMPAQ SPARE SPS: 255245-001
The Lucent chip had:
LUCENT 1643 T48PCH 12 9806S 3256540 C 95 LUCENT
Lots of small stickers all over it. Almost a fire hazard!
"REV V1.00" "159" "E01" "307" "H"
A silver oval thing had
A small chip had:
1034AH 9749H 1479974
If there is any tool that you would like for me to run to squeeze more info out of it, let me know.
Thanks to the contributors as mentioned above and to the members of the Linux-Laptop and Debian-Laptop mailing lists. Special thanks to: