Re: [hylafax-users] MultiModemZPX-PCI Not Running After SLES Service Pack Upgrade

[David Forrest <drf@xxxxxxxxxxxxx>]

On Sun, 31 Aug 2008, michael hernandez wrote:

> I ran faxsetup again.  Then when running faxaddmodem,  I received this message.
>
> Probing for best speed to talk to modem: 38400 19200 9600 4800 2400 1200
> Unable to deduce DTE-DCE speed; check that you are using the
> correct device and/or that your modem is setup properly.  If
> all else fails, try the -s option to lock the speed.
>
> Something in the upgrade ( my service pack took me from Hylafax 5.2.2 to 5.2.3) has caused my modem to not be detected.  Where else should I look?
>
> Thanks.
>
> -Mike
>
>
> --- On Sun, 8/31/08, David Forrest <drf@xxxxxxxxxxxxx> wrote:
> From: David Forrest <drf@xxxxxxxxxxxxx>
> Subject: Re: [hylafax-users] Modem Not Running After SLES Service Pack Upgrade
> To: "michael hernandez" <mikehernandez99@xxxxxxxxx>
> Cc: hylafax-users@xxxxxxxxxxx
> Date: Sunday, August 31, 2008, 12:23 PM
>
> On Sun, 31 Aug 2008, michael hernandez wrote:
>
> > I upgraded my server this weekend from SUSE Linux Enterprise Server SP1
> > to SP2.  Everything is back to normal except my modem.  I am using a
> > MultiModemZPX fax board.
> >
> > Below is the output from "faxstat"
> >
> > linux-0f1s:~ # faxstat
> > HylaFAX scheduler on linux-0f1s.site: Running
> > Modem ttyS1 (3989109): Waiting for modem to come ready
> >
> > What impact would the service pack upgrade have on the modem?
> >
> > Thanks.
> >
> > -Mike
>
> I'm not a SUSE user but I had a similar problem upgrading Fedora that was
> solved by running faxsetup again and rebooting.  I don't remember
> re-running faxaddmodem but it shouldn't hurt (as long as you made no
> changes originally).  Don't really recall why I did that, but my stuck
> ZPX-PCI woke up.
>
> David Forrest                     e-mail   drf@xxxxxxxxxxxxx
> Maple Park Development Corporation  http://www.maplepark.com
> St. Louis, Missouri

I had that problem also.  On boot up my OS detected a different tty and I 
was trying to open the wrong thing.  I solved it by running: dmesg|grep 
tty like this:
[root@maplepark ~]# dmesg |grep tty
console [tty0] enabled serial8250:
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:09:
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 0000:02:08.0:
ttyS1 at I/O 0x8400 (irq = 18) is a 16550A
hash matches device tty51
[root@maplepark ~]#

and found it was /dev/ttyS1

I then ran setserial -G like this:
[root@maplepark ~]# setserial -G /dev/ttyS1
/dev/ttyS1 uart 16550A port 0x8400 irq 18 baud_base 115200 spd_normal 
skip_test
[root@maplepark ~]#

and set my modem baud rate in my config.ttyS1 to the 115200. That worked. 
(When I subsequently upgraded again, faxaddmodem suggested 57600, and I 
just left it at that. Seems to function OK).

For what's it worth, my config.ttyS1 now contains this for my 
MT5634ZPX-PCI MultiTech modem:

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
ModemSetupDTRCmd:	AT&D3		# hang up and reset on DTR drop
Class1EnableV34Cmd:	AT+F34=14,1,2	# 33600-2400 primary, 2400-1200 
control
Class1TMConnectDelay:	400		# counteract quick CONNECT 
response
Class1HasRHConnectBug:	yes		# cope with +FRH=3 CONNECT errors

Dave

David Forrest                     e-mail   drf@xxxxxxxxxxxxx
Maple Park Development Corporation  http://www.maplepark.com
St. Louis, Missouri