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
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz
label=linux
root=/dev/hda1
vga = normal
read-only
append="mem=128M"
Im using a k6/2 450 on a gigabyte board. This is the only
system ive had to use the mem=xxx append.
I wouldnt get heaps stressed over a few k of ram.
remember that you can experiemnt at the lilo prompt
lilo: linux mem=XXXM
youll see lots of kernel crashes but dont worry, nothing
has been mounted to be damaged.
Dean
Howard Lowndes wrote:
>
> 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.
>
> --
> Howard.
> ____________________________________________________
> LANNet Computing Associates <http://lannetlinux.com>
> "...well, it worked before _you_ touched it!"
>
> On Mon, 25 Dec 2000, 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"
>
> --
> SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
> More Info: http://slug.org.au/lists/listinfo/slug
--
BONG: http://www.bong.com.au
EMAIL...
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
ICQ: 16867613
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
