Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!newsfeed.internetmci.com!papergirl.highway1.com!chnws02.highway1.com!ndnws01.ne.highway1.com.!news
From: Ted Buswell <tbuswell@balrog.ml.org>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Why can't I get a login on ttyd0?
Date: 24 Jun 1997 22:08:40 -0400
Organization: CLI Junkies Anonymous
Lines: 37
Message-ID: <87zpsfl9hz.fsf@balrog.ml.org>
References: <5ojthg$c3h@news.ox.ac.uk>
NNTP-Posting-Host: tbuswell.ne.highway1.com
X-Newsreader: Gnus v5.3/Emacs 19.34
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:43449
Neil Long <neil.long@materials.oxford.ac.uk> writes:
> I am failing to get a 'login' prompt on a PC running 2.2.2 and I can't
> figure out what I have missed.
Does it work OK if you say cuaa0 instead of ttyd0? If so, then
probably getty is waiting for DCD.
One way to get around this is to add something like the appended
lines to your /etc/rc.serial. This modification and an otherwise
stock /etc with a minimal set of wires allow me to login via my
trusty hp48.
My guess is that your serial cable is missing DCD.
-Ted
########################################
nodcd() {
# Lose DCD so that open() [and other things] don't wait for
# carrier detect, which might not come due to a lack of hardware
# support (=> cable doesn't have the wire).
ci=$1; shift
co=$1; shift
for i in $*
do
stty < /dev/ttyi$ci$i clocal
stty < /dev/ttyl$ci$i clocal
stty < /dev/ttyi$co$i clocal
stty < /dev/ttyl$co$i clocal
done
}
# Turn off DCD on all 4 serial ports.
nodcd d d 0 1 2 3 4