April 2026 - coreboot - mail.coreboot.org

[coreboot - Bug #576] (New) GPIO locking is broken on Kaby Lake and possibly other platforms
by Mate Kukri June 3, 2026

June 3, 2026

Issue #576 has been reported by Mate Kukri. ---------------------------------------- Bug #576: GPIO locking is broken on Kaby Lake and possibly other platforms https://ticket.coreboot.org/issues/576 * Author: Mate Kukri * Status: New * Priority: Normal * Target version: none * Start date: 2025-01-30 ---------------------------------------- Many supported Kaby Lake boards (and possibly newer platforms as well) are vulnerable to [TPM GPIO reset attacks](https://mkukri.xyz/2024/06/01/tpm-gpio-fail.html). Trying to fix this by marking the affected GPIOs as locked in gpio.h and even also selecting `SOC_INTEL_COMMON_BLOCK_SMM_LOCK_GPIO_PADS` does not work. This was discovered last year and briefly discussed on #coreboot, but it came up again on the Heads matrix group in relation to supporting the TPM on the in-progress ThinkPad T480 port. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

3 5

[coreboot - Support #636] (New) Building GCC v14.2.0 for target ... failed. Check 'build-i386-elf-GCC/build.log'.
by Ahmet Ozkesek May 23, 2026

May 23, 2026

Issue #636 has been reported by Ahmet Ozkesek. ---------------------------------------- Support #636: Building GCC v14.2.0 for target ... failed. Check 'build-i386-elf-GCC/build.log'. https://ticket.coreboot.org/issues/636 * Author: Ahmet Ozkesek * Status: New * Priority: Low * Category: build system * Target version: none * Start date: 2026-03-22 ---------------------------------------- Hi all, Thank you for coreboot, first of all. I am looking for building coreboot with u-boot payload. I started from scratch as documented on my Fedora 44 beta system. I hit the error below, -please scroll-down for it- and hoping that someone already either fixed or done a workaround for this making crossgcc-i386. I somewhat did workaround for -V command-line argument error for gnatgcc and g++, and got version info out there, but no lock for this `error: no matching function for call to 'S2C(const char8_t [2])` . I attached config&build log from util/crossgcc/build-i386-elf-GCC. Welcome to the coreboot cross toolchain builder v2026-01-30_235bb1e617 Building toolchain using 10 thread(s). Target architecture is i386-elf Found compatible Ada compiler, enabling Ada support by default. Downloading and verifying tarballs ... * gmp-6.3.0.tar.xz (cached)... hash verified (b4043dd2964ab1a858109da85c44de224384f352) * mpfr-4.2.2.tar.xz (cached)... hash verified (a63a264b273a652e27518443640e69567da498ce) * mpc-1.3.1.tar.gz (cached)... hash verified (bac1c1fa79f5602df1e29e4684e103ad55714e02) * binutils-2.45.tar.xz (cached)... hash verified (09fd8a50a95be4a94412fe3847d16280996679c5) * gcc-14.2.0.tar.xz (cached)... hash verified (d91ecc3d20ce6298bd95f9b09cc51dc6d3c73ae3) Downloaded tarballs ... ok Unpacking and patching ... * gmp-6.3.0.tar.xz o gmp-6.3.0_fix-c23-prototypes.patch o gmp-6.3.0_generic-build.patch * mpfr-4.2.2.tar.xz * mpc-1.3.1.tar.gz * binutils-2.45.tar.xz o binutils-2.45_as-ipxe.patch o binutils-2.45_no-makeinfo.patch * gcc-14.2.0.tar.xz o gcc-14.2.0_asan_shadow_offset_callback.patch o gcc-14.2.0_gnat.patch o gcc-14.2.0_libcpp.patch o gcc-14.2.0_libgcc.patch o gcc-14.2.0_musl_poisoned_calloc.patch o gcc-14.2.0_rv32iafc.patch Unpacked and patched ... ok Building packages ... Building GMP v6.3.0 for host ... ok Building MPFR v4.2.2 for host ... ok Building MPC v1.3.1 for host ... ok Building BINUTILS v2.45 for target ... ok Building GCC v14.2.0 for target ... failed. Check 'build-i386-elf-GCC/build.log'. make[2]: *** [Makefile:20: build_gcc] Error 1 make[1]: *** [Makefile:36: build-i386] Error 2 make: *** [util/crossgcc/Makefile.mk:32: crossgcc-i386] Error 2 ---Files-------------------------------- config.log (39.2 KB) build.log (284 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

3 7

[coreboot - Bug #448] (New) Thinkpad T440P ACPI Battery Value Issues
by Karsten Schnier May 5, 2026

May 5, 2026

Issue #448 has been reported by Karsten Schnier. ---------------------------------------- Bug #448: Thinkpad T440P ACPI Battery Value Issues https://ticket.coreboot.org/issues/448 * Author: Karsten Schnier * Status: New * Priority: Normal * Target version: none * Start date: 2023-01-11 * Affected versions: master * Related links: [[https://github.com/linrunner/TLP/issues/657]] * Affected hardware: Thinkpad T440p * Affected OS: Artix / Arch Linux ---------------------------------------- Hello, I have been having some issues with TLP on my corebooted T440p. I am running artix linux with grub on top of coreboot (self compiled libreboot). I have had issues with the ACPI battery readings. Coreboot does not provide power readings, but instead only current readings. More details can be found in the TLP github issue: [[https://github.com/linrunner/TLP/issues/657#issuecomment-1293730559]] This causes TLP to not recognize the thinkpad and go to default mode. Additional, it prevents recalibration of the battery even when the thinkpad battery driver is forced. Is this due to misconfiguration in the coreboot build or issues with coreboot itself? Thank you! -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

2 1

2026-04-29 - coreboot Leadership Meeting Minutes
by mina＠coreboot.org April 30, 2026

April 30, 2026

# 2026-04-29 - coreboot Leadership Meeting ## Open Action Items * 2024-11-27 * [Open] Send out poll with regards to LLM usage (requested by SFC) * 2024-10-30 * [Open] Add clarification to docs: “Do not use gerrit change-id or CB: format in reference to already-merged patches.” * 2024-10-16 * [Open] Matt: Set up a meeting to discuss board status alternatives and send out invites. * Decouple data collection with uploading * Require gerrit credentials or other auth to push * Json format? * https://github.com/chrultrabook/linux-tools/blob/main/debugging.sh * 2024-09-18 * [Open] Jon: Schedule a dedicated meeting to discuss the Coverity defects and action plan. * Werner: Send out an invite for the meeting. Sent out a poll to find a time slot: https://rallly.co/invite/1c8J3azXAcje * 2024-05-01 * [Open] Nick Van Der Harst volunteered for Dutch. "gogo gogo" would like to translate to Russian (?). * 2024-01-10 * Nico: (https://review.coreboot.org/q/topic:enforce_region_api) * [Open] Daniel: Look at how we want to localize (non-console) strings for coreboot. Long-term project. ## Announcements & Events * Next Open System Firmware - OCP Project Meeting * Date : [April 6, 2026](https://coreboot.org/calendar.html) * [OSFC 2026](https://www.osfc.io) * Date: 15 - 17 September * CFP open until 2026/06/22 ## Attendees Mina Aante, Maximilian Brune, Werner Zeh, Tom Hiller, Alicja Michalska,David Hendricks, Matt DeVillier. ## Minutes ### [Tom Hiller] coreboot and me_cleaner collaboration, any possible next steps? * The owner of the me_cleaner project, Nicola Corna, has not had time to maintain it and development has fragmented across a number of different forks. They have expressed interest in adding collaborators, (https://github.com/corna/me_cleaner/issues/441#issuecomment-4018664344) and (https://review.coreboot.org/c/coreboot/+/91548/3#message-288ed1584c4d8defc9…) but I am wondering coreboot would be willing to adopt me_cleaner if approved by the owner? If so, I am curious/worried about the potential noise that it may produce given the amount of questions that are asked about me_cleaner used on stock firmware. Perhaps have a similar set up as flashrom, its own GitHub repo with the ability to open issues but development done through gerrit. As I am not the owner of me_cleaner, it is not my place to be suggesting this but did want to mention the idea for coreboot's leadership to discuss and perhaps reach out to Nicola Corna. * Would moving it from github actually help increase development? * The Github instance currently has 297 forks. * Nicola originally added me_cleaner in util/ in ~2017, then created the github repo in 2018. * [Matt] Similar situation as deguard * github instance is now a read-only mirror of our deguard repo * [Max] It will be best for Nicola to add maintainers to the original repo. * [Matt] Removing me_cleaner from coreboot could break some integration * Needs to be made into a submodule like we do with FSP, etc. * We can mirror it, at least. * [David] Be cautious in hosting a repo like me_cleaner on coreboot infrastructure because a tool like this one (meant for disabling features which should not be disabled, based on reverse-engineering). coreboot could run into legal issues. ## [Werner] European Union Horizon initiative * Open Internet Stack Sovereign Solution - basically a way to ensure software independence in Europe * Dasharo (3mdeb) and coreboot (Werner) are participating * coreboot cannot get funding due to not being an EU-based project (SFC is US-based), but individuals in the EU can participate. ### [Alicja] What to do with openSIL Kconfig patches? * We currently have a read-only mirror openSIL. * Upstream does not take patches. * It also cannot be built standalone without Alicja's patches. * Martin suggests we should use coreboot's Kconfig system. * So we need to have a read-write mirror of openSIL? # Next Leadership Meeting Date * May 13, 2026. * [coreboot Calendar](https://coreboot.org/calendar.html). # Notice Decisions shown here are not necessarily final and are based on the current information available. If there are questions or comments about decisions made, or additional information to present, please put it on the leadership meeting agenda and show up if possible to discuss it. Of course items may also be discussed on the mailing list, but as it's difficult to interpret tone over email, controversial topics frequently do not have good progress in those discussions. For particularly difficult issues, it may be best to try to schedule another meeting. # coreboot Leadership Meeting Notes https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgK….

1 0

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org April 27, 2026

April 27, 2026

Dear coreboot Community, Please note that our upcoming coreboot leadership meeting is scheduled for Wednesday, April 29, 2026. [1] Kindly update the agenda with any issues or topics you would like to discuss during the meeting. [2] Thank you. ## Current Agenda Items * No active issues on the agenda yet. [1](https://coreboot.org/calendar.html). [2](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkK….

1 0

coreboot and me_cleaner
by Tom Hiller April 26, 2026

April 26, 2026

Hello, The owner of the me_cleaner project, Nicola Corna, has not had time to maintain it and development has fragmented across a number of different forks. They have expressed interest in adding collaborators, https://github.com/corna/me_cleaner/issues/441#issuecomment-4018664344 and https://review.coreboot.org/c/coreboot/+/91548/3#message-288ed1584c4d8defc9…, but I am wondering coreboot would be willing to adopt me_cleaner if approved by the owner? If so, I am curious/worried about the potential noise it that may produce given the amount of questions that are asked about me_cleaner used on stock firmware. Perhaps have a similar set up as flashrom, its own GitHub repo with the ability to open issues but development done through gerrit. As I am not the owner of me_cleaner, it is not my place to be suggesting this but did want to mention the idea for coreboot's leadership to discuss and perhaps reach out to Nicola Corna. Tom Hiller/ThrillerAtPlay

2 1

[coreboot - Project ideas #639] (New) support LGA771 Xeon CPU's on 5000P/5000X N.B 631xESB/632xESB/3100 S.B using EARLY_CBMEM_INIT / RESOURCE_ALLOCATOR_V4
by Walter Sonius April 26, 2026

April 26, 2026

Issue #639 has been reported by Walter Sonius. ---------------------------------------- Project ideas #639: support LGA771 Xeon CPU's on 5000P/5000X N.B 631xESB/632xESB/3100 S.B using EARLY_CBMEM_INIT / RESOURCE_ALLOCATOR_V4 https://ticket.coreboot.org/issues/639 * Author: Walter Sonius * Status: New * Priority: Low * Category: board support * Target version: none * Start date: 2026-04-26 ---------------------------------------- Boards containing dual LGA771 Xeon CPU's with intel 5000P northbridge and 3100 southbridge chipsets have been supported with coreboot in the past but were dropped before "EARLY_CBMEM_INIT" and "RESOURCE_ALLOCATOR_V4" were introduced see: Supermicro X7DB8 https://review.coreboot.org/c/coreboot/+/493 ASUS DSBF https://review.coreboot.org/c/coreboot/+/1223 Fujitsu TX200-S3(unmerged) https://review.coreboot.org/c/coreboot/+/1202 Removal of these boards was done when "LATE_CBMEM_INIT" became unsupported: https://review.coreboot.org/c/coreboot/+/22030 https://review.coreboot.org/c/coreboot/+/22031 VIA CX700: Likewise the VIA CX700 support was also removed in past because of "LATE_CBMEM_INIT" but was restored years later, however that chip is probably a lot less complex than the dual socket intel series: https://review.coreboot.org/c/coreboot/+/26678 https://review.coreboot.org/c/coreboot/+/82770 Currently coreboot supports a even older dual socket MPGA604 Xeon server board and multiple single socket LGA775 desktop boards. The later should already unofficially support a single modded LGA771 Xeon CPU (drilled holes, stickermod and microcode) by current coreboot codebase: ``` #CPU_INTEL_SOCKET_MPGA604 aopen/dxplplusu #select CPU_INTEL_SOCKET_LGA775 asus/p5qc asus/p5gc-mx asus/p5qpl-am asus/p5ql-em foxconn/g41s-k acer/g43t-am3 asrock/g41c-gs gigabyte/ga-945gcm-s2l gigabyte/ga-g41m-es2l intel/dg43gt intel/dg41wv lenovo/thinkcentre_a58 ``` Why Research 5000P? Although these LGA771 server boards may "not" seem interesting for any current server or workstation use and are mostly unobtainable, some of them ship with regular ATX / FAN power connectors and socket-ed PLCC-32 ROM's mostly Asus, Gigabyte and Supermicro. These may still assist in debugging coreboot support for other boards with similar chipsets that lack socket-ed ROM's. See the retroweb summary of some socket 5000P boards: https://theretroweb.com/motherboards?itemsPerPage=24&chipsetIds%5B%5D=1221 See the retroweb summary of some socket 5000V boards: https://theretroweb.com/motherboards?itemsPerPage=24&chipsetIds%5B%5D=1223 See the retroweb summary of some socket 5000X boards, see Dell Precision 490(soldered PLCC32) and SuperMicro DB7A* boards with similar MEM/CPU layout: https://theretroweb.com/motherboards?itemsPerPage=24&chipIds%5B0%5D=317 Why research 5000X (Greencreek)? Possible interesting workstations that can easily accommodate 6+ HDD's, push full 10Gbe without a problem and still work silent (including FAN control) are easily available from Apple. However with the downside of these boards being "EFI32" and soldered 40pin TSOP "M50FW016" 2MB FWH ROM's which makes coreboot development a PITA... They all share dual LGA771 CPU sockets (quadcore on mp11 needs mp21 firmware) and have 8 FB-DIMMS with 4x DIMM on 2 risers, with different PCIe configs: Apple MacPro 1,1 (4x PCIe x16 slots @2.5GT/s with 3x PCIe x8 lanes and 1x PCIe x1 lane option) Apple MacPro 2,1 (4x PCIe x16 slots @2.5GT/s with 3x PCIe x8 lanes and 1x PCIe x1 lane option) Apple MacPro 3,1 (4x PCIe x16 slots wtih 2x x16 lanes @5GT/s and 2x PCIe x4 lanes @2.5GT/s locked) (mp3,1 has 5400 northbridge instead which has +Harpertown CPU upgrade support) One step closer to coreboot support for these MacPro's is flashrom support was lacking for writing the full ROM on these early MacPro's. However with a special Mac OSX bless command and power-on procedure writing the full ROM from linux with flashrom is now verified both on mp21 and mp31 (more details in flashrom ticket). But this is just a very tiny step from coreboot support... How much effort will re-supporting these intel 5000p and possibly 5000x northbridge series with current coreboot codebase be? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 1

[coreboot - Bug #637] (New) Sandybridge: C-States and Turbo not working in coreboot
by Patrick Rudolph April 25, 2026

April 25, 2026

Issue #637 has been reported by Patrick Rudolph. ---------------------------------------- Bug #637: Sandybridge: C-States and Turbo not working in coreboot https://ticket.coreboot.org/issues/637 * Author: Patrick Rudolph * Status: New * Priority: Normal * Category: chipset configuration * Target version: none * Start date: 2026-04-06 ---------------------------------------- Observations showed that in coreboot: - C-States are not working (asm("mwait"); has no effect) - Turbo states (core above P0 frequency) aren't working The P-state can be changed after BIOS_RESET_CPL, but it never goes into turbo mode. On Linux both are working fine. It would be nice to have both fixed as turbo states could reduce boot time when extracting the LZMA payload. Tests show that around 20msec of boottime improvements are possible, just for extracting the LZMA payload. Tested version: 654f32847428f36c92c19932bdfec9f3510bf384 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

4 7

Gerrit and Jenkins outage
by David Hendricks April 23, 2026

April 23, 2026

Hi folks, Quick heads up that Gerrit and Jenkins are currently down and we're looking into it. Sorry for any inconvenience!

1 0

2026_04_22 coreboot Group Review Session
by mina＠coreboot.org April 20, 2026

April 20, 2026

Hello coreboot, Kindly note that our upcoming group patch review session is scheduled for Wednesday, April 22: https://meet.google.com/kpu-yozw-gtt Check the coreboot calendar for the time in your timezone: https://coreboot.org/calendar.html Here is a link to the list of patches to be reviewed this week: (https://docs.google.com/spreadsheets/d/1io-tewVlkX3PAkhR9ttCKjJXiXR9Emy6qsY…) Please add any specific patches you'd like the group to review to the top of the sheet. Since an hour may not be sufficient to address all patches on the list, reviewing patches in advance is greatly appreciated. Thank you. Best regards, Mina.

1 0