From: Andy Ferguson (ilug at domain moil.demon.co.uk)
Date: Fri 07 May 1999 - 19:34:47 IST
On Wed, 5 May 1999, John P. Looney wrote:
> Indeed. Should the presence of the 'direct y' in the config file nullify
> the need for a '-r' flag ?
Seems to. With mgetty.config set with
port ttyS0
direct y
speed 19200
and inittab as
s0:23:respawn:/sbin/mgetty ttyS0
Everything worked for me. However, I still got references to
resetting the modem in the logfile - this must be a red-herring (AKA
bug) - here's my snippet
--
05/07 18:10:30 yS0 mgetty: experimental test release 1.1.18-Sep11
05/07 18:10:30 yS0 check for lockfiles
05/07 18:10:30 yS0 locking the line
05/07 18:10:31 yS0 lowering DTR to reset Modem
05/07 18:10:32 yS0 waiting...
05/07 18:12:44 yS0 WARNING: starting login while DCD is low!
05/07 18:12:44 ##### data dev=ttyS0, pid=19637, caller='none', conn='DIRECT', name='', cmd='/bin/login', user='devel'
--
This was activated by a minicom session on another machine and
worked perfectly.
So it seems your mgetty setup is fine
> > the source and maybe in the info files. Check the info files for
> > your exact problem under the heading
> > mgetty works. /bin/login hangs
> > You may need to rewire your serial cable, it seems, if the problem
> > persists.
>
> The serial cable works. I can do hotsyncs & stuff with it at 57600 bps.
You did read the info file?
Serial cables can and do work with only two wires connected (pins 2
& 3) even over fairly long distances. Your problem seems to be with
the login program, not mgetty, which in turn the docs suggest is a
cable wiring problem such that login expects the DCD signal to be
high.
toggle-dtr n
may also be required in your mgetty.config file, in fact this
prevents the "lowering DTR to reset Modem" line in the logfile too.
Andy Ferguson
~~~~~~~~~~~~~
Sysop MOIL BBS +44-1247-273357
andy at domain moil.demon.co.uk
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:04:11 GMT