2.4.19 and sparse e820 map

Ronald G. Minnich rminnich at lanl.gov
Wed Dec 4 23:41:01 CET 2002


The first problem is this:
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 0000000000000bcc (reserved)
 BIOS-e820: 0000000000000bcc - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 00000000000f0400 (reserved)
 BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
 BIOS-e820: 0000000100000000 - 0000000120000000 (usable)
3712MB HIGHMEM available.
896MB LOWMEM available.

those MEM numbers are quite bogus. The second problem is that it can't 
find the initrd in the image. On a good load the initrd is at 2000a000 
i.e. 512MB+some, and that puts it on this mem right at memory that doesn't 
exist. 

I think it is getting confused early in the game and ending up with an 
initrd somewhere bogus.

ron




More information about the coreboot mailing list