In seawolf, lilo.conf has 'append="mem=64M"', and I specified mem=96M at the LILO prompt. The kernel uses 64M instead. I suspect the issue is in the kernel's parsing of command line arguments... it's taking the first instead of the last. Interestingly, you do not get similar behavior for "init=" kernel boottime parameter.... lilo.conf: >> image=/boot/vmlinuz-2.4.2-2 >> label=linux >> read-only >> root=/dev/hda5 >> append="mem=64M" lilo prompt: LILO: linux mem=96M cat /proc/cmdline: BOOT_IMAGE=linux ro root=305 BOOT_FILE=/boot/vmlinuz-2.4.2-2 mem=64M mem=96M cat /proc/meminfo | head -4: >> total: used: free: shared: buffers: cached: >> Mem: 64151552 31064064 33087488 0 2748416 16683008 >> Swap: 139788288 0 139788288 >> MemTotal: 62648 kB
The kernel parses both and takes the smallest to be safe... Fix your lilo.conf ;) You should not need any mem= line with our kernel now anyway.