From owner-freebsd-questions Wed Jul 4 12:48: 7 2001 Delivered-To: freebsd-questions@freebsd.org Received: from web13305.mail.yahoo.com (web13305.mail.yahoo.com [216.136.175.41]) by hub.freebsd.org (Postfix) with SMTP id 4D0A437B405 for ; Wed, 4 Jul 2001 12:48:03 -0700 (PDT) (envelope-from gwq_uk@yahoo.com) Message-ID: <20010704194803.81322.qmail@web13305.mail.yahoo.com> Received: from [213.122.38.97] by web13305.mail.yahoo.com; Wed, 04 Jul 2001 20:48:03 BST Date: Wed, 4 Jul 2001 20:48:03 +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: <20010704090512.A89686@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, I once came across a problem in connecting two auto sensing interfaces using a X-over UTP cable. The resolution to the problem was to connect both pieces of equipment to a HUB. Or set one to a constant speed. (It was connecting a NIC in my server directly to a Cisco Router's NIC.) (I noticed that someone had a similar PR; Intel NIC's connecting to a Cisco router with a timeout error.) Unfortunately setting the interface to a constant speed did not get it working, but the Cisco router did detect the speed change! Should I get a different Intel NIC, do more current ones have the same problem? Regards Greg --- David Greenman wrote: > >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. ____________________________________________________________ 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