mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Tim Connors <tconnors@astro.swin.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: small memory machine, large reserved memory
Date: Sun, 3 Nov 2002 18:15:09 -0800	[thread overview]
Message-ID: <20021104021509.GS23425@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0211041304010.16003-100000@hexane.ssi.swin.edu.au>

On Mon, Nov 04, 2002 at 01:10:36PM +1100, Tim Connors wrote:
> In light of the recent discussions about config_tiny, etc, I decided to
> install 2.4.19 on my old 8MB 486, to see whether it performed any better
> than my previous attempts with 2.2.* and 2.4.*
> The strange thing is, the memory init line at bootup (eg Memory:
> 255296k/261996k available (1584k kernel code, 5972k reserved, 1353k data
> , 108k init, 0k highmem)) says that only about 5 or 6MB are availabel,
> with a whopping 2.x MB reserved. I have done a web search, and the only
> answer I have come up with is that the top 384kb of the 1MB lower
> portion of RAM should be here, but what else could be eating up all my
> RAM?
> There is nothgin suspicious in the BIOS - all BIOS and video caching is
> turned off. The machine only (natually) has ISA slots in it, most are
> empty. What else could possibly be wrong?
> Is there something I can hack in the kernel to get it to use that, or can
> anyone give me pointers as to what else I can change? I would really love
> to regain that 2MB - its a pain when the shell gets swapped out after
> doing an `ls` :)

How does 2.5.44 (or 2.5.x-bk) do?


Bill

  reply	other threads:[~2002-11-04  2:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04  2:10 Tim Connors
2002-11-04  2:15 ` William Lee Irwin III [this message]
2002-11-08  3:21   ` Tim Connors
2002-12-01  9:07   ` Tim Connors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021104021509.GS23425@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tconnors@astro.swin.edu.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®