From owner-freebsd-alpha Wed Dec 5 14: 2:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 21CDA37B416 for ; Wed, 5 Dec 2001 14:02:44 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA19477; Wed, 5 Dec 2001 17:02:38 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id fB5M2DG47605; Wed, 5 Dec 2001 17:02:13 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15374.39269.403872.837182@grasshopper.cs.duke.edu> Date: Wed, 5 Dec 2001 17:02:13 -0500 (EST) To: "Koster, K.J." Cc: "'freebsd-alpha@freebsd.org'" Subject: RE: as2100 saga continues: memory trouble? *sigh* In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FDA180@l04.research.kpn.com> References: <59063B5B4D98D311BC0D0001FA7E452205FDA180@l04.research.kpn.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Koster, K.J. writes: > > Suppose that I know the bad memory range, any way of telling FreeBSD not to > use it? Perhaps abuse the option ROM device to claim that memory range for > itself? I have another idea.. install from Wilko's mininst CDROM. Alpha now (after 4.4-RELEASE) has support for setting hw.physmem to limit the amount of memory freebsd uses (settable from the boot loader). Try setting it to 32M & see if you make it through the install. If 32M are bad, the odds are good they're not in the 32MB you're going to use.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message