From owner-freebsd-stable Wed Jan 24 23:18:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 23EC237B400 for ; Wed, 24 Jan 2001 23:18:27 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f0P7HrE28494; Wed, 24 Jan 2001 23:17:54 -0800 (PST) Date: Wed, 24 Jan 2001 23:17:53 -0800 (PST) From: Doug White To: Mikhail Kononenko Cc: freebsd-stable@FreeBSD.ORG Subject: Re: EtherExpress100 on Intel Easton In-Reply-To: <024301c08642$e09fb3a0$210aa8c0@mikhail> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Jan 2001, Mikhail Kononenko wrote: > Sorry, if this is offtopic here, but I could not get answer from native > lists... > > Linux kernel-2.2.17 on D815EEAL (with integrated NIC). The driver used: > eepro100. Traditionally, the Linux Intel EtherExpress Pro/100 drivers have, quite frankly, sucked. This is a known problem with no solution. This is counter to FreeBSD, where the fxp driver is one of the best ethernet drivers in the system :-) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message