thanks a lot. i'm confused. ;-)
here it comes.
modemdata.txt
The most recent update of scanmodem accessed at
http://linmodems.technion.ac.il/packages/scanModem.gz
should ALWAYS be used before requesting help from
discuss@linmodem.org,
URLs to cogent advice are regularly entered and updated, and your problem may be solved therein.
If further help is needed, send a description of your problem to:
discuss@linmodems.org
with this ModemData.txt Attached, using the following in the email Subject Line:
scanModem, mandrake kernel 2.4.21-0.13mdk
-------------- System information ------------------------
mandrake Mandrake Linux release 9.1 (Bamboo) for i586
on system: Linux localhost 2.4.21-0.13mdk #1 Fri Mar 14 15:08:06 EST 2003 i686 unknown unknown GNU/Linux"
GCC=
UPDATE=2003 October 3
Path to lspci is: /usr/bin/lspci
--------- lspci scan ----------------
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:04.0 CardBus bridge: Texas Instruments PCI1420
00:04.1 CardBus bridge: Texas Instruments PCI1420
00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:08.0 Multimedia audio controller: Cirrus Logic Crystal CS4281 PCI Audio (rev 01)
00:10.0 Communication controller: Lucent Microelectronics LT WinModem
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
-------------------------------------
Reading more detail for the Device at:
PCI bus
-------
00:10.0 Class 0780: 11c1:0450
Subsystem 144f:4005
00:10.0 Communication controller: Lucent Microelectronics LT WinModem
Subsystem: Askey Computer Corp. Magnia SG20
Flags: medium devsel, IRQ 9
Memory at fc011000 (32-bit, non-prefetchable) [disabled] [size=256]
I/O ports at 1050 [disabled] [size=8]
I/O ports at 1400 [disabled] [size=256]
Capabilities: [f8] Power Management version 2
-------------------------------------------------------
11c1:0450 PCI_ID of the PCI bus with vendor: 11c1
144f:4005 PCI_ID of Subsystem with vendor: 144f
-------------------------------------------------------
are key Sought Descriptions of your modem firmware.
Have them ready when visiting URLs with service software!!
DSP=1
The modem has a Lucent/Agere chipset for digital signal
processing with primary PCI_ID: 11c1:0450
First accessing chipset provider and modem assembler information
for the modem SubSystem under the AC'97 or MC97 Controller.
=== Checking 144f through chipset providers and modem assemblers ====
Vendor 144f is Askey Computer Corp.
http://www.askey.com/
=== Checking 11c1 through chipset providers and modem assemblers ====
Vendor=11c1 corresponds to Lucent Technologies or subsidiary Agere Systems, Inc.
Information is at:
http://www.agere.com/support/client/modem_drivers.html
but without any relevant to Linux.
0x0450 -- Mars 3 Mercury data fax Global board
====== PCI_ID checking completed ======
Update=2003 October 3
The desired installer name is like:
========================================
ltmodem-kv-2.4.21_0.13mdk-8.26a9-1.i686.rpm
----------------------------------------
ltmodem-kv-Kernel_FL-LTver--.CPU.rpm explains the versioning.
For your System
Kernel_FL is 2.4.21-0.13mdk , the full kernel version displayed by: uname -r
LTver is 8.26a9, the release of the compiler kit
8.26 is the Agere core code designation.
The proccesor type or CPU is: i686 dispayed by: uname -m
used in compiling and assembling driver packages.
A suitable installer is not available as of this 2003 October 3 update.
Check in the section mandrake at
http://ltmodem.heby.de/
for a subsequent Installer submission.
If not present use the ltmodem-8.26a9.tar.gz compiler kit.
The list of available Installers for mandrake
is inserted into to /tmp/modem/ModemData.txt.2
The following information blocks just query some ppp support items.
====================================================================
g The most recent update of scanmodem accessed at
http://linmodems.technion.ac.il/packages/scanModem.gz
should ALWAYS be used before requesting help from
discuss@linmodem.org,
URLs to cogent advice are regularly entered and updated, and your problem may be solved therein.
If further help is needed, send a description of your problem to:
discuss@linmodems.org
with this ModemData.txt Attached, using the following in the email Subject Line:
scanModem, mandrake kernel 2.4.21-0.13mdk
-------------- System information ------------------------
mandrake Mandrake Linux release 9.1 (Bamboo) for i586
on system: Linux localhost 2.4.21-0.13mdk #1 Fri Mar 14 15:08:06 EST 2003 i686 unknown unknown GNU/Linux"
GCC=
UPDATE=2003 October 3
Path to lspci is: /usr/bin/lspci
--------- lspci scan ----------------
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:04.0 CardBus bridge: Texas Instruments PCI1420
00:04.1 CardBus bridge: Texas Instruments PCI1420
00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:08.0 Multimedia audio controller: Cirrus Logic Crystal CS4281 PCI Audio (rev 01)
00:10.0 Communication controller: Lucent Microelectronics LT WinModem
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
-------------------------------------
Reading more detail for the Device at:
PCI bus
-------
00:10.0 Class 0780: 11c1:0450
Subsystem 144f:4005
00:10.0 Communication controller: Lucent Microelectronics LT WinModem
Subsystem: Askey Computer Corp. Magnia SG20
Flags: medium devsel, IRQ 9
Memory at fc011000 (32-bit, non-prefetchable) [disabled] [size=256]
I/O ports at 1050 [disabled] [size=8]
I/O ports at 1400 [disabled] [size=256]
Capabilities: [f8] Power Management version 2
-------------------------------------------------------
11c1:0450 PCI_ID of the PCI bus with vendor: 11c1
144f:4005 PCI_ID of Subsystem with vendor: 144f
-------------------------------------------------------
are key Sought Descriptions of your modem firmware.
Have them ready when visiting URLs with service software!!
DSP=1
The modem has a Lucent/Agere chipset for digital signal
processing with primary PCI_ID: 11c1:0450
First accessing chipset provider and modem assembler information
for the modem SubSystem under the AC'97 or MC97 Controller.
=== Checking 144f through chipset providers and modem assemblers ====
Vendor 144f is Askey Computer Corp.
http://www.askey.com/
=== Checking 11c1 through chipset providers and modem assemblers ====
Vendor=11c1 corresponds to Lucent Technologies or subsidiary Agere Systems, Inc.
Information is at:
http://www.agere.com/support/client/modem_drivers.html
but without any relevant to Linux.
0x0450 -- Mars 3 Mercury data fax Global board
====== PCI_ID checking completed ======
Update=2003 October 3
The desired installer name is like:
========================================
ltmodem-kv-2.4.21_0.13mdk-8.26a9-1.i686.rpm
----------------------------------------
ltmodem-kv-Kernel_FL-LTver--.CPU.rpm explains the versioning.
For your System
Kernel_FL is 2.4.21-0.13mdk , the full kernel version displayed by: uname -r
LTver is 8.26a9, the release of the compiler kit
8.26 is the Agere core code designation.
The proccesor type or CPU is: i686 dispayed by: uname -m
used in compiling and assembling driver packages.
A suitable installer is not available as of this 2003 October 3 update.
Check in the section mandrake at
http://ltmodem.heby.de/
for a subsequent Installer submission.
If not present use the ltmodem-8.26a9.tar.gz compiler kit.
The list of available Installers for mandrake
is inserted into to /tmp/modem/ModemData.txt.2
The following information blocks just query some ppp support items.
====================================================================
grep ppp /etc/modules.conf
--------------------------------
--------------------------------
Be sure to read the section about ppp related modules and aliases in /tmp/modem/ModemData.txt.2
=== ifconfig test ====
lo Link encap:Local Loopback
DEVPPP=crw------- 1 root root 108, 0 gen 1 1970 /dev/ppp
DEVFS=active
DEVFSD=/etc/devfsd.confrep ppp /etc/modules.conf
--------------------------------
--------------------------------
Be sure to read the section about ppp related modules and aliases in /tmp/modem/ModemData.txt.2
=== ifconfig test ====
lo Link encap:Local Loopback
DEVPPP=crw------- 1 root root 108, 0 gen 1 1970 /dev/ppp
DEVFS=active
DEVFSD=/etc/devfsd.conf
modemdata.txt.2
Do NOT send this common information to
discuss@linmodems.org
==============
Several sections are included in this file:
The 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.nn compiler warning
Ethernet interference with DNS (domain name service)
COMPILING DRIVERS, for Newbies
Followup actions, to get online.
RATIONAL
This ./scanModem service is sadly necessary because of the precompiled 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 Linux distributions do not deliver Closed Source code,
or tools adequate to fully identify the modem. This script tries to close
this information gap. It will happily be terminated or shortened,
as Linux distributions can host more comprehensive modem diagnostic tools.
USB modems will not be detected UNTIL proper USB support is installed.
See
http://www.linux-usb.org/USB-guide/x332.html
http://www.smlink.com may provide support for
SmartUSB56 (ST7554) based modems with vendor/product usb ids: 0483:7554
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 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.
Linux SUPPORT SUMMARY - as of 2003 October 3
-------------------------------------
Conexant - all modems supported:
http://www.linuxant.com
SmartLink - all modems supported:
http://www.smlink.com
Intel Inc. -
http://developer.intel.com/design/mo...rt/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 probably 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 slmdm-2.7.10 (and NO later version) drivers are effective for now.
Lucent/Agere
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 slmdm-2.7.10 drivers are effective for now, through only under Some AC'97/MC97 controllers,
Coding of support for PCI soft modems has not yet begun, and probably will first be available within 2004.
PCTel -
http://pctelcompdb.sourceforge.net/
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 of the HSP soft modems are served well by the SmartLink slmdm-2.7.10 drivers.
Broadcom modems in Dell laptops - can be made to function under 2.4 kernels, but code hasn't been updated recently.
ESS - no formal support since 2.2.2 kernels
Motorola - no formal support since 2.4.5 kernels
3Com/US Robotics
more expensive Controller chip modems use the serial.o driver
Winmodems - no support
Controller chip modems are also assembled by several other companies including
TOPIC SEMICONDUCTOR Corp.
-------------------------------------------
SUPPORT under 2.6.nn kernels
The proprietary component of winmodem resouces will have to be re-compiled by chipset vendors.
Thus at this time, only the more expensive Controller chip modems,
using the Open Source serial driver, can be expected to function.
See:
http://linmodems.technion.ac.il/arch.../msg01900.html
------------------------------------
COMPILING - Preparing winmodem drivers will generally require compiling.
If you are not familar with this process DEFINITELY read carefully
the section of /tmp/modem/ModemData.txt.2 on "COMPILING DRIVERS, for Linux Newbies"
Silicon chipset (SIL) analysis information
-------------------------------------------
During bootup, kernel diagnostics on the System are stored for later display by:
dmesg
The scanModem script processes dmesg output to capture AC97 modem information and
parses it into a SIL_id with display of modem manufacturer 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 a digital audio card and the ac97_codec had to 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 SI Do NOT send this common information to
discuss@linmodems.org
==============
Several sections are included in this file:
The 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.nn compiler warning
Ethernet interference with DNS (domain name service)
COMPILING DRIVERS, for Newbies
Followup actions, to get online.
RATIONAL
This ./scanModem service is sadly necessary because of the precompiled 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 Linux distributions do not deliver Closed Source code,
or tools adequate to fully identify the modem. This script tries to close
this information gap. It will happily be terminated or shortened,
as Linux distributions can host more comprehensive modem diagnostic tools.
USB modems will not be detected UNTIL proper USB support is installed.
See
http://www.linux-usb.org/USB-guide/x332.html
http://www.smlink.com may provide support for
SmartUSB56 (ST7554) based modems with vendor/product usb ids: 0483:7554
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 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.
Linux SUPPORT SUMMARY - as of 2003 October 3
-------------------------------------
Conexant - all modems supported:
http://www.linuxant.com
SmartLink - all modems supported:
http://www.smlink.com
Intel Inc. -
http://developer.intel.com/design/mo...rt/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 probably 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 slmdm-2.7.10 (and NO later version) drivers are effective for now.
Lucent/Agere
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 slmdm-2.7.10 drivers are effective for now, through only under Some AC'97/MC97 controllers,
Coding of support for PCI soft modems has not yet begun, and probably will first be available within 2004.
PCTel -
http://pctelcompdb.sourceforge.net/
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 of the HSP soft modems are served well by the SmartLink slmdm-2.7.10 drivers.
Broadcom modems in Dell laptops - can be made to function under 2.4 kernels, but code hasn't been updated recently.
ESS - no formal support since 2.2.2 kernels
Motorola - no formal support since 2.4.5 kernels
3Com/US Robotics
more expensive Controller chip modems use the serial.o driver
Winmodems - no support
Controller chip modems are also assembled by several other companies including
TOPIC SEMICONDUCTOR Corp.
-------------------------------------------
SUPPORT under 2.6.nn kernels
The proprietary component of winmodem resouces will have to be re-compiled by chipset vendors.
Thus at this time, only the more expensive Controller chip modems,
using the Open Source serial driver, can be expected to function.
See:
http://linmodems.technion.ac.il/arch.../msg01900.html
------------------------------------
COMPILING - Preparing winmodem drivers will generally require compiling.
If you are not familar with this process DEFINITELY read carefully
the section of /tmp/modem/ModemData.txt.2 on "COMPILING DRIVERS, for Linux Newbies"
Silicon chipset (SIL) analysis information
-------------------------------------------
During bootup, kernel diagnostics on the System are stored for later display by:
dmesg
The scanModem script processes dmesg output to capture AC97 modem information and
parses it into a SIL_id with display of modem manufacturer 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 a digital audio card and the ac97_codec had to 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 FolderLtest a text file in This Folder
have a good reading
i look forward hearing from you
bye
piero