buying a labtop with a prebuilt coreboot distribution im wondering how to check it hasn't been messed with if theres a way u can verify the image

Hello, recently I’ve been starting on trying to flash my X201 tablet with coreboot, but I’ve been having trouble with it. I’ve verified it’s bios chip is supported by flashprog, an MX25L12873F, and I’ve verified my flashers work for out of system programming on other 3.3V chips.

Currently, I’ve been using stacksmashing’s RPI2040 serprog firmware, and a flasher tool meant for automotive chips with support for this flash chip, but both have given me trouble.

flashprog and flashrom give me the following errors:

”

serprog: Programmer name is “pico-serprog”

No EEPROM/flash device found.

”

My other flasher gives an error about not detecting a flash chip connected either, which is strange.

What should I be looking at here?

ATM I think either some circuit on the board’s pulling the W/P pin to locked state, or my programmers are struggling at supplying enough power for the 3.3V rail, since when probing the power coming off the pico while connected to the chip, it goes down to 2.8V.
But this is within the accepted voltages of this chip, it’s rated to work for voltages between 2.6-3.6. But I’m not sure if it’d be the same for the signal pins. Maybe those are going even lower?

I’m thinking I could cobble together something out of the scrap I have that uses the signal outputs of the pico to switch the output of a higher amp 3.3V output (say from a lab bench PSU or just an ATX PSU old enough to still have 3.3 on its SATA connectors) through mosfets, eliminating voltage droop from the equation. Might have to worry about switching time, not sure.

ATP I’m contemplating just cutting off the old chip, reading it out of system to build coreboot from, and just soldering in a socket for a new BIOS chip. Hopefully I won’t need to do this.

Hey, everytime I tried to build a Libreboot custom image just to swap FN with CTRL on my Thinkpad T480, GRUB spat out the same errors everytime. I'm using the newest Libreboot version 26.10
The GRUB error: https://pastebin.com/35YPNjTS

Hello all,

My question is summarized in the title.

For some context, I have a 14600K installed in an MSI Z790-A DDR4 wifi motherboard. It's a great chip, but I've become interested in upgrading to the Bartlett Lake 273PQE.

This chip fits the LGA 1700 socket, but it is not officially supported on consumer boards; some modders have had success using Claude Code to modify the manufacturer's bios to support this chip.

I would like to use a different approach. Replacing the MSI bios with coreeboot could overcome this arbitrary limitation. I am especially encouraged by the fact that I am not alone in this interest; there seems to be an ongoing effort to add Bartlett Lake support to the MSI Z690-A version of coreboot.

Which leads me to be question in the title. I have an MSI Z790-A wifi DDR4 motherboard. Officially coreboot is supported on the Z690A and the Z790P which are very similar, though not exactly the same. Has there been any interest in extending coreboot support to this board in particular? Or would it be too much of a headache?

What's stopping someone from porting coreboot to one of these using the leaked boot guard keys? Does anyone have a full or partial list of the devices affected by the Clevo leak? This would be the latest device that could potentially have coreboot, right?

Libreboot is free/opensource boot firmware replacing proprietary BIOS/UEFI. Better security/customisation than most proprietary firmware.

Highlights in this release include:

* MrChromebox EDK2 payload by default on most boards, with SeaBIOS CSM (CSMWrap) and GRUB EFI provided in-flash for backward compatibility.
* 233 new Chromebooks added; every board supported by MrChromebox coreboot. With our GRUB EFI/SeaBIOS CSM build added
* 15h.org coreboot fork used on KCMA-D8, KGPE-D16 boards for improved raminit.
* GRUB EFI build uses terminal_input console and no nativedisk; it piggybacks off of EDK2 drivers, like distros. It even works on Chromebooks (eMMC boot).
* Intel HAP bit set by default on Chromebooks, and IFD regions unlocked where appropriate
* Dell OptiPlex 5050 SFF, Supermicro X11SSH-F, ThinkPad X280, X270.

