Hallo, thanks for your answer. I had the coreboot-read.bin from the coreboot source "coreboot-v2-4475", it is just renamed (coreboot.rom). I used the target for IEI_JUKI_511P board because it is near the same as I have. I have two EEProm Chips ... it should be safe to test coreboot on this board. I changed the Config.lb, because I want to use seabios:
payload /root/coreboot/bios.bin.elf-0.4.1
And I had a problem with the Rom size. ... I changed this:
option CONFIG_COMPRESS=1
Then coreboot.rom compiled without an error. The next Step was to add the VGA bios. But it dosnt worked. Sorry for my bad english.
I had this problem too. I wonder: add vgabios.bin pci1078,0104.rom 0 ^ is that a letter "O" or a number "0". It looks like a zero.
I think it needs to be an o?
Sorry, I am running on memory here, and can't test it right now, can you verify that you are using the right "type" as the final argument?
ron
Hallo, thanks for your answer. I had the coreboot-read.bin from the coreboot source "coreboot-v2-4475", it is just renamed (coreboot.rom). I used the target for IEI_JUKI_511P board because it is near the same as I have.
Does this board have CBFS support? If it didn't, try this again with Patrick's patches. The error looks like cbfstool didn't find CBFS in your ROM image.
Thanks, Myles
On Sat, Aug 1, 2009 at 4:23 PM, Myles Watsonmylesgw@gmail.com wrote:
Hallo, thanks for your answer. I had the coreboot-read.bin from the coreboot source "coreboot-v2-4475", it is just renamed (coreboot.rom). I used the target for IEI_JUKI_511P board because it is near the same as I have.
Does this board have CBFS support? If it didn't, try this again with Patrick's patches. The error looks like cbfstool didn't find CBFS in your ROM image.
yes, what was I thinking? Do what Myles said :-)
The one test worth always making cbfstool <filename> print That can tell you right away what's going on.
ron