On Thu, 23 Jun 2011 10:18:55 -0700, Stefan Reinauer wrote:
Is it integrated into the payload? Reading the QEMU_Build_tutorial, http://www.coreboot.org/QEMU_Build_Tutorial,
$ qemu -bios build/coreboot.rom -hda /dev/zero -serial stdio
This resulted in something else entirely, the shell output
in the following:
coreboot memory table: 0. 0000000000000000-0000000000000fff: CONFIGURATION TABLES 1. 0000000000001000-000000000009ffff: RAM 2. 00000000000c0000-0000000017feffff: RAM 3. 0000000017ff0000-0000000017ffffff: CONFIGURATION TABLES 4. 00000000ff800000-00000000ffffffff: RESERVED Wrote coreboot table at: 17ff1400 - 17ff15c4 checksum 6c1c coreboot table: 452 bytes. Multiboot Information structure has been written. 0. FREE SPACE 17ff3400 0000cc00 1. GDT 17ff0200 00000200 2. IRQ TABLE 17ff0400 00001000 3. COREBOOT 17ff1400 00002000 Check CBFS header at fffcfc39 magic is 386f92fa ERROR: No valid CBFS header found! CBFS: Could not find file fallback/payload Boot failed.
You're now running coreboot, but coreboot was unable to find your payload (eg, SeaBIOS).
However, it seems the CBFS header is corrupted, so it is not even checking for a payload file.
Not sure why, on first sight.
ramstage was found successfully, so this might be a matter of chip mapping (or rather its emulation)