From owner-freebsd-questions Sun Jul 13 21:26:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27232 for questions-outgoing; Sun, 13 Jul 1997 21:26:02 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.186.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27223 for ; Sun, 13 Jul 1997 21:25:56 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id VAA03885; Sun, 13 Jul 1997 21:25:51 -0700 (PDT) Date: Sun, 13 Jul 1997 21:25:51 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: kleon@bellsouth.net cc: questions@FreeBSD.ORG Subject: Re: silo overflow with 16450 chip In-Reply-To: <199707140049.UAA00187@myplace.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 13 Jul 1997, Charlie Root wrote: > I've been running 2.1.5 for the last 6 months on a IBM PS/Note and > having very good time except for the problem with the 16450 chip > controling my serial port. I get silo overflow messages every 3 minutes > when online. Is there an earlier version that didn't have this > difficulty that is still usable? The only way to stop the overflows is to slow down your baudrate. The 16450 can only handle speeds of 9600 baud or so without dropping packets. You can buy serial cards with 16550 UARTs on them, which I'd recommend if you're trying to do high speed comm on this port. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo