*BSD News Article 18424


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!sequoia!ultima!kralizec.zeta.org.au!kralizec.zeta.org.au!not-for-mail
From: bde@kralizec.zeta.org.au (Bruce Evans)
Newsgroups: comp.os.386bsd.questions
Subject: Re: sio - problem with login hanging up
Date: 14 Jul 1993 23:00:00 +1000
Organization: Kralizec Dialup Unix Sydney: +61-2-837-1183 V.32bis
Lines: 22
Message-ID: <22100gINN85a@kralizec.zeta.org.au>
References: <g89r4222.742204159@kudu>
NNTP-Posting-Host: kralizec.zeta.org.au

In <g89r4222.742204159@kudu> g89r4222@kudu.ru.ac.za (Geoff Rehmet) writes:

>I have just installed the sio drivers in my kernel, but have
>encountered a couple of problems.  I have 2 serial ports
>configured, one of which is a mouse (still works fine) and the
>other is connected to a PC which can be used as a dumb terminal.

>The problems start when I try to log in from the PC: after I
>enter a login name the line hangs, I don't get a password prompt,
>and I am left with a login process sitting there.  (The setup I
>have worked perfectly - apart from silo overflows - with the old
>com drivers.)

This might be because you don't have carrier detect wired on the cable
to the PC (it should be connected to DTR on the PC end or wired on).
sio starts up in clocal mode to help avoid such problems.  But just
before getty exec()s login, it does bad things to the terminal control
flags including throwing away most of the values in the gettytab entry
and turning off clocal.  The old com driver "worked" with bad cables
because it faked carrier detect always being on.
-- 
Bruce Evans  bde@kralizec.zeta.org.au