Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!xlink.net!fauern!news.th-darmstadt.de!iti.informatik.th-darmstadt.de!deeken
From: deeken@iti.informatik.th-darmstadt.de (Hannes Deeken)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: ed0 driver (was Re: NFS Crash)
Date: 25 Aug 1993 18:12:04 +0200
Organization: TU Darmstadt, ITI
Lines: 46
Message-ID: <deeken.746294927@iti.informatik.th-darmstadt.de>
References: <wgSpAmS00iV2016idL@andrew.cmu.edu>
NNTP-Posting-Host: spock.iti.informatik.th-darmstadt.de
"Alex R.N. Wetmore" <aw2t+@andrew.cmu.edu> writes:
>Excerpts from netnews.comp.os.386bsd.bugs: 25-Aug-93 Re: NFS crash
>(NetBSD 0.9) by David Greenman@agora.rai
>> The new driver does work with the 3c503, and the performance and
>> reliability with it exceed the 'ec' driver. As far as the over-run's that
>> you are seeing are concerned, the 'ec' driver experiances these as well -
>> it just doesn't do anything about it, which can lead to board lock-ups
>> and other not-so-nice behavior. And regarding the d0000 default for ed0,
>> nothing prevents you from setting this to anything you like. I use cc000
>> myself so that I can switch between SMC 8013 boards and 3c503 boards
>> without rebuilding a different kernel.
>I had a lot of problems getting the ed0 driver setup with a 3c503 as
>well (using d0000, 250). I couldn't figure out how to configure the
>driver to use the aui port (instead of the thin port). It looked like a
>flags 0x01 in the config file would do it, but no such luck.
INSTALL_NOTES, lines 789 - 793:
> If you are using the AUI connector on a 3C503 card, you
> must also set the LLC0 flag (the default is to use the BNC
> connector):
>
> ifconfig ed0 130.252.23.86 llc0
[...]
>It did annoy me that the default NetBSD-0.9 kernel came with the ed0
>driver installed in a way that the 3c503 didn't support, because I
>needed networking to get the kernel source.
INSTALL_NOTES, lines 5 - 8:
> Be sure to read _ALL_ of this document before you try to
> install NetBSD/i386. NetBSD/i386 probably looks a bit similar
> to things that you've seen before (perhaps 386BSD), but the
> installation procedures are quite different.
I suppose _ALL_ includes the lines 789 to 793. ;-)
Ciao,
Hannes
--
Hans-Christoph Deeken | hannes@flinx.{RoBIN.de,hotb.sub.org} (home)
Gerauer Str. 20 | deeken@iti.informatik.th-darmstadt.de (university)
60528 Frankfurt/M | IRC: Glenlivet