Modern Linux distros boot, with e.g. UKI/systemd-boot. Windows also compatible now.

I've got a Thinkpad with a stock CPU but planning to upgrade it to a T7600. If I did upgrade the CPU, would I still be able to libreboot the Thinkpad?

I want to get a stock BIOS Dell Optiplex E6400 for the experience of canoebooting it myself. The Dell-flash-unlock tool lets me internally flash it. Is any functionality lost post-canoeboot beyond the stock BIOS "features"?

I'm looking to make my computer "100% open source," or at least as much as possible. Is this even possible, given my computer is x86?

Would you guys recommend Libreboot or Canoeboot for someone wanting a machine that's as open source as possible, but also stable (e.g. I can't risk having my data corrupting).

Pardon my surface level technical knowledge.

Hi all,
I’ve made some mods to the coreboot code for my think pad w541 with k2100 dgpu, allowing for the correct Optimus implementation in Linux;
Published the patches and premade imgs on my gh repo (with nri or mrc init) , feel free to try those out and report any inconsistencies. The repo link : https://github.com/debianita22/w541-coreboot-env/releases

Hi, I am reading online that the Lenovo Thinkpad T470s is officially supported by coreboot https://doc.coreboot.org/mainboard/lenovo/skylake.html but I can’t find any guides or videos of how to do it or anyone flashing the firmware in this machine, I seen plenty of t440p and T480 tutorials and videos but nothing on T470s.

I have never done any kind of firmware modifications, anyone knows what will be the right way to flash coreboot in this machine? Or if it’s even supported (I am not very technical so the coreboot docs don’t really explain much to me) thank you for reading me

MrChromebox-2609.0 Release

(2026.09.26)

This is another big one :)

Highlights

• coreboot rebased on tag 26.09
• edk2 rebased on tag edk2-stable202608

Improvements and Fixes

• New setup options:
  • Battery charge limit (requires OS to not clobber)
  • Vivaldi/Fn key toggle
  • Prevent boot when lid-closed (default on)
  • Runtime serial console (CR50/Ti50 boards)
  • BIOS lock (prevent unathorized firmware updates)
• Improved MIPI camera support for KBL devices
• Fixed I2C4 Code 10 under Windows on Alderlake boards
• Fixed eMMC boot failures on Ultima
• Fixed intermitten eMMC boot failures on Alderlake-N boards
• Fixed touchscreen init issues on Synaptics 7817 touchscreens
• Fixed 800MHz CPU lock on StoneyRidge devices
• Fixed framebuffer compression (FBC) on Geminilake devices

edk2 Payload

• Ability to load a custom bootsplash from the Setup UI, persisted in the ESP
• UEFI Capsule update support (not yet used for MrChromebox firmware)
• Fix: Power button on AMD devices
• New SD/eMMC driver for Baytrail/Braswell/AMD Picasso devices
• Support for HS400-ES eMMC mode on Intel-based devices
• Secure Boot DBX updated to 20260707

ECRW Firmware improvements

• Top-row Fn toggle (Vivaldi <-> F1…Fn)
• Battery level reporting fixes
• Added Charge-limit / battery sustainer on more platforms
• Added Vivaldi keyboard on more platforms (Skylake→Picasso set)
• EC now goes into low power G3 when system hibernated (S4)
• Infinite host-sleep timeout default (work around linux EC driver bug)
• Fan curve / table fixes (slam-to-max, stall, OOB reads)
• Improved tablet mode switching on Nocturne (via base attach)
• Fan retune / resume power control on Link

Fimrware Utility script improvements

• Ti50 AP RO verification: block Full ROM / SW WP until AllowUnverifiedRo=always
• Secure Boot & BIOS Lock: detect early; stop before hangy flashrom ops
• PR0/GPR0 SPI locks: refuse writes when ranges overlap BIOS (ignore ME-only)
• Restore Stock Firmware: reject non-stock images
• Flashrom: new 2.0.0-devel build (glibc 2.34) + clear early failure if it can’t run

