Libreboot 26.10 Brings EDK2 UEFI and Windows 11 Boot Support to Legacy PCs

Following more than eight months of development since the previous Libreboot 26.01 release in January, the open-source BIOS and UEFI replacement project has executed a massive architectural shift. As reported by Linuxiac and 9to5Linux, and detailed in the official release notes by Libreboot founder and lead developer Leah Rowe, Libreboot 26.10 transitions almost all supported 64-bit Intel and AMD hardware to an EDK2-based UEFI payload by default. Alongside that foundational rewrite, the release adds new desktop, laptop, and server mainboards, imports 233 Intel and AMD Chromebook configurations into its build system, overhauls AMD Family 15h initialization, and enables modern PCIe graphics card support.

Why does a traditionally Linux- and BSD-centric firmware project suddenly matter so much to the wider PC and Windows hardware community? Because firmware is the ultimate gatekeeper of PC longevity. By embracing a standard, battle-tested UEFI implementation, Libreboot is no longer just a niche shelter for legacy ThinkPads running minimalist Linux setups—it is now a viable, customizable, open-source firmware platform capable of booting Windows 10 and Windows 11 alongside modern UEFI-native Linux and BSD installations.

The EDK2 Revolution: Full UEFI Comes to Libreboot​

Historically, Libreboot relied primarily on bare-metal GRUB or SeaBIOS payloads to hand off control from coreboot hardware initialization to the operating system, with U-Boot offering lightweight UEFI capabilities on a small subset of boards. While GRUB and SeaBIOS served legacy BIOS workflows and traditional Linux distributions well, modern operating systems and bootloaders increasingly expect a compliant Unified Extensible Firmware Interface (UEFI) environment.

In Libreboot 26.10, the project adopts EDK2 ( specifically version 26.09.2, utilizing a fork maintained by MrChromebox adapted as a generic coreboot payload) as the default payload across virtually all 64-bit-compatible Intel and AMD mainboards equipped with at least 4 MB of flash storage. Even classic 64-bit machines at the older end of Libreboot's compatibility list—such as the Lenovo ThinkPad X200, T400, and T500—now run EDK2 by default, all the way up to Intel Kaby Lake systems like the ThinkPad T480 and Dell OptiPlex 5050. Only older, strictly 32-bit mainboards retain the previous bare-metal SeaBIOS and GRUB configuration.

According to the project's testing documentation in the Libreboot 26.10 release notes, this transition immediately unlocks broad operating system compatibility:

• Microsoft Windows: Both Windows 10 and Windows 11 have been tested and confirmed to boot on supported platforms via the EDK2 payload.
• Modern Linux Boot Paths: Systems can now utilize systemd-boot and Unified Kernel Images (UKIs) directly without relying on a flashed GRUB payload.
• BSD Systems and Niche OSes: FreeBSD in UEFI mode, OpenBSD using an EFI bootloader with GPT partitioning, and Plan 9 fork 9front have all been verified to work. (ReactOS, which currently lacks UEFI support in this configuration, did not boot in project testing, while RedoxOS remains untested).

Beyond sheer OS compatibility, the move to EDK2 introduces quality-of-life features that PC builders and enterprise administrators take for granted on commercial boards:

• Persistent Settings via SMMSTORE: Enabled by default on all EDK2 targets, SMMSTORE allows users to enter a standard setup interface at boot and save changes—such as modifying the boot order—persistently inside flash without having to recompile and reflash the entire firmware ROM.
• TPM Activation: Trusted Platform Module (TPM) support is now enabled where hardware is available across all targets utilizing EDK2—a crucial prerequisite for modern Windows 11 security features and measured boot workflows.
• Network Booting: An iPXE boot method is now accessible directly through the EDK2 boot menu by pressing ESC at startup.
• Simplified Firmware Access: Users booting via the included EFI GRUB option can use a new fwsetup menu entry to reboot straight back into the EDK2 configuration utility.

