*BSD News Article 27276


Return to BSD News archive

Xref: sserve comp.os.386bsd.questions:8708 comp.windows.x.i386unix:7256
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!cs.utexas.edu!uunet!epiwrl.entropic.com!usenet
From: kenh@wrl.epi.com (Ken Hornstein)
Newsgroups: comp.os.386bsd.questions,comp.windows.x.i386unix
Subject: Re: Problems with NetBSD-0.9/XFree86-2.0
Date: 10 Feb 1994 01:18:42 -0500
Organization: Entropic Research Laboratory, Washington DC
Lines: 29
Message-ID: <2jcjk2$344@sparc10.entropic.com>
References: <2j3r5t$34t@newsserv.cs.sunysb.edu> <MIKE.LONG.94Feb7173040@cthulhu.analog.com> <michaelv.760723129@ponderous.cc.iastate.edu>
Reply-To: kenh@wrl.epi.com
NNTP-Posting-Host: sparc10.entropic.com

In article <michaelv.760723129@ponderous.cc.iastate.edu>,
Michael L. VanLoon <michaelv@iastate.edu> wrote:
>In <MIKE.LONG.94Feb7173040@cthulhu.analog.com> Mike.Long@analog.com (Michael W. Long) writes:
>
>>In article <2j3r5t$34t@newsserv.cs.sunysb.edu> rick@cs.sunysb.edu (Rick Spanbauer) writes:
>
>>>	1.  com0 occasionally hangs kermit/tip in a state that kill -9
>>>	    will not remove them (process state SE+).
>
>>I've had this happen to me.  The com driver is sensitive to XOFF (^S)
>>even when it is told to use RTS/CTS flow control (SET FLOW RTS/CTS in
>>kermit).  If you unprefix ^S and download a binary that contains a ^S,
>>the serial port hangs consistently.  This bug still exists in
>>NetBSD-current as of 1/24/94.
>I've never experienced this.  Does the *serial port* (not the program)
>know that it's supposed to be ignoring xon/xoff?  Try doing a "stty -f
>/dev/tty00 -ixon -ixoff crtscts" before entering kermit (assuming
>you're using tty00).

Will that stty setting work?  I thought those parameters are reset upon close
of the tty device.  I myself have experienced this hanging problem that is
being described.

Personally, I found the com driver too buggy and slow; I recently switched
over to using sio under NetBSD (someone on the mailing list had done a partial
port), and it has been working a lot better.  I'm going to give the com drivers
another try when I get my 16550 serial card, however.

--Ken