Below please find the results of my running the scanModem script, delimited with [[begin ModemData.txt]] [[end ModemData.txt]] followed by my comments.
[[begin ModemData.txt]]
The most recent update of scanModem accessed at
http://linmodems.technion.ac.il/packages/scanModem.gz
should ALWAYS be used!! Current UPDATE=2004 February 11
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, redhat kernel 2.4.22-1.2115.nptl
Always send this ENTIRE ModemData.txt. It includes subtle diagnostic ouputs needed to best guide you.
-------------- System information ------------------------
redhat Fedora Core release 1 (Yarrow)
on system: Linux localhost.localdomain 2.4.22-1.2115.nptl #1 Wed Oct 29 15:42:51 EST 2003 i686 i686 i386 GNU/Linux"
GCC=3.3.2
======= Fedora code changes =======
SmartLink slmodem-2.9.n and Intel537 drivers are already Fedora competent.
For usage of winmodems with the kernel-2.4.nn Fedora releases
a change in the serial-like driver code of WinModems is necessary.
See for guidance:
http://hepunx.rl.ac.uk/~wmurray/pctel/pctel.html
Basically , the line:
if ((tty->count == 1) && (state->count != 1)) {
should be changed into:
if (atomic_read(&tty->count) == 1 && state->count != 1) {
This works in the ltmodem code too. See
http://linmodems.technion.ac.il/arch.../msg02360.html
redhat is not yet providing pre-compiled drivers for WinModems
An AC'97 modem codec was not detected
Path to lspci is: /sbin/lspci
--------- lspci scan ----------------
PCI_bus
00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 05)
00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 05)
00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus Controller (rev 02)
00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY
02:02.0 CardBus bridge: Texas Instruments PCI1250 PC card Cardbus Controller (rev 01)
02:02.1 CardBus bridge: Texas Instruments PCI1250 PC card Cardbus Controller (rev 01)
02:03.0 Multimedia audio controller: ESS Technology ES1988 Allegro-1 (rev 12)
02:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
02:08.0 Ethernet controller: Intel Corp. 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 42)
-------------------------------------
Modem candidates are at PCI_buses: 00:1f.6
Providing detail for device at PCI_bus 00:1f.6
with vendor-ID:device-ID
----:----
Class 0703: 8086:2486 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02) (prog-if 00 [Generic])
SubSystem 144f:1050 Askey Computer Corp.: Unknown device 1050
Flags: medium devsel, IRQ 10
I/O ports at 2000 [size=256]
I/O ports at 1c00 [size=128]
The modem Subsystem operates under an AC'97 or MC97 controller
The AC'97 or MC97 Controller is:
8086:2486 82801CA/CAM AC'97 (ICH3)
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/
Vendor 11c1 corresponds to Lucent Technologies or subsidiary Agere Systems, Inc.
Information is at:
http://www.agere.com/support/client/modem_drivers.html
---------------
Under the controller 8086:2486 82801CA/CAM AC'97 (ICH3) ,
the modem subSystem 144f:1050
will ONLY be supported by AgereSoftModem drivers if it has Agere chipset.
Thus establish identity of the softmodem chipset through tests described in ModemData.txt.2
Software access is initiated through code sponsor IBM:
http://www-3.ibm.com/pc/support/site...cid=MIGR-52698
AC'97/MC97 link modems may evoke a modem_codec with SIL_id = 39.
Should the Agere software fail the SmartLink slmodem-2.9.n or slmdm-2.7.10 may serve.
Current support from AgereSystems is only under the following modem controllers:
8086

2416 2426 2446 7196 2486 24C6) , with 8086 == Intel
1039:7013 SIS
1106:3068 VIA
----------------
Under the controller 8086:2486 82801CA/CAM AC'97 (ICH3) ,
the modem subSystem 144f:1050
may be supported by the SmartLink slmodem-2.9.n drivers, even for non-SmartLink chipsets.
------------------------------
Vendor 163c is SmartLink,
http://www.smlink.com/
There is good information on soft modems thereat, with Linux software downloaded
from
ftp://ftp.smlink.com/linux/unsupported/ and some backups at:
http://linmodems.technion.ac.il/packages/smartlink/
slmodem-2.8.1 and later versions support multiple modems on the same PC.
If there should be mis-dialing problems either use slmdm-2.7.10 or upgrade to a 2.6.nn kernel.
The slmodem-2.9.n drivers are already competent for 2.6.nn Linux kernels
They also support MANY non-SmartLink soft modem chipsets under AC'97/MC97 Controllers.
There may be a warning about a not-SmartLink modem as the drivers load.
But just proceed with modem functionality tests,
as described at the end of ModemDriverCompiling.txt
Beginning with slmodem-2.9.4 , a report on the softmodem chipset identity is provided.
Display it after bootup by querying the dmesg buffer:
# dmesg | grep slam
# dmseg | grep SIL
Please report this information to
discuss@linmodems.org,
if not already included in ModemData.txt
See details concerning slmodem usage in ModemData.txt.2
------------------------------
=== Checking 8086 through chipset providers and modem assemblers ====
Vendor=8086 is Intel, Inc. producing HaM and 536ep host controller free (HCF) modems, the 537 soft modem
and AC'97 and MC97 controllers managing a varierty of non-Intel soft modem subSystems.
These subSystems will in have PCI_IDs assigned by the modem assembler, not Intel.
Download available drivers from:
http://developer.intel.com/design/mo...rt/drivers.htm
Also check at:
http://linmodems.technion.ac.il/resources.html
for early releases and perhaps Already compiled drivers for some Linux distributions
======= PCI_ID checking completed ======
Update=2004 February 11
Some installers may alternately be found by searching for ltmodem at:
http://rpm.pbone.net/
GCCversion=3.3.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 ModemData.txt.2
DEVPPP=crw------- 1 root root 108, 0 Sep 15 09:40 /dev/ppp
A /dev/modem symbolic link is not present
No devfsd.conf file sound, indicated absense of the devfsd daemon package
for device file system (devfs) symbolic link support.
DEVFSD=
---- dmesg queries -------
BIOS-e820: 000000001fef0000 - 000000001feff000 (ACPI data)
BIOS-e820: 000000001feff000 - 000000001ff00000 (ACPI NVS)
ACPI: have wakeup address 0xc0001000
ACPI: RSDP (v000 PTLTD ) @ 0x000f6a40
ACPI: RSDT (v001 GATEWA 450 0x20020808 LTP 0x00000000) @ 0x1fef84bd
ACPI: FADT (v001 GATEWA 450 0x20020808 PTL 0x0000001e) @ 0x1fefef64
ACPI: BOOT (v001 GATEWA 450 0x20020808 LTP 0x00000001) @ 0x1fefefd8
ACPI: DSDT (v001 GATEWA 450 0x20020808 MSFT 0x0100000d) @ 0x00000000
ACPI: Subsystem revision 20031002
ACPI: Interpreter disabled.
The ModemDriverCompiling.txt is a MUST READ,
if you are not experienced in configuring kernel-source/
or get "Unresolved symbols" upon driver insertion.
Most recent WinModem fixes are in:
http://linmodems.technion.ac.il/FAQ.html
[[end ModemData.txt]]
There's lot of stuff here to sort thru, so I'll review and get back to you.
Will be looking forward to your response.
Thanks Again!