Project

General

Profile

Actions

Bug #300

open
WB

Error building coreboot for t440p

Bug #300: Error building coreboot for t440p

Added by wi be almost 5 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/17/2021
Due date:
% Done:

0%

Estimated time:
Affected versions:
Needs backport to:
Affected hardware:
Affected OS:

Description

GenFv: ERROR 3000: Invalid
the required fv image size 0x51e400 exceeds the set fv image size 0x3e0000

full error log:
https://termbin.com/t134

defconfig:
https://termbin.com/80qv

full config:
https://termbin.com/oovf

PM Updated by Paul Menzel almost 5 years ago Actions #1

This is a TianoCore issue. Please try a different payload as a workaround.

WB Updated by wi be almost 5 years ago Actions #2

~~
i have tried now selecting the tianocore edk2 build from coreboot.
which resulted in UefiPayloadPkgIa32x64.dsc not to be found in
./payloads/external/tianocore/tianocore/UefiPayloadPkg/.*

as soon as i reverted my configuration back to the original as stated above
the build worked.~~

it was a custom bootsplash img that exceeded the size limits

PM Updated by Paul Menzel almost 5 years ago Actions #3

How big is /tmp/build/t440p/splash/bootsplash.bmp?

WB Updated by wi be almost 5 years ago Actions #4

Paul Menzel wrote:

How big is /tmp/build/t440p/splash/bootsplash.bmp?

i am not sure, as i deleted it.

I managed to create a buildable splash image, as described in this
tutorial: https://www.garyhawkins.me.uk/custom-logo-on-uefi-boot-screen/

JW Updated by Jamal Wright almost 5 years ago Actions #5

You can make more space using ME cleaner. I left the FD unlocked and was able to flash an image that spans both chips. Maybe adding a bootsplash is what grew tianocore? My file was only 24kb.

The vendor bios will ignore the changed ME chip.

DK Updated by Daniel Kulesz over 4 years ago Actions #6

Did you try increasing the CBFS size? The default is pretty small and doesn't even fit GRUB.

I recommend trying to increase it to 0x2A0000 or 0x7A0000 and trying again.

Actions

Also available in: PDF Atom