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

[michael hernandez <mikehernandez99@xxxxxxxxx>]

Yes, all is good.  Thank you very much!!  I am glad to have our fax system back up before the holiday weekend is over.  "ttyS0" is still referenced when I issue command "dmesg |grep tty."  And my modem is detected at "ttyS4."  I deleted the file "config.ttyS1" and "ttyS1" does not show from the command "faxstat".  In my "etc/initab" file I removed "ttyS1" and replaced with "ttyS4"  where the command to execute faxgetty is located.  AvantFax is our application of choice for Hylafax and I have re-configured it for use with ttyS4.

One theory I had on what caused this on my system (SUSE Linux Enterprise Server 10 - SP2) was that I had configured my modem at the command line via faxsetup and faxaddmodem.  The OS's GUI system tool -YsST, does not show the modem as set up.  So to YaST the modem does not exist.

I will keep these practices in mind for the next upgrade :)

-Mike



--- On Mon, 9/1/08, David Forrest <drf@xxxxxxxxxxxxx> wrote:

From: David Forrest <drf@xxxxxxxxxxxxx>
Subject: Re: [hylafax-users] MultiModemZPX-PCI Not Running After SLES Service Pack Upgrade
To: "michael hernandez" <mikehernandez99@xxxxxxxxx>
Cc: hylafax-users@xxxxxxxxxxx
Date: Monday, September 1, 2008, 12:33 PM

OK Mike, good.  That's the same thing I got- a spurious tty (or perhaps 
just another serial port).  Your system detected that one on boot up.  No 
matter, just delete your old config.ttyS1, as you really don't need (or 
want) it. If you're starting faxgetty from init, you should delete the 
faxgetty /dev/ttyS1 that is not being used by your hylafax. reboot and 
then rerun
 dmesg|grep tty and faxstat.  The extra ttyS0 will probably stay 
as your OS found it before, but the real modem ttyS4 should be there. 
Faxstat should show you up and running on ttyS4.

I don't know know why upgrades change the port on us.  It has happened 
several times on my system.  I think it has to do with the discovery 
routines the kernel goes through.  Those seem to be upgraded auto 
magically.  Maybe they now find a loose chip better or something.  Since 
you are not using it, just ignore it.  I have copied my earlier 
config.tty(whatever) over in the past and don't do that anymore as this 
problem just doesn't exist on a clean install, faxsetup, faxaddmodem, 
faxgetty setup, and reboot.  Actually, it takes less time than this note. 
:-)

Dave

On Mon, 1 Sep 2008, michael hernandez wrote:

> Thanks David!  I believe that I am up and running again.   I ran
"dmesg | grep tty"
 and it showed me that my port was
"ttyS4".  I then ran faxaddmodem using "ttyS4". 
>
> After running faxaddmodem with ttyS4 I issued the command "dmesg
|grep tty" and the output is below.  I also ran faxstat to see what is
going on.  Can you tell me what is going on with "ttyS0" and
"ttyS1" from the output below?  What should I do with
"ttyS0" and "ttyS1" now that I am configured on port
"ttyS4"?
>
> linux-0f1s:~ # dmesg |grep tty
> serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> 0000:08:02.0: ttyS4 at I/O 0xec00 (irq = 225) is a 16550A
> linux-0f1s:~ # faxstat
> HylaFAX scheduler on linux-0f1s.site: Running
> Modem ttyS1 (3989109): Waiting for modem to come ready
> Modem ttyS4 (3989109): Running and idle
> linux-0f1s:~ #
>
> Regards,
>
> -Mike
>
>
> --- On Sun, 8/31/08, David Forrest
 <drf@xxxxxxxxxxxxx> wrote:
> From: David Forrest <drf@xxxxxxxxxxxxx>
> Subject: Re: [hylafax-users] MultiModemZPX-PCI Not Running After SLES
Service Pack Upgrade
> To: "michael hernandez" <mikehernandez99@xxxxxxxxx>
> Cc: hylafax-users@xxxxxxxxxxx
> Date: Sunday, August 31, 2008, 1:36 PM
>
> 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
>
>
>

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