Date: Wed, 14 Jan 1998 08:29:54 -0600 (CST) From: Jay Nelson <jdn@acp.qiv.com> To: David Alan Kott <dakott@alpha.delta.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: [Q] Getty, Qume 101 ser. terms. and gettytab (fwd) Message-ID: <Pine.BSF.3.96.980114080500.307A-100000@acp.qiv.com> In-Reply-To: <Pine.OSF.3.95.980113040915.2566A-100000@alpha.delta.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, I understand more, but don't have a complete answer. I missed that
you were using software flow control. I saw 19200 and assumed
hardware.
9600 is about as fast as you can reliably run software flow control.
So for starters, I'd set everything to 9600. As far as the echoctl, it
is probably being reset either by the string in your gettytab or your
termcap.
After thinking about this, I'm not sure I'd want to turn off echoctl
(I've never done it anyway). It may cause some interesting side
effects.
So the answer is: I have no answer. You'll have to prowl around your
termcap entrys and gettytab entries and find the connection. You may
want to try setting -opost and see what happens.
Sorry I couldn't really help.
-- Jay
On Tue, 13 Jan 1998, David Alan Kott wrote:
>
> >It would be interesting to see _all_ stty's output on the ttyd2 port.
> >Why are you trying to enable a login on a call_out_ port?
>
> well, right off, I am not at all sure as to the difference. 1:) ttyd2 (as
> I had it) wasn't working for me.. and 2:) I seem to have read somewhere
> that one should use call out ports when you DON'T have "modem control
> lines" which I took to be the 4 control lines present on a RS-232 serial
> port, which I don't have; just running TX and RX and the Signal ground.
>
>
> Thank you Jay, for taking the time to answer my post.
>
> Yes, Ininitially, I did indeed use the callin port. However, that wasn't
> working.. in the same way that the current callout port isn't working..
> or, more specifically, I don't have it set up right such that it CAN
> work.
>
> Anyways, at your suggestion, here is the complete dump from stty for that
> port BEFORE login starts... (and getty is just hanging there)
>
> %stty -a -f /dev/ttyd2
> speed 19200 baud; 0 rows; 0 columns;
> lflags: icanon isig iexten echo echoe -echok echoke -echonl -echoctl
> -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo
> -extproc
> iflags: -istrip icrnl inlcr -igncr ixon ixoff ixany imaxbel -ignbrk
> brkint -inpck -ignpar -parmrk
> oflags: opost onlcr oxtabs
> cflags: cread cs8 -parenb -parodd hupcl clocal -cstopb -crtscts -dsrflow
> -dtrflow -mdmbuf
> cchars: discard = ^O; dsusp = <undef>; eof = <undef>; eol = <undef>;
> eol2 = <undef>; erase = ^H; intr = ^C; kill = ^U;
> lnext = <undef>; min = 1; quit = ^\; reprint = <undef>;
> start = ^Q; status = <undef>; stop = ^S; susp = <undef>;
> time = 0; werase = <undef>;
>
> Now.. the output AFTER said login session starts.. and getty has gone it's
> merry way.
>
> %stty -a -f /dev/ttyd2
> speed 19200 baud; 0 rows; 0 columns;
> lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
> -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo
> -extproc
> iflags: -istrip icrnl inlcr -igncr ixon ixoff ixany imaxbel -ignbrk
> brkint -inpck -ignpar -parmrk
> oflags: opost onlcr oxtabs
> cflags: cread cs8 -parenb -parodd hupcl clocal -cstopb -crtscts -dsrflow
> -dtrflow -mdmbuf
> cchars: discard = ^O; dsusp = <undef>; eof = <undef>; eol = <undef>;
> eol2 = <undef>; erase = ^H; intr = ^C; kill = ^U;
> lnext = <undef>; min = 1; quit = ^\; reprint = <undef>;
> start = ^Q; status = <undef>; stop = ^S; susp = <undef>;
> time = 0; werase = <undef>;
>
> and, as before, I get similiar behavior with the callin port; echoctl is
> inhibited before the session starts, and there is nothing I can do (or,
> have done) to keep it from being set AFTER the session starts.
>
> Frustratingly Yours,
>
> David Kott
>
>
> > Greetings,
> >
> > I have been, for a few days now, attempting to get a Qume QVT-101 serial
> > dumb terminal to work over one of my serial ports on my 2.2.5 stable
> > system with only limited success.
>
> > %uname -rsv
> > FreeBSD 2.2.5-STABLE FreeBSD 2.2.5-STABLE #0: Sat Jan 3 01:07:09 EST 1998
> >
> > Gettytab entry I am using currently...
> > ...
> > std.19200.qvt101|19200-baud:\
> > :np:sp#19200:xc:
> > ...
> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980114080500.307A-100000>