Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!usc!cs.utexas.edu!asuvax!chnews!ornews.intel.com!agora!davidg From: davidg@agora.rain.com (David Greenman) Subject: Re: ed0: device timeout, freebsd cslip Message-ID: <CEDCsE.FJ5@agora.rain.com> Organization: Open Communications Forum Date: Mon, 4 Oct 1993 10:50:36 GMT Lines: 30 plotkin@alumni.cs.Colorado.EDU (Leo Classic) writes: > I had the same problem with my D-Link DE100 (ne1000 clone) > 'running' FreeBSD EPSILON. (386/33DX. Gastropods can't run.) > > I suspect the problem was caused by an invalid shared memory > address for this card. I deleted the iomem 0xXXXXX from the > ed0 definition and re-compiled. Worked like a charm! The iomem parameter is ignored for NE1000/2000 boards. I suspect that instead the cause was a conflict with another driver (most likely the isolan driver, as we have seen this before), and you removed that from your kernel at the same time you made the other changes. The isolan driver's probe is invasive and will interfere with the 'ed' device. > Incidentally, I've seen a 3c503 which became unhappy when paired > with a 8900c video card in one cheap no name clone. 3com tech > support told me to disable shared memory and DMA, and it started > working. While this is possible, another more common conflict is that many VGA boards use irq 2 (9) and this often conflicts with ethernet devices that are set to use this interrupt. Since the 3c503 only allows the use of irq 2-5, and irq 3 & 4 are usually COM1 and COM2...this only leaves 2 & 5, so there's lots of chance that the card is set to 2/9 and thus lots of chance that it will conflict with a VGA board. The solution to this problem is to either reassign the 3c503 to use irq 5 or to disable the VGA board's use of irq 2/9 (which isn't needed in *BSD). -DG