coreboot

coreboot@coreboot.org

1 participants
39762 discussions

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org 17 Mar '25

17 Mar '25

Dear coreboot Community, Our upcoming leadership meeting is scheduled for Wednesday, March 19, 2025. [1] Please take a moment to update the agenda with matters you wish to see addressed during the meeting. [2] Thank you. Best regards, Mina Asante. [1](https://coreboot.org/calendar.html) [2](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkK…

1 0

coreboot 25.03 release schedule
by coreboot org 14 Mar '25

14 Mar '25

Hi everyone, This is the notification that we're two weeks away from the coreboot 25.03 release tag, scheduled for Thursday, March 27th. Please mark patches you want to be merged before the release with the hashtag “coreboot_release_25.03”. There's no promise that these will get merged, but we will try to get everything on the list in. Mark any patches that need to be merged *after* the release with the hashtag "post_coreboot_release_25.03" As usual, we have a 1 week delay after the new version is tagged before the announcement to allow for testing of the release. This gives us a chance to fix any issues that are found before making the release public. The 25.03 public announcement is scheduled for April 3rd. If you have any questions or concerns, please let the coreboot release team know or reply to this email. Thanks, Martin

1 0

[coreboot - Feature #461] Replacing Haswell mrc.bin blob with free software
by gaspar ilom 12 Mar '25

12 Mar '25

Issue #461 has been updated by gaspar ilom. The patch train got merged: https://review.coreboot.org/c/coreboot/+/81897/4 Anyway, in heads we have made an effort to use NRI on the W541 and T440p boards. However boot times are between 10 and 20s. So it seems like the mrc cache is not properly build and reused. Also, on the W541 S3 resume does not work (just reboots the machine). I can offer testing and helping debugging this feature: https://github.com/linuxboot/heads/pull/1923 ---------------------------------------- Feature #461: Replacing Haswell mrc.bin blob with free software https://ticket.coreboot.org/issues/461#change-1999 * Author: akjuxr3 akjuxr3 * Status: In Progress * Priority: Normal * Assignee: Angel Pons * Category: chipset configuration * Target version: none * Start date: 2020-04-01 * Related links: https://review.coreboot.org/q/topic:haswell-nri * Affected hardware: All Haswell mainboards ---------------------------------------- Currently in case of the ability to run as less amount of closed source software as possible and still have Microcode updates the reduced Intel ME with disabled bit in IFD and the lga1155 or the mobile versions of those cpus are the only option for x86_64 out there. The next cpu generation (Haswell) inside for example T440p and W541 require the binary blob mrc.bin Are there any plans of replacing the Haswell mrc.bin with free software? Or have the x86_64 platform be given up when the goal is to run just free software and the people should move to aarch64 or risc-v? -- 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 0

2025_03_12 coreboot Group Review Sesssion
by mina＠coreboot.org 10 Mar '25

10 Mar '25

Hello coreboot! Please note that we have an upcoming group review session scheduled for Wednesday, March 12. https://meet.google.com/kpu-yozw-gtt Check the coreboot calendar for the time in your timezone: https://coreboot.org/calendar.html As usual, we'll begin by reviewing a few patches together, then switch to individual reviews. However, everyone will still be available if you have questions about the patch you're reviewing. Here is the link to the list of patches to be reviewed this week: (https://docs.google.com/spreadsheets/d/1io-tewVlkX3PAkhR9ttCKjJXiXR9Emy6qsY…). Kindly add any specific patches you'd like the group to review to the top of the sheet. Thank you. Best regards, Mina.

1 0

[coreboot - Bug #580] (New) smbios table only recorded data for one slot
by Keith Hui 09 Mar '25

09 Mar '25

Issue #580 has been reported by Keith Hui. ---------------------------------------- Bug #580: smbios table only recorded data for one slot https://ticket.coreboot.org/issues/580 * Author: Keith Hui * Status: New * Priority: Normal * Category: coreboot common code * Start date: 2025-03-09 * Affected hardware: asus/p8z77-v_le_plus ---------------------------------------- I entered smbios slot description for 5 slots in devicetree (via an overridetree.cb), but after booting only the last slot is recorded in the data table. overridetree.cb ``` device domain 0 on subsystemid 0x1043 0x84ca inherit device ref peg11 on # PCIEX_16_2 smbios_slot_desc "SlotTypePciExpressGen3X8" "SlotLengthLong" "PCIEX16_2" "SlotDataBusWidth8X" end chip southbridge/intel/bd82x6x register "usb_port_config" = "{ /* not relevant */ }" register "gen1_dec" = "0x000c0291" # NCT6779 HWM register "gen4_dec" = "0x0000ff29" # Could be for KB3722 EC device ref pcie_rp1 on # PCIEX_16_3 (electrical x2 or x4) smbios_slot_desc "SlotTypePciExpressGen2X4" "SlotLengthLong" "PCIEX16_3" "SlotDataBusWidth4X" end device ref pcie_rp3 on smbios_slot_desc "SlotTypePciExpressGen2X1" "SlotLengthShort" "PCIEX1_1" "SlotDataBusWidth1X" end device ref pcie_rp4 on smbios_slot_desc "SlotTypePciExpressGen2X1" "SlotLengthShort" "PCIEX1_2" "SlotDataBusWidth1X" end device ref pcie_rp5 on # RTL8111F LAN chip drivers/net register "customized_leds" = "0x482" device pci 00.0 on subsystemid 0x1043 0x8505 end end end device ref pcie_rp6 on # ASM1083 PCI bridge subsystemid 0x1043 0x8489 smbios_slot_desc "SlotTypePci" "SlotLengthLong" "PCI1" "SlotDataBusWidth32Bit" end device ref pcie_rp7 on # Marvell 88SE9120 ESATA6G subsystemid 0x1043 0x83ba end device ref pcie_rp8 on # ASM1042 USB3 subsystemid 0x1043 0x8488 end device ref hda on subsystemid 0x1043 0x841a end device ref lpc on chip superio/nuvoton/nct6779d device pnp 2e.1 off end # Parallel device pnp 2e.2 on # UART A io 0x60 = 0x3f8 irq 0x70 = 4 end device pnp 2e.3 off end # UART B, IR device pnp 2e.5 on # PS2 KBC io 0x60 = 0x0060 # KBC1 base io 0x62 = 0x0064 # KBC2 base irq 0x70 = 1 # Keyboard IRQ irq 0x72 = 12 # Mouse IRQ # KBC 12Mhz/A20 speed/sw KBRST drq 0xf0 = 0x82 end device pnp 2e.6 off end # CIR device pnp 2e.7 off end # GPIOs 6-8 device pnp 2e.8 off end # WDT1 GPIO 0-1 device pnp 2e.108 on end # GPIO0 device pnp 2e.109 on end # GPIO1 device pnp 2e.509 on end # GPIO5 all in device pnp 2e.a on # ACPI drq 0xe7 = 0x11 drq 0xf2 = 0x5d # Enable PME end device pnp 2e.b on # H/W Monitor, FP LED io 0x60 = 0x290 io 0x62 = 0 irq 0x70 = 0 drq 0xe4 = 0xf9 # Use GP50/52/55 end device pnp 2e.d off end # WDT1 device pnp 2e.e off end # CIR wake-up device pnp 2e.f off end device pnp 2e.14 on end # Port 80 UART device pnp 2e.16 off end # Deep sleep end end end end ``` Output of dmidecode -t9 ``` # dmidecode 3.6 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Handle 0x0015, DMI type 9, 19 bytes System Slot Information Designation: PCI1 Type: PCI Data Bus Width: 32 bit Current Usage: In Use Length: Long ID: 0 Characteristics: 5.0 V is provided 3.3 V is provided PME signal is supported Bus Address: 0000:00:1c.4 Data Bus Width (Base): 1 Peer Devices: 0 ``` I expect to see all 5 slots returned. -- 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 0

[announce] flashprog v1.4 is out!
by Nico Huber 09 Mar '25

09 Mar '25

Hi, I'm glad to announce the release of flashprog v1.4. This time we've mostly updated the flash chip database, added 90 new entries and polished many existing ones. You can read more about it in the full release notes[1]. As usual, you can download the source via Git[2] (tag `v1.4`) or as tarball[3]. Cheers, Nico [1] https://flashprog.org/wiki/Flashprog/v1.4 [2] https://github.com/SourceArcade/flashprog [3] https://flashprog.org/releases/flashprog-v1.4.tar.bz2

1 0

2025-03-05 - coreboot Leadership Meeting Minutes
by mina＠coreboot.org 06 Mar '25

06 Mar '25

# 2025-03-05 - coreboot Leadership Meeting ## Attendees Mina Asante, Jon Murphy, Felix Singer, Benjamin Doron, Felix Held, Andre, Andy Ebrahiem, Jeremy Compostella, Martin Roth, Matt DeVillier, David Hendricks, Jay Talbott, Julius Werner, Karthik R. ## 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. ## Minutes ### [Benjamin] Add support for sharing SMM with the payload * To support UEFI secure boot effectively, we need to perform the verify and write steps of its variables together, in SMM. Consequently, we propose a solution where coreboot ‘owns’ SMM (initialises and installs all its regular SMI handlers), and the payload is permitted to install its own SMI handlers within a dedicated SMRAM region that coreboot will call into (and return from) for payload-specific use-cases. While this was developed for EDK2, to support secure boot, note that it’s not UEFI-specific, and contains nothing specific to secure boot. This is a superior solution to one we proposed in 2023, called “[Add support for calling SMM payloads.](https://docs.google.com/document/d/1S1hLGc7nhBIaD3wN3eylyjhMMqEo… * Earlier proposal handed SMM control to the payload, which caused issues since some things like suspend/resume and EC functionality needed to be provided in SMM controlled by coreboot. * This new approach allows EDK2 to read, verify, and potentially write secure boot related variables in an "atomic" manner (using coreboot's SPI driver on the backend?). This solves a problem from the earlier solution where secure boot variables could be changed by an attacker in between EDK2 and coreboot interactions. * [A.I] Benjamin to publish a[ blog post at the 9E blog](https://9elements.com/blog/) about this so that we can review the design in more detail. (DFAD/ETA: unknown, probably after university exams) ### [Martin] Updating website * Privacy Policy * Leadership page * Trademark & logo ### [Martin] Email server * As we agreed previously, the email service remained on Stefan’s server. This includes the mailing list * Stefan, Patrick and myself are admins there. ### [Jon] cbmem updates * Google is pursuing testing of coreboot with Android. As such, we do need to make some changes to coreboot mechanisms to facilitate a slightly different OS. Can we get review on some cbmem changes to add support in sysfs: (https://review.coreboot.org/q/topic:%22cb em-in-sysfs%22) ### [Martin] We can post blogs on the coreboot blog if people are interested in writing things. * Don’t want to make it an advertising area, but we’d like news about devices using coreboot. * Martin can write something about opensil with coreboot after the Phoenix & Turin Proof-of-Concept (Non-production) openSIL releases. # Next Leadership Meeting * March 19, 2025. * [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 minutes https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgK…

1 0

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org 03 Mar '25

03 Mar '25

Dear coreboot Community, Please note that we have an upcoming leadership meeting scheduled for Wednesday, March 5, 2025. [1] Kindly review the agenda and share your thoughts or suggest additional items you would like to discuss during the meeting. [2] Thank you. ## Current Agenda Items ### [Benjamin] Add support for sharing SMM with the payload * To support UEFI secure boot effectively, we need to perform the verify and write steps of its variables together, in SMM. Consequently, we propose a solution where coreboot ‘owns’ SMM (initialises and installs all its regular SMI handlers), and the payload is permitted to install its own SMI handlers within a dedicated SMRAM region that coreboot will call into (and return from) for payload-specific use-cases. While this was developed for EDK2, to support secure boot, note that it’s not UEFI-specific, and contains nothing specific to secure boot. This is a superior solution to one we proposed in 2023, called “Add support for calling SMM payloads.” [1](https://coreboot.org/calendar.html) [2](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkK…

1 0

(preping to coreboot) laptop X230 stuck on 2.75 - I cannot downgrade to 2.60!
by bruno＠slingshotsecurity.pro 02 Mar '25

02 Mar '25

I think I got myself in trouble stuck on 2.75 - I cannot downgrade to 2.60 (X230) via IVprep or the lenovo tool (I get "This app can't run on your PC"). Is there a way forward, please? Here is what I did and was planning to do (1vyrain, skulls and clean/disable/break the Intel ME): ## 1. EC Patching (accept all batteries and keyboards) https://github.com/hamishcoleman/thinkpad-ec/ It recomends using on the last modifiable version: x230 -BIOS 2.75 (G2ETB5WW) EC 1.14 (G2HT35WW) Therefore I upgraded from my 2.55 to 2.75, by downloading g2uj31us.exe, saving on a usb stick and running on the target machine's windows (the bootable iso would not dd well to the usb stick). https://support.lenovo.com/ec/en/downloads/ds029187 ## 2. Downgrade from 2.75 to 2.60 (X230) (I cannot perform from here onwards): https://github.com/n4ru/IVprep/tree/master Downloaded both IVprep and g2uj17us.exe and saved on the usb stick to run on target machine's windows but then I get I get "This app can't run on your PC". I have tested with both: BIOS Setup -> Security -> UEFI BIOS Update Option. Set Flash BIOS Updating by End-Users to Enabled, and Secure RollBack Prevention to Disabled BIOS Setup -> Security -> UEFI BIOS Update Option. Set Flash BIOS Updating by End-Users to Enabled, and Secure RollBack Prevention to Enabled ## 3. Get rid of the ME https://github.com/corna/me_cleaner I gues for this one, I should boot the target machine with a Live Linux, clone the repo and execute ## 4. Install Skulls via 1vyrain https://github.com/n4ru/1vyrain This would be burn the usb stick to the 1vyrain, use the ethernet cable and the skulls release URL https://github.com/merge/skulls/releases ## This question has been also posted on: - https://github.com/n4ru/1vyrain/issues/144- https://forum.qubes-os.org/t/how-to-use-ivprep-and-1vyrain-and-disable-inte… https://github.com/merge/skulls/issues/302 - https://github.com/hamishcoleman/thinkpad-ec/issues/266

1 0

Re: PC with coreboot - boot menu locked
by Paul Menzel 28 Feb '25

28 Feb '25

Dear Andrea, Welcome to coreboot. Please do not send messages over 500 kB (definitely not more than 1 MB) to mailing lists. Am 16.02.25 um 18:30 schrieb Andrea Battelli: > I have an embedded system that I want to reuse but the bios is locked up > and when I press the f12 key, it shows only a boot option (payload). How > can I disassemble the bios or rebuild another one? > > Attached is the dump of the rom and the screenshot of the boot menu It’d be great if you just copied the text output from the payload. SeaBIOS (version SageBIOS-20161017_085144-ttyree-dev-gtk-gtech-com) Select boot device: 1. Payload [igt_secure] Sage Engineering [1] *was* a company offering coreboot development a long time ago. No idea, if they upstreamed this board, or how to get the source code. What board is it exactly? Anyway, your attached dump has a coreboot image (CBFS – coreboot file system), you can dump with `cbfstool`: ``` $ ~/src/coreboot/util/cbfstool/cbfstool bios_igt_orig.bin print FMAP REGION: COREBOOT bios_igt_orig.bin: 16384 kB, bootblocksize 1024, romsize 16777216, offset 0xc00000 alignment: 64 bytes, architecture: x86 Name Offset Type Size Comp roothashes 0xc00000 (unknown) 192 none fallback/romstage 0xc00100 stage 60241 none fallback/ramstage 0xc0ecc0 stage 94548 none fallback/payload 0xc25e80 simple elf 49158 none bootsplash.jpg 0xc31ec0 bootsplash 48411 none etc/boot-menu-wait 0xc3dc40 raw 8 none (empty) 0xc3dc80 null 4888 none keyupdate 0xc3efc0 mma 8192 none (empty) 0xc41000 null 3992 none keystore 0xc41fc0 mrc 131072 none img/igt_secure 0xc62000 simple elf 83362 none vgaroms/videobios.rom 0xc76600 optionrom 65536 none (empty) 0xc86640 null 51544 none bootorder 0xc92fc0 raw 4096 none (empty) 0xc94000 null 2604952 none cpu_microcode_blob.bin 0xf0ffc0 microcode 38912 none (empty) 0xf19800 null 157592 none mrc.cache 0xf3ffc0 mrc_cache 65536 none (empty) 0xf50000 null 65432 none fsp.bin 0xf5ffc0 spd 524288 none (empty) 0xfe0000 null 12248 none bootorder_sata 0xfe3000 raw 4096 none bootorder_usb 0xfe4040 raw 4096 none bootorder_sec 0xfe5080 raw 4096 none (empty) 0xfe60c0 null 24 none rootpub 0xfe6100 fsp 2064 none (empty) 0xfe6940 null 103000 none ``` It does not seem to contain the build configuration, but you might be able to boot from a USB device. From there you should be able to read the logs with `cbmem` and find out the coreboot version and board name. Maybe that brings you further. I have never heard of `igt_secure`. As you can access the dump, you can at least build the payload yourself, and replace `fallback/payload` or add it under `img/`. Maybe that works. No idea if the keys/hashes verify anything from this. Anyway, the above should get you going. Kind regards, Paul [1]: https://se-eng.com/ [2]:

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot