Symptom:
An internal modem, that is a modem aboard a card which can be plugged into
the bus of a pc, is built in. Drivers are supplied for
this modem for the Windows operating system, especially in the VXD format.
The modem is nearly always Plug-and-Play
capable. The mainboard BIOS is Plug-and-Play capable, too. Plug-and-Play functions
of the mainboard BIOS are not disabled
for testing purposes. The BIOS of the computer displays only the previously
existing internal respectively external serial ports,
but not any additional port supplied by the card modem. Linux does not recognize
the modem.
Cause:
The modem is likely to be a so-called WinModem, that is not controlled
by a serial port, but the digital signal processor (DSP) on
board must be controlled directly by the main CPU. There are a well defined
command set for modems, standardized by the ITU
(International Telecommunications Union, www.itu.ch) and TIA (Telecommunications
Industry Association,
www.tiaonline.org ). These standards ITU V.250 and TIA/EIA 602 define the
command set of a modem. This command set has
the ancient names Hayes command set or AT command set. Linux operates modems
conforming to the standards mentioned
above. WinModems contravene these standards, their interface details are
not uncovered frequently.
Solution:
1.Buy a regular modem
2.Do your communication business with another operating system.
3.Write a driver on your own or dispose someone to write a driver.
Conclusion:
Even I have tried to configure an internal modem . I had used a Dax internal
modem. But since it was a WinModem all my
efforts were futile . Until unless modem manufacturers release information
about their modems a driver for an internal modem
can't be made. The reason being the modem runs on software and has a virtual
UART instead of a hardware UART . In view
of the above given solutions I would suggest you to buy an internal modem
(if you are keen for it) with a hardware UART .
Such modems do exist one being a Hayes Accura 33.6 internal .