[hylafax-users] INSTALLING THE MODEM

[dc <damasosc@xxxxxxxxxx>]

Hi,

I've a modem installed.
I verify that is running:

root@GPLxServer ScanModems]# ls
scanModem.gz
[root@GPLxServer ScanModems]# gunzip scanModem.gz
[root@GPLxServer ScanModems]# ls
scanModem
[root@GPLxServer ScanModems]# chmod +x scanModem
[root@GPLxServer ScanModems]#  ./scanModem
 
 
UPDATE=2004 June 22
ONLY use scanModem downloaded as: http://linmodems.technion.ac.il/packages/scanM
odem.gz
 ./scanModem should ONLY be run within a Linux/UNIX partition.
   If within a MicroSoft/DOS partition, abort with Ctrl-C now !!!
   Copy scanModem.gz to your Linux partition and restart.
 
To continue:    Enter
 
 This script primarily utilizes the LSPCI tool from the package PCIUTILS
 and various component sciptlets, to identify the modem chipset,
 This enables direction to supporting software and/or more detailed information.
 LSPCI tool from the package PCIUTILS and and various component sciptlets are us
ed
 ISA bus modems and 16 bit PCMCIA card modems will not be recognized
 See the output files for guidance on these cases.
 
 The script originated as scanPCI written by Chris Hebeisen,
 to recognize modems with DSP (digital signal processing) chipsets made by Lucen
t/AgereSystems.
 It now aspires to provide useful information on other modems as well.
 For the  Lucent/Agere DSP chip modems, System information is used to recommend
Installers,
 from the Installer list output from Chris's repository:   http://ltmodem.heby.d
e/
 
 Three types of information are acquired from your System:
 1) General system information necessary for your guidance;
 2) The PCI_ID of the modem card, or for the increasingly prevalent "soft modems
",
  the PCI_IDs of  its AC'97/MC97 controller and its modem subsystem.
 3) For soft modems, a SIL_ID of the subsystem is either acquired
 OR instructions provided for manual acquisition
 
 The remainder of ./scanModem is a repository of "modem gossip" or URLs thereto.
 Only information blocks most relevant to your System will be output into
      ModemData.txt and ModemGeneral.txt
 Should you need assistance after FIRST following all the advice and/or URLs,
 1) Browse the general information at:  http://linmodems.technion.ac.il/  and
 2) ONLY thereafter send ModemData.txt to:   discuss@xxxxxxxxxxxxx
 ModemData.txt.2  has common information the List need not be bothered with.
 3) Also the archive SEARCH ENGINE at  http://linmodems.technion.ac.il/
 may be useful once PCI or SIL  IDs are acquired.
 
 This script can be read and word searched with a text browser.
 Blocks of Information with little code begin and end with #####.
 
 In case of a failure concerning "lspci", rerun ./scanModem after login to a con
sole with
 # su - root
 as Root permission may be necessary for access to lspci.
 
 Updated on 2004 June 22 by  Marv Stodolsk for access through:
     http://linmodems.technion.ac.il/packages/scanModem.gz
 Please do NOT use a scanModem.gz from any other site!!
 -------------------------------------------------------------------------------
----
 
To continue:    Enter
 
Providing detail for device at PCI_bus 00:07.0
  with vendor-ID:device-ID
            ----:----
Class 0780: 11c1:044c   Communication controller: Lucent Microelectronics LT Win
Modem (rev 02)
  SubSystem 11c1:044c   Lucent Microelectronics LT WinModem
        Flags: bus master, medium devsel, latency 64, IRQ 10
        Memory at dfffbf00 (32-bit, non-prefetchable) [size=256]
        I/O ports at d400 [size=8]
 
 The modem has a supported Lucent/Agere DSP (digital signal processing) chipset
  with primary PCI_ID:  11c1:044c
 DSP=1
 
  Please read ModemData.txt, ModemDriverCompiling.txt, ModemTesting.txt, ModemGe
neral.txt
  Only send ModemData.txt to Discuss@xxxxxxxxxxxxx , if necessary
 
[root@GPLxServer ScanModems]#

Hylafax on

/usr/sbin/faxsetup

ask for

Serial port that modem is connected to []? ttyS0

But is not the right answer, I think, as at the end,

Now we are going to probe the tty port to figure out the type
of modem that is attached.  This takes a few seconds, so be patient.
Note that if you do not have the modem cabled to the port, or the
modem is turned off, this may hang (just go and cable up the modem
or turn it on, or whatever).
 
Probing for best speed to talk to modem: 38400 19200 9600 4800 2400 1200
Unable to deduce DTE-DCE speed; check that you are using the
correct device and/or that your modem is setup properly.  If
all else fails, try the -s option to lock the speed.

What am I doing wrong?

Thank's
Dâmaso Constantino