Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!cs.utexas.edu!uwm.edu!caen!hellgate.utah.edu!cc.usu.edu!ivie From: ivie@cc.usu.edu Newsgroups: comp.os.386bsd.questions Subject: Re: Devices, we0, and WD8013EP ethernet card Message-ID: <1993May9.135900.67517@cc.usu.edu> Date: 9 May 93 13:59:00 MDT References: <1993May7.142133@orac.crissp.qut.edu.au> Organization: Utah State University Lines: 35 In article <1993May7.142133@orac.crissp.qut.edu.au>, reilly@orac.crissp.qut.edu.au (Andrew Reilly) writes: > 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. I'm using some flavor of soft-configured WD8003 (mine only has one jumper) and I haven't had any problems at all. A friend is using an NE2000 clone and also had slow Ethernet. He was able to fix it by changing TCP_MAXWIN from 65535(?) to 1024 (don't know what file it's in, sorry; my NetBSD machine is at the office). > > From the next re-boot to the present day, the system has not > recognized the existance of the ethernet card at all. I would probably go back to the SOFT,NONE configuration since you did get the system to recognize that once and fiddle with TCP_MAXWIN. > > 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... In the file that defines the cdevsw[] and bdevsw[] arrays (conf.c?), the major device number is given by the index of the device driver into the array. Roger Ivie ivie@cc.usu.edu