From owner-freebsd-questions Wed Jul 4 3:13:36 2001 Delivered-To: freebsd-questions@freebsd.org Received: from web13302.mail.yahoo.com (web13302.mail.yahoo.com [216.136.175.38]) by hub.freebsd.org (Postfix) with SMTP id 7A81937B403 for ; Wed, 4 Jul 2001 03:13:32 -0700 (PDT) (envelope-from gwq_uk@yahoo.com) Message-ID: <20010704101332.9108.qmail@web13302.mail.yahoo.com> Received: from [213.1.128.112] by web13302.mail.yahoo.com; Wed, 04 Jul 2001 11:13:32 BST Date: Wed, 4 Jul 2001 11:13:32 +0100 (BST) From: =?iso-8859-1?q?Greg=20Quinlan?= Reply-To: gwq_uk@yahoo.com Subject: Re: fxp NIC error! To: David Greenman Cc: freebsd-questions@freebsd.org In-Reply-To: <20010702155941.A83552@nexus.root.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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 Hi all, Further to this problem. I downloaded a diag. tool (originally designed for Linux). Ran it and came up with the following report: =======================8<============================= vpn# ./eepro -p ec00 -t 0 -e eepro100-diag.c:v2.05 6/13/2001 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Assuming a Intel i82557/8/9 EtherExpressPro100 adapter at 0xec00. Intel EtherExpress Pro 10/100 EEPROM contents: Station address 00:A0:C9:90:18:C6. Receiver lock-up bug exists. (The driver work-around *is* implemented.) Board assembly 668081-004, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. ==========================>8========================== 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. Greg --- David Greenman wrote: > >Hi all, > > > >Does anyone know why I have one fxp type interface > >that works but the other gives these errors. > > > >I have been told it is because Plug & Play OS is > set > >to yes? Why? > > Did setting it to NO fix the problem? > The issue has to do with interrupt routing and > other BIOS related stuff. > > -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. ____________________________________________________________ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message