Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!uniwa!info.curtin.edu.au!cproto From: cproto@cs.curtin.edu.au (Computer Protocol) Newsgroups: comp.os.386bsd.bugs Subject: Re: com driver problems in NetBSD 0.9 Date: 9 Sep 93 15:45:11 GMT Organization: Curtin University of Technology Lines: 58 Message-ID: <cproto.747589511@marsh> References: <1993Sep5.184053.5872@newstand.syr.edu> <cproto.747358704@marsh> <26l2nv$ja7@netbsd08.dn.itg.telecom.com.au> <cproto.747585384@marsh> NNTP-Posting-Host: marsh.cs.curtin.edu.au cproto@cs.curtin.edu.au (Computer Protocol) writes: >tdwyer@netbsd08.dn.itg.telecom.com.au (Terry Dwyer netbsd08 619 491 5161) writes: >>Computer Protocol (cproto@cs.curtin.edu.au) wrote: >>: dhhoveme@rodan.syr.edu (David H. Hovemeyer) writes: >>: >Howdy, >>: > I posted to comp.os.386bsd.questions last week and got >>: >some sympathy but no direct answers, so I thought I'd try my >>: >luck here. I upgraded from 0.8 to 0.9, and now can't get >>: >my VT102 connected to com1 on my generic IDE card to >>: >work. The login banner and prompt appear as usual, but >>: >programs that do terminal I/O (more, elvis) cause a row >>: >of garbage to be printed and the line settings to be messed >>: >up. This set up used to work under NetBSD 0.8. >>Did it? I am surprised, I had the same problems with NetBSD-0.8. It turned >>out to be I was logging in using 8N1 (from a dialup), doing an >>stty cs8 -parenb to allow me to use 8 bit, and then when I used more or vi >>I would get the same problems as you described. There was quite a lengthy >>thread on this subject in one of the c.o.3.* groups about 3 - 5 weeks ago. >>Anyway, I fixed my problem by using 7E1 when I log in from my SCO (UGH) box >>at home to my NetBSD-0.8 box at work. No problems with vi, more, less... >>anything. If you can set your hard wired terminal to those params it may >>solve your problem. >>Good luck, I haven't upgraded to '0.9 yet, I'm waiting until these little >>problems are sorted out. B-). >>: > Can anyone shed some light on this problem? >>: Same problem here. I can't use VI (elvis) on my com port otherwise >>: the settings become very insane. >>: Regards - Tibor Sashegyi (cproto@cs.curtin.edu.au) >>Hope that is of some help. >>Terry. >No, the problem has nothing to do with 8N1 versus 7E1. I tried >a number of different setting including different line speed >without success. If I remember right the settings reported by >stty -a < /decom0 were reasonable (done on the console). >Regards - Tibor Sashegyi (cproto@cs.curtin.edu.au) The settings are _almost_ reasonable but I just noticed that the setting becomes "a bit strange". After login the setting is 8N1. Once I start VI/ELVIS it becomes 7N1. My first terminal goes doesn't have 7N1 and throws up in a bad way. The second junk terminal can be set to 7N1 and works happily with this setting. It's a bit inconvenient though to enter setup before and after an edit session. Regards - Tibor Sashegyi (cproto@cs.curtin.edu.au)