From owner-freebsd-stable Sun Apr 6 23:10:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA24858 for stable-outgoing; Sun, 6 Apr 1997 23:10:47 -0700 (PDT) Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA24853 for ; Sun, 6 Apr 1997 23:10:45 -0700 (PDT) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by mercury.uniserve.com (8.8.2/8.8.2) with SMTP id XAA03908; Sun, 6 Apr 1997 23:06:02 -0700 (PDT) Date: Sun, 6 Apr 1997 23:16:16 -0700 (PDT) From: Tom Samplonius To: Richard Todd cc: stable@freebsd.org, danny@wildstar.net Subject: Re: problem with 3C509 ethernet cards in machine running FreeBSD 2.1.7-RELEASE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Apr 1997, Richard Todd wrote: > We're having a problem with a Pentium 166 machine with two 3Com Ethernet > cards in it running FreeBSD 2.1.7-RELEASE and acting as an NFS server. ... The FreeBSD drive for the 3C509 isn't the greatest. Apparently 3COM has been less than forthcoming with the hw info. Some hw revs work better than others. The de0 drive is known to be very solid for 10mbs ethernet cards (has problems probling 100mbs cards). I use the SMC Etherpower 10, with NEVER a problem. The Intel PRO100B is supposed to be a very good 100ms card. The driver supports full-duplex operation too. Tom