Mgetty not answering

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

Hi,

On Sun, Jan 04, 1998 at 07:30:45PM -0500, Zheng Wang wrote: 
> I tried again and get the following message from
> /var/log/mgetty.log.ttyS3. Actually, I don't quite understand the first 
> part  in your email. It goes: "run mgetty from /etc/inittab, use a
> higher debug level," 

It means:

  - start mgetty by adding it to /etc/inittab, don't run from the command
    line (because it wouldn't work).
  - run mgetty with "-x5", so that the log file contains more data.

> 01/04 18:48:28 yS3  mgetty: experimental test release 1.1.14-Apr02
> 01/04 18:48:28 yS3  check for lockfiles
> 01/04 18:48:28 yS3  locking the line
> 01/04 18:48:29 yS3  WARNING: DSR is off - modem turned off or bad cable?
> 01/04 18:48:29 yS3  lowering DTR to reset Modem
> 01/04 18:48:29 yS3  send: \dATQ0V1H0[0d]
> 01/04 18:48:30 yS3  waiting for ``OK''
> 01/04 18:48:50 yS3  timeout in chat script, waiting for `OK'
> 01/04 18:48:50 yS3  init chat timed out, trying force-init-chat
> 01/04 18:48:50 yS3  send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
> 01/04 18:48:54 yS3  waiting for ``OK''
> 01/04 18:49:14 yS3  timeout in chat script, waiting for `OK'
> 01/04 18:49:14 yS3  init chat failed, exiting...: Interrupted system call
> 01/04 18:49:14 ##### failed in mg_init_data, dev=ttyS3, pid=5347

Now that looks pretty much like "wrong serial port", or "broken serial
port", or "modem switched off".  There is no DSR signal, and the modem
doesn't answer.

You're sure the modem is on ttyS3?  DOS' com3 is ttyS*2* under Linux.

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