[hylafax-users] Suddenly "Can not initialize modem"

[Martin Schürrer]

Hi,

I've used HylaFax happily in production for quite a while. Now
suddenly my modem seems to be broken. I haven't changed anything at
all.

Here's the log:
Oct 2 11:14:53 server FaxGetty[14412]: OPEN /dev/modem HylaFAX (tm)
Version 6.0.5
Oct 2 11:14:54 server FaxGetty[14412]: MODEM set DTR OFF
Oct 2 11:14:54 server FaxGetty[14412]: DELAY 75 ms
Oct 2 11:14:54 server FaxGetty[14412]: MODEM set DTR ON
Oct 2 11:14:54 server FaxGetty[14412]: DELAY 2600 ms
Oct 2 11:14:57 server FaxGetty[14412]: MODEM set baud rate: 19200
baud, input flow XON/XOFF, output flow XON/XOFF
Oct 2 11:14:57 server FaxGetty[14412]: DELAY 10 ms
Oct 2 11:14:57 server FaxGetty[14412]: MODEM flush i/o
Oct 2 11:14:57 server FaxGetty[14412]: <-- [4:ATZ\r]
Oct 2 11:14:57 server FaxGetty[14412]: <-- <3:41 54 5A>
Oct 2 11:14:57 server FaxGetty[14412]: <-- <1:0D>
Oct 2 11:15:27 server FaxGetty[14412]: MODEM TIMEOUT: reading line from modem
Oct 2 11:15:27 server FaxGetty[14412]: MODEM <Timeout>
Oct 2 11:15:27 server FaxGetty[14412]: MODEM set DTR OFF
Oct 2 11:15:27 server FaxGetty[14412]: DELAY 75 ms
Oct 2 11:15:28 server FaxGetty[14412]: MODEM set DTR ON
Oct 2 11:15:28 server FaxGetty[14412]: DELAY 2600 ms
Oct 2 11:15:31 server FaxGetty[14412]: MODEM set baud rate: 19200
baud, input flow XON/XOFF, output flow XON/XOFF
Oct 2 11:15:31 server FaxGetty[14412]: DELAY 10 ms
Oct 2 11:15:31 server FaxGetty[14412]: MODEM flush i/o
Oct 2 11:15:31 server FaxGetty[14412]: <-- [4:ATZ\r]
Oct 2 11:15:31 server FaxGetty[14412]: <-- <3:41 54 5A>
Oct 2 11:15:31 server FaxGetty[14412]: <-- <1:0D>
Oct 2 11:16:01 server FaxGetty[14412]: MODEM TIMEOUT: reading line from modem
Oct 2 11:16:01 server FaxGetty[14412]: MODEM <Timeout>
Oct 2 11:16:01 server FaxGetty[14412]: MODEM set DTR OFF
Oct 2 11:16:01 server FaxGetty[14412]: /dev/modem: Can not initialize modem.
Oct 2 11:16:01 server FaxGetty[14412]: STATE CHANGE: BASE ->
MODEMWAIT (timeout 30)

and so forth until hylafax decides that the modem is wedged.

Here's the modem config:
ModemType: Class1 # use class 1 interface
ModemRate: 19200 # rate for DCE-DTE communication
ModemFlowControl: xonxoff # software flow control
#
ModemSetupDTRCmd: ATS13=1&D2 # setup so DTR drop resets modem
ModemSetupDCDCmd: AT&C1 # setup so DCD reflects carrier (or not)
ModemNoFlowCmd: AT&H0&I0&R1 # setup modem for no flow control
ModemHardFlowCmd: AT&H1&I0&R2 # setup modem for hardware flow control
ModemSoftFlowCmd: AT&H2&I2&R1 # setup modem for software flow control
ModemResultCodesCmd: ATQ0X4 # enable result codes
#
ModemMfrQueryCmd: !USR
ModemModelQueryCmd: ATI3
ModemRevQueryCmd: ATI7 # XXX returns a multi-line result
#
ModemDialCmd: ATX3DT%s
#
# When AT+FCLASS=1 is issued the modem automatically switches
# to software flow control; these parameters let the fax software
# reset flow control as needed after entering Class 1.
#
Class1NFLOCmd: AT&H0&I0&R1 # setup modem for no flow control
Class1HFLOCmd: AT&H1&I0&R2 # setup modem for hardware flow control
Class1SFLOCmd: "" # modem does this automatically
#
# This should resolve "DIS/DTC received 3 times" errors:
#
Class1ResponseWaitCmd: AT+FRS=1 # wait after sending TCF for response
#
# The remainder of this configuration is included so that the
# modem "idles" in Class 0 while not sending or receiving facsimile.
#
ModemSetupAACmd: AT+FCLASS=0 # leave modem idling in class 0
ModemAnswerCmd: AT+FCLASS=1A # answer in Class 1
#
# When using AT+FRS=n we see USR modems reset themselves in the middle
of sessions
# this is not good. So, we seem to work-around that problem by not using the
# command. Unfortunately, this isn't an ideal thing.
#
Class1SwitchingCmd: "<delay\0727>"

Anyone got any ideas what's going on?

Thanks,
Martin Schuerrer


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

[shouldbe q931]

I'm guessing that this is an internal modem, and that it has either
died, or completely locked up.

If it is an internal modem, have you tried power cycling the box ?
If it is an external modem, have you tried power cycling the modem ?

[Martin Schürrer]

It's an external "old" serial modem, it's hooked up over USB.

I've tried power cycling the modem and power cycling the PC multiple
times. Didn't help.

[John Hudak]

From the sounds of things, I think your modem has gone to that big bit
bucket in the the sky.

One suggestion: Try to flash the firmware with the current of a newer
version. There is an outside chance that this may cure it.

good luck
John

On Tue, Oct 2, 2012 at 10:28 AM, Martin Sch�rrer <mar...@schuerrer.org>wrote:

> It's an external "old" serial modem, it's hooked up over USB.
>
> I've tried power cycling the modem and power cycling the PC multiple
> times. Didn't help.
>
> On Tue, Oct 2, 2012 at 4:11 PM, shouldbe q931 <should...@gmail.com>
> wrote:

> > On Tue, Oct 2, 2012 at 10:21 AM, Martin Sch�rrer <mar...@schuerrer.org>

[Tim Nelson]

----- Original Message -----
> From the sounds of things, I think your modem has gone to that big
> bit bucket in the the sky.
>
> One suggestion: Try to flash the firmware with the current of a newer
> version. There is an outside chance that this may cure it.

Also, USB<->serial adapters can be notoriously finicky. Try a real serial port, or an adapter with a known good chipset. I've had fantastic experiences with those from Tripp-Lite, specifically this one:

http://www.tripplite.com/en/products/model.cfm?txtModelID=2430

--Tim

[John Hudak]

It appears that hylafax is not happy with the response it is getting from
the modem when it tries to initialize the modem. Without looking at the
code, I don't know what it is unhappy about. After performing an I/O
flush, the modem takes longer to respond than hylafax wants, e.g. TIMEOUT.
I suspect the modem has some sort of hardware failure.
Have you tried any other programs such as minicom or efax, just to test the
modem? If a replacement modem is not available (my first troubleshooting
step), I'd try testing your current modem with minicom.

J