>> >It could be a bios thing. in lilo somewhere you need to put "append
>> >"mem=32"" or something like that. Look through the lilo man page and one
>> >of the HOW TOs for kernel options.
>> Thanks, I'll check that.
>I had the same problem. In the and it was the motherboard which did not
>accept more than 16 mb.
Watch your computer at boot. If you have the memory test
enabled in BIOS, you can usually see it running through the
RAM, and it tells you how much it sees.
If that says 16 even though you have more, check to see that
the SIMMs/DIMMs/whatever are seated correctly. 16 MB is a
pretty small limit for any motherboard. Also check for weird
jumpers; you never know what you might find. If none of that
works, then maybe your new memory's bad.
If it says your memory's all there, then add the line
(or use whatever number of MB you have instead of 32)
and--and this is what caught me--run the 'lilo' command while
logged in as root. Drove me nuts seeing four hundred posts
saying "use append..." but nobody saying "run lilo..."
However, it's my understanding that Linux autodetects
any memory up to 64 MB. So you shouldn't be having
this problem at all...
"If it wasn't a two-step process,
I wouldn't be in a twelve-step