From owner-freebsd-hardware Wed Dec 6 16:59:12 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA14504 for hardware-outgoing; Wed, 6 Dec 1995 16:59:12 -0800 (PST) Received: from super.super.org (super.super.org [192.31.192.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA14495 for ; Wed, 6 Dec 1995 16:59:08 -0800 (PST) Received: from gotham.super.org (gotham [192.239.79.2]) by super.super.org (8.7.1/8.6.12.1) with ESMTP id TAA19404; Wed, 6 Dec 1995 19:54:36 -0500 (EST) Received: from descartes.super.org (descartes [192.239.79.5]) by gotham.super.org (8.6.12/8.6.12.1) with ESMTP id TAA29449; Wed, 6 Dec 1995 19:57:35 -0500 Received: (waarbau@localhost) by descartes.super.org (8.6.12/8.6.12.client) id TAA20809; Wed, 6 Dec 1995 19:57:35 -0500 Date: Wed, 6 Dec 1995 19:57:33 -0500 (EST) From: "William A. Arbaugh" To: Kevin Martin cc: freebsd-hardware@FreeBSD.org Subject: Re: >16Mb on ISA/EISA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.org Precedence: bulk On Tue, 5 Dec 1995, Kevin Martin wrote: > > I checked the archives, but was unable to find an answer to this question, > although it's been posed before in one form or another: > > I have a 486 with 28Mb of RAM (don't ask me why so much). When I installed > a recent snapshot (just before the release), FreeBSD would only recognize > 16Mb of that RAM. > > What, if anything, can I do to get the additional RAM recognized and used? > This is an HP Vectra, EISA bus I believe. > The problem is likely that the BIOS on your machine will only advertise 16MB because of the OLD AT bus limitation. My Dell EISA machines have the same problem. In several discussions with Dell, their position was to bad....the IBM spec is gospel and we won't change. The blasted BIOS even changes the value to 16M if I try and make it higher (I even tried to slam the value in with some of the BIOS write programs out there- no luck. The next time I booted the BIOS said hmmm 32M isn't right changing to 16M.) So here's what I did: I just modified the var biosextmem in the kernel (I can't remember the exact file name) to the appropriate number, and then remade the kernel. Ideally, the kernel should, if on an EISA machine, probe the EISA BIOS for the right value. I wasn't able to find where that was though. bill ---------------------------------------------------------------- Bill Arbaugh "Waste of time is the most waarbau@super.org extravagant of all expenses" waa@dsl.cis.upenn.edu -Theophrastus ----------------------------------------------------------------