Eddie,
Thanx for your info on your related problem. I've put it in my notes.
Linux is now recognizing the full amount of memory. Why, I'm not sure.
I ended up trying a few different minor changes of the append line,
running lilo after each change. None had any affect. So, I went back to
the original edited version 'append = "mem=384M"'. At this point, I was
thinking that maybe I had mis-read the amount of memory that the boot POST
had seen and checked. So, I did a reboot, and the resulting POST showed
all the memory. And for some reason, this time when Linux booted up, it
saw the correct amount.
Why now? What's changed? I don't know.
I'm curious about another thing. 'free' shows more than "384M":
total used free shared buffers cached
Mem: 396759040 346677248 50081792 88686592 195481600 88330240
OK, a thousand in computer hardware (binary) land is 1024, so that the
total is not 384MB is understandable, but just how accurate do you have to
be with the 'append' line in lilo.conf? And if Linux can find the true
amount of memory, why do we even have to have this append line when memory
is over 64MB?
Thank you all for your help on this matter.
- Martin J. Brown, Jr. -
- [EMAIL PROTECTED] -
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
