Re: [hylafax-users] Faxgetty cannot init modem, but probemodem works.

To: hylafax-users@xxxxxxxxxxx
Subject: Re: [hylafax-users] Faxgetty cannot init modem, but probemodem works.
From: jeff leads <jleads@xxxxxxxxx>
Date: Sun, 7 May 2006 13:09:33 -0700 (PDT)

I commented out the line in inittab and the reran
"init q" to stop faxgetty on the modem connected to
ttyS0.  I then tried to access the modem with Minicom
which worked. I was able to type AT commands and get
responses in minicom.  I then reenabled the device in
inittab, did "init q" and same problem.  Faxgetty cant
init the modem.  

Looking for some fresh ideas... ;-)

Jeff

--- jeff leads <jleads@xxxxxxxxx> wrote:

> I disconnected the modem from the Digi baord and
> plugged it directly into /dev/ttyS0 on the back of
> the
> server (a HP ML350 G4) in an attempt to eliminate a
> variable (the Digi Portserver).  It faxgetty still
> acts the same, it cannot init the modem.  Probemodem
> sees the modem just fine though..
> 
> Mucho Help! :-)
> 
> Thx
> 
> 
> May  6 19:39:59 server2 FaxGetty[23311]: CAUGHT
> SIGNAL
> 15
> May  6 19:39:59 server2 FaxGetty[23311]: CLOSE
> /dev/ttyS0
> May  6 19:39:59 server2 FaxGetty[23370]: OPEN
> /dev/ttyS0  HylaFAX (tm) Version 4.2.5
> May  6 19:39:59 server2 FaxGetty[23370]: /dev/ttyS0:
> Can not lock device.
> May  6 19:39:59 server2 hylafax: faxgetty shutdown
> succeeded
> May  6 19:40:29 server2 FaxGetty[23370]: Purge stale
> UUCP lock /var/lock/LCK..ttyS0
> May  6 19:41:37 server2 FaxGetty[23370]: /dev/ttyS0:
> Can not initialize modem.
> May  6 19:44:54 server2 FaxGetty[23370]: Unable to
> setup modem on /dev/ttyS0; giving up after 2
> attempts
> May  6 19:44:54 server2 FaxGetty[23370]: CLOSE
> /dev/ttyS0
> May  6 19:44:54 server2 FaxQueuer[23359]: MODEM
> /dev/ttyS0 appears to be wedged
> May  6 19:44:54 server2 FaxQueuer[23359]: MODEM
> WEDGED: bin/wedged "ttyS0" "/dev/ttyS0"
> May  6 19:44:54 server2 FaxGetty[23847]: OPEN
> /dev/ttyS0  HylaFAX (tm) Version 4.2.5
> May  6 19:44:54 server2 FaxQueuer[23359]: NOTIFY
> exit
> status: 0 (23846)
> 
> --- jeff leads <jleads@xxxxxxxxx> wrote:
> 
> > I have a USR Courier V.Everything attached to a
> Digi
> > Portserver TS8, I'm running a new install of
> Redhat
> > ES4 and Hylafax 4.2.5 (installed using RPM).  I
> cant
> > seem to figure out why faxgetty can't speak to the
> > modem to initialize it.  I set logging to 0xfff
> > (output below).  I have also tried differnt ports
> on
> > the portserver with the same result.  Probemodem
> > works
> > fine however (output below).  I have attached my
> > config.tty407 (output below).
> > 
> > Can some one point me in the right direction?  
> > 
> > Thanks a bunch
> > 
> > Jeff
> > 
> > 
> > [root@server2 etc]# ls -la /dev/tty407
> > crw-rw-rw-  1 uucp root 251, 7 May  6 15:01
> > /dev/tty407
> > 
> > 
> > 
> > [root@server2 ~]# probemodem tty407
> > Now we are going to probe the tty port.  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 OK.
> > 
> > This looks like a Class 1 and 2.0 modem.
> > 
> > ATI0    RESULT = "OK"   RESPONSE = "5608A"
> > ATI1    RESULT = "E77B" RESPONSE = "E77B"
> > ATI2    RESULT = "OK"   RESPONSE = "OK"
> > ATI3    RESULT = "OK"   RESPONSE = "USRobotics
> > Courier
> > V.Everything EXT"
> > ATI4    RESULT = "OK"   RESPONSE = "USRobotics
> > Courier
> > V.Everything Settings..."
> > ATI5    RESULT = "OK"   RESPONSE = "USRobotics
> > Courier
> > V.Everything NVRAM Settings..."
> > ATI6    RESULT = "OK"   RESPONSE = "USRobotics
> > Courier
> > V.Everything Link Diagnostics..."
> > ATI7    RESULT = "OK"   RESPONSE = "USRobotics
> > Courier
> > V.Everything Configuration Profile..."
> > ATI8    RESULT = "ERROR"        RESPONSE = "ERROR"
> > ATI9    RESULT = "OK"   RESPONSE =
> > "(1.0USR00BA\MODEM\PNPC107\USRobotics Courier
> > V.Everything EXT)"
> > 
> > 
> > 
> > 
> > [root@server2 ~]#tail -f /var/log/messages
> > May  6 15:30:53 server2 FaxGetty[31028]: OPEN
> > /dev/tty407  HylaFAX (tm) Version 4.2.3
> > May  6 15:30:53 server2 FaxGetty[31028]: Purge
> stale
> > UUCP lock /var/lock/LCK..tty407
> > May  6 15:30:54 server2 FaxGetty[31028]: MODEM set
> > DTR
> > OFF
> > May  6 15:30:54 server2 FaxGetty[31028]: DELAY 75
> ms
> > May  6 15:30:55 server2 FaxGetty[31028]: MODEM set
> > DTR
> > ON
> > May  6 15:30:55 server2 FaxGetty[31028]: DELAY
> 2600
> > ms
> > May  6 15:30:58 server2 FaxGetty[31028]: MODEM set
> > baud rate: 38400 baud, input flow RTS/CTS, output
> > flow
> > RTS/CTS
> > May  6 15:30:58 server2 FaxGetty[31028]: DELAY 10
> ms
> > May  6 15:30:58 server2 FaxGetty[31028]: MODEM
> flush
> > i/o
> > May  6 15:30:58 server2 FaxGetty[31028]: <--
> > [4:ATZ\r]
> > May  6 15:31:28 server2 FaxGetty[31028]: MODEM
> > TIMEOUT: reading line from modem
> > May  6 15:31:28 server2 FaxGetty[31028]: MODEM
> > <Timeout>
> > May  6 15:31:28 server2 FaxGetty[31028]: MODEM set
> > DTR
> > OFF
> > May  6 15:31:28 server2 FaxGetty[31028]: DELAY 75
> ms
> > May  6 15:31:28 server2 FaxGetty[31028]: MODEM set
> > DTR
> > ON
> > May  6 15:31:28 server2 FaxGetty[31028]: DELAY
> 2600
> > ms
> > May  6 15:31:47 server2 FaxGetty[31028]: MODEM set
> > baud rate: 38400 baud, input flow RTS/CTS, output
> > flow
> > RTS/CTS
> > May  6 15:31:47 server2 FaxGetty[31028]: DELAY 10
> ms
> > May  6 15:31:47 server2 FaxGetty[31028]: MODEM
> flush
> > i/o
> > May  6 15:31:47 server2 FaxGetty[31028]: <--
> > [4:ATZ\r]
> > May  6 15:32:17 server2 FaxGetty[31028]: MODEM
> > TIMEOUT: reading line from modem
> > 
> > 
> > 
> > [root@server2 ~]#cat
> > /var/spool/hylafax/etc/config.tty407
> > 
> > # Configuration for using the Class 2.0 command
> > interface
> > # with a USR v.34 Courier or Sporster modem.
> > #
> > # RTS/CTS flow control is used default.
> > #
> > #
> > CountryCode:            1
> > AreaCode:               859
> > FAXNumber:              +1.859.544.7475
> > LongDistancePrefix:     1
> > InternationalPrefix:    011
> > DialStringRules:        etc/dialrules
> > ServerTracing:          0xFFF
> > SessionTracing:         11
> > RecvFileMode:           0644
> > LogFileMode:            0644
> > DeviceMode:             0666
> > RingsBeforeAnswer:      1
> > SpeakerVolume:          off
> > GettyArgs:              "-h %l dx_%s"
> > LocalIdentifier:        "KRN Business FAX"
> > TagLineFont:            etc/lutRS18.pcf
> 
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*

Follow-Ups:
- Re: [hylafax-users] Faxgetty cannot init modem, but probemodem works.
  - From: Lee Howard

References:
- Re: [hylafax-users] Faxgetty cannot init modem, but probemodem works.
  - From: jeff leads

Prev by Date: Re: [hylafax-users] TR: Unable to Add Second Modem
Next by Date: [hylafax-users] text as unknown document type?
Previous by thread: Re: [hylafax-users] Faxgetty cannot init modem, but probemodem works.
Next by thread: Re: [hylafax-users] Faxgetty cannot init modem, but probemodem works.
Index(es):
- Main
- Thread

Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services