From owner-freebsd-hardware Fri Nov 14 13:25:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04695 for hardware-outgoing; Fri, 14 Nov 1997 13:25:00 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04689 for ; Fri, 14 Nov 1997 13:24:54 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA09366; Fri, 14 Nov 1997 13:24:26 -0800 (PST) Message-Id: <199711142124.NAA09366@implode.root.com> To: sarah@BLaCKSMITH.com cc: Jim Shankland , phk@critter.freebsd.dk, freebsd-hardware@FreeBSD.ORG Subject: Re: four-port ethernet card compatible with freebsd In-reply-to: Your message of "Fri, 14 Nov 1997 14:58:17 EST." <199711141958.OAA03148@mccullers.blacksmith.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 14 Nov 1997 13:24:26 -0800 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Thanks for the input on the znyx. I checked it out and noticed that it has >the Dec chip 21140, which is essentially the same as the adaptec that we were >looking at. I'm not sure how freeBSD drivers are written, but it could be >that a driver for the znyx would work on the adaptec(cogent). If there are >known problems with the znyx we probably want to avoid it. > >I have another related question, though. Our fileserver runs freeBSD 2.1.6 >and has an intel etherexpress pro 100b ethernet card. We've been noticing >increasingly high Ierrs with this setup, which is kind of scary with it being >the fileserver and all. One of my co-workers has the exact same setup on >his home machine and is experiencing the same problem. Is there a known >problem with that driver? If so, is it fixed in later versions of freeBSD? >Any ideas on how to minimize the Ierrs? There shouldn't be any input errors - this is indicating that something is wrong. The version of the driver in 2.1.6 doesn't support full duplex, but the card will try to negotiate it in any case. If you have the machine connected to a switch, then this is likely the problem. You'll need to configure the switch port to half duplex or upgrade to the current release of FreeBSD (which supports full duplex operation). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project