[hylafax-users] Modem wedged. A hardware problem?

["Paul Smith" <paul@xxxxxxxx>]

I've had hylafax 4.2.2 running just fine, sending and receiving, on a debian
etch box for around 6 weeks.  The modem is a "MODEM LT V.92 1.0
MT5634ZPX-PCI-U INTERNAL DATA/FAX/VOICE MODEM VERSION 1.32I LT V.92 1.0
MT5634ZPX-PCI-U Internal Data/Fax/Voice Modem Version 1.32i/"

Yesterday people were having sporadic sending problems ("Busy signal
detected", "No carrier detected") and today I've started getting "modem
wedged" emails and this kind of thing in the logs:

Jan 25 12:03:01 faxsvr FaxGetty[3215]: Unable to setup modem on /dev/ttyS14;
giving up after 2 attempts
Jan 25 12:03:01 faxsvr FaxGetty[3215]: CLOSE /dev/ttyS14
Jan 25 12:03:01 faxsvr FaxQueuer[1990]: MODEM /dev/ttyS14 appears to be
wedged
Jan 25 12:03:01 faxsvr FaxQueuer[1990]: MODEM WEDGED: bin/wedged "ttyS14"
"/dev/ttyS14"
Jan 25 12:03:01 faxsvr FaxGetty[3843]: OPEN /dev/ttyS14  HylaFAX (tm)
Version 4.2.4
Jan 25 12:03:10 faxsvr FaxGetty[3843]: /dev/ttyS14: Can not initialize
modem.

I've restarted the services, rebooted and cold booted the machine all to no
avail.  I even upgraded Hylafax to the latest available 4.2.4 in the hope
that might fix the problem but nothing I do seems to make much difference.
Some previous discussions on this list pointed me towards cu but that
disconnects as soon as I start typing.

faxsvr:~# cu -l ttyS14
cu: ttyS14: Line in use
faxsvr:~# cu -l ttyS14
Connected.
t
Disconnected.
faxsvr:~# ti3

Are there any other tests I can do?  Is the modem faulty?

Thanks

Paul

Attachment: smime.p7s
Description: S/MIME cryptographic signature