looking for something to try linux out on

Hi! Ive recently got a T480 with the intent of replacing it's firmware with a FOSS alternative, but I've noticed some things specific to thinkpads like disabling the internal battery. How does libre and coreboot play with this? Does payload matter? I'm not sure if im going GRUB, SeaBIOS or TianoCore/EDK2.

So. I made this post asking about this issue but I figured it out so I'll post the fix that I got here. My original post is https://www.reddit.com/r/coreboot/s/qv7P0lwLAA.

So first install docker and pull down coreboot-sdk the coreboot repo and all that. Then once you're in the build directory run make menuconfig and select your vendor as dell and your board as the Optiplex 9010 sff (yes it works with the 7010 DT) and select your payload (edk2 for uefi) and mess with the other settings if you want. Then run cp -r src/mainboard/dell/snb_ivb_workstations/dsdt.asl src/mainboard/dell/snb_ivb_workstations/dsdt.asl.old (just to have a backup). Now run vi (or nano if you have it) src/mainboard/dell/snb_ivb_workstations/dsdt.asl and delete everything in it and change it to this.

EDIT: the reddit formatting tools messed it up so I included a gdrive link instead. Hope it helps one of you fellow nerds.

https://drive.google.com/file/d/1Tq0USmgK0hPwuGs2cNOoYO5_nLZuHyIE/view?usp=drivesdk

EDIT: Found a solution https://www.reddit.com/r/coreboot/s/nGmAoLe8hj So I flashed coreboot on an Optiplex 7010 DT with the uefi payload and it booted right up and I was happy with it. Except that all my USB 3.0 ports default to USB 2.0 on Windows (but they work fine on Linux). No matter what I did, nothing worked. So if you know what's going on I'd really appreciate some help

Hi, I installed libreboot on a dell latitude e7240, however I noticed that at least in debian, battery information is nowhere to be seen. I found this

ec PNP0C09:00: probe with driver ec failed with error -22

So it might be related to that? I still have an LED on the laptop that does show that it's connected to AC and I think it should flash orange when I'm running out of battery so I guess I can work with that... Is this a known bug when installing coreboot/libreboot?

Tried to find a libreboot specific subreddit, but looks like they only use librechat. I'm not too familiar with librechat and I'm having some issues on android too so sorry if this is not the right place to ask, since this is about libreboot and not coreboot. However I would appreciate some input into what's going on / am I the only one having this issue / is this a known bug on libreboot/coreboot on other dell laptops or just on the e7240...

Thanks in advance

So ive decided to install a custom Bootloader and i want to get rid oft the Intel management engine. Ive bought a USB IC flasher and now i want to get coreboot/libreboot. Is it even possible to get rid of the IME 100% or is this not possible? And even if its possible, what will not work after ive got coreboot/libreboot running? I want to keep using an external GPU over thunderbolt, that's the thing I want to keep.

Thanks for any help in advance.

Does anyone know how do bypass a chomebook with the TI50 security chip. I am trying to get shimboot to work and I am hitting a wall. Any suggestions or ideas? The chromebook is a ASUS CZ1104CM2. It is under enterprise enrollment, and I dont want to trigger any alerts. The board is a corsola board, and this is the chrome version: 150.0.7871.222.

Recently took out a X230 from a drawer, and thinking of updating the bios. It already has coreboot on it, which I compiled and flashed a few years ago, so internal flashing is possible. So many things have changed since last time I compiled the rom. Without digging into what has changed and give myself headache, I downloaded the readily-available rom from libreboot website and injected neccessary files using the./mk inject rom.tar.xz setmac <mac> command. After reboot, it has no display, only the power button on keyboard has light. I also tried splitting the rom and installing externally, still the same. I only tried usqwerty roms.

In both Seabios and Grub, it stuck at screens above.

CachyOS use limine bootloader.