![]() |
Thanks, I've tried the modem under XP since I have a dual boot and the modem works so it's not a hardware issue. It must be a driver issue as it did work in the past. I fired up minicom and tried sending the AT commands from the log file and I get the same errors. I saw some other people with the same issues but not a solution. http://www.hylafax.org/archive/2007-05/msg00192.php On Thu, Aug 12, 2010 at 12:37 PM, John H <arizonamythtv@xxxxxxxxx> wrote: > Thanks for the responses. Over time, with new kernels the martian > modem may have changed a bit but I would think not enough to keep it > from working. It did work in the past albeit it was unreliable as > sometimes it worked well and other times not. It was the modem that > came with my PC before I got into linux and after getting into linux I > realized the softmodems weren't the best. I'm not adverse on getting a > new modem but I want to get one that works better with Hylafax and > linux. > > Any input on the following modems > > http://www.frys.com/product/5048755 > http://www.frys.com/product/5892163 > http://www.frys.com/product/3984638 > http://www.frys.com/product/4829330 > > I'd prefer internal as my desk is pretty cluttered. > > Thanks for the help > > On Thu, Aug 12, 2010 at 5:27 AM, Ranjan Das > <ranjan.das@xxxxxxxxxxxxxxxxx> wrote: >> 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----- >>> >> >> > ____________________ 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@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*