[coreboot] Gigabyte M57SLI - 4MB Chip - LAB doesn't boot like expected
bari at onelabs.com
Tue May 27 00:29:36 CEST 2008
Harald Gutmann wrote:
> Am Samstag, 24. Mai 2008 20:46:49 schrieb Carl-Daniel Hailfinger:
>> On 24.05.2008 19:31, Harald Gutmann wrote:
>>> Am Samstag, 24. Mai 2008 19:14:59 schrieb Carl-Daniel Hailfinger:
>>>> On 24.05.2008 17:34, Harald Gutmann wrote:
>>>>> how can i check if the payload is corrupt or not?
>>>>> the uncompressed payload, the compressed one and an manually
>>>>> uncompressed ( lzma-utils from http://tukaani.org/lzma/) are included
>>>>> here: http://rapidshare.com/files/117291876/payloads.tar.bz2.html
>>>> Don't use the tukaani.org lzma-utils. They have a different header
>>>> format and our decompression will choke on it.
>>> I just used the utils to decompress the compressed payload, and diffed it
>>> against the uncompressed which is generated from buildrom-devel.
>>> I didn't use those tools to create a coreboot rom file, i just used
>>> buildrom-devel and did the changes which i posted in the start-mail of
>>> that thread.
>> Very strange. Can you try the compressed payload I uploaded to
>> http://rapidshare.de/files/39510268/lab-payload.elf.correctlzma.html and
>> report back?
> I tried it now to build an image with the playload from the link, but it has
> the same problem than i've with my coreboot.rom file.
> LZMA Error on booting and the scratchpad-size reported with your previous
> patch is also the same like with the original rom-file from me.
> Thanks anyway.
> Is it possible to flash an rom-file with lower file-size than the chip has,
> and to boot from it? As this would work i'd try to generate a rom-file with 1
> or 2MB. My "problem" is, that i've just an 512kB Chip, and the 4MB one, and
> on 512kB there is too less space for LAB or linux as payload.
I've been using buildrom for the kernel+ initrd along with coreboot V2
to build coreboot + LAB rom images without any issues.
Be sure to use the compressed elf lzma payload that buildrom generates
lab-payload.elf.lzma found in the deploy/ directory.
Your Options.lb in your targets/../... directory have to set properly as
well. It is a bit confusing since the docs are not clear.
Below is what I have been using successfully:
## set option rom size for LAB without BOCHS or vgabios
### Compute the location and size of where this firmware image
### (coreboot plus bootloader) will live in the boot rom chip.
## coreboot C code runs at this location in RAM
### Compute the start location and size size of
### The coreboot bootloader.
# option ROM_IMAGE_SIZE=0x20000
# payload $(HOME)/filo-0.5/filo.elf
# payload $(HOME)/payloads/memtest
buildrom ./coreboot.rom ROM_SIZE "fallback"
More information about the coreboot