Libreboot 26.10 adds full UEFI support and code for 233 Chromebooks

⏱️ Reading time: 10 min

Libreboot 26.10, nicknamed “Ominous Olive,” was released on October 15, 2026, with a change its own community had been debating for years: full UEFI support, enough to install Windows on hardware that until yesterday only ran Linux or BSD with free firmware.

📑 En este artículo

1. TL;DR
2. What Libreboot is
3. What happened in Libreboot 26.10
4. Context and project history
5. Technical details: how UEFI support works in Libreboot 26.10
6. Impact and analysis
7. What’s next
8. Frequently Asked Questions
   1. What does the name “Ominous Olive” for this release mean?
   2. Does Libreboot let you install Windows on a computer with this firmware?
   3. Which of Libreboot’s 233 Chromebooks are actually tested?
   4. What happens to the bare-metal versions of GRUB and SeaBIOS in Libreboot?
   5. What is the AGENTS.md policy that Ominous Olive debuts?
   6. Where can you download Libreboot version 26.10?
9. References

The release also adds 233 Intel and AMD Chromebooks imported from the MrChromebox project and debuts an official policy banning the use of generative artificial intelligence in the firmware’s own development.

TL;DR

• Libreboot 26.10 (Ominous Olive) arrived on October 15, 2026, with full UEFI support via MrChromebox’s EDK2.
• The project imported 233 Intel and AMD Chromebooks from MrChromebox, but only tested the Baytrail model (“Kip”).
• Bare-metal GRUB and SeaBIOS are now deprecated; they now run as EFI builds inside EDK2 for compatibility.
• The release debuts AGENTS.md, Libreboot’s official policy against using AI in its development.
• The 233 new Chromebooks are source code only: there are no binaries, each one has to be compiled individually.

What Libreboot is

Libreboot is the open-source boot firmware that replaces proprietary BIOS or UEFI on compatible Intel, AMD, and ARM64 computers, built on coreboot. Its goal is to eliminate closed firmware from the boot process. Libreboot 26.10 adds the project’s first full UEFI support, making it possible for the first time to install Windows on freed hardware.

The project has been maintained by Leah Rowe since 2013 and is funded through community donations, without relying on a manufacturer. Unlike coreboot, which targets integrators and manufacturers first, Libreboot packages ready-to-use configurations so that someone with no firmware experience can flash their own machine following instructions designed for non-technical users.

What happened in Libreboot 26.10

The release’s core change is the default payload: Libreboot moves from coreboot’s native payload to EDK2, the UEFI implementation maintained by Tianocore that MrChromebox already uses to provide UEFI support for Chromebooks. Libreboot takes that same payload, changes the background color to its signature purple, and swaps the coreboot logo for its own, but keeps standard UEFI behavior, including compatibility with Windows installers.

GRUB and SeaBIOS don’t disappear: they now live inside EDK2 as EFI applications that the user selects at boot with the ESC key, alongside MemTest86+ and iPXE on boards that already supported them. The “bare metal” versions of GRUB and SeaBIOS, meaning the ones that ran directly as a coreboot payload without going through EDK2, are marked deprecated in this release. The changelog warns they could be removed in a future version, though they’ll remain available for anyone who compiles Libreboot from source.

This release also imports 233 Intel and AMD Chromebooks already supported by MrChromebox, ranging from Haswell-based models to the most recent ones on both architectures. The full list of boards is too long to summarize in a paragraph, but the official changelog details it board by board. Important: this batch of 233 machines ships as source code only, with no precompiled binaries, and of all of them only the Baytrail model known as “Kip” was tested by the Libreboot team before launch.

Context and project history

MrChromebox is, in practice, the coreboot branch specialized in Chromebooks maintained by an independent developer using that same handle, and it’s the one most Chromebook users already use without realizing it when they enable developer mode. Libreboot clarifies in its own changelog that this integration is not a fork of MrChromebox, but rather treats that project as its “upstream” for Chromebooks, the same way it treats coreboot as upstream for the rest of the hardware it supports.

To import 233 boards at once, Libreboot built an internal tool called mrimport, which automatically generates the configurations, revisions, and submodules needed within its build system (lbmk) from the MrChromebox tree. According to the changelog, this lets future updates sync by comparing successive versions of that same tool instead of rebuilding each board by hand.

This release’s changelog is measured against the previous one, Libreboot 26.01. Following the year-month scheme the project uses to number its versions, that would place that release in January 2026, about nine months before this one.

Technical details: how UEFI support works in Libreboot 26.10

The jump to UEFI isn’t just about changing a boot menu. First, coreboot still does what it always did: it initializes the memory controller, the CPU, and the rest of the low-level hardware. Only after that does coreboot hand off control to EDK2 instead of handing it directly to GRUB or SeaBIOS as in previous releases. That order is what lets a Windows installer see a standard UEFI interface and boot without additional patches.

The second relevant mechanism is how the Intel Management Engine (ME) is handled. Libreboot sets the so-called “HAP bit” at compile time, an Intel platform flag that disables the ME more reliably than the software flashing scripts typically used by the MrChromebox community, which depend on the user running the right step at the right time. By setting it during the build, Libreboot guarantees the ME is disabled before the image leaves compilation, without depending on a later manual step.

⚠️ Heads up: of the 233 imported Chromebooks, Libreboot only tested the Baytrail model (“Kip”) before publishing the release. The rest compile without test binaries, so it’s worth checking your own board’s status in the repository before flashing hardware that’s hard to recover.

