Re: Still haven't resolved this. INITRD/RAMSIZE detect changes in 2.4

From: Mike Galbraith (mikeg@weiden.de)
Date: Sun Aug 27 2000 - 01:54:51 EST


On Sat, 26 Aug 2000, Michael Peddemors wrote:

> On Sat, 26 Aug 2000, you wrote:
>
> > It hasn't moved. Did you try the suggestion I sent you?
>
> Hmmm.. I might have missed a suggestion, the last one I got record of was the
> mem=31M which worked.. but that isn't an acceptable alternative for
> distribution.

(e820 reporting problem seems likely, and in setup.S there's this
little goodie..
   280 #ifndef STANDARD_MEMORY_BIOS_CALL
   281 movb %al, (E820NR)
..to help you verify that)

That's a suggestion to try defining STANDARD_MEMORY_BIOS_CALL ;-)
It may well be that your BIOS is buggy.

        -Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 21:00:18 EST