On Sat, 23 Dec 2000, Dave Kempe wrote:
Linux doesn't seem to be detecting all my RAM now.
It only detects 64MB of 128MB, im running Debian with 2.2.18
woody with it only recently installed.
The bios counts up the RAM fine, and windows detects it fine.
Top only reports 64mb available.
I've
On Monday 25 December 2000 11:24, Stephen Robert Norris wrote:
I'd be surprised if either of them worked, as they are wrong!
append="mem=128MB"
does, though.
worked great for me
thanks for everyone who contributed.
dave
--
SLUG - Sydney Linux User Group Mailing List -
Hey sluggers,
Happy christmas :)
Linux doesn't seem to be detecting all my RAM now.
It only detects 64MB of 128MB, im running Debian with 2.2.18
woody with it only recently installed.
The bios counts up the RAM fine, and windows detects it fine.
Top only reports 64mb available.
I've dug around
December 2000 20:37
To: [EMAIL PROTECTED]
Subject: [SLUG] Not detecting all my RAM
Hey sluggers,
Happy christmas :)
Linux doesn't seem to be detecting all my RAM now.
It only detects 64MB of 128MB, im running Debian with 2.2.18
woody with it only recently installed.
The bios counts up the RAM fin
On Mon, Dec 25, 2000 at 10:39:07AM +1100, Bernhard Lüder wrote:
Hi,
Add a line to the lilo.conf
append="mem=131039232"
some will tell you these will also work, but I had no success:
append="mem=131039KB"
append="mem=131MB"
I'd be surprised if either of them worked, as they are
I guess this is not working because it uses 1024 bytes per KB and not
1000.
I have definitely got append="mem=128M" to work [Note: not MB and not 131]
I also believe that the value has to be adjusted downwards if your
graphics card steals memory from your RAM but I cannot confirm that.
--
mem just has to be equal to or less than how much physical
ram is in your system. One byte more and the kernel will crash
and burn.
Lilo counts ram in using 1024, so 128MB is correct.
cat /proc/meminfo gives me the same value as the ram check does.
my lilo.conf..
boot=/dev/hda
map=/boot/map
