From owner-freebsd-stable Wed Jan 10 2: 3:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gryphon.itssa.curtin.edu.au (gryphon.itssa.curtin.edu.au [134.7.72.31]) by hub.freebsd.org (Postfix) with ESMTP id 7854137B401 for ; Wed, 10 Jan 2001 02:03:32 -0800 (PST) Received: (from www@localhost) by gryphon.itssa.curtin.edu.au (8.9.3/8.9.3) id SAA06757; Wed, 10 Jan 2001 18:03:18 +0800 (WST) (envelope-from satherrl@gryphon.itssa.curtin.edu.au) Date: Wed, 10 Jan 2001 18:03:18 +0800 (WST) From: Richard Sather Message-Id: <200101101003.SAA06757@gryphon.itssa.curtin.edu.au> X-Authentication-Warning: gryphon.itssa.curtin.edu.au: www set sender to satherrl@itssa.curtin.edu.au using -f To: freebsd-stable@freebsd.org Reply-To: satherrl@gryphon.itssa.curtin.edu.au References: <6D5097D4B56AD31190D50008C7B1579BC97DD7@exlan5.rjf.com> In-Reply-To: <6D5097D4B56AD31190D50008C7B1579BC97DD7@exlan5.rjf.com> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.11 Subject: RE: Intel PRO/100+ driver or hardware? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Ian Cartwright : > A few weeks back I mentioned a similar problem I was having with a Compaq > Dexkpro EN. It has a built in 82559 chip. Under FreeBSD it would hang every > so often with a device timeout. Under Win2k it works great. I tried > everything I could think of (swapping cables, hubs, etc.) with no success > for FreeBSD. I tried the mailing lists but no one saw my post I guess. ;-/ ok - I have 12 CompaQ EN's sitting next to me aswell. Exactly the same timeout problem. 3.5.1-RELEASE also refuses to acknowledge their existence. We have tried a netgear 10Base hub at autonegotiate and fixed at 10Mbps aswell as through a Netgear FS 116 16 port switch with the same effect. We tried locking the card at 100Mbps which 'seemed' to cure the problem but our solution for the time being has been to use Pro 100/10B's. Regards Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message