From: "Casey Allen Shobe" <cshobe@osss.net>
To: linux-kernel@vger.kernel.org
Subject: mem=options changed in 2.6.x?
Date: Wed, 31 Mar 2004 16:28:35 -0500 (EST) [thread overview]
Message-ID: <44574.64.25.5.177.1080768515.squirrel@webmail.thebrittinggroup.com> (raw)
I have a Compaq Proliant 5000 with 320Mb RAM.
If I boot up either linux 2.4.22 or 2.6.4, it only identifies 12Mb of memory.
With 2.4.22, the kernel parameters "mem=exactmap mem=640k@0M mem=319M@1M"
worked to make the kernel identify all of the memory.
I have tried the same with linux 2.6.4, but with the above flags the
kernel will not boot. With "mem=320M", the system boots, but it still
thinks it has only 12Mb RAM.
Something I'm missing or did this change between releases?
Thanks in advance,
--
Casey Allen Shobe
Open Source Software Solutions
cshobe@osss.net
next reply other threads:[~2004-03-31 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 21:28 Casey Allen Shobe [this message]
2004-03-31 21:42 ` Randy.Dunlap
2004-03-31 21:56 ` mem=options changed in 2.6.x? (resolved) Casey Allen Shobe
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=44574.64.25.5.177.1080768515.squirrel@webmail.thebrittinggroup.com \
--to=cshobe@osss.net \
--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
all inboxes | Powered by JetHome®