Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Brendan Wajon on June 07, 2001, 07:46:46 PM
-
Hello,
I've tried to setup an HylaFAX server on mine E-smith 4.1.2 box using the Hylafax HowTo of Ernst Bergen.
But I can't get it to work. It starts with the required files:
libtiff-3.5.5-7.i386.rpm -> no problems installing this package
ghostscript-fonts-6.0.2.noarch.rpm -> no problems installing this package
XFree86-libs-4.0.1-1.i386.rpm -> BINGO, problem:
XFree86-libs ##################################unpacking of archive failed on file /usr/X11R6/lib/libXfont.so.1.3: cpio: read failed - Bad file descriptor
compat-libstdc++6.2-2.9.0.9.i386.rpm -> no problems installing this package
ghostscript-6.50-2.i386.rpm -> BINGO, next problem:
error: failed dependencies:
libICE.so.6 is needed by ghostscript-6.50-2
libSM.so.6 is needed by ghostscript-6.50-2
libX11.so.6 is needed by ghostscript-6.50-2
libXext.so.6 is needed by ghostscript-6.50-2
libXt.so.6 is needed by ghostscript-6.50-2
and I stopped here.
Does someone have an working HylaFAX server on his/hers E-smith 4.1.2 box.
I just can't get it to work.
Brendan
-
XFree86-libs-4.0.1-1.i386.rpm -> BINGO, problem:
XFree86-libs ##################################unpacking of archive failed on file /usr/X11R6/lib/libXfont.so.1.3: cpio: read failed - Bad file descriptor
download this rpm new, maybe from a other server. It looks like the downloaded
file is corrupt.
jochen
-
Thank you Jochen,
Sorry for the stupidity on my part. Never even thought of re-downloading the error-given RPM.
I downloaded the XFree86-libs-4.0.1-1.i386.rpm again and the problem was gone.
Thanks for the tip.
Brendan Wajon
-
Hello,
I''ve got another problem with Hylafax on my E-smith 4.1.2 Box. I can't get it to answer faxes correctly, but I can send them.
I've installed Hylafax with the use of Ernst Bergen How-To on http://www.e-smith.org/docs/howto/contrib/HylaFAX-HowTo.html
At first the "faxsetup" couldn't find the file /usr/bin/gs but I found it in /usr/local/bin and copied it to /usr/bin (changing the PATH in "faxsetup" as shown in the How-To didn't resolve this, but I still changed the PATH).
I added a line to /etc/inittab:
4:2345:respawn:/usr/sbin/faxgetty ttyS0
This I got from www.hylafax.org, they mentioned this with the /usr/local/sbin but on my E-smith box faxgetty resides in /usr/sbin
I know I shouldn't adjust the inittab in /etc/, but change it in the templates-directory, but I don't know how!!
But that doesn't help, faxgetty doesn't seem to start according to faxsetup. When I run faxsetup to see if it notice faxgetty is says that I'm not running faxgetty.
System Specs:
Intel 166 mhz MMX
64 Mb RAM
Realtek PCI NIC (Sitecom 10/100mb)
S3 Videocard
E-tech PnP ISA modem 33K6 (fax-capability)
Disabled PnP OS in BIOS
Configured the modem with pnpdump -c --outputfile=/etc/isapnp.conf
then run: isapnp /etc/isapnp.conf > works, isapnp are enabled at startup
added a line in /etc/rc.d/rc.local:
setserial /dev/ttyS0 irq 4 port 0x3E8 (read it from isapnp.conf and works with minicom)
And if I run faxgetty at the prompt (logged in as root):
faxgetty ttyS0
The computer seems to hang, I can't do anything. Pressing CONTROL-C gives back the control of the computer to me.
But it answers incoming calls, but that results in transmission errors. (I tried to send a fax from my laptop to my computer through the phone). And I have Hylafax running, could see that with the Hylafax Client Cypheus.
Summary:
- Unable to get faxgetty started at boot
- People who send faxes to me get an transmission error
Can someone help me?
Brendan
-
> I added a line to /etc/inittab:
> 4:2345:respawn:/usr/sbin/faxgetty ttyS0
Try this line instead:
mo:23457:respawn:/usr/sbin/faxgetty ttyS0
and issue the command:
/sbin/init q
Stephan
-
Thanks Stephan,
With that adjustment faxgetty starts at startup an does answers calls.
Only when my Hylafax is being called, it answers it and after a while hangs up. Giving my laptop (testing if Hylafax receives faxes) an "transmission error". And asked some friends to fax, they received the same error.
The logfile off Hylafax says:
Jun 08 15:09:25.82: [ 1447]: SESSION BEGIN 00000021 310360365214276
Jun 08 15:09:25.82: [ 1447]: <-- [4:ATA\r]
Jun 08 15:10:28.98: [ 1447]: --> [10:NO CARRIER]
Jun 08 15:10:28.98: [ 1447]: ANSWER: Ring detected without successful handshake
Jun 08 15:10:28.98: [ 1447]: SESSION END
How is this happening? Hylafax sends faxes without any problem, only receiving them is just not an option at my place.
Does someone know what I have to change so that this error will not occur everytime?
Thanks,
Brendan
-
Fixed it.
Changed the line:
ModemSetupAACmd: AT+FCLASS=0 in
ModemSetupAACmd: AT+FCLASS=1
This will always answers calls as a fax-call (to my understanding). And doesn't even considers that it might be a voice-call.
In /var/spool/fax/etc/config.ttyS0
And commented the line:
/usr/sbin/faxmodem ttyS0 in /etc/rc.d/rc.local
Brendan.