From owner-freebsd-questions Tue Nov 26 6:28:37 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 166D537B401 for ; Tue, 26 Nov 2002 06:28:36 -0800 (PST) Received: from sage-one.net (adsl-65-71-135-137.dsl.crchtx.swbell.net [65.71.135.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id E83C743E9C for ; Tue, 26 Nov 2002 06:28:34 -0800 (PST) (envelope-from jackstone@sage-one.net) Received: from sagea (sagea [192.168.0.3]) by sage-one.net (8.11.6/8.11.6) with SMTP id gAQESWD39264; Tue, 26 Nov 2002 08:28:33 -0600 (CST) (envelope-from jackstone@sage-one.net) Message-Id: <3.0.5.32.20021126082832.010f3850@mail.sage-one.net> X-Sender: jackstone@mail.sage-one.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 26 Nov 2002 08:28:32 -0600 To: Lowell Gilbert , freebsd-questions@FreeBSD.ORG From: "Jack L. Stone" Subject: Re: FreeBSD detecting less than total memory In-Reply-To: <44vg2kh14e.fsf@be-well.ilk.org> References: <20021125025712.L23803-100000@alpha.yumyumyum.org> <20021125025712.L23803-100000@alpha.yumyumyum.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 09:11 AM 11.26.2002 -0500, Lowell Gilbert wrote: >Kenneth Culver writes: > >> Hi, >> I'm running FreeBSD 4.7-STABLE as of a couple of days ago... and >> it seems that FreeBSD is not detecting the total amount of ram that I have >> on my system. I have 512M but here's my dmesg (where memory is concerned: >> >> real memory = 402669568 (393232K bytes) >> Physical memory chunk(s): >> 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) >> 0x004ad000 - 0x17ffbfff, 397733888 bytes (97103 pages) >> avail memory = 386895872 (377828K bytes) >> >> This is much less than what is really available. /boot/loader detects the >> proper amount, but for some reason the kernel won't. Any ideas? > >Did you try telling it explicitly, as recommended in the FAQ? > If all else fails, try pulling the strip(s) and switching the slots. Then, if you have more than one strip, drop to 1 and add 1 back at a time. If one or more isn't seen, then the strip has probably gone bad. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message