From owner-freebsd-current Sun Nov 22 15:05:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23443 for freebsd-current-outgoing; Sun, 22 Nov 1998 15:05:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bouvreuil.cybercable.fr (bouvreuil.cybercable.fr [212.198.3.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA23434 for ; Sun, 22 Nov 1998 15:05:09 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 24468 invoked from network); 22 Nov 1998 23:07:24 -0000 Received: from d019.paris-8.cybercable.fr (HELO cybercable.fr) (212.198.8.19) by bouvreuil.cybercable.fr with SMTP; 22 Nov 1998 23:07:24 -0000 Message-ID: <36589853.58BA9D8D@cybercable.fr> Date: Mon, 23 Nov 1998 00:03:47 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith CC: Mike , freebsd-current@FreeBSD.ORG Subject: Re: Problems with this network card / driver? References: <199811222110.NAA13433@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Hi guys... using 3.0 release on 2 servers....3.0 reports this particular > > card like this on boot > > > > lnc1: rev 0x25 int a irq 14 on pci1.5.0 > > lnc1: PCnet-FAST address 00:60:94:57:4c:f2 > > Yeah. The lnc driver is pretty marginal at the moment. I'd avoid it > if at all possilble. I ran some tests at the local IBM evaluation lab > and I wasn't too happy with the onboard ethernet. Try an Intel > EtherExpress Pro/100B instead if you're really concerned. Hello, Just for the record, I've set up a pretty ancient (but working well) 486DX2 - 66 from HP with an on-board Lnc NIC, and I've got lots of these errors (on a busy net). But the box is running happily. TfH > > > In any case should I be concerned at all? Like I said the machine hums > > along perfectly but being the paranoid little guy that I am, I want to know > > all the details before they > > reach up and bite me on the ass. > > If it's working OK, then it'll probably continue to work just fine. > It's quite likely that the BSD/OS driver just doesn't bother to report > this error (which seems to indicate a very busy ethernet). > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message