Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: problem compiling hylafax on Redhat 5.2
Hallo
: From: darren@info.tpc.int
:
: Do you need to compile from source? Why not use the RPM?
I wanted to use mgetty instead of getty and had some problems with the
RPM, so I decided to compile from source. I fetched the SRPM, which
contains one or two patches, and compiled it (no problem). But my
problems are still there.
: If you're on RedHat I highly recommend migrating to the new beta release,
: which has no known problems at the moment (tempting fate).
:
: ftp://ftp.hylafax.org/hylafax/hylafax-4.1/binary/linux/
I took the SRPM again, there was no problem compiling hylafax4.1b, but
it seems as I have still some modem problems (the same as before):
I use a rockwell-based noname-Modem:
Jul 28 19:29:05 mathes FaxSend[2066]: MODEM /V4.1 AUG-23-95 DM2814/2A/RC288DPI V.34/PCB:490-22801-xx or 490-22802-xx or 490-21407-xx or 490-21420-xx BZT POSTZULASSUNG-FIRMWARE VERSION:V.105
It is class2 (says the manual and faxsetup), so I took the config/class2 and
config/rc288dpi (I tried the config made by faxsetup, but it didn't worked).
If I send a fax, there are still errors and the file isn't send:
Jul 28 19:29:05.93: [ 2066]: SESSION BEGIN 00000005 494518132250
Jul 28 19:29:05.93: [ 2066]: SEND FAX: JOB 2 DEST 8132250 COMMID 00000005
[...]
Jul 28 19:29:08.96: [ 2066]: <-- [10:AT+FTBC=0\r]
Jul 28 19:29:09.10: [ 2066]: --> [5:ERROR]
[...]
Jul 28 19:29:09.24: [ 2066]: <-- [13:AT+FPHCTO=30\r]
Jul 28 19:29:09.38: [ 2066]: --> [5:ERROR]
Jul 28 19:29:09.38: [ 2066]: MODEM Command error
[...]
Jul 28 19:29:09.89: [ 2066]: <-- [10:AT+FTBC=0\r]
Jul 28 19:29:10.13: [ 2066]: --> [5:ERROR]
[...]
Jul 28 19:29:10.37: [ 2066]: <-- [13:AT+FPHCTO=30\r]
Jul 28 19:29:10.61: [ 2066]: --> [5:ERROR]
Jul 28 19:29:10.61: [ 2066]: MODEM Command error
[...]
Jul 28 19:29:11.09: [ 2066]: DIAL 8132250
Jul 28 19:29:11.09: [ 2066]: <-- [12:ATDT8132250\r]
Jul 28 19:29:49.15: [ 2066]: --> [180:[MUCH TRASH THERE...]]
Jul 28 19:29:49.15: [ 2066]: SEND FAILED: Unknown problem (check modem power)
Jul 28 19:29:49.15: [ 2066]: <-- [5:ATH0\r]
Jul 28 19:29:49.15: [ 2066]: --> [10:NO CARRIER]
Jul 28 19:29:49.15: [ 2066]: MODEM No carrier
Jul 28 19:29:49.16: [ 2066]: SESSION END
If I use the original (faxsetup) config, then there are the same errors,
but at the end it seems to bei okay:
Jul 28 19:17:55.99: [ 994]: REMOTE CSI "SSI-Stefan Hussfeldt"
Jul 28 19:17:55.99: [ 994]: --> [22:+FDIS: 1,5,1,2,2,0,0,0]
Jul 28 19:17:56.10: [ 994]: --> [2:OK]
Jul 28 19:17:56.10: [ 994]: REMOTE best rate 14400 bit/s
Jul 28 19:17:56.10: [ 994]: REMOTE max page width 2048 pixels in 255 mm
Jul 28 19:17:56.10: [ 994]: REMOTE max unlimited page length
Jul 28 19:17:56.10: [ 994]: REMOTE best vres 7.7 line/mm
Jul 28 19:17:56.10: [ 994]: REMOTE best format 2-D Uncompressed Mode
Jul 28 19:17:56.10: [ 994]: REMOTE best 0 ms/scanline
Jul 28 19:17:56.10: [ 994]: USE 14400 bit/s
Jul 28 19:17:56.10: [ 994]: USE 0 ms/scanline
Jul 28 19:17:56.10: [ 994]: <-- [5:ATH0\r]
Jul 28 19:17:56.31: [ 994]: --> [2:OK]
Jul 28 19:17:56.31: [ 994]: SESSION END
But the fax doesn't arrive "on the other side". Does anybody know, what
to do ?
Thanx
Bastian
--
Bastian Mathes, Tel. +49-451-53247