RE: *FIXED* lilo append mem problem in 2.4.20

[rtilley <rtilley@vt.edu>]

>===== Original Message From Alan Cox <alan@lxorguk.ukuu.org.uk> =====
>On Sun, 2002-12-08 at 11:02, GertJan Spoelman wrote:
>>         append="mem=exactmap mem=640K@0 mem=319M@1M"
>> to get the kernel to see all the memory.
>> So probably you can get it working again with:
>>         append="mem=exactmap mem=640K@0 mem=1023M@1M"
>> Maybe you also could do directly: exactmap mem=1024M@0
>> or 1G@0, but I haven't tried that yet.
>> It seems the mem parameter now only can be used to limit the amount of 
memory
>> used by the kernel.
>
>Without exactmap yes (fixed in 2.4.19 I believe). Also on many compaqs
>you can set the OS in the BIOS to "unixware" and get sane results

append="mem=exactmap mem=640K@0 mem=1023M@1M" solved the memory issue in RH's 
latest kernel (2.4.18-18.7.xsmp) and in (2.4.20smp-ac1). However, ac1 only 
uses ~900MB whereas RH uses all of the RAM, but I think that's because I 
turned highmem of when building ac1.

This answers several questions that I had about RH's last two releases (7.3 & 
8.0). Neither release would install on this server, each would end with a "Not 
enough memory to install" right when beginning the installation. When I told 
the installer to do "linux mem=1024M" the install would progress a bit further 
before giving a kernel panic about being unable to mount the root filesystem.

I'm tempted to go back and try the above mentioned append to see if that will 
make one of the newer relesases install.

Thanks to all for the help.

Brad