Re: [hylafax-users] Mainpine Rockforce DUO+ Wedge

Andrew,

Here’s a more detailed log. Yes, I followed the Linux instructions on your website.

Normally faxing in and out are without any problems, so I would think that the settings are all correct.

Config

=====

ModemType: Class1.0 # use this to supply a hint

ModemRate: 57600 # must be at least as fast as the DCE-DCE communication

ModemFlowControl: rtscts # many firmwares have broken software flow control

Class1EnableV34Cmd: AT+F34=14,1,2 # 33600-2400 primary, 2400-1200 control

Class1TMConnectDelay: 400 # counteract quick CONNECT response

ModemDialCmd: ATDT,%s

ModemResetCmds: "AT+GCI=9C;+VCID=1"

Class1RMQueryCmd: "!3,24,48,72,73,74,96,97,98,121,122,145,146"

Class1TMQueryCmd: "!3,24,48,72,73,74,96,97,98,121,122,145,146"

ModemModelQueryCmd: "!Mainpine Venus V.92 I03.04.02 (0026SD) Voice V2 V92cap 12ns RAM Mercury"

ModemMfrQueryCmd: "!Mainpine Venus V.92 I03.04.02 (0026SD) Voice V2 V92cap 12ns RAM Mercury"

ModemClassQueryCmd: "!0,1,1.0,2,2.1,8"

QualifyCID: etc/cid # CID access control list file

CallIDPattern: "NMBR=" # pattern string for phone number info

CallIDPattern: "NAME=" # pattern string for identity info

Class1Cmd: AT+FCLASS=1

lspci

====

00:14.0 Modem: MainPine Ltd PCI <-> IOBus Bridge (rev 32) (prog-if 00 [Generic])

Subsystem: MainPine Ltd: Unknown device 0c00

Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-

Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-

Interrupt: pin A routed to IRQ 5

Region 0: I/O ports at e800 [size=128]

Region 1: Memory at e6400000 (32-bit, non-prefetchable) [size=1M]

Alex Koh

From: andrew rinaldi [mailto:andrew.rinaldi@xxxxxxxxxxxx]
Sent: Wednesday, May 24, 2006 5:44 PM
To: Alex Koh; 'Hylafax Users Mailing List'
Subject: RE: [hylafax-users] Mainpine Rockforce DUO+ Wedge

Hi Alex.

Please ensure that you have completed the online questionnaire;

http://www.mainpine.com/supportquestionnaire.html

And include details of how you have configured and installed your board (did you include the multiport register ?);

http://www.mainpine.com/faqs/linux_ans/ans1_linux.htm

Regards

ANDREW RINALDI

Mainpine Ltd. Support

USA +1 718 701 2422 | Asia/Europe +44 1225 436137

andrew.rinaldi@xxxxxxxxxxxx | www.mainpine.com

From: hylafax-users-bounce@xxxxxxxxxxx [mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of Alex Koh
Sent: 24 May 2006 06:28
To: Hylafax Users Mailing List
Subject: [hylafax-users] Mainpine Rockforce DUO+ Wedge

Hi,

I am using rockforce duo+ card with hylafax 4.2.5, redhat 8.0 with recompiled kernel 2.4.23 on a Via M10000 ITX board with a single PCI riser card.

I managed to replicate the “wedged” problem EVERYTIME using this:

1) port A sends to port B

2) port B sends to port A

When both sends AT THE SAME TIME, after a while, hylafax will not be able to initialize 1 of the port, while the other port still works.

Anyone else encountering this same problem?

Alex Koh

ps: this email is also sent to Mainpine support

========================================

Some logs in /var/log/messages:

May 24 10:29:12 Innofax FaxGetty[11910]: MODEM MAINPINE VENUS V.92 I03.04.02 (0026SD) VOICE V2 V92CAP 12NS RAM MERCURY Mainpine Venus V.92 I03.04.02 (0026SD) Voice V2 V92cap 12ns RAM Mercury/

May 24 10:29:12 Innofax FaxGetty[11910]: <-- [5:ATM0\r]

May 24 10:29:12 Innofax FaxGetty[11910]: --> [2:OK]

May 24 10:29:12 Innofax FaxGetty[11910]: <-- [14:AT+F34=14,1,2\r]

May 24 10:29:12 Innofax FaxGetty[11910]: --> [2:OK]

May 24 10:29:12 Innofax FaxGetty[11910]: STATE CHANGE: LOCKWAIT -> RUNNING (timeout 30)

May 24 12:53:19 Innofax FaxGetty[20495]: /dev/ttyS5: Can not initialize modem.

May 24 12:53:19 Innofax FaxGetty[20495]: STATE CHANGE: LOCKWAIT -> MODEMWAIT (timeout 30)

May 24 12:53:19 Innofax FaxGetty[20495]: QUIT

May 24 12:53:19 Innofax FaxGetty[20495]: CLOSE /dev/ttyS5

May 24 12:53:19 Innofax FaxGetty[15360]: OPEN /dev/ttyS5 HylaFAX (tm) Version 4.2.5

May 24 12:53:20 Innofax FaxGetty[15360]: MODEM set DTR OFF

May 24 12:53:20 Innofax FaxGetty[15360]: DELAY 75 ms

May 24 12:53:20 Innofax FaxGetty[15360]: MODEM set DTR ON

May 24 12:53:20 Innofax FaxGetty[15360]: DELAY 2600 ms

May 24 12:53:24 Innofax FaxGetty[15360]: MODEM set baud rate: 57600 baud, input flow RTS/CTS, output flow RTS/CTS

May 24 12:53:24 Innofax FaxGetty[15360]: DELAY 10 ms

May 24 12:53:24 Innofax FaxGetty[15360]: MODEM flush i/o

May 24 12:53:24 Innofax FaxGetty[15360]: <-- [4:ATZ\r]

May 24 12:53:54 Innofax FaxGetty[15360]: MODEM TIMEOUT: reading line from modem

May 24 12:53:54 Innofax FaxGetty[15360]: MODEM <Timeout>

May 24 12:53:54 Innofax FaxGetty[15360]: MODEM set DTR OFF

May 24 12:53:54 Innofax FaxGetty[15360]: DELAY 75 ms

May 24 12:53:54 Innofax FaxGetty[15360]: MODEM set DTR ON

May 24 12:53:54 Innofax FaxGetty[15360]: DELAY 2600 ms

May 24 12:56:42 Innofax FaxGetty[15360]: MODEM set baud rate: 57600 baud, input flow RTS/CTS, output flow RTS/CTS

May 24 12:56:42 Innofax FaxGetty[15360]: DELAY 10 ms

May 24 12:56:42 Innofax FaxGetty[15360]: MODEM flush i/o

May 24 12:56:42 Innofax FaxGetty[15360]: <-- [4:ATZ\r]

May 24 12:57:12 Innofax FaxGetty[15360]: MODEM TIMEOUT: reading line from modem

May 24 12:57:12 Innofax FaxGetty[15360]: MODEM <Timeout>

May 24 12:57:12 Innofax FaxGetty[15360]: MODEM set DTR OFF

May 24 12:58:14 Innofax FaxGetty[15360]: /dev/ttyS5: Can not initialize modem.

May 24 12:58:14 Innofax FaxGetty[15360]: STATE CHANGE: BASE -> MODEMWAIT (timeout 30)

May 24 12:58:14 Innofax FaxGetty[15360]: QUIT

May 24 12:58:14 Innofax FaxGetty[15360]: CLOSE /dev/ttyS5