HylaFAX The world's
most advanced open source fax server
Re: [hylafax-users] Debian upgrade from 4.2.2 - 4.2.5:
"Mark Gillingham" <Mark.Gillingham@xxxxxxxxxxxxxx> wrote:
I finally got the nerve to upgrade my Hylafax from Debian stable (Sarge) to
testing so that I could get the new modem features and security patches.
I'm receiving faxes fine on the two internal serial ports, but by PCI SiiG
2-port card is problematic. I want to send on ttyS2.
faxstat reports that ttyS2 (the first Siig port) is "waiting for modem to
cu can talk to the modem on ttyS2 when it is not engaged with Hylafax in
I double-checked the setserial settings, in case the upgrade changed them
in some way.
I re-read the installation instructions, but I must have missed something.
Where should I look now? Thanks.
The last time I was on a debian install, I was surprised by the fact that
the init script synchronised /etc/hylafax and /var/spool/hylafax/etc, and
also that it was itself starting faxgetty, if configured to do so. The init
script sources a config file something like (from memory)
/etc/defaults/hylafax and this file tells the init script how to handle the
starting of faxgetty. I guess what I'm saying here is just to make sure you
understand how faxgetty is being started on your system.
Is it possible you have a couple of different faxgettys fighting for the
modem? Do you only ever see one in the process table?
What if you run probemodem on ttyS2 when there are no faxgettys running
right after a cold boot of the server and a power-cycle of the modem? Can it
chat with the modem?
____________________ 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*