mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Terry" <tmacmill@rivernet.net>
To: "Douglas McNaught" <doug@mcnaught.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Incorrect RAM Detected at kernel init
Date: Mon, 22 Aug 2005 21:49:11 -0400	[thread overview]
Message-ID: <000401c5a784$dc23e9f0$6301a8c0@finian.net> (raw)
In-Reply-To: <m23bp11r38.fsf@Douglas-McNaughts-Powerbook.local>

I have not been able to get the memory hole turned off at the 16M mark
Going through some of the Documentation files, I noticed that I can specify 
a ram map with the mem boot option. I know the mem=768M hasn't worked, so 
what about trying the memory map option? Could that be a solution to my 
problem? If so, what would be the proper way to put the command?
As well I have downloaded the 2.4.18 kernel and in the latest distro of 
Slackware, 10.1, it doesn't want to compile, I can't remember the exact 
error, but it was referenced back to one of the asm headers as the problem. 
I will dig that error up and maybe post based on that to get that kernel 
running.
As well, going to a 2.6 kernel just in not overly feasable at this time as 
it takes 24 hrs to compile with the state the machine is in right now.

Terry
----- Original Message ----- 
From: "Douglas McNaught" <doug@mcnaught.org>
To: "Terry" <tmacmill@rivernet.net>
Cc: <linux-kernel@vger.kernel.org>
Sent: Monday, August 22, 2005 7:36 PM
Subject: Re: PROBLEM: Incorrect RAM Detected at kernel init


> "Terry" <tmacmill@rivernet.net> writes:
>
>> The kernel appears to compile perfectly, installs fine, but after reboot 
>> it
>> is only reporting 16M of RAM. I have tried with and without the mem=768M
>
> I've seen this happen with BIOSes of your vintage when there's a
> "memory hole at 16M" turned on--the kernel doesn't see anything beyond
> it.  See if you can get into the Setup program and turn that off.
>
> Since earlier kernels work, the later kernels are probably trusting
> the e820 tables which may not be set up properly...
>
> [Not that I know that much about this stuff]
>
> -Doug
>
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.338 / Virus Database: 267.10.13/78 - Release Date: 8/19/2005
>
> 



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.13/78 - Release Date: 8/19/2005


  reply	other threads:[~2005-08-23  1:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22  3:27 Terry
2005-08-22 23:36 ` Douglas McNaught
2005-08-23  1:49   ` Terry [this message]
2005-08-23 14:14 ` Lennart Sorensen

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='000401c5a784$dc23e9f0$6301a8c0@finian.net' \
    --to=tmacmill@rivernet.net \
    --cc=doug@mcnaught.org \
    --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®