Section Summary: By making MrChromebox's EDK2 fork the default payload on 64-bit systems with 4 MB or more of flash, Libreboot 26.10 brings industry-standard UEFI boot capabilities, persistent SMMSTORE settings, TPM enablement, and verified Windows 10/11 support to nearly its entire x86_64 hardware roster.

Backward Compatibility, Migration Caveats, and the "Missing Core" Quirk​

Whenever a firmware project replaces its foundational boot payload, existing users rightly worry whether an update will leave their current operating system unbootable. Libreboot 26.10 addresses this by bundling EFI builds of both GRUB (updated to version 2.16) and SeaBIOS CSM (via CSMWrap) directly inside the EDK2 flash image.

If you have an existing legacy Linux or BSD installation that expects Libreboot's classic boot behavior, you do not have to wipe your drive immediately. By pressing ESC when prompted during startup, you can select the EFI GRUB build or SeaBIOS CSM from the EDK2 menu. The EFI GRUB build is engineered to mimic Libreboot's former coreboot-payload GRUB, retaining the ability to parse configurations from CBFS (coreboot filesystem) and using a simplified single-entry loop that tries USB storage first.

However, migrating to 26.10 comes with important technical caveats that every administrator and tinkerer should review before running a flash utility:

1. The CSMWrap CPU Core Penalty: While SeaBIOS CSM is included via CSMWrap for legacy BIOS compatibility, Libreboot's release notes warn of a major current limitation: CSMWrap hogs an entire CPU core at boot time. On a quad-core processor, booting via CSMWrap will cause the system to appear as a three-core machine inside Linux. Until a future release resolves this design limitation, the project strongly recommends migrating to native UEFI boot with an EFI System Partition (ESP), or using the GRUB EFI compatibility option, which does not suffer from the core-hogging bug.
2. FreeBSD Legacy Text Mode Limitations: FreeBSD users who rely on legacy BIOS-mode bootloaders require VGA text mode, which conflicts with coreboot's standard framebuffer initialization when using compatibility wrappers. Unless users manually compile coreboot from source with Legacy VGA text mode enabled, FreeBSD users are advised to perform fresh UEFI-mode installations booted directly through EDK2.
3. Keyboard Layout Changes: Because EDK2 input drivers now handle both USB and PS/2 keyboards and pass console input to EFI GRUB, pre-compiled ROM images with separate language keymaps are no longer distributed. While MrChromebox's upstream EDK2 defaults to a US QWERTY layout, Libreboot—being a UK-based project—patched its EDK2 build to default to UK QWERTY across the board, with plans to add a persistent graphical locale and keymap selector via HiiDatabase and SMMSTORE in a future update.
4. Removal of SeaGRUB: On the few older boards that still rely on bare-metal payloads, the combined "SeaGRUB" arrangement has been permanently retired in favor of separate standalone GRUB or SeaBIOS images.

Section Summary: Existing setups can still boot via integrated EFI GRUB and SeaBIOS CSM payloads accessed with the ESC key, but users should avoid SeaBIOS CSM (CSMWrap) where possible because it currently consumes a full CPU core during operation.

Hardware Expansion: 233 Chromebooks and New PC Targets​

Hardware support takes a massive leap forward in Libreboot 26.10, though one headline figure requires careful context for anyone looking to download a ready-made ROM.

Using a new automated import utility (util/mrimport) created by Rowe, Libreboot 26.10 imports 233 Intel and AMD Chromebook board configurations from the MrChromebox coreboot distribution into Libreboot's lbmk build system. Rather than forking MrChromebox's work, Libreboot treats it as an upstream source for x86 Chromebooks.

However, as Linuxiac points out and the official release notes emphasize, all 233 Chromebook configurations are strictly source-only in this release. Prebuilt binary ROMs are not provided for them on the download mirrors; users must compile the images themselves using the lbmk build system. Furthermore, only the Intel Bay Trail-based HP Chromebook 11 G3/G4 ("Kip") platform has been hardware-tested by the project so far, meaning the remaining 232 configurations require community testing and validation.

