FSF Backs GNU Boot in Push for Fully Free Computer Firmware

The Free Software Foundation has added another project to its fiscal sponsorship roster. On September 14, 2026, the organization announced that GNU Boot now sits alongside efforts such as GNU Guix inside the Working Together for Free Software Fund. The move brings stable funding, legal structure and wider visibility to a small team determined to erase the last proprietary layer from ordinary computers.

Almost every machine sold today ships with nonfree BIOS or UEFI code. It runs first. It configures memory, initializes hardware, then hands control to the operating system. For decades that early code stayed hidden. Manufacturers treated its binaries as trade secrets. Users received no source, no right to modify, no guarantee the software did only what the manual claimed. The FSF has long called this situation unacceptable. Its campaign page traces the problem back to the earliest IBM PCs. Back then the BIOS lived in mask ROM. Replacement meant swapping chips. The obstacle felt physical, therefore tolerable. Flash memory changed the equation. Suddenly the same ethical breach that applies to Windows or Photoshop applied to the code that boots the machine.

GNU Boot offers one answer. It is not a single new program. The project packages, patches and distributes existing free components: Coreboot for hardware initialization, GRUB as the payload that loads the operating system, SeaBIOS for legacy compatibility. Think of it as a distribution in the same sense that Trisquel or Guix System are distributions. The maintainers audit every binary blob, remove what they can, document the rest. They emphasize reproducible builds so that two independent teams compiling the same source obtain identical firmware images. That practice mirrors the discipline already established inside GNU Guix.

Zoë Kooyman, executive director of the FSF, described the stakes plainly. “The BIOS is a delicate but essential part of software freedom for computing today,” she said in the September announcement. “GNU Boot aims to make sure that we can continue using our computers in freedom. With the way it builds on the work of others to replace UEFI, we know it can remain firm in the free software philosophy and stay vital to digital autonomy and user freedom.”

The project traces its roots to 2022. Denis “GNUtoo” Carikli and Adrien “neox” Bourmault founded it after watching earlier efforts fracture. Libreboot, once recommended by the FSF, later relaxed its no-blob policy to support more hardware. Canoeboot, maintained in parallel by Leah Rowe, kept a stricter line yet remained independent. GNU Boot chose to stay inside the strictest definition of free software while still aiming for practical installation. Its long-term ambition is modest on paper but ambitious in practice: let ordinary users flash their firmware without first mastering domain-specific skills. The same promise free operating-system distributions made two decades ago now extends to the code that runs before the kernel loads.

Adrien Bourmault welcomed the sponsorship. “Making this decision with the FSF allows us to focus more on what we do best: writing and debugging code that keeps our machines fully free,” he told the organization. The benefits flow both ways. Fiscal sponsorship gives GNU Boot access to the FSF’s nonprofit status, donation processing, and governance tools. In return the FSF gains another concrete example of its principles applied to the lowest layers of the computing stack. Donations marked for GNU Boot flow directly to the project while the FSF handles receipts and reporting. The arrangement mirrors the support already extended to GNU Toolchain and other initiatives listed in the fund.

But the road remains narrow. Coreboot itself advances. A late-September 2026 release added support for dozens of new motherboards, yet many still require binary blobs for critical functions such as memory training on recent Intel and AMD platforms. GNU Boot can only ship what upstream makes fully free. That constraint limits compatible hardware to older ThinkPads, certain desktop boards, and a handful of servers. The FSF itself once relied on donated IBM machines that resisted free firmware. Over time technical workarounds appeared. Today every computer at FSF headquarters runs free boot code. That outcome was not inevitable. It required years of reverse engineering, persistent pressure on vendors, and the patient assembly of distribution layers like GNU Boot.

Recent coverage has been light. Slashdot picked up the announcement on October 4, repeating the FSF’s language and noting the project’s similarity to free GNU/Linux distributions. Tux Machines mirrored the full press release the day after the original statement. No major new technical breakthroughs appeared in the weeks since. On X, the FSF’s own post generated modest engagement, mostly among existing free-software accounts. The conversation has not yet broken out of familiar circles. That may change if the project can expand its hardware list without compromising its principles.

Reproducibility stands out as a quiet strength. By insisting on bit-for-bit identical builds, GNU Boot reduces the chance that a compromised mirror or malicious build server slips altered code into users’ machines. The same technique protects Guix users from supply-chain attacks higher in the stack. Applied to firmware it addresses a threat class many administrators still treat as theoretical. Firmware lives below the operating system. It can reflash itself, hide in System Management Mode, or exfiltrate keys before the first line of kernel code executes. Free software cannot magically solve every silicon-level backdoor. It does remove the vendor’s unilateral ability to push updates or insert behavior without public review.

Critics sometimes dismiss these efforts as quixotic. Why chase perfect freedom on 2012-era hardware when cloud instances, locked-down phones, and signed bootloaders dominate the market? The counterargument is straightforward. Control at the lowest layer sets the tone for everything above it. An organization that cannot verify the first instructions executed on its own metal cannot claim full sovereignty over its data. Governments and large enterprises have begun to notice. Some now require open-source firmware on critical servers. Others simply want an audit trail that proprietary BIOS vendors will never provide. GNU Boot, though small, supplies one more practical option for those demands.

The sponsorship also signals continuity. The FSF has promoted free BIOS work since the early 2000s. It certified refurbished laptops running Libreboot under the Respects Your Freedom program, then updated its recommendations when that project shifted direction. GNU Boot now occupies the recommended slot for users seeking the strictest policy. The organization’s October 2026 newsletter listed the sponsorship alongside hiring notices and an essay on GitHub’s shortcomings. The message is consistent: free software must remain uncompromising at every level, from the bootloader to the desktop environment.

Practical adoption still hinges on documentation and ease of installation. Flashing firmware has historically frightened non-experts. One wrong command can brick a laptop. GNU Boot’s maintainers hope that clearer guides, better scripts, and eventual integration with graphical tools will lower that barrier. They study how Guix and Trisquel made complex package management approachable for new users. The same lessons could apply here. If they succeed, the phrase “free your BIOS” might move from activist slogan to routine checklist item for anyone installing a fresh operating system.

Plenty of obstacles remain. New chipsets grow more complex. Memory controllers hide more microcode. Vendor lock-in appears in management engines and firmware update mechanisms. Yet each year the list of supported boards inches longer. Coreboot’s September update demonstrated continued momentum. GNU Boot can ride that wave while filtering out nonfree components. The fiscal sponsorship supplies oxygen for that filtering work: paid time for auditing, testing, and upstream contributions instead of weekend labor alone.

And the stakes feel more concrete now than in the days of mask ROM. Modern firmware can phone home, enforce remote attestation, or refuse to boot unsigned operating systems. Those features are marketed as security. To many in the free-software community they look like control. GNU Boot cannot disable every such feature on every board. It can at least let technically capable users choose hardware where those features are absent or removable. That choice, once rare, is becoming a deliberate part of procurement decisions in certain niches.

The FSF’s decision to sponsor GNU Boot therefore fits a larger pattern. It invests in the pieces that sit beneath the operating system because those pieces determine the meaning of freedom on the devices people actually use. Without them the GNU operating system Richard Stallman envisioned decades ago would still run atop secret code. With them the vision edges closer to reality, one reproducible firmware image at a time.