Re: PROBLEM: Incorrect RAM Detected at kernel init

[Terry]

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@xxxxxxxxxxxx>
To: "Terry" <tmacmill@xxxxxxxxxxxx>
Cc: <linux-kernel@xxxxxxxxxxxxxxx>
Sent: Monday, August 22, 2005 7:36 PM
Subject: Re: PROBLEM: Incorrect RAM Detected at kernel init


> "Terry" <tmacmill@xxxxxxxxxxxx> 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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/