From owner-freebsd-stable Thu Apr 8 9:22:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from bluto.lgc.com (jking1.lgc.com [134.132.228.2]) by hub.freebsd.org (Postfix) with ESMTP id D5FB81510D for ; Thu, 8 Apr 1999 09:22:40 -0700 (PDT) (envelope-from king@sstar.com) Received: from raspberry ([134.132.228.7]) by bluto.lgc.com (8.9.3/8.9.1) with SMTP id LAA37677 for ; Thu, 8 Apr 1999 11:21:07 -0500 (CDT) (envelope-from king@sstar.com) Message-Id: <4.1.19990408111831.00975680@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 08 Apr 1999 11:20:38 -0500 To: freebsd-stable@freebsd.org From: Jim King Subject: Re: 3Com 3C5x9 Network cards In-Reply-To: References: <4.1.19990408100512.00ba7570@mail.supranet.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:16 PM 4/8/99 +0300, you wrote: >Hi! > >On Thu, 8 Apr 1999, Benjamin Gavin wrote: > >> this card working fine in 2.2.x and 3.0-STABLE boxes. It seems that >> sometime between 3.0-STABLE and 3.1-RELEASE that the code for this card was >> broken. > > I have had the same problem under 3.1-STABLE with ISA 3C509B cards - > FreeBSD did detect them, but had problems with sending/receiving data > through them. I've rolled back to simple ne2000 cards. > > BTW as I remember, FreeBSD had never worked good with this card's type. I always got much better performance with an NE2000 or SMC Elite16C than with the 3C509B. This wasn't just with FreeBSD - the 3C509B was also a bad performer under Windows NT. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message