lkml.org 
[lkml]   [1998]   [Jul]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectMemory: 2.0.30 Can but 2.0.32 Can't?
Hi,

I'm running RH5.0 on a PCI machine with 96MB of memory. I also have a spare 1G
partition that I use just to play on, and I've discovered something.

When I install RH5.0 (kernel 2.0.32), it only recognizes up to 64MB as is widely
"known". However, when I install RH4.2 (kernel 2.0.30) it recognizes MORE than
64MB (something a little less than 96MB, due to ROM shadowing). This is not due
to a lilo "mem=" option. In fact, on the very first boot of the newly installed
RH4.2 - before I've changed anything - both 'free' and 'top' show memory just
shy of 96MB. To me, this seems rather convincing that the kernel *can* recognize
more than 64MB (at least from a PCI bios).

So the obvious question is "Why?" I've done a little digging and I suspect that
this behavior might be related to changes in the kernel to bios32.c or something
that calls it. But this is my first look at the kernel source, so I'm hoping
someone more knowledgable than me can supply some insight or perhaps know exactly
where the problem lies.

Someone has already suggested to me that it is probably a custom Redhat kernel
but I'm skeptical that Redhat is customizing the kernel.

Steve


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

\
 
 \ /
  Last update: 2005-03-22 13:43    [W:0.048 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site