[coreboot] Gigabyte M57SLI - 4MB Chip - LAB doesn't boot like expected

Carl-Daniel Hailfinger c-d.hailfinger.devel.2006 at gmx.net
Tue May 27 00:11:44 CEST 2008


On 26.05.2008 23:32, 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.
>   

Thanks for testing.

> 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.
>   

I'll have to investigate that after LinuxTag. Most important would be a
runtime check for correct headers. The values you're seeing suggest a
possible problem with ROM mapping. I suspect it will go away if you use
an 1 MB image as described below.

> 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.
>   

Try creating a ROM file with 2 MB, then run
cat coreboot.rom coreboot.rom >final.rom
and flash final.rom. A ROM file with 1 MB would use the following:
cat coreboot.rom coreboot.rom coreboot.rom coreboot.rom >final.rom
That should work fine for the ROMsize!=flashsize problem.

Regards,
Carl-Daniel




More information about the coreboot mailing list