The third mechanism is unlocking the Intel Flash Descriptor (IFD) regions via ifdtool, configured to be left in read-write mode during the build process itself. Before, every flash descriptor that came from MrChromebox had to be edited by hand, and since there are hundreds of variants across the 233 models, doing it board by board wasn’t feasible. Automating that step is, in effect, what made it possible to import the entire catalog at once.

Finally, on Intel Chromebooks up through the Kaby Lake generation, Libreboot uses libgfxinit instead of the GOP (Graphics Output Protocol) that MrChromebox ships by default. libgfxinit is coreboot’s open-source library for initializing video output without relying on an Intel binary blob; the changelog notes they’ll integrate the same change for newer generations in an upcoming release, once MrChromebox finishes adopting it.

flowchart TD
A["CPU boots"] --> B["coreboot initializes hardware"]
B --> C["EDK2 payload"]
C --> D["ESC menu: GRUB EFI, SeaBIOS CSM, MemTest86+"]
C --> E["Operating system: Linux, BSD, or Windows"]

Impact and analysis

That a project born to erase proprietary firmware ends up enabling Windows, the proprietary operating system par excellence, is the most discussed paradox of this release. Leah Rowe resolves it in the changelog itself by separating the goal from the means: Libreboot is still free firmware, but free firmware no longer requires the operating system on top of it to be free too. It’s a pragmatic compromise, not a change of mission, and the project is betting that more users will try hardware with auditable firmware if that hardware can also run the operating system they already use every day.

The second strong signal in this release arrives before any line of code: a new file, AGENTS.md, inside Libreboot’s build system (lbmk), with a policy explicitly against using generative artificial intelligence in the project’s development. The announcement itself describes it as the most important change in the release, ahead even of UEFI support. In an ecosystem where more and more firmware and kernel projects accept AI-assisted patches, Libreboot chooses the opposite stance precisely in the area where trusting someone else’s code (ME binaries, GOP blobs, third-party firmware) was already the original problem the project was created to solve.

💭 Key takeaway: Libreboot clarifies that this integration with MrChromebox is not a fork: it treats that project as upstream, the same way it treats coreboot for the rest of the hardware, and plans to keep syncing changes release after release.

For anyone managing fleets of recycled Chromebooks, the expansion to 233 boards suddenly multiplies the universe of hardware eligible to run desktop Linux with auditable firmware instead of the factory firmware aimed at ChromeOS. The practical limit, once again, is that almost the entire catalog arrives without binaries: it has to be compiled from source, which still filters out a large share of the non-technical users that Libreboot’s own mission says it prioritizes.

What’s next

The changelog leaves two explicit tasks for after launch. The first is finishing the integration into Libreboot of the CBFS-based VBT and GOP handling that Leah Rowe requested from MrChromebox and that project has already implemented in its own tree; it still needs to be ported to Libreboot. The second is extending libgfxinit to Intel generations after Kaby Lake once MrChromebox finishes that work on its own branch.

Beyond that, the biggest task is left to the community: of the 233 imported Chromebooks, the vast majority still has no public confirmation that it boots correctly with the new image, beyond compiling without errors. Until real users test each model and report results, “official” support for much of the catalog remains, in practice, unverified support.

Try it yourself: download the image for your board from rsync.libreboot.org/stable/26.10/ or check the full changelog at libreboot.org before flashing.

Frequently Asked Questions

What does the name “Ominous Olive” for this release mean?

It’s the internal codename Libreboot assigns to each major version, as it has done in previous releases (for example, Libreboot 26.01). It doesn’t change any firmware functionality: it’s just the release’s code name.

Does Libreboot let you install Windows on a computer with this firmware?

Yes, starting with this release, because the EDK2 payload exposes a standard UEFI interface that Windows installers recognize just like on a commercial motherboard. Before, Libreboot only offered coreboot payloads without UEFI, incompatible with official Windows installers.

Which of Libreboot’s 233 Chromebooks are actually tested?

According to the changelog, only the Haswell-CPU model known as Baytrail “Kip” was verified by the Libreboot team before launch. The rest of the catalog compiles from source, but still without public confirmation of successful booting.

What happens to the bare-metal versions of GRUB and SeaBIOS in Libreboot?

They’re marked deprecated. They still work and can be compiled from source, but the changelog warns they could be removed in a future version of the project.

What is the AGENTS.md policy that Ominous Olive debuts?

It’s a new file inside Libreboot’s build system (lbmk) that sets an official stance against using generative artificial intelligence to write the firmware’s own code. The changelog presents it as the most important change in the release.

Where can you download Libreboot version 26.10?

From rsync.libreboot.org/stable/26.10/ or any of the mirrors listed on Libreboot’s official site.

References

• Libreboot.org: official changelog for release 26.10 “Ominous Olive,” signed by Leah Rowe on October 15, 2026.
• Libreboot.org: the project’s official site, with installation documentation and the full list of supported hardware.
• Coreboot.org: the free firmware project Libreboot is based on.
• MrChromebox.tech: the independent Chromebook firmware project Libreboot uses as upstream in this release.

📱 Enjoying this content? Follow @programacion on Telegram for daily tech content in Spanish: quick summaries, fresh content every day.

Featured image: Foto de Albert Stoynov en Unsplash