March 2026 - coreboot - mail.coreboot.org

[coreboot - Bug #598] (New) Lenovo m920x RAM compatibility issue
by Dawid Wrobel April 6, 2026

April 6, 2026

Issue #598 has been reported by Dawid Wrobel. ---------------------------------------- Bug #598: Lenovo m920x RAM compatibility issue https://ticket.coreboot.org/issues/598 * Author: Dawid Wrobel * Status: New * Priority: Normal * Target version: none * Start date: 2025-06-04 * Affected versions: main ---------------------------------------- Hi there, I recently flashed my m902x with coreboot (25.03-643-g69a067a9d62c-dirty). Everything seemed to work fine until I tried upgrading the memory from a single 8GB stick to 2 x 32GB (Crucial CT2K32G4SFD832A, https://eu.crucial.com/memory/ddr4/CT2K32G4SFD832A) The system won't boot in any configuration (a single stick in either slot or both). I get no display out, the system stays on and stuck, apparently, with high CPU usage causing fans to kick in. I have no serial port in this system at the moment (backordered an extension module), but am wondering if it will be of any help and if there's any other way to debug it? Do note that the system *is* capable of running 64GB memory, as it was reported already, so I wonder if this is a matter of some SPD misconfiguration? Crucial lists the 2x16GB modules as compatible with this system (https://eu.crucial.com/compatible-upgrade-for/lenovo/thinkcentre-m920x-tiny…) and they have seemingly identical specs as the 2x32GB ones. -- 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 - Bug #592] (New) Lenovo M920q can't use DIMM2 RAM slot
by Coreboot Enjoyer April 6, 2026

April 6, 2026

Issue #592 has been reported by Coreboot Enjoyer. ---------------------------------------- Bug #592: Lenovo M920q can't use DIMM2 RAM slot https://ticket.coreboot.org/issues/592 * Author: Coreboot Enjoyer * Status: New * Priority: Normal * Category: coreboot common code * Target version: none * Start date: 2025-04-15 * Affected versions: main * Related links: https://github.com/Thrilleratplay/coreboot-builder-scripts/issues/33 Also, it looks like a similar issue to https://ticket.coreboot.org/issues/462 * Affected hardware: Lenovo M920q ---------------------------------------- Building the current coreboot source, as well as commits 497298708c330deb479fbf3ee6a3acc8bff2a102, 640a41f3ee938b794b140218921e0fd63b1d9235 and 7945a31e9172ec2939cc1abc6036962a6efb601b, produces the firmware, that allows to initialize the motherboard if only DIMM1 RAM slot is filled. It fails to initialize, if DIMM1 RAM slot is empty and DIMM2 is filled, as well as if both DIMM1 and DIMM2 are filled. The issue is reproducible with different RAM sticks. I tried every possible combination with Kingston 32GB (2666MHz, CL 19-19-19-43) and Samsung 8GB (2400MHz, CL 17-17-17-39) -- the motherboard recognizes RAM sticks correctly, but still fails when the DIMM2 is filled with any RAM stick. I have also attached the build config file, which uses most of the default options. ---Files-------------------------------- m920q-dimm2-config.txt (27.6 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

6 8

[coreboot - Bug #627] (New) Lenovo ThinkPad X280 (20KE) only shows 4GB of RAM out of 16GB
by Ladislav Ezr April 6, 2026

April 6, 2026

Issue #627 has been reported by Ladislav Ezr. ---------------------------------------- Bug #627: Lenovo ThinkPad X280 (20KE) only shows 4GB of RAM out of 16GB https://ticket.coreboot.org/issues/627 * Author: Ladislav Ezr * Status: New * Priority: Normal * Category: board support * Target version: none * Start date: 2026-02-11 * Affected versions: main * Affected hardware: Lenovo ThinkPad X280 * Affected OS: all ---------------------------------------- Hi, X280 (20KE-S2EW08) flashed with main coreboot (git clone a few hours ago). Only shows 4GB of RAM when it's actually a 16GB model. ---Files-------------------------------- X280 coreboot .config.txt (28.3 KB) X280 cbmem -1 log.txt (54 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

2 4

[coreboot - Bug #624] (New) Memory speed in SMBIOS is incorrectly doubled on Haswell
by Ron Nazarov April 6, 2026

April 6, 2026

Issue #624 has been reported by Ron Nazarov. ---------------------------------------- Bug #624: Memory speed in SMBIOS is incorrectly doubled on Haswell https://ticket.coreboot.org/issues/624 * Author: Ron Nazarov * Status: New * Priority: Normal * Assignee: Angel Pons * Target version: none * Start date: 2026-01-21 * Affected versions: main * Affected hardware: Haswell ---------------------------------------- Tested on a Dell Precision T1700 SFF with NRI, my 1600 MT/s (800 MHz) RAM is reported by `dmidecode -t 17` as running at 3200 MT/s. This bug was introduced in https://review.coreboot.org/c/coreboot/+/89598/6. The frequency is doubled in `dimm->ddr_frequency = ddr_freq_mhz * 2; /* In MT/s */`, however (at least on NRI, I did not test MRC), `ddr_freq_mhz` (defined as `(mchbar_read32(MC_BIOS_DATA) * 13333 * 2 + 50) / 100`) is actually in MT/s, and so already doubled. I also see this in coreboot logs: `[DEBUG] memcfg DDR3 clock 1600 MHz`. This debug print (added in https://review.coreboot.org/c/coreboot/+/89599/4) is printing `DIV_ROUND_CLOSEST(mchbar_read32(MC_BIOS_DATA) * 13333 * 2, 100)`, which is pretty much the same as `ddr_freq_mhz` (except using `DIV_ROUND_CLOSEST`). -- 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 4

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

April 2, 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

1 4

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org March 30, 2026

March 30, 2026

Dear coreboot Community, Please note that we have an upcoming leadership meeting scheduled for Wednesday, April 1, 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

2026_03_25 coreboot Group Review Session
by mina＠coreboot.org March 23, 2026

March 23, 2026

Hello coreboot, Kindly note that our upcoming group patch review session is scheduled for Wednesday, March 25: 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

[coreboot - Bug #620] (New) X230(t) does not work since commit 97dbfd3098ae12ef3f51e5f95cd6d66c25214205 was merged
by Hustler One March 22, 2026

March 22, 2026

Issue #620 has been reported by Hustler One. ---------------------------------------- Bug #620: X230(t) does not work since commit 97dbfd3098ae12ef3f51e5f95cd6d66c25214205 was merged https://ticket.coreboot.org/issues/620 * Author: Hustler One * Status: New * Priority: High * Category: coreboot common code * Target version: main * Start date: 2025-12-31 * Affected versions: main * Related links: https://www.reddit.com/r/coreboot/comments/1pu5vlp/x230t_does_not_get_past_… https://www.reddit.com/r/coreboot/comments/1pyzcvf/no_video_output_with_upd… * Affected hardware: x230t ---------------------------------------- Releases 25.09, 25.12 are affected. 25.06 works. The commit 97dbfd3098ae12ef3f51e5f95cd6d66c25214205 prevents the x230t from going past the `postcar` stage, hence it being inoperable since it won't load into the main payload. I have attempted to debug using flashconsole but the trail runs cold after `postcar`. Credit to iam_tj for finding the commit. Also, Libreboot is somehow unaffected by this. I don't know if lbmk undoes this commit or not at this time. -- 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 4

[coreboot - Bug #628] (New) mb/asus/h61-series: variant p8h61-i_r2_0 won't POST on recent coreboot version mmio / tpm range ?
by Walter Sonius March 22, 2026

March 22, 2026

Issue #628 has been reported by Walter Sonius. ---------------------------------------- Bug #628: mb/asus/h61-series: variant p8h61-i_r2_0 won't POST on recent coreboot version mmio / tpm range ? https://ticket.coreboot.org/issues/628 * Author: Walter Sonius * Status: New * Priority: Normal * Assignee: Patrick Rudolph * Target version: none * Start date: 2026-02-21 * Affected versions: main ---------------------------------------- Variant Asus h61-series p8h61-i_r2_0 WIP code under review: https://review.coreboot.org/c/coreboot/+/91337 Possible issue commit sb/intel/bd82x6x/lpc: Advertise all fixed MMIO ranges: https://review.coreboot.org/c/coreboot/+/91040 If this patch is applied to old coreboot codebase 25.06-77-g812d0e2f626d as a whole or on current codebase, boot will stall before POST/BOOT so no screen but machine stays powered on and hangs forever, on old codebase you seen USB poweron on current codebase you don't! SPI console log snippet loops here from old coreboot codebase, see diff at line ~470 and ~550: ``` Resource didn't fit!!! PNP: 002e.a 60 * size: 0x8 limit: fff io ``` Uploaded 3 SPI logs from old coreboot base, mmio123456 means whole patch CB:91040 applied and mmio12346 means skipped the TPM part (5th block) of that patch, the shortest named file is the one with original unpatched `lpc.c` file! ---Files-------------------------------- p8h61ir2-21-old-edk2-spilogdb-cbmem.rom.log (256 KB) p8h61ir2-21-old-edk2-spilogdb-mmio12346-cbmem.rom.log (256 KB) p8h61ir2-21-old-edk2-spilogdb-mmio123456-cbmem.rom.log (256 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

2026-03-18 - coreboot Leadership Meeting Minutes
by mina＠coreboot.org March 19, 2026

March 19, 2026

# 2026-03-18 - 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: [March 26, 2026](https://coreboot.org/calendar.html) ## Attendees Angel Pons, David Hendricks, Jay Tallbott, Maximilian Brune, Matt DeVillier, Julius Werner, Mina Asante, Alicja Michalska. ## Minutes ### Information: coreboot 26.03 tag release is scheduled for Thursday, March 19. * Mark patches to be merged before the release with the hashtag “coreboot_release_26.03”. * Mark patches to be merged after the release with the hashtag "post_coreboot_release_26.03". # Next Leadership Meeting Date * April 1, 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