Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!uunet!in1.uu.net!news-out.communique.net!not-for-mail From: Jim King <jim@ase.telerate.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: lnc driver in 2.1.5R Date: Mon, 04 Nov 1996 09:01:45 -0600 Organization: Communique Inc. Lines: 16 Message-ID: <327E0559.608F@ase.telerate.com> NNTP-Posting-Host: ns.ase.telerate.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (WinNT; I) I just upgraded my main server from 2.1R to 2.1.5R. This PC has an on-board AMD 1500T Ethernet interface, which worked fine with the lnc network interface driver in 2.1R. Under 2.1.5R I get LOTS of messages like "Receive CRC error", "Missed packet -- no receive buffer", and "last message repeated XXXX times". It _seemed_ to be working OK, but I got nervous and stuck in an NE2000. This is an ISA PC with 32 MB RAM. Could this be a problem with bounce buffers (or lack of them, as a quick scan of if_lnc.c doesn't seem to indicate that it uses them)? Did the lnc driver just get munged somehow in 2.1.5R? In case I have to make the NIC change permanent, what's the preferred ISA NIC these days? Jim