Modems hanging up

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

Hi,

On Sat, Nov 07, 1998 at 02:55:35AM +0100, Greg Berardi wrote:
> >Allways try recent (1.1.18) version of mgetty (because 1.1.xx are
> >development versions).
> 
> I have been chasing the version monster for the last year and a half.
> I will try 1.1.18 if you really think it is necessary.

I don't really think that this is necessary here.  The modem part is
fairly unchanged - mgetty bugs (or new features) manifest differently.

> >Send your modem configuration (start minicom and write: atl5l6l7)
> 
> Is this really a lower case L as in ATL5L6L7? The string^^^^^^^^
> didn't work just reported an error with atl5l6l7 and atl5 atl6 atl6.
> 
> or is it ati5, ati6, ati7?

Most likely, it's "ati", but on some modems, the configuration can be
AT&V as well (classical Hayes).

[..]
> Is there something that I am missing?  I can't seem to find anyway
> to get to the configuration on these MultiTechs.  The USRs will report 
> all the info by using ati5 ati6 ati7.

There are some MultiTech experts on this list... Russ?

> >Maybe line is noisy or serial line speed is wrong (I don't know what the
> $SB
> >parameter is for but I had problems with it some time ago), and ...
> 
> The serial line speed is set at 57600 as per MultiTech.
> If I change this to 38400 will this decrease the throughput?
> Or should I go higher, 115200?  The cables that go to these modems
> are the flat cables that were supplied cyclades.  Could these be the 
> culprit?

Ah. Cyclades.  For Cyclades cards, make SURE that you

  - use the very latest drivers (in that case, it IS necessary, because
    earlier versions had bad bugs)

  - do NOT compile the Linux kernel with egcs or any other C compiler
    than gcc 2.7.2.3.  Other C compilers may create non-working kernels.

> I noticed that my mgetty.config file has this at line 20:
> 
> # access the modem(s) with 38400 bps
> speed 38400
> 
> This should probably be 57600?  Since my mgetty lines in inittab have
> -s 57600

Command line overrides mgetty.config.

> >May current init chat string is:
> >
> >  init-chat "" \d\d\d+++\d\d\dATZ OK AT OK ATB0L0M0&C1&D3&E4X4 OK
> 
> Is this in the policy.h?  The line #309:
> 
> #define MODEM_INIT_STRING       "ATS0=0Q0&D3&C1"

mgetty.config overrides policy.h, but yes, the policy.h string will be
used if you don't set "init-chat" in mgetty.config.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de