![]() |
Hi Joea. I would strongly suggest that you address your RockForce board installation questions to support@xxxxxxxxxxxx because you will get an answer from someone with the relevant experience. Unfortunately, that isn't me and so I can't answer your questions today but I will attempt to find someone over the weekend who can. For the quickest response please complete the support questionnaire; http://www.mainpine.com/supportquestionnaire.php Regards ANDREW RINALDI Mainpine Ltd. Support USA +1 718 701 2422 | Asia/Europe +44 1225 436137 andrew.rinaldi@xxxxxxxxxxxx | www.mainpine.com -----Original Message----- From: hylafax-users-bounce@xxxxxxxxxxx [mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of joea (joea@xxxxxxxxxxxxxxx) Sent: 20 May 2006 16:37 To: hylafax-users@xxxxxxxxxxx Subject: Re: [hylafax-users] Configure mainpine quattro+ on suse This morning, after a cold boot, I come back with none found as shown below: ******************************************* FS2-L:~ # wvdialconf modemtest Scanning your serial ports for a modem. ircomm4<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ircomm5<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ircomm6<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ircomm7<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ircomm8<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ircomm9<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ircomm10<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ircomm11<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ircomm14<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ircomm15<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ircomm16<*1>: ATQ0 V1 E1 -- failed at 9600 and 19200 baud. ************************************************** When I do the steps shown on your web page, I get a response that suggests this is an "older revision" board, although just purchased brand new. The link to instructions for that board give a "404" error. I sent this info to the support address. I did get an indiaction, last evening, that the first port was ttyS14, when running "wvdialconf modemtest", after having made some attempts at configuring. I did not bother saving the setserial commands, as they did not seem to be working 100%. joea Support<support@xxxxxxxxxxxx> Boldly Declared: 5/19/2006 7:07 PM: > > You can find out what ttyS number was assigned to the first port of > the Mainpine board by running this from a command prompt: > > wvdialconf modemtest > > After you get the first ttyS#, you can proceed with the Mainpine > installation instructions located here: > > http://www.mainpine.com/faqs/linux_ans/ans1_linux.htm > > This will help you configure your rc.serial file with the correct > setserial commands. > > Note: If you are running a Linux 2.6.x kernel version, you cannot add > the setserial line with the "set_multiport" setting. Leave that last > line out when you are adding your configuration lines to the rc.serial > file. That setting is not required for 2.6.x kernel systems. > > If you still have problems, you may contact our support department > directly at support@xxxxxxxxxxxx . > > Thank you, > > Derrek Sypert > Mainpine, Inc. Support Manager > USA +1 718 701 2422 | Asia/Europe +44 1225 436137 > derrek.sypert@xxxxxxxxxxxx | www.mainpine.com > > -----Original Message----- > From: hylafax-users-bounce@xxxxxxxxxxx > [mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of joea > Sent: Friday, May 19, 2006 3:37 PM > To: hylafax-users@xxxxxxxxxxx > Subject: Re: [hylafax-users] Configure mainpine quattro+ on suse > > So, muddling my way, have defined the serial ports (as ttyS4-ttyS7), > but get a "UART unknown" when doing a "setserial". The rest of the > output seems reasonable. > > How can I tell it what the UART is. And how would I know? > > joea > > joea<joea@xxxxxxxxxxxxxxx> Boldly Declared: 5/19/2006 5:54 PM: >> Need to configure mainpine quattro+ on sles 9 with hylafax 4.2.5 >> >> Found specifics for RH (geeky) and Fedora (magic). YAST on Suse does >> not seem to fit the bill, expect geekness to intrude. Docs, > somewhere? >> >> joea >> >> ____________________ 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* > > > ____________________ 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* ____________________ 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* ____________________ 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*