1) The documentation specifically warns against blindly setting the mem
variable. If the bios is copied into main memory, or if main memory is
otherwise "adjusted" before the OS see it, this will be a problem.
2) I had to turn off the "memory hole" option on my MB in order to get past
16M. 64M is the limit for cache on many older motherboards. On some newer
ones, a BIOS option must be switched to get past 64M. I would think that
the memory would still be detected, though.
Nathan
> -----Original Message-----
> From: CaT [SMTP:cat@zip.com.au]
> Sent: Saturday, September 11, 1999 8:36 AM
> To: Mathias Wiklander
> Cc: kernel linux
> Subject: Re: Linux-2.2.9
>
> On Sat, Sep 11, 1999 at 01:17:50PM +0000, Mathias Wiklander wrote:
> > I have a problem with kernel 2.2.9 and just wanted
> > to report it. It dosen't find all my memory. I
> > have 96MB in it and i only detsct 64 of it. Is it
> > something you knew about?
>
> a. upgrade to 2.2.12. it wont solve the above problem but it's a safer
> kernel to use.
>
> b. put append="mem=96M" in lilo.conf under the appropriate image config.
> AFAIK your BIOS is a tad buggy.
>
> --
> CaT (cat@zip.com.au) URL:
> http://www.zip.com.au/dev/null
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/