From: Randy Dunlap <rdunlap@infradead.org>
To: Long Wind <longwind2009@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: how to use memmap= option
Date: Thu, 30 Jan 2014 16:56:35 -0800 [thread overview]
Message-ID: <52EAF4C3.1040009@infradead.org> (raw)
In-Reply-To: <CAB-gxZAGL8TqvN+Jmc1vwEU+Vcos=FTWJ5No0tp-cDiJ4YPt3w@mail.gmail.com>
On 01/08/2014 06:06 AM, Long Wind wrote:
> On 1/8/14, Long Wind <longwind2009@gmail.com> wrote:
>> I have asked Debian users, they don't seem to know
>> kernel 2.4/2.6 fail to boot on my PC
>> probably because it can't detect my memory
>> so I have to tell kernel memory map
>>
>> the following is copied from kernel-parameters.txt:
>>
>> memmap=exactmap [KNL,X86] Enable setting of an exact
>> E820 memory map, as specified by the user.
>> Such memmap=exactmap lines can be constructed based on
>> BIOS output or other requirements. See the memmap=nn@ss
>> option description.
>>
>>
>>
>> Could you tell me how to construct memmap= lines?
>>
>
> Sorry, it seems that I have posted wrong list
> If you could tell me which list I should join, I will very appreciate
> I'm leaving the list
No, this is the correct mailing list for your question (or use
linux-mm@kvack.org).
First you obtain a listing of your computer's valid memory map,
either from Linux booting on it (maybe not so likely on your computer)
or maybe from BIOS SETUP.
With that information, you construct a kernel command line with multiple
memmap= options.
You can see an example of this here:
http://lkml.indiana.edu/hypermail/linux/kernel/0809.1/0664.html
Hope that helps you.
--
~Randy
prev parent reply other threads:[~2014-01-31 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 11:30 Long Wind
2014-01-08 14:06 ` Long Wind
2014-01-31 0:56 ` Randy Dunlap [this message]
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=52EAF4C3.1040009@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longwind2009@gmail.com \
/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
Powered by JetHome