System Details
- Device: [fizz]
- OS: [Linux]
- Firmware Type: [UEFI Full ROM]
- Firmware Version: [04/06/2026]
- Internal storage type: [NVMe] (if applicable)
Summary of the Issue
###################################### [‘GenFv’, ‘-a’, ‘/home/user/coreboot/payloads/external/edk2/workspace/Build/UefiPayloadPkgX64/RELEASE_GCC/FV/Ffs/PLDFV.inf’, ‘-o’, ‘/home/user/coreboot/payloads/external/edk2/workspace/Build/UefiPayloadPkgX64/RELEASE_GCC/FV/PLDFV.Fv’, ‘-i’, ‘/home/user/coreboot/payloads/external/edk2/workspace/Build/UefiPayloadPkgX64/RELEASE_GCC/FV/PLDFV.inf’]
build.py…
: error 7000: Failed to generate FV
build.py…
: error 7000: Failed to execute command
- Failed -
Build end time: 00:16:51, Apr.11 2026
Build total time: 00:02:33
Failed!
make[1]: *** [Makefile:376: /home/user/coreboot/payloads/external/edk2/workspace/Build/UefiPayloadPkgX64/RELEASE_GCC/FV/UEFIPAYLOAD.fd] Error 1
make: *** [payloads/external/Makefile.mk:199：build/UEFIPAYLOAD.fd] Error 2
It was OK on 04/08/2026, but failed on 04/10/2026, when updated the repository using “git pull” command.
this isn’t useful to determine what failed, need the whole (verbose) log.
run:
build-uefi.sh fizz (eg)
then
V=1 make > build.log 2>&1
and upload the build log to pastebin or similar. also provide your host OS and build command run.
everyting builds fine here so this isn’t a repo issue
I’ve read the build.log, no errors found but the last few lines: fv image oversize！
Fd File Name:UEFIPAYLOAD (/home/user/coreboot/payloads/external/edk2/workspace/Build/UefiPayloadPkgX64/RELEASE_GCC/FV/UEFIPAYLOAD.fd)
Generate Region at Offset 0x0
Region Size = 0x800000
Region Name = FV
Generating PLDFV FV
Generating DXEFV FV
###################################### [‘GenFv’, ‘-a’, ‘/home/user/coreboot/payloads/external/edk2/workspace/Build/UefiPayloadPkgX64/RELEASE_GCC/FV/Ffs/PLDFV.inf’, ‘-o’, ‘/home/user/coreboot/payloads/external/edk2/workspace/Build/UefiPayloadPkgX64/RELEASE_GCC/FV/PLDFV.Fv’, ‘-i’, ‘/home/user/coreboot/payloads/external/edk2/workspace/Build/UefiPayloadPkgX64/RELEASE_GCC/FV/PLDFV.inf’]
Return Value = 2
GenFv: ERROR 3000: Invalid
the required fv image size 0x84c1a0 exceeds the set fv image size 0x800000
useless without knowing the build command you’re using, repo state, etc
“cd coreboot↲
./build-uefi.sh fizz↲”
That’s the command as usual. It worked well on 04/06/2026(firmware date). On 04/10 I found the repo updated 10 hours ago. I used “git pull” command and it didn’t work any more.
you’ve clearly made changes to edk2 based on the image posted. clear the edk2 repo and do a clean build.
I deleted the whole coreboot dir and following the instructions document on your website reclone the repo today, but still stuck on the FV build. It’s not the first time building with errors. Last time the same thing happened in February, but resolved few days later. I found the repo updated today, but still not work. Maybe I have to wait some days. Thank you very much!
there’s nothing to wait for, it builds properly now.
if yours isn’t building, you need to provide much more detail on your build environment, branch, etc
literally nothing has changed, I have not updated the repo since the 2603.1 release
I found what cause the problems. in the config.xxxx.uefi file,
CONFIG_EDK2_ENABLE_IPXE=y will cause UEFIPAYLOAD.fd oversize
CONFIG_EDK2_ENABLE_IPXE=n works well, but you will lose network boot.
it’s not a problem here, using the configs as is. not sure why your payload would be larger than yours
I don’t know, maybe someone made changes of the repo. I wipped the whole disk, reinstall the system, keep everything as default. and followed your guidance on the website of https://mrchromebox.tech. made no change of everything. it still stucks there. when IPEX disabled. it works well.
I’m literally the only person with write privileges, so I suspect not. More than likely, even though coreboot is compiled with its own toolchain, edk2 is compile with the host (system) toolchain, and your system toolchain is different and is producing a larger binary. What version of gcc is installed on your system?
could be, I’m using 14 or 15
OK, thank you. I’ll try a newer version.