Outside the Chromebook ecosystem, Libreboot 26.10 adds full prebuilt release support for several popular business desktops, ThinkPads, and server/workstation boards:

Two engineering details on the desktop and server side stand out for hardware enthusiasts:

• Supermicro X11SSH-F Fast Booting: Server boards like the X11SSH-F typically utilize Intel Server Platform Services (SPS) firmware. In Libreboot 26.10, contributor Ron Nazarov configured the board to use regular Intel Management Engine (ME) firmware neutered via the deguard utility (which also bypasses Intel Boot Guard restrictions on supported boards). While this requires a slightly larger flash allocation for the ME region, it allows Memory Reference Code (MRC) caching to function properly—meaning the motherboard caches its RAM training data and reboots rapidly instead of retraining memory on every single startup.
• Kaby Lake CPU Pin-Mod Support: Kaby Lake motherboards in this release received an Intel Flash Descriptor (IFD) modification that allows hardware modders to run six-core and eight-core Intel Coffee Lake CPUs via physical pin modifications.

Section Summary: Libreboot 26.10 adds prebuilt firmware for the ThinkPad X270, ThinkPad X280, Dell OptiPlex 5050 SFF, Dell OptiPlex 3040 Micro, and Supermicro X11SSH-F (while re-enabling the ThinkPad X301), alongside 233 source-only Chromebook build targets imported from MrChromebox.

Modern GPU Support, Resizable BAR, and AMD Family 15h Overhaul​

For desktop and workstation users, running open-source firmware used to mean accepting severe limitations on discrete graphics cards. With EDK2 in place, Libreboot 26.10 enables PCIe Option ROM execution by default where necessary on desktop boards, and introduces support for modern GPUs that require PCIe memory allocations above the 4 GB boundary when paired with PCIe Resizable BAR (ReBAR).

There is a catch to keep in mind before installing a modern graphics card: Resizable BAR is disabled by default in prebuilt images. During testing on machines like the Dell OptiPlex 9020 SFF and 5050 SFF, developers discovered that enabling ReBAR broke integrated Intel GPU display output during the boot payload phase when using coreboot's native libgfxinit video initialization. Even when that payload display bug occurs, Linux's i915 kernel driver still properly initializes the display once the OS loads via KMS/DRM, or users can bypass it by inserting an external graphics card. Advanced users running discrete-GPU-only setups can manually enable ReBAR in coreboot's menuconfig when compiling from source.

Meanwhile, owners of classic AMD Family 15h workstation and server hardware—such as the dual-socket ASUS KGPE-D16 and single-socket KCMA-D8—get what Rowe describes as the first truly reliable initialization for these boards. Libreboot dropped its aging coreboot 4.11_branch tree (which relied on custom initialization code) and switched to the community-maintained 15h.org coreboot fork. By utilizing AMD AGESA source code, the new implementation dramatically improves CPU and memory controller initialization, supports larger RAM capacities, and resolves longstanding bugs with IOMMU virtualization and TPM hardware. Note that because the onboard ASPEED AST2050 graphics chip on these server boards only starts in text mode without a proprietary VGA ROM, prebuilt binaries for the KGPE-D16 and KCMA-D8 still ship with SeaBIOS and GRUB payloads, while experimental EDK2 images (intended for use with add-in graphics cards) must be compiled from source.

Section Summary: Desktop targets gain PCIe Option ROM support and above-4G memory capability for modern graphics cards, while AMD Family 15h server boards benefit from a far more stable AGESA-based coreboot fork from 15h.org.

Why U-Boot Was Dropped on x86—and Libreboot's Anti-AI Stance​

One of the most outspoken sections of the Libreboot 26.10 release notes explains why EDK2 didn't just join U-Boot on x86 hardware, but completely replaced it. (U-Boot remains in use solely on ARM64 Chromebooks, held at an early 2025 revision because a late-2026 upstream update broke the bootflow menu UI).

Rowe originally envisioned U-Boot becoming Libreboot's primary lightweight UEFI payload on x86. However, Libreboot 26.10 introduces a strict, project-wide anti-AI policy codified in a new AGENTS.md file inside its build repository—a policy Rowe explicitly labels "the most important change in the release". According to the release notes, the developer primarily responsible for maintaining the x86 coreboot payload fork of U-Boot began heavily utilizing AI "vibe-coding" to generate patches and pressured upstream maintainers to merge the AI-generated code.

Combined with existing stability issues in x86 U-Boot, the Libreboot project declared U-Boot a liability on x86 architectures and pivoted entirely to Intel-originated EDK2 code. Looking further ahead, Rowe noted that Libreboot may eventually integrate CrabEFI—a Rust-based UEFI implementation designed to minimize memory-safety bugs—once Rust compiler tooling stabilizes across Linux and BSD distributions, while continuing to rely on pure C-based EDK2 for its predictable compiler behavior and maturity today.

From an industry perspective, this highlights a growing fault line in open-source infrastructure and systems programming. While major commercial tech vendors are racing to embed generative AI into every layer of software development, foundational firmware and kernel maintainers are increasingly pushing back over concerns regarding code auditability, licensing hygiene, maintainer trust, and subtle bugs in low-level memory initialization. Whether or not a user shares Rowe's broader political critique of artificial intelligence, the practical engineering outcome for Libreboot users is clear: swapping a buggy, contested x86 U-Boot implementation for MrChromebox's battle-tested EDK2 payload makes the firmware vastly more capable today.

Section Summary: Libreboot removed U-Boot on x86 machines and enacted a strict ban on AI-generated code via its new AGENTS.md policy, favoring the proven stability of C-based EDK2 while keeping an eye on Rust-based CrabEFI for the future.

Practical Precautions Before You Flash​

If the prospect of running open-source UEFI firmware with Windows 11 or Linux on a refurbished ThinkPad T480 or OptiPlex desktop has you reaching for a flash utility, keep Libreboot's core installation safety rules front and center:

1. Always Back Up Your Current Flash First: Whether you are overwriting factory vendor BIOS or upgrading from Libreboot 26.01 to 26.10, always read and verify multiple dumps of your existing SPI flash chip using flashprog -p internal -r dump.bin (and compare their SHA-1 checksums) before writing a single byte.
2. Prepare an External SPI Flashing Setup: While existing Libreboot installations (that haven't locked down their flash) and certain desktops with service-mode jumpers can be flashed internally from a running Linux or BSD environment, firmware flashing carries an inherent risk of bricking the board if interrupted. Libreboot's installation documentation strongly advises having a working external SPI hardware flasher (such as a SOIC clip or probe setup) on hand before attempting internal upgrades.
3. Inject Vendor Files When Using Prebuilt ROMs: If you download prebuilt binary images from Libreboot's 26.10 stable mirrors rather than compiling from source, remember that certain boards require vendor microcode, Intel Management Engine regions, or HP Embedded Controller (EC) firmware to be injected into the ROM image prior to flashing, as well as setting your board's Gigabit Ethernet MAC address via nvmutil on Intel Flash Descriptor platforms.
4. Verify Your OS Boot Mode: Before updating an existing Libreboot machine to 26.10, check whether your installed OS uses legacy MBR/BIOS booting or UEFI with an EFI System Partition. Be prepared to press ESC at startup to select the GRUB EFI compatibility payload—or convert your bootloader to native UEFI—so you aren't caught off guard by the new default boot path.

Libreboot 26.10 "Ominous Olive" is available now via the project's official stable release directories and rsync mirrors, complete with updated toolchains including GCC 15.2, binutils 2.46.1, NASM 3.02, and a सितंबर 2026 revision of flashprog. For hardware enthusiasts who believe they should own every layer of their PC from the silicon up—without giving up the ability to boot Windows 11 or modern UEFI operating systems—open-source firmware just took its biggest step forward in years.