Re: mem=64MB oh yes! mem=128MB oh no! (2.0.34pre16)

Damacus Porteng (kernel@damacus.dyn.ml.org)
Fri, 22 May 1998 02:36:15 -0500 (CDT)

I had the same problem when I upgraded RAM from 16M to 80M. The solution
is simply appending mem=~1 MB less than what you have (For instance, I
have append=79M). I believe this is because the system may be using some
of the memory for shadowing, cacheing and whatnot.

-Damacus

On Fri, 22 May 1998, Lluisma wrote:

> I have a Dual PPro with 128MB of memory, 4.1 GB HDD on an Adaptec 2940 controller.
>
> After installing Red Hat Linux 5.0 last night, I got a copy of the 2.0.34pre16 patch, applied it, uncomment the line SMP=1, compiled a new kernel, made LILO use the new image, and rebooted. Everything went fine but I forgot to specify that I have 128MB of memory.
>
> So I modified my lilo.conf with an append statement. Sad to say when I rebooted my machine, I got a kernel panic. It says it can't mount the root fs. I booted from a floppy, removed the append statement in my lilo.conf and run /sbin/lilo. Again, I rebooted my machine, this time I specified mem=128MB in the LILO boot prompt. It encountered the same problem.
>
> I restarted the machine. Didn't specify anything at the boot prompt. Everything went fine but the kernel only detects 64MB of RAM. Am I missing something here? Is there a problem somewhere else?
>
> Joseph Edcel R. Lluisma
> jrl@curricula.net
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu