From owner-freebsd-hardware Fri Jan 24 01:22:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA17074 for hardware-outgoing; Fri, 24 Jan 1997 01:22:01 -0800 (PST) Received: from mccomm.nl (root@gateppp.mccomm.nl [193.67.87.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA17069 for ; Fri, 24 Jan 1997 01:21:57 -0800 (PST) Received: from hpserver.mccomm.nl (hpserver.mccomm.nl [193.67.87.13]) by mccomm.nl (8.7.5/8.7.3) with SMTP id KAA05586 for ; Fri, 24 Jan 1997 10:20:05 +0100 Message-Id: <199701240920.KAA05586@mccomm.nl> Received: by hpserver.mccomm.nl (1.38.193.5/16.2) id AA26722; Fri, 24 Jan 1997 10:19:26 +0100 From: Rob Schofield Subject: Re: [Q] aah-2940uw To: freebsd-hardware@freebsd.org (Hardware list at FreeBSD) Date: Fri, 24 Jan 97 10:19:26 MET In-Reply-To: <199701232250.OAA17262@freefall.freebsd.org>; from "Jonathan M. Bresler" at Jan 23, 97 2:50 pm Mailer: Elm [revision: 70.85.2.1] Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > fixed that. nwo the aha-2940uw works well with the > st32550n. > > new problem.....the ethernet card, smc 8013ewc, does not work. > the error message is > > ed0: failed to clear shared memory at cc000 - check configuration. > > the card is hard jumpered to irq 10, ioaddr 300, mem cc000. > worked great at that setting before i flashed the bios ;) > installed 2.2-alpha via the this ethernet card at those settings. Could be if you've blown the Flash with a new BIOS, that it whacked any on-board settings to defaults. I know my 1742 came configured for BIOS base address of CC000h, and I had to change it. It could be that your eth card has the same expectations as before, and your Disk controller is now arguing with it on it's home turf. I would check the BIOS base address for the AHA before suspecting the eth card. As for the comment regarding 8/16 bit controllers, this applies to systems using the 16-bit ISA bus, ie. all controllers in the Upper memory expansion range (640k-1024k) must have the same address resolution range, otherwise you get clashes between cards due to some cards improperly decoding 16-bit addresses and creating duplicate, "shadow" address ranges that could overlap. Rob -- Witticisms are hard to define on Monday mornings... schofiel@xs4all.nl http://www.xs4all.nl/~schofiel rschof@mccomm.nl