Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!in2.uu.net!quack!quack.kfu.com!nsayer From: nsayer@quack.kfu.com (Nick Sayer) Subject: Problems with 2.1.0 lnc0 driver Message-ID: <nd0Krox@quack.kfu.com> Sender: news@quack.kfu.com (0000-News(0000)) Organization: The Duck Pond public unix, +1 408 249 9630, log in as guest. Date: Sun, 14 Jan 1996 18:57:06 UTC Lines: 22 I've kind of always had this problem to some degree, but I thought perhaps that it might improve in 2.1.0. It hasn't. I have a 486 VLB motherboard and an NE2100 clone. Whenever I start doing large scale I/O I get massive numbers of Receive overflow and transmit underflow errors. My best guess would be that I would have to fiddle with the BIOS chipset settings in some way so that the motherboard can keep up with the card. Am I right? I can't prove it, but I believe similar sorts of things happen under win95 (of course there are no diagnostics to help there). I thought getting a DMA based Ethernet card would be a better deal than a shared memory one. :-( (due to an unrelated problem, news is not working here at the moment, at least on the receive side, so please reply via e-mail and I will summarize what works, if anything. Thanks). -- Nick Sayer <nsayer@quack.kfu.com> | The token ring futility rule: N6QQQ @ N0ARY.#NORCAL.CA.USA.NOAM | Any effort spent avoiding network coll- +1 408 249 9630, log in as 'guest' | isions has a negative impact at best URL: http://www.kfu.com/~nsayer/ | equal to that of the collisions.