From: Jan Knutar <jk-lkml@sci.fi>
To: linux-kernel@vger.kernel.org
Subject: mem= parameter, 2.4.18 vs 2.4.24
Date: Tue, 17 Feb 2004 19:08:59 +0200 [thread overview]
Message-ID: <200402171908.27583.jk-lkml@sci.fi> (raw)
Just upgraded an old computer from 2.4.18 to 2.4.24. The system has 24M
ram, but the bios reports only 16.
Discovered that mem=24M doesn't let Linux use all of it, like in 2.4.18,
only 16M in 2.4.24.
mem=8M@16M has the desired result, making the whole incredibly large 24M
ram available :-)
RTFSing leads me to believe that mem=xxxM can only limit ram size, but
Documentation/memory.txt and Documentation/kernel-parameters.txt make
me think ram=24M should work like it did in 2.4.18. I'm guessing
nobody updated the documentation? :)
reply other threads:[~2004-02-17 23:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200402171908.27583.jk-lkml@sci.fi \
--to=jk-lkml@sci.fi \
--cc=linux-kernel@vger.kernel.org \
/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