Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sgiblab!swrinde!gatech!newsxfer.itd.umich.edu!newsrelay.iastate.edu!news.iastate.edu!griffon
From: griffon@iastate.edu (William Stoltenberg)
Newsgroups: comp.os.386bsd.development
Subject: Re: vi (elvis) and more dont work on com ports
Date: 9 Mar 1994 05:53:50 GMT
Organization: Iowa State University, Ames, Iowa (USA)
Lines: 31
Message-ID: <2ljo9e$2qv@news.iastate.edu>
References: <1994Mar8.191449.5104@mcshub.dcss.mcmaster.ca>
Reply-To: griffon@phoenix.vorpal.com
NNTP-Posting-Host: pv0555.vincent.iastate.edu
Keywords: tty01 vi more ioctl termio TCSETS
In article <1994Mar8.191449.5104@mcshub.dcss.mcmaster.ca>,
Mike Anderson <mike@CEB.McMaster.CA> wrote:
>I have found that in netBSD 0.9 the more and vi programs call an ioctl
>to set modes on the tty and this results in the serial lines going into
>some useless mode where the same nonesense is echoed no-matter what is
>typed in. This problem only occurs on the tty (COM1 COM2) serial ports,
>not on the PCs own console.
>
>Does anyone know about or experienced this problem or know of a fix?
>
>mike anderson
>mike@cebnet.ceb.mcmaster.ca
I have this same problem with an hp150 terminal hooked up to my com
port. At first I figured that the problem was due to some screw up in the
termcap entry, but after analyzing what came through the line, saw this was
not the case. The characters I see on the screen are two blotchy squares and
a '{' for each key typed (doesn't matter what I type) or just nothing at all.
It seems as if sometimes the computer isn't even receiving what the terminal
wants to send.
As to a fix...tell me when you find one :)
-Will
--
Will Stoltenberg | "We never said our love was evergreen, or as
Ames, Iowa (515) 294-3992| unchanging as the sea, but please promise me that
"Tamber Kelsain" | sometime, you will think of me."
griffon@iastate.edu | Christine, Phantom of the Opera.