Yes your right.. some of the award bios chipsets have that setting you
refer to. I have seen it on almost all clone type BX chipsets. And had
similar issues previously as to the one explained. Try the bios thing, if
that fails last resort the lilo append command.
I found I had core dumps when using the lilo append command, and without
doing the bios setting. Once I changed it all around and removed the
append command the system worked fine in question and no core dumps. Plus
it detected all the memory on its own :)
On Tue, 31 Oct 2000, chesty wrote:
> On Tue, Oct 31, 2000 at 04:33:30PM +0800, Dion Curchin wrote:
> > Hi there,
> > I'm having some problems with a Mandrake 7.2 beta...it fails to
> > detect my 256 MB of ram. Instead in decides I have only 16 and consequently
> > my smp machine runs like a dog, KDE is impossibly slow to initialise. I've
> > looked through a number of books and docs and not found anything meaningful.
> > Are there any boot commands I can give at startup to tell my machine that I
> > have a specific amount of ram or whatever??
>
> I vaguely remember that if you have some memory hole setting in the bios
> turned on, this can happen.
>
> This happened to me on an old compaq server but I couldn't find any
> memory hole settings, still, its worth checking anyway.
>
> Otherwise the bootprompt howto has the answer,
> adding something like append = "mem=256m" to /etc/lilo.conf should do it.
>
> If you tell the kernel you have more memory than you really do it will crash,
> I've heard its safer to use the the number the bios reports when it boots,
> normally in kilobytes.
>
> --
> chesty
>
>
>
> --
> SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
> More Info: http://slug.org.au/lists/listinfo/slug
>
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
