Do NOT send this ModemData.txt.2 with common information to discuss@linmodems.org ============== Several sections are included in this file: Rational of scanModem service; summary of modem Support under Linux description of the SIL_ID test some output from scanModem specific to your System an explanation of the GCC 2.95 compiler warning ethernet Interference with DNS (domain name service) COMPILING DRIVERS. Please Linux Newbies read carefully!! Followup Actions, to get online, with dialout examples. RATIONAL This scanModem service is sadly necessary because of the pre-compiled format (binary, Closed Source) of some modem supporting code. Intellectual property is protected within the binary component. But this prevents compatibility assessments/debugging against Linux Open Source code. Skipping many details, the consequence is that some Linux distributions do not deliver Closed Source code, or tools adequate to fully identify the modem's chipset. This script tries to close this information gap. USB modems will not be detected UNTIL proper USB support is installed. See http://www.linux-usb.org/USB-guide/x332.html ftp://ftp.smlink.com/linux/unsupported/ may provide support for SmartUSB56 (ST7554) based modems with vendor/product usb ids: 0483:7554 It is the CHIPSET, and Not the modem BrandName which is informative for Linux support. For modems not recognized by scanModem, chipset information may be obtained under Microsoft Windows through: 1) Start > Settings > Control Panel > Modem Start > Settings > Control Panel > System > Devices > Modem Do the modem query test, if available, looking for manufacturer chipset, information in the output. Try to identify the modem setup file, with name perhaps MODEM.INF 2) Open a COMM console, and send ATI commands to the modem (ATI, ATI1, ATI2, etc) which may elicit chipset and driver information. SUPPORT SUMMARY - as of 2003 November 17 ------------------------------------- Controller chipsets are used in the most expensive modems and are supported. They utilize the same driver, serial.o , and most commonly the ports /dev/ttyS0 thru 3. Such chipsets are produced by 3Com, AgereSystems (the Venus chipset), Topic Semiconductor Corp., and others. But the same companies may produce unsupported WinModems. Do not depend on the Brand Name. Look for an explicit statement of Linux support AVOID the following modem chipsets: ESS - no formal support since 2.2.2 kernels Motorola - no formal support since 2.4.5 kernels 3Com/US Robotics winmodems - never supported under Linux SmartLink - newer chipsets are supported: http://www.smlink.com ftp://ftp.smlink.com/linux/unsupported/ Moreover, the slmodem-2.9.n drivers will support Most other modems that serve under AC'97/MC97 controllers, which send much of the work load to companion digital audio cards. Conexant - all modems supported with drivers at: http://www.linuxant.com Testcode for slow 14,400 mH support is free, BUT there is a one time charge for the full speed support. Intel Inc. - http://developer.intel.com/design/modems/support/drivers.htm For early releases check at: http://linmodems.technion.ac.il/resources.html The HaM modem is supported, but code is no longer updated and will likely fail under emerging 2.6 kernels. The 536ep modem is actively supported. The 537 AC'97 Link modem subSystem will be supported by Intel soon, but the SmartLink slmodem-2.9.n drivers are effective for now. Lucent /AgereSystems The Venus chipset modem uses the serial.o driver and is thus supported. Modems with digital signal processing (DSP) chipsets are supported: http:/ltmodem.heby.de AC'97/MC97 soft modem support is enroute to release, but SmartLink slmodem-2.9.n drivers are effective for now. Coding of support for has Not yet begun PCI soft modems with PCI_IDs 11c1:048? and probably will first be available within 2004. PCTel modem business has been sold to Conexant Driver compiler resources are at: http://pctelcompdb.sourceforge.net/ However, the pre-compiled binary component is yet to be assembled with the gcc 3.nn used in newer Linux releases, so forced (-f) insertions may be necessary: insmod -f pctel Some/all? of the HSP soft modems are supported by the SmartLink slmdm-2.7.10 or slmodem-2.9.n drivers. Broadcom modems in Dell laptops and PCs - can be made to function under 2.4 kernels, but code hasn't been updated recently. --------- end chipset section ---------------------- SUPPORT under the emerging 2.6.nn kernels. The more expensive Controller chipset modems are functioning. SmartLink slmodem-2.9.n drivers are functioning. The Lucent/Agere digital signal processing (DSP) chipsets do have an informal hack extending service into 2.6.0-test kernels. Intel, Agere Systems and Linuxant (for Conexant chipsets) are firmly expected to continue support into 2.6.nn. ------------------------------------ Preparing winmodem drivers will generally require compiling. If you are not familar with this process DEFINITELY read carefully the section below "COMPILING DRIVERS, for Linux Newbies" Silicon chipset (SIL) analysis information ------------------------------------------- Skip this section if your modem's chipset was adequately identified in ModemData.txt During bootup, kernel diagnostics on the System are stored for later display by: dmesg This information may include a SIL_id of modems under AC'97/MC97 Controllers, depending upon the type of briding of the modem card to the motherboard. The scanModem script processes dmesg output to capture AC'97 modem information, parses it into a SIL_id if possible, and then displays of modem chipset information. Guidance to sources of modem supporting software may thus be obtained. The transfer of the AC97 information to the dmesg buffer requires that modules supporting both the digital audio card and the ac97_codec be loaded during bootup: modprobe ac97_codec modprobe audio_drivers (such as i810_audio) This can be checked after bootup with: lsmod This script can also be used by entering a test block with nomenclature: scanModem SILtest with SILtest a text file in This Folder containing a section of a dmesg output or /var/log/messages like: i810: Intel ICH 82801AA found at IO 0xdc00 and 0xd800, IRQ 11 i810_audio: Audio Controller supports 2 channels. ac97_codec: AC97 Audio codec, id: 0x4144:0x5340 (Analog Devices AD1881) i810_audio: AC'97 codec 0 Unable to map surround DAC's (or DAC's not present), total channels = 2 ac97_codec: AC97 Modem codec, id: 0x5349:0x4c22 (Silicon Laboratory Si3036) which does include a line beginning with: ac97_codec: AC97 Modem codec, id: ---------- End SIL_id section --------------- ==================== AC'97/MC97 summary ========================== Any of the Controllers in the left most column could support a variety of subSystem soft modems. Hence the current ambiguity in possible support by drivers under Linux VendorID:DeviceID == PCI_ID Controller type bus PCI_ID subSystemID AC97 MC97 try drivers from ---------- ----------- ---------------- ---------------- Intel: 8086:2416 82801AA (ICH) + p c 8086:2426 82801AB (ICH0) + 8086:2446 82801BA (ICH2) + p c 8086:2486 ICH3 + p c 8086:24c6 INTEL ICH4 + 8086:1040 S1724 8086:7196 ???? + 1543:3052 1543:3000 SI3052 1039:7013 SIS 630 + p 1039:7018 SIS 960 + 1055:9178 Standard Microsystems + 10de:01c1 Nvidia Corp + 1106:3068 VIA + p c 1131:3400 Philips Semiconductors + 1022:7446 AMD 10a5:3052 Racal Interlan + 10b9:5450 ALI 5450 10b9:5451 ALI 5451 10b9:5453 ALI p c 10b9:5457 ALI 5457 + p c 10b9:545a ALI + e159:0001 TigerJet 320 e159:0001 0359:0003 TJ320 v3.1 e159:0001 8086:0003 TJ320 v2.0 PCI cards with SmartLink support at least from slmodem-2.9.n 10b9:5459 ALI 5459 SmartPCI561 ++ 10ec:8197 - SmartLAN56 (RealTek ether/modem combo) ++ 1131:3400 - SmartPCI56 (Philips UCB1500) ++ 163c:5459, 10a5:5459 - kinds of SmartPCI561 ++ -------------------------------------------------------- p http://pctelcompdb.sourceforge.net/ c Conexant - http://www.linuxant.com + SmartLink HAMR5600 compatible AMR/CNR/MDC soft modems ++ SmartLink PCI bus modems For drivers: ftp://ftp.smlink.com/linux/unsupported/ , Try the most recent slmodem-2.9.n ====================================================================== Soft modems under AC'97 or MC97 Controllers ============================= If a modem_codec SIL_id was not output earlier, please reboot Linux to freshen the bootup dmesg buffer and then rerun scanModem, to acquire an expected SIL_id. However The roughly classified with AC'97 modems may be housed within an AMR connector, the MDC connector, IBM's CDC connector, or a mini PCI slot. SmartLink http://www.smlink.com has a readible documentation set on soft modem rational and technologies. Their common feature is that they utilize the services of a digital audio card through use of an ac97_codec. This greatly reduces the cost of the modem hardware and specialization to the diverse telephone line standards around the world. Hoever the primary PCI_ID 10b9:5457 identifies Only the Controller of the soft modem Subsystem 1734:100a. This commonly FAILS to designate the chipset!! Queries under MS windows may be informative, by the following routes: Open a COMM console and send ATI commands to the modem, which may provide identifying information: ATI, ATI1, ATI2 etc. For a good report see: http://phep2.technion.ac.il/linmodems/archive/msg05099.html Get whatever detail information is available through: Start > Settings > Control Panel > Modem There may be a TestModem option available. Start > Settings > Control Panel > System > Devices > Modem Try to identify the modem setup file, with name perhaps MODEM.INF Information therein including driver names may help to identify the chipset. If the Primary and Subsystem Vendor information was not adeqaute, it may be useful to download http://www.yourvote.com/pci/vendors.txt and search it for the Vendor IDs with and without caps, for example: both 114d and 114D ---------------------------------------- Analyzing information for PCMCIA device at PCI Bus 00:0b.0 00:0b.0 CardBus bridge: ENE Technology Inc CB1420 Cardbus Controller (rev 01) Subsystem: Unknown device 1734:100a Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at 10000000 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=02, subordinate=02, sec-latency=176 Memory window 0: 10400000-107ff000 (prefetchable) Memory window 1: 10800000-10bff000 I/O window 0: 00004000-000040ff I/O window 1: 00004400-000044ff 16-bit legacy interface ports at 0001 GREPping for an inserted PCMCIA modem with filter: ommunication Analyzing information for PCMCIA device at PCI Bus 00:0b.1 00:0b.1 CardBus bridge: ENE Technology Inc CB1420 Cardbus Controller (rev 01) Subsystem: Unknown device 1734:100a Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at 10001000 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=03, subordinate=03, sec-latency=176 Memory window 0: 10c00000-10fff000 (prefetchable) Memory window 1: 11000000-113ff000 I/O window 0: 00004800-000048ff I/O window 1: 00004c00-00004cff 16-bit legacy interface ports at 0001 GREPping for an inserted PCMCIA modem with filter: ommunication If a PCMCIA modem is currently inserted and the sockets activated by /etc/init.d/pcmcia start then the PCMCIA bridge is NOT transparent. If the modem is known to have a Lucent digital signal processing chipset, then PCMCIA.tar.gz variant assembled by Joern Wustenfeld is necessary, rather than the standard ltmodem-8.26a9.tar.gz at http://ltmodem.heby.de/ --------------------------------------------------------------------------------------------- The proprietary Binary component of the some current winmodem drivers were compiled with version 2.9n gcc compiler. Red Hat 8.0 and Mandrake 9.0 releases utilize version 3.nn gcc compilers. This currently is causing difficulties either in compiling and/or insertion of updated winmodem drivers. The gcc compiler version of this System is: 3.3.2 It will likely be necessary to force (-f) insertion of winmodem drivers, with credit to Jos Vos: http://phep2.technion.ac.il/linmodems/archive/msg04510.html For the ltmodem drivers with proprietary binary provided by Agere Systems, compiling with versions gcc=3.nn is successful. A minor edit required to compile PCTEL drivers has also been reported: http://phep2.technion.ac.il/linmodems/archive/msg04684.html Simple driver insertion fails in these cases with a message like: ----begin error---- % insmod lt_modem Using /lib/modules/2.4.18-14/ltmodem/lt_modem.o /lib/modules/2.4.18-14/ltmodem/lt_modem.o: The module you are trying to load (/lib/modules/2.4.18-14/ltmodem/lt_modem.o) is compiled with a gcc version 2 compiler, while the kernel you are running is compiled with a gcc version 3 compiler. This is known to not work. -----end error----- It is necessary as Root to force (-f) loading with commands like: insmod -f pctel respecting the dependency ordering of the drivers. Then check for insertion with: lsmod If driver insertion is successful, the forcing can be automated by putting the lines (credit to Bhaskaran Raman) like the following, install pctel /sbin/insmod --force pctel In order of preference depending on your particular Linux installation. Put these lines into ONLY ONE of the following files, within any modem loading subsection if present: /etc/modutils/ltmodem /etc/modutils/aliases /etc/modules.conf Then inform your System of the edit for Debian like Systems with update-modules which rewrites and reads /etc/modules.conf . For other System types depmod -a re-reads the edited /etc/modules.conf . Thereafter module loading should behave as previously. For the ltmodem drivers loading, it should suffice to either start a ppp session or modprobe ptserial ----------------------------------------------------- The System has Ethernet capability. If not expert, shut down ethernet before initiated modem usage with: # ifconfig eth0 down 00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Unknown device 1734:100a Flags: bus master, medium devsel, latency 64, IRQ 11 I/O ports at 8c00 [size=256] Memory at f0406800 (32-bit, non-prefetchable) [size=256] Capabilities: