The most recent update of scanModem accessed at http://linmodems.technion.ac.il/packages/scanModem.gz
 should ALWAYS be used!!  Current  UPDATE=2004_Aug_24
 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.6.5-1.358
 Always send this ENTIRE Modem/ModemData.txt. It includes subtle diagnostic ouputs needed to best guide you.
 If your PC is a laptop, please provide Make and Modem information.

 For instructions to UNSUBSCRIBE from discuss@linmodems.org,
   send an email to:   discuss-help@linmodems.org

 --------------  System information ------------------------
 redhat Fedora Core release 2 (Tettnang)
 on System with processor: i686
 supported by kernel:      2.6.5-1.358

 The kernel-2.6.5-1.358 was compiled with CONFIG_REGPARM, providing more compact and faster code.

 assembled with compiler:  3.3.3
 with current System compiler GCC=3.3.3
 Modem symbolic link is:  /dev/modem -> /dev/537
 COMM services are not active

 Under 2.6.n kernels, there is currently modem support by:
 	the more expensive Controller chipset modems using the open source serial code
 	Conexant software downloaded through http://www.linuxant.com
 	SmartLink slmodem drivers, including USB hardware
	USB modems using the Open Source acm.ko driver
	Lucent DSP (digital signal processing) chipsets but NOT:
	soft modems ( though some are supported by slmodem drivers)
        Intel 536EP and 537 modems
 For all other modems, support projections are not available as of this update=2004_Aug_24

 PPP support module  bsd_comp.ko  not found!
 Resident PPP support modules are properly uncompressed .

  ======= Fedora code changes =======
 SmartLink slmodem-2.9.n, Lucent/Agere DSP,  Intel 536ep and 537 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
  An error about "rs_close" during compiling is a signature that the fedora fix is needed

  Beginning with Fedora 2  kernel-2.6.6-1.427, kernel-headers needed for compiling drivers are provide at: /lib/modules/kernel-version/build/
  Thus upgrading above kernel 2.6.5-1.358 to 2.6.6-* is Stongly Recommended
  redhat is not yet providing pre-compiled drivers for WinModems

 An AC97 modem codec was not detected

Path to lspci is: /sbin/lspci
--------- lspci scan ----------------
PCI_bus
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:07.0 Communication controller: Individual Computers - Jens Schoenfeld Intel 537
00:0f.0 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R350 [Radeon 9800]
01:00.1 Display controller: ATI Technologies Inc Radeon R350 [Radeon 9800] (Secondary)
-------------------------------------
PCIBUS= 00:07.0

Modem candidates are at PCI_buses:   00:07.0
Providing detail for device at PCI_bus 00:07.0
  with vendor-ID:device-ID
	    ----:----
Class 0780: e159:0001   Communication controller: Individual Computers - Jens Schoenfeld Intel 537
  SubSystem 8086:0003   Intel Corp.: Unknown device 0003
	Flags: bus master, medium devsel, latency 32, IRQ 10
	I/O ports at ec00
	Memory at dfffb000 (32-bit, non-prefetchable) [size=4K]

 Internal_test:   ./scanModem test e159:0001 8086:0003 redhat 2.6.5-1.358 3.3.3 

	Use Intel-537-2.60.80.0.tgz
 === Checking e159 through chipset providers and modem assemblers ====

 Vendor e159 is Tiger Jet (TJ).
  e159:0001  translates PCI commands to the serial link used by
     the silabs DAA from the si3034, si3044 and si3056 family.
  e159:0001  8086:0003  TJ320 v2.0 , with subsystem 8086:0003 Intel537 soft modem
     supported by:  Intel-537-2.37.50.1.tgz
  e159:0001  0359:0003  TJ320 v3.1


  ======= PCI_ID checking completed ====== 
 Update=2004_Aug_24
A PCMCIA CardBus is not detected on this System.
The following information blocks just query some ppp support items.
====================================================
   grep ppp /etc/modprobe.conf
-------------------------------------

-------------------------------------
Be sure to read the section about ppp related modules and aliases in Modem/General.txt
DEVPPP=crw------- 1 root root 108, 0 Feb 23 2004 /dev/ppp

  The current modem symbolic link is: /dev/modem -> /dev/537
  The ports /dev/ttyS0 or 1,2,3 are for standard Controller chip modems


 No devfsd.conf file found, indicated absense of the devfsd daemon package
 for device file system (devfs) symbolic link support.

DEVFSD=
 ---- dmesg queries -------
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off'
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
sound 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

537_boot failing

/proc/modules