All of lore.kernel.org
 help / color / mirror / Atom feed
From: GertJan Spoelman <kl@gjs.cc>
To: rtilley <rtilley@vt.edu>, linux-kernel@vger.kernel.org
Subject: Re: lilo append mem problem in 2.4.20
Date: Sun, 8 Dec 2002 12:02:32 +0100	[thread overview]
Message-ID: <200212081202.32754.kl@gjs.cc> (raw)
In-Reply-To: <3DFDE59F@zathras>

Hi Brad,

On Sunday 08 December 2002 04:28, rtilley wrote:
> Hello,
>
> Compaq proliant 5000 4 way Pentium Pro with 1 GB RAM only uses 12 to 13 MB
> of RAM when I use kernel 2.4.20 with ac1 patch even when I do
> append="mem=1024" in /etc/lilo.conf
>
> RH 7.2 is the distro and its default kernel (2.4.7-10smp), works flawlessly
> with the mem append, it sees and uses all the RAM. But, their latest kernel
> 2.4.18-18.7.xsmp fails to use the RAM as well; it too only sees 12 to 13
> MB... this is why I tried the kernel.org kernel.
>
> I used RH's 686-smp kernel config file to build the 2.4.20-ac1 kernel. I
> turned High Mem support off as I don't think 1 GB is high mem... is it?
> Anyone know how I can use all of the RAM?
>

I had the same problem on an old Compaq 2500 with 320Mb memory,
the following line used to work :
        append="mem=320M"
now I have to use:
        append="mem=exactmap mem=640K@0 mem=319M@1M"
to get the kernel to see all the memory.
So probably you can get it working again with:
        append="mem=exactmap mem=640K@0 mem=1023M@1M"
Maybe you also could do directly: exactmap mem=1024M@0
or 1G@0, but I haven't tried that yet.
It seems the mem parameter now only can be used to limit the amount of memory 
used by the kernel.
-- 

    GertJan

  parent reply	other threads:[~2002-12-08 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-08  3:28 lilo append mem problem in 2.4.20 rtilley
2002-12-08  8:06 ` Joseph D. Wagner
2002-12-08  9:20   ` Barry K. Nathan
2002-12-08  9:09 ` Zwane Mwaikambo
2002-12-08 11:02 ` GertJan Spoelman [this message]
2002-12-08 14:30   ` Alan Cox

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=200212081202.32754.kl@gjs.cc \
    --to=kl@gjs.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtilley@vt.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.