From owner-freebsd-questions Tue Apr 22 15:12:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA10165 for questions-outgoing; Tue, 22 Apr 1997 15:12:44 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA10160 for ; Tue, 22 Apr 1997 15:12:42 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id PAA24444; Tue, 22 Apr 1997 15:12:33 -0700 (PDT) Date: Tue, 22 Apr 1997 15:12:33 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Jaime Bozza cc: questions@freebsd.org Subject: Re: Driver Question In-Reply-To: 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 Tue, 22 Apr 1997, Jaime Bozza wrote: > > We've been running FreeBSD systems (Currently 2.1.7's and 2.2.1's) with > 3C509 cards in them for a while. I'm curious about the driver support for > the 3C900 (Etherlink XL) card. I know the support exists, but how *IS* > it? Even though LINT says the 3C509 support is buggy, we've never had an > issue of the systems not working, crashing, etc... > > Basically, is the 3C900 support mature enough to use in a live situation? It worked okay for me. I had a lot of input and output errors, although I think this was linked to the cable I was using. The 3c900 has very little onboard cache; if this machine is going to be busy, you may not want to use this. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major