That would be great. Either option is fine by me. Here is a little more
info on the system I am testing on. Grub from a running kernel:
GRUB version 0.5.95 (640K lower / 3072K upper memory)
grub> displaymem
EISA Memory BIOS Interface is present
Address Map BIOS Interface is present
Lower memory: 640K, Upper memory (to first chipset hole): 3072K
[Address Range Descriptor entries immediately follow (values are
64-bit)]
Usable RAM: Base Address: 0x0 X 4GB + 0x0,
Length: 0 X 4GB + 655360 bytes
Reserved: Base Address: 0x0 X 4GB + 0xa0000,
Length: 0 X 4GB + 393216 bytes
Usable RAM: Base Address: 0x0 X 4GB + 0x100000,
Length: 0 X 4GB + 3145728 bytes
and the 2.4.0 kernel:
[root@7000m10 /root]# cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 973062144 696074240 276987904 0 548122624 39321600
Swap: 0 0 0
MemTotal: 5144560 kB
MemFree: 4464800 kB
MemShared: 0 kB
Buffers: 535276 kB
Cached: 38400 kB
HighTotal: 4325328 kB
HighFree: 4270712 kB
LowTotal: 819232 kB
LowFree: 194088 kB
SwapTotal: 0 kB
SwapFree: 0 kB
of course grub at boot time gives totally different "displaymem" output,
but I don't have a way to log that one at present. That one does show
much more memory. Thoughts on how to log this? Is serial console working
for this? I could dig up a null modem and log from there I suppose.
OKUJI Yoshinori wrote:
>
> From: Tim Riker <[EMAIL PROTECTED]>
> Subject: Re: prepare_0_5_95
> Date: Fri, 16 Jun 2000 11:25:45 -0600
>
> > 2.5: If a mem= option is found with no value, grub removes the option
> > and does not add another.
>
> I don't think that would be very intuitive. I prefer adding an
> option into the command "kernel" to messing around with arguments for
> Linux.
>
> Okuji
--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.
