HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

[hylafax-users] flow control with MT5634ZBA



Right now I'm using default config file (software flow contro +flo=1). Do
you think I should try using hardware flow control? Are there some drawbacks
to using hardware flow control (i see on the modem manual that default is
software).

Aug 27 21:05:13 b FaxSend[6550]: MODEM MULTI-TECH SYSTEMS
MT5634ZBA-V92/1.28c
Aug 27 21:05:13 b FaxSend[6550]: SEND FAX: JOB 1367 DEST 01234567890 COMMID
00001729 DEVICE '/dev/ttyS1'
Aug 27 21:06:01 b FaxSend[6550]: SEND FAX: JOB 1367 SENT in 0:18
Aug 27 21:06:12 b kernel: ttyS1: 1 input overrun(s)
Aug 27 21:06:12 b FaxSend[6559]: /dev/ttyS1: Can not initialize modem.
Aug 27 21:06:53 b kernel: ttyS1: 1 input overrun(s)
Aug 27 21:06:53 b FaxSend[6559]: Error getting modem capabilities
Aug 27 21:07:33 b kernel: ttyS1: 1 input overrun(s)
Aug 27 21:07:34 b FaxSend[6559]: Unable to setup modem on /dev/ttyS1; giving
upafter 2 attempts
Aug 27 21:07:34 b FaxQueuer[636]: MODEM /dev/ttyS1 appears to be wedged
Aug 27 21:07:34 b FaxQueuer[636]: MODEM WEDGED: bin/wedged "ttyS1"
"/dev/ttyS1"
Aug 27 21:07:45 b kernel: ttyS1: 1 input overrun(s)
Aug 27 21:08:17 b FaxSend[6583]: MODEM MULTI-TECH SYSTEMS /1.28c
Aug 27 21:08:17 b FaxSend[6583]: SEND FAX: JOB 1361 DEST 02222222 COMMID
00001730 DEVICE '/dev/ttyS1'
Aug 27 21:08:48 b kernel: ttyS1: 1 input overrun(s)
Aug 27 21:08:53 b kernel: ttyS1: 1 input overrun(s)
Aug 27 21:10:22 b FaxSend[6583]: SEND FAX: JOB 1361 SENT in 1:34
...

I do have
ModemRate:              57600       # for V.34 faxing

I started using multitech on 18 aug

zgrep "input overrun" /var/log/messages*
/var/log/messages:Aug 25 13:28:11 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages:Aug 25 13:28:51 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages:Aug 27 21:06:12 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages:Aug 27 21:06:53 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages:Aug 27 21:07:33 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages:Aug 27 21:07:45 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages:Aug 27 21:08:48 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages:Aug 27 21:08:53 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages:Aug 27 21:10:35 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages:Aug 27 21:11:34 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages:Aug 27 21:11:58 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages.1.gz:Aug 21 13:27:07 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages.1.gz:Aug 21 13:27:49 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages.1.gz:Aug 21 13:28:53 b kernel: ttyS1: 1 input overrun(s)
/var/log/messages.4.gz:Aug  1 21:09:04 b kernel: ttyS1: 1 input overrun(s)


So this happens only sporadically.

As I understand it, overrun means that host sent to the modem more data that
it (modem) could handle, right?

Thanks

-- 
giulioo@pobox.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@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*




Project hosted by iFAX Solutions