Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!news.qut.edu.au!orac.crissp.qut.edu.au!reilly
From: reilly@orac.crissp.qut.edu.au (Andrew Reilly)
Subject: Devices, we0, and WD8013EP ethernet card
Message-ID: <1993May7.142133@orac.crissp.qut.edu.au>
Sender: news@news.qut.edu.au (USENET News System)
Reply-To: A.Reilly@qut.edu.au
Organization: Signal Processing Research Center, QUT, AUS
Date: Fri, 7 May 93 04:21:48 GMT
Lines: 75
Hello,
I would appreciate a pointer or two to relevant references, (or even a
solution or two?) if possible:
I have just installed NetBSD-0.8 on a 486DX-33 ISA bus machine with 4M
RAM, an 80M IDE disk drive (Connor Periphs.) an ET4000 VGA card, and
what I believe to be a Western Digital WD8013EP ethernet card. This
card has two sets of configuration jumpers across the top of the card,
labelled:
W1-CONFIG
I/O, IRQ, RAM
SOFT
280,3,D0000
300,10,CC000
W2-ROM ADDRESS
NONE/SOFT
D8000
all of which seems to be self explanatory (which is just as well,
because this card was scrounged from somewhere in the School, and I
don't have the documentation.)
The situation is this:
When I first installed NetBSD, my plan was to use FTP to retrieve all
of the parts for extraction. This seemed to be working, but the data
transfer rates were on the order of 0.8K bytes/sec. I.e., incredibly
slow. Pinging the machine from the server indicated that a very great
number of packets were being lost, and those that got through took a
very long time. At this stage the jumpers just mentioned were in the
SOFT,NONE positions. Oh, I thought. It's probably using some
fall--back, programmed IO, and doing it badly. The INSTALL guide
listed this card as wanting I/O,IRQ,RAM=280,2,D0000: i.e., different
from the options available on the jumpers.
So I finished the installation with floppies, which turned out to be
much faster and not much effort. I installed everything except the
non-kernel sources.
From the next re-boot to the present day, the system has not
recognized the existance of the ethernet card at all.
I thought: Just re-compile the kernel to look for the card at one of
the configurations that I can set the jumpers for. I did this
(several times -- for the different possibilities) and still the boot
sequence didn't recognize the card. That is the situation I am in at
the moment.
The questions:
Does anyone know what I have to do to the config file to use this
card?
Why doesn't the /dev/MAKEDEV script have a section to create /dev/we0?
Why doesn't /sys/i386/conf/devices (?) list a major device number for
we0, so that I could modify the MAKEDEV script?
Where would I find such a number? I'm new to device drivers...
Is this even relevant? (There aren't MAKEDEV options for any of the
other accepted ethernet devices, either, so maybe that's not the way
it works.)
Help?
Thanks in advance,
-- Andrew Reilly -- | A.Reilly@qut.edu.au |
Signal Processing Research Centre |
QUT, GPO 2434, Brisbane 4001, Australia. |
phone: +61 7 864 2124 | fax: +61 7 864 1516 |