Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!decwrl!elroy.jpl.nasa.gov!ames!agate!dog.ee.lbl.gov!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 386BSD new user questions
Message-ID: <1992Oct8.012759.16861@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
References: <1992Oct5.151326.13126@hpcvmcdj.cv.hp.com> <1992Oct7.154113.3611@hpcvmcdj.cv.hp.com>
Date: Thu, 8 Oct 92 01:27:59 GMT
Lines: 50
In article <1992Oct7.154113.3611@hpcvmcdj.cv.hp.com> carlj@hpcvmcdj.cv.hp.com (Carl Johnson) writes:
>A couple days ago I asked for help getting my WD8003 card working. I
>now have it working, so I am posting the results, in case others have
>a similar problem.
>
>My lan would hang when I tried to make a connection to another machine,
>and any incoming packets would give a 'reject 65531' message. Peter
>Cooper suggested by email that there might be a conflict in the kernel
>with one of the other lan card drivers. I removed the other lan card
>drivers from the configuration and then re-configured the kernel, and
>now the lan works fine.
Kernels with some (not all and certainly not Beta level) patches are on
agate and have been there for some time. They are basically replacement
dist.fs disks. One of the "fixes" incorporated is leaving out either the
isolan or wd80x3 driver, respectively.
Whenever you have a problem with booting, you should strip the hardware
and try again. If this fails, either start building boot disks (if you
have more than one machine, and one of them works) or start downloading
dist.fs images from agate and elsewhere (the machine "rachel" in the UK,
which I can never get to, has or will have fully patched kernels on
dist.fs disk images, ready for download; Adrian Hall, who posts here,
runs the 386BSD archive there).
The problem is basically that PC hardware is too stupid to autoconfigure
it's hardware if it's on an ISA bus or an EISA bus pretending it's ISA.
The ethernet drivers generally "probe" on the basis of making sure the
memory address is there, and then (most of the time) checksumming the
ROMs... thus they can find things which aren't there. Since most of the
ethernet drivers camp on IRQ 2, this means only one of them is going to
be able to handle the interrupts. This is generally the last board that
is "found" to be installed.
Once you are set up to rebuild the kernel, do it, removing all drivers for
devices not in your machine. This will reduce the chances for future
conflicts, as well as taking care of most existing ones.
Terry Lambert
terry@icarus.weber.edu
terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------