From owner-freebsd-stable Thu Feb 24 11:23:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id DF03337BD42 for ; Thu, 24 Feb 2000 11:22:36 -0800 (PST) (envelope-from king@sstar.com) Received: from JKING ([134.132.75.164]) by sstar.com with ESMTP (IPAD 2.52) id 1956300; Thu, 24 Feb 2000 13:22:11 -0600 Message-Id: <4.2.0.58.20000224132002.00a70e98@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 24 Feb 2000 13:22:11 -0600 To: Jon Rust , stable@FreeBSD.ORG From: Jim King Subject: Re: good network card (xl0 packet dropping) In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:05 AM 2/24/2000 -0800, Jon Rust wrote: >At 1:03 AM -0500 2/18/00, Will Saxon wrote: >>What was the problem? I had a problem once doing the same thing with mine, >>but it was user error - the other side was 100mbit full duplex and I had >>forgotten to enable full-duplex. REALLY slow :P. > >This is why I won't use 10/100 Intel cards. I've had numerous problems >with them and my cisco cat 2924. They really don't seem to like talking to >another auto-negotiating device. I end up having to manually set one side >(or both) to get it to work. An unnecessary pain in the arse if you ask >me. It's been a while since I tried, so maybe it was a driver issue and >was fixed. For my money, the Kingston kne100tx's work fine, and the >lne100tx's from Linksys do as well. No superlatives, they just work. YMMV. In my office we had a Catalyst (5000?) that wouldn't auto-negotiate with TI Thunderlan NICs, but does fine with Intel and 3Com. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message