From owner-freebsd-current Mon Nov 23 12:29:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id MAA12287
for freebsd-current-outgoing; Mon, 23 Nov 1998 12:29:16 -0800 (PST)
(envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9])
by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12137
for <freebsd-current@FreeBSD.ORG>; Mon, 23 Nov 1998 12:28:55 -0800 (PST)
(envelope-from paul@originative.co.uk)
Received: by OCTOPUS with Internet Mail Service (5.5.1960.3)
id <XPD5RPCZ>; Mon, 23 Nov 1998 20:27:59 -0000
Message-ID: <E40CBF0361C7D111914000C0F0303D1087EE@OCTOPUS>
From: Paul Richards <paul@originative.co.uk>
To: "'Mike Smith'" <mike@smith.net.au>, Mike <mgrommet@insolwwb.net>
Cc: freebsd-current@FreeBSD.ORG
Subject: RE: Problems with this network card / driver?
Date: Mon, 23 Nov 1998 20:27:58 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
> -----Original Message-----
> From: Mike Smith [mailto:mike@smith.net.au]
> Sent: Sunday, November 22, 1998 9:11 PM
> To: Mike
> Cc: freebsd-current@FreeBSD.ORG
> Subject: Re: Problems with this network card / driver?
>
>
> > Hi guys... using 3.0 release on 2 servers....3.0 reports
> this particular
> > card like this on boot
> >
> > lnc1: <PCNet/PCI Ethernet adapter> 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.
Have you any specific details on why you think it's not working? It
seems there's a bug been introduced recently relating to detecting cards
that I'll look into but I'm not aware of any other problems with the
driver that would make it necessary to avoid using it.
In any case, I'm going to give the code an overhaul soon since I haven't
looked at it for a few years so if you or anyone else has been having
problems with this driver then now's the time to let me know :-)
> > 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).
This particular error report is perfectly normal and indicates a
saturated network (assuming there aren't any bugs). It's true that one
criticism that can be thrown at lnc is that it reports errors where many
cards do not. I still claim that this is a good thing :-)
Paul Richards Ph.D.
Originative Solutions Ltd
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message