Cyclades and Mgetty

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

I recently installed Slackware 3.4 on my dial up server.  This server has 18 
modems connected via a Cyclades-Y card.  After I compiled the kernel, I 
saw that the Cyclades card wasn't talking to the modems so I downloaded the 
patch from Cyclades, recompiled and everything worked just fine, I thought...

I am having the strangest problem...  I use mgetty to handle the modems.
The problem happens like this:

A modem rings then is answered.  Mgetty presents the login prompt.
The user enters their name then mgetty starts to pass the name to the login
program.  The login program presents the user with the password prompt.
Then that modem port seems to freeze?  Sort of like the modem just hung up?

The thing that makes it hard to figure this out is that the problem moves
around.  Sometimes it might affect ttyC0, ttyC1 but all the other ports are
ok.  After a time (5 to 30 mins) ttyC0 and C1 will be working fine but
another port might not be?  Sometimes all ports work fine.  

Killing the mgetty process, init q, etc doesn't seem to have any affect.  I
have tried cycling the modems off and on to no avail?  

The real strange thing about this problem is the way is moves around and 
sometimes isn't there at all..

The Cyclades card and modem worked just perfectly on the Slackware 3.1
system that I had to replace.

I have tried two different versions of mgetty and a version of uugetty?  
Same exact symptoms?  I am pretty sure this is not an mgetty problem but
thought I would post this message here because you are familiar with the
way the getty/login process works.

Thanks,

Ralph  (ralphw@satcom.whit.org)


-- 
*******************************************************************
*  Ralph J. Whittaker, Jr.            FidoNet 1:128/139 CSAC BBS  *
*                                     Internet  ralphw@rmii.com   *
*******************************************************************