Hylafax 6.0.5 on FC15 - modem not working.

[UNIXgreybeard]

I know the modem works as I am able to talk to it directly with minicom but I can't get hylafax to work with the modem - keeps saying its wedged.

systemd config:
[root@redhat system]# pwd
/etc/systemd/system
[root@redhat system]# cat faxgetty-ttyR0.service
[Unit]
Description=FaxGetty Start Modem ttyR0

[Service]
Type=simple
User=root
Group=root
Restart=always
ExecStart=/usr/local/sbin/faxgetty /dev/ttyR0
RestartSec=30

[Install]
WantedBy=multi-user.target


when I systemctl start faxgetty-ttyR0.service
May 3 21:44:34 redhat FaxGetty[23673]: OPEN /dev/ttyR0 HylaFAX (tm) Version 6.0.5
May 3 21:45:43 redhat FaxGetty[23673]: /dev/ttyR0: Can not initialize modem.
May 3 21:48:59 redhat FaxGetty[23673]: Unable to setup modem on /dev/ttyR0; giving up after 2 attempts
May 3 21:48:59 redhat FaxGetty[23673]: MODEM /dev/ttyR0 appears to be wedged
May 3 21:48:59 redhat FaxGetty[23673]: CLOSE /dev/ttyR0
May 3 21:49:29 redhat systemd[1]: faxgetty-ttyR0.service holdoff time over, scheduling restart.

I've set the debugging level to max:
[root@redhat etc]# grep fff *
config:ServerTracing: 0xfffff
config.ttyR0:ServerTracing: 0xfffff
config.ttyR0:SessionTracing: 0xfffff

Yet I'm not getting any real useful output telling me what part of the system is not configured correctly.

Suggestions that are not "use efax"?

[george_toolan]

Check your permissions

ls -l /usr/local/sbin/faxgetty /dev/ttyR0

If faxgetty isn't allowed to access the modem then it cannot be initialized ;-)

[UNIXgreybeard]

Originally Posted by george_toolan

Check your permissions

ls -l /usr/local/sbin/faxgetty /dev/ttyR0

If faxgetty isn't allowed to access the modem then it cannot be initialized ;-)

Already though of that and I can produce conditions where faxgetty will "throw an error":
May 4 05:14:45 redhat systemd[1]: faxgetty-ttyR0.service holdoff time over, scheduling restart.
May 4 05:14:45 redhat systemd[1]: Unit faxgetty-ttyR0.service entered failed state.
May 4 05:14:45 redhat systemd[1]: faxgetty-ttyR0.service: main process exited, code=exited, status=255


OR:
May 4 05:35:47 redhat systemd[1]: faxgetty-ttyR0.service holdoff time over, scheduling restart.
May 4 05:35:47 redhat systemd[1]: Unit faxgetty-ttyR0.service entered failed state.
May 4 05:35:47 redhat FaxGetty[5054]: The fax server must run with real uid root.
May 4 05:35:47 redhat systemd[1]: faxgetty-ttyR0.service: main process exited, code=exited, status=255


(entered failed state - I know that. Tell me WHY. If I wanted 'there is a failure' message with no WHY I'll use Microsoft software thankyouverymuch)


Here is an example of the non-permissions mucked up communications. (sitting in a log file that should not have been in messages...*sigh*)
May 3 18:39:36 redhat FaxGetty[22352]: OPEN /dev/ttyR0 HylaFAX (tm) Version 6.
0.5
May 3 18:39:37 redhat FaxGetty[22352]: MODEM set DTR OFF
May 3 18:39:37 redhat FaxGetty[22352]: DELAY 75 ms
May 3 18:39:37 redhat FaxGetty[22352]: MODEM set DTR ON
May 3 18:39:37 redhat FaxGetty[22352]: DELAY 2600 ms
May 3 18:39:40 redhat FaxGetty[22352]: MODEM set baud rate: 19200 baud, input f
low RTS/CTS, output flow RTS/CTS
May 3 18:39:40 redhat FaxGetty[22352]: DELAY 10 ms
May 3 18:39:40 redhat FaxGetty[22352]: MODEM flush i/o
May 3 18:39:40 redhat FaxGetty[22352]: <-- [4:ATZ\r]
May 3 18:40:10 redhat FaxGetty[22352]: MODEM TIMEOUT: reading line from modem
May 3 18:40:10 redhat FaxGetty[22352]: MODEM <Timeout>
May 3 18:40:10 redhat FaxGetty[22352]: MODEM set DTR OFF
May 3 18:40:10 redhat FaxGetty[22352]: DELAY 75 ms
May 3 18:40:10 redhat FaxGetty[22352]: MODEM set DTR ON
May 3 18:40:10 redhat FaxGetty[22352]: DELAY 2600 ms
May 3 18:40:14 redhat FaxGetty[22352]: MODEM set baud rate: 19200 baud, input f
low RTS/CTS, output flow RTS/CTS
May 3 18:40:14 redhat FaxGetty[22352]: DELAY 10 ms
May 3 18:40:14 redhat FaxGetty[22352]: MODEM flush i/o
May 3 18:40:14 redhat FaxGetty[22352]: <-- [4:ATZ\r]
May 3 18:40:44 redhat FaxGetty[22352]: MODEM TIMEOUT: reading line from modem
May 3 18:40:44 redhat FaxGetty[22352]: MODEM <Timeout>
May 3 18:40:44 redhat FaxGetty[22352]: MODEM set DTR OFF
May 3 18:40:44 redhat FaxGetty[22352]: /dev/ttyR0: Can not initialize modem.
May 3 18:40:44 redhat FaxGetty[22352]: STATE CHANGE: BASE -> MODEMWAIT (timeout
30)

Over on a working machine this is the permissions BTW:
[root@redhat etc]# ls -l /usr/sbin/faxgetty /dev/ttyR0
crw------- 1 uucp uucp 46, 0 May 4 04:51 /dev/ttyR0
-rwxr-xr-x 1 root root 63964 Apr 19 2007 /usr/sbin/faxgetty

[george_toolan]

Learn how to READ and stop complaining about linux ;-)

May 4 05:35:47 redhat FaxGetty[5054]: The fax server must run with real uid root.

[UNIXgreybeard]

Originally Posted by george_toolan

Learn how to READ

Perhaps *I* was not clear in *my* communications.

I can create the permissions problem by FORCING it to run as UIDS not intended.

Correct UIDs and incorrect UIDs result in the same end condition - not working.

As my output noted - it will complain when the UID is not correct.

Oh, and as noted later in my communication I showed a working machine that has different UIDs/GIDs. Perhaps you would like to explain that difference rather than state

Learn how to READ

Originally Posted by george_toolan

and stop complaining about linux ;-)

How is this for an actual complaint then?

The driver shipped with the kernel:
[ 28.195173] RocketPort device driver module, version 2.09, 12-June-2003

The driver from Comtrol:
[ 1231.523931] RocketPort device driver module (SMP:yes), version 3.16, 11-Aug-2011

in 2 years the driver in the Linux kernel will be 10 years old.


If it is the old stale driver I'll be sure to post that solution.

---------- Post added at 01:12 PM ---------- Previous post was at 10:52 AM ----------

Resolution:

FC15 does not ship with setrocket but did ship with rocket.ko

The shipping rocket.ko is from 2003. The latest driver from Comtrol is from 2011 and ships with setrocket.

By replacing the 2003 rocket.ko with the driver from Comtrol faxgetty now works. I don't know if the 2011 vintage setrocket will work with the default rocket.ko.

(with narry a concern about the permissions)