Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!news.ksu.ksu.edu!lazrus.cca.rockwell.com!cacd.rockwell.com!news-feed-1.peachnet.edu!gatech!news.mathworks.com!newsxfer.itd.umich.edu!news2.acs.oakland.edu!news1.cris.com!jaguar.cris.com!not-for-mail From: rbeer@jaguar.cris.com () Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Problems with 2.1.0 lnc0 driver Date: 16 Jan 1996 17:39:25 GMT Organization: Concentric Internet Services Lines: 23 Message-ID: <4dgnsd$hck@spectator.cris.com> References: <nd0Krox@quack.kfu.com> NNTP-Posting-Host: jaguar.cris.com X-Newsreader: TIN [UNIX 1.3 950824BETA PL0] In article <nd0Krox@quack.kfu.com> you wrote: : 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 Although I get different errors, my lnc0 also reports strange (possibly invalid?) error conditions. I have an onboard lnc0 type of networking device on an AST Premmia GX P/90 system. My logs are full of the following lnc0 related error conditions: "lnc0: Framming error" "lnc0: Transmit of packet failed after 16 attempts -- TDX = 'x'" "lnc0: Receive CRC error" And so on. To my knowledge, my network connection is extremely clean, too - this all seems to have popped up at a certain point in 2.1.0-STABLE and has lasted through to 2.1.0-RELEASE. R Beerman -- PGP encrypted mail preferred. Finger rbeer@jaguar.cris.com for public key.