[coreboot] YABEL full debug problems

Joseph Smith joe at settoplinux.org
Fri Feb 19 19:06:28 CET 2010

On Fri, 19 Feb 2010 18:16:33 +0100, Stefan Reinauer <stepan at coresystems.de>
> On 2/19/10 4:42 PM, Joseph Smith wrote:
>> Hello,
>> I am currently having an issue with a vga bios. I am trying to find the
>> source of the issue using YABEL's awsome full debug feature (0x31ff).
>> problem is I think YABEL may be broken. I can't seem to get past copying
>> the rom. Can someone please test YABEL in full debug(0x31ff), so we can
>> figure out if indeed YABEL is broken or if it is just me?
>> Note: this same vga bios works fine with Real_Mode.
>> Starting Graphics Initialization
>> Check CBFS header at fffeffe0
>> magic is 4f524243
>> Found CBFS header at fffeffe0
>> Check fallback/coreboot_ram
>> CBFS: follow chain: fff80000 + 38 + c80e + align -> fff8c880
>> Check pci8086,3577.rom
>> In cbfs, rom address for PCI: 00:02.0 = fff8c8b8
>> PCI Expansion ROM, signature 0xaa55, INIT size 0x10000, data ptr 0x0040
>> PCI ROM Image, Vendor 8086, Device 3577,
>> PCI ROM Image,  Class Code 030000, Code Type 00
>> copying VGA ROM Image from fff8c8b8 to 0xc0000, 0x10000 bytes
>> <------Locks up here----------->
> You did also enable "CONFIG_DEBUG", did you?
Hmm, I will have to check that. Is that in Kconfig yet? Or do I have to go
and manually enable it?

Joseph Smith

More information about the coreboot mailing list