i think i have seen in the martian modems download page that they have specified that martian drivers cant be used for faxing.
On Thu, Aug 12, 2010 at 5:43 PM, Aidan Van Dyk
<aidan@xxxxxxxx> wrote:
* John H <arizonamythtv@xxxxxxxxx> [100812 00:34]:
> 02:0c.0 Communication controller: Agere Systems LT WinModem (rev 02)
> Subsystem: Agere Systems LT WinModem
> Kernel driver in use: martian
> Kernel modules: martian_dev
So you're using a "softmodem".
And eventually when HylaFAX uses the device, it gives errors (EIO):
> Aug 11 20:52:09.99: [ 3580]: MODEM READ ERROR: errno 5
> Aug 11 20:52:09.99: [ 3580]: MODEM READ ERROR: errno 5
> Aug 11 20:52:10.08: [ 3580]: MODEM WRITE ERROR: errno 5
> Aug 11 20:52:10.26: [ 3580]: MODEM WRITE ERROR: errno 5
> Aug 11 20:52:10.36: [ 3580]: MODEM WRITE ERROR: errno 5
> Aug 11 20:52:10.45: [ 3580]: MODEM WRITE ERROR: errno 5
> Aug 11 20:52:10.54: [ 3580]: MODEM WRITE ERROR: errno 5
Note that the errors didn't happen immediately, but only once it had
started... But at that point, it even gives EIO when told to hangup!
So it looks like a bug in the "modem" that is causing it to crash only
mid-fax-session.
> Aug 11 20:52:11.54: [ 3580]: <-- [5:ATH0\r]
> Aug 11 20:52:11.54: [ 3580]: MODEM WRITE ERROR: errno 5
> Aug 11 20:52:11.54: [ 3580]: SESSION END
> Any suggestions would be appreciated.
Did your softmodem driver change recently? Has it been reloaded? Since
it's returning EIO when HylaFAX reads/writes to it, it's definitely a
modem problem... But in this case, "modem" refers to both the "driver +
hardware". I'ld start looking for errors in dmesg, and then start
looking at the driver/hardware...
a.
--
Aidan Van Dyk aidan@xxxxxxxx
Senior Software Developer +1 215 825-8700 x8103
iFAX Solutions, Inc. http://www.ifax.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFMY+VsuVxNPsxNPScRAoNDAKCWZYkPbQJcXKB91kS2WreRh3iXdgCeKXAr
zI/RFRWZRePVYhI6DHPSo44=
=L54b
-----END PGP SIGNATURE-----