From owner-freebsd-questions Tue Sep 3 20:42:41 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA18692 for questions-outgoing; Tue, 3 Sep 1996 20:42:41 -0700 (PDT) Received: from gamespot.com (ns1.gamespot.com [206.169.18.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA18682 for ; Tue, 3 Sep 1996 20:42:36 -0700 (PDT) Received: from tech-a.gamespot.com (tech-a.gamespot.com [206.169.18.59]) by gamespot.com (8.7.5/8.6.12) with SMTP id UAA06631 for ; Tue, 3 Sep 1996 20:29:58 GMT Message-Id: <199609032029.UAA06631@gamespot.com> Comments: Authenticated sender is From: "Ian Kallen" To: FreeBSD Questions Date: Tue, 3 Sep 1996 20:36:09 +0000 Subject: Re: ep driver buggy? Reply-to: ian@gamespot.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've had 3c509's give me no problems whatsoever on two machines I have running freeBSD. Just for kicks, I bought two SMC 10/100baseT cards (the 9332, I think 'twas called) -- those cards were so buggy under Windows95 I _hope_ they are the high performance n'er do quit cards that I've heard that they are under freeBSD (I'm pretty sure that Yahoo uses those for their freeBSD boxes) - anyway, they are leaving their current Win95 hosts ASAP: on those machines at least, they suck! The 3c509, once plug n play is off, everything's great. And 3com includes a DOS utility that is even useful, unlike SMC. > Date: Tue, 3 Sep 1996 19:06:01 -0700 (PDT) > From: Doug White > Reply-to: dwhite@resnet.uoregon.edu > To: Garth Corral > Cc: FreeBSD Questions > Subject: Re: ep driver buggy? > On Tue, 3 Sep 1996, Garth Corral wrote: > > > Found this while browsing the FreeBSD handbook at freebsd.org: > > > > [from section 5.3.8. Networking] > > > > device ep0 at isa? port 0x300 net irq 10 vector epintr > > > > 3Com 3C509 (buggy) > > > > What exactly does 'buggy' mean? Is this up to date? > > The 3c509 driver has come on hard times recently. It isn't very stable, > main example being that the card will 'disappear' until it is disabled and > re-enabled with 'ifconfig ed0 down' and 'ifconfig ed0 up'. > > The NE2000 code is still as solid as ever :-) > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > > Ian Kallen ian@gamespot.com Director of Technology & Web Administration http://www.gamespot.com