From owner-freebsd-questions Fri Oct 6 03:24:04 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA21531 for questions-outgoing; Fri, 6 Oct 1995 03:24:04 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA21526 for ; Fri, 6 Oct 1995 03:24:02 -0700 Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id DAA07421; Fri, 6 Oct 1995 03:23:49 -0700 From: Julian Elischer Message-Id: <199510061023.DAA07421@ref.tfs.com> Subject: Re: Help ! Problem with Ethernet card To: davidg@Root.COM Date: Fri, 6 Oct 1995 03:23:48 -0700 (PDT) Cc: armando_ferreira@il.us.swissbank.com, questions@freebsd.org In-Reply-To: <199510060947.CAA00286@corbin.Root.COM> from "David Greenman" at Oct 6, 95 02:47:39 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1467 Sender: owner-questions@freebsd.org Precedence: bulk > One thing I got bitten on recently.. some new PCs have an option in the BIOS "Shadow ram hole" (or similar) this must be set to ON and at the address of your card, otherwise these 'oversmart' PCs will map shadow ram over your card (which won't work) > >>I am having trouble installing a Western Digital card on my PC. > >> > >>The configuration I used in to configure the kernel was > >>device ed0 at isa? port 0x300 net irq 5 iomem 0xCA000 vector edintr > >> > >>I changed the jumpers on the card to match the above irq and memory address > >>configuration. and I get the following problem at boot time: > >>>>ed0: failed to clear shared memory at ca000 - check configuration<< > >> > >>Can you please tell me if there is something else to setup or if I have done > >>something wrong ? > > > > This usually indicates that there is another card in that shared memory > >area. Try the values 0xc8000, 0xd0000, and 0xd8000...and see if any of those > >will work for you. It's only necessary to change the kernel (no need to change > >the settings on the card for this). > > I just realized another thing: Do to the way that these cards are designed, > I think there might be a requirement that the shared memory address be on > 16K boundry - so you should use 0xc8000, 0xcc000, 0xd0000, 0xd4000, 0xd8000, > or 0xdc000. On some motherboards you might also be able to use addresses in > the 0xe0000-0xec000 range, but this often does't work. > > -DG >