Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.EDU.AU!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!news.sprintlink.net!news00.sunet.se!sunic!news99.sunet.se!newsfeed.tip.net!torget.bgnett.no!ugress.uib.no!nntp-trd.UNINETT.no!nntp-trd.UNINETT.no!due.unit.no!pvv.unit.no!arnej From: arnej@pvv.unit.no (Arne H. Juul) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: Need help with SMC8013EWC in Micron Millenia Plus under NetBSD 1.0 Date: 25 Oct 1995 14:16:25 GMT Organization: Norwegian Institute of Technology Lines: 40 Sender: arnej@boks.pvv.unit.no (Arne H. Juul) Message-ID: <46lgrp$6en@due.unit.no> References: <DGzpoz.MGz@news2.new-york.net> NNTP-Posting-Host: boks.pvv.unit.no In article <DGzpoz.MGz@news2.new-york.net>, "Steven M. Jones" <smj@Crash.COM> writes: |> But when I booted the newly installed system ed0 was useless - keeps spitting |> out "ed0: NIC memory corrupt - invalid packet length 0" messages. I've tried it |> with a rebuilt GENERICBT kernel, and with a custom built kernel with all the |> goodies like loadable kernel modules, and I still get these messages instead of |> carefree network utilization. I've seen similar problems reported on the mailing list, and then the following info was posted: > Date: Tue, 28 Mar 1995 14:26:06 -0500 > From: Alexandra Ellwood <aellwood@tetrahydrocannabinol.mit.edu> > Message-Id: <199503281926.OAA05911@tetrahydrocannabinol.mit.edu> > Subject: Re: SMC Elite16C Ultra Memory Corrupt? [problem description removed...] > Actually what's much more likely is a very strange conflict between > the floppy driver (fd) and the ed driver. If you are using a kernel > (like one of the boot floppy kernels) that has two floppy drivers > configured (fd0 and fd1) and you only have one floppy drive, then you > will receive that error on ifconfig. Must be something like the fd1 > driver grabs the ethernet card or something...very bizarre. > > The fix: either get another floppy drive or rebuild yourself a kernel > with only one floppy drive configured in it. Some people on this list > might also be able to build you a kernel. I bootstrapped with a > friend's floppy drive until I could build myself another kernel. > > (Yeah I know this sounds like a funky bug but I know of at least 2 > other people besides myself who've seen it). > > Alexandra Ellwood > (aellwood@mit.edu) I don't know whether this is still true, but it might be of help to you. Good luck, - Arne H. J.