From owner-freebsd-questions Wed Jul 4 9:15:42 2001 Delivered-To: freebsd-questions@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 4593B37B403 for ; Wed, 4 Jul 2001 09:15:40 -0700 (PDT) (envelope-from dg@root.com) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id f64G5Cm96396; Wed, 4 Jul 2001 09:05:12 -0700 (PDT) (envelope-from dg) Date: Wed, 4 Jul 2001 09:05:12 -0700 From: David Greenman To: Greg Quinlan Cc: freebsd-questions@freebsd.org Subject: Re: fxp NIC error! Message-ID: <20010704090512.A89686@nexus.root.com> References: <20010702155941.A83552@nexus.root.com> <20010704101332.9108.qmail@web13302.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010704101332.9108.qmail@web13302.mail.yahoo.com>; from gwq_uk@yahoo.com on Wed, Jul 04, 2001 at 11:13:32AM +0100 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Intel EtherExpress Pro 10/100 EEPROM contents: > Station address 00:A0:C9:90:18:C6. > Receiver lock-up bug exists. (The driver work-around ... >I'm not quite sure what this means! It mentions >something about a receiver lock-up bug??? > >Does anyone have any knowledge of this bug and if 4.3S >has the work around. Yes, I'm familiar with the bug, and yes, FreeBSD does have the work-around for it. It is not the cause of the problem that you're reporting. Have you tried setting the speed and duplex to manual/forced settings? -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message