Bug #552
openX201 not booting with edk2 payload
0%
Description
Hello,
I tried to update my x201 with a new version of coreboot(I lost the working one).
After building(using default config + set to x201 + bigger cbfs + linear high-res framebuffer) with latest release I couldn't get anything with edk2 to boot on it.
I've tried changing RESOURCE_ALLOCATION_TOP_DOWN and using newer/older tags of MrChromebox's edk2 fork.
Files
Updated by Maya Matuszczyk 9 months ago
- File WORKING-EFI WORKING-EFI added
Maya Matuszczyk wrote:
Hello,
I tried to update my x201 with a new version of coreboot(I lost the working one).
After building(using default config + set to x201 + bigger cbfs + linear high-res framebuffer) with latest release I couldn't get anything with edk2 to boot on it.
I've tried changingRESOURCE_ALLOCATION_TOP_DOWNand using newer/older tags of MrChromebox's edk2 fork.
Turns out I had a skill issue and set a too big cbfs. I'm attaching a config that works on an X201 and 04bb74a7267a64d39ca87ba8c9b4f9f34c7d2bbb commit
Updated by Walter Sonius about 21 hours ago
Please close / resolve this ticket since it was already working for MrChromebox 2408 edk2 fork confirmed by the original topic starter and months ago by me in this ticket. Also verified this recently since RESOURCE_ALLOCATION_TOP_DOWN became enabled again by default, on Coreboot 25.03-467-gf0ad05b57ebe 05/14/2025 with MrChromebox 2502 edk2 fork on this x201.
[ 0.000000] DMI: LENOVO 3680WVT/3680WVT, BIOS CBET4000 25.03-467-gf0ad05b57ebe 05/14/2025
Don't forget to remove from the changelog/release notes as well.