Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!ira.uka.de!math.fu-berlin.de!cs.tu-berlin.de!lunde From: lunde@cs.tu-berlin.de (Lars Grupe) Newsgroups: comp.os.386bsd.questions Subject: Re: Devices, we0, and WD8013EP ethernet card Date: 9 May 1993 02:30:29 GMT Organization: Technical University of Berlin, Germany Lines: 103 Message-ID: <1shqc5$dqm@news.cs.tu-berlin.de> References: <1993May7.142133@orac.crissp.qut.edu.au> NNTP-Posting-Host: troll.cs.tu-berlin.de Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit reilly@orac.crissp.qut.edu.au (Andrew Reilly) writes: >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 | I am using NETBSD 0.8 with an SMC Elite 16 card which is Western Digital compatible. It has exactly the same jumpers as your card. On my site NETBSD created the device we0 automatically. If you miss it I could give you the major/minor number (I don't have it handy right now) but if you correctly install NETBSD you SHOULD have one. In the soft setting of jumper W1 you can configure the card with a program called ezsetup (DOS) supplied with your card. But you can also use on of the preconfigured alternatives. In either case you would have to reconfigure and recompile your kernel. The config file just need to be edited at the device we0 line. Change irq and io and base adress to your values. You should disable the other network devices. Hope that helps. -- ------------------------------------------------------------------------------- Lars Grupe UID lunde <lunde@cs.tu-berlin.de> Technische Universitaet Berlin -------------------------------------------------------------------------------