> On Wed, 29 Apr 1998, Alan Cox wrote:
>
[snip]
> that's weird, but i solved this problem with setting 127M instead. As i
> was told, and as i suspect now, just the missed part, perhaps is used by
> BIOS or something, b/c if memory had corrupted, 1MB hardly could solve the
> problem, plus i didn't have any "XXX memory hole" messages.
> Well, thanks for the hints, and sorry for bother...
>
Recently I read that sometimes the last 384KB are not available to the system
thus causing oddities when setting the memory to 128MB. Try setting the memory
to 130688KB instead of 131072KB (128MB).
My .02
Nils
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Nils Philippsen @college: nils@rhlx01.rz.fht-esslingen.de Vogelsangstrasse 115 @home: nils@wombat.dialup.fht-esslingen.de D 70197 Stuttgart phone: +49-711-6599405 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Wer heute an der Bildung spart, Those who scrimp on education today, hat morgen noch bloedere Politiker. get even dumber politicians tomorrow.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu