Why Replace Proprietary BIOS and UEFI with the Fully Free GNU Boot Firmware

The Free Software Foundation announced in September 2026 that it is providing financial and legal support to the GNU Boot project, which aims to deliver a completely open-source replacement for traditional BIOS and UEFI firmware. GNU Boot builds on coreboot to initialize hardware at boot time and layers a free bootloader such as GRUB or SeaBIOS on top, ensuring no proprietary binary blobs are required. The initiative emerged after a 2022 split from Libreboot, which began accepting closed-source components to broaden hardware support, while GNU Boot strictly adheres to GNU licensing criteria that prohibit any non-free code. Supported platforms remain limited to older systems from roughly 2008–2012, including specific ThinkPad models, certain early Apple MacBooks, and a handful of AMD and Intel desktop boards, because newer Intel Boot Guard and AMD equivalent mechanisms enforce signed firmware that prevents unsigned replacements. Closed firmware from Intel Management Engine and AMD Platform Security Processor runs before the main operating system, possesses unrestricted memory access, and cannot be audited or disabled on most modern hardware. By offering reproducible builds and clearer installation instructions, GNU Boot seeks to lower the barrier for users who want to eliminate potential backdoors, Wi-Fi whitelist restrictions, and forced updates found in vendor firmware.

HabrTranslated from Russian

Read at source

The Free Software Foundation took the GNU Boot project under its wing in September 2026, providing both financial backing and legal support for the effort to create a fully free firmware replacement for conventional BIOS and UEFI.

When a computer powers on, the motherboard firmware is the first code to execute. It initializes memory, the CPU, controllers, and the video adapter before handing control to the bootloader. Almost all current implementations are distributed only as closed binaries, making inspection or modification difficult and often blocked by hardware or cryptographic protections.

Security and Freedom Concerns with Closed Firmware

Modern Intel and AMD processors contain autonomous subsystems—Intel Management Engine and AMD Platform Security Processor—that start before the main operating system. These components have full access to system memory and sometimes network interfaces, yet their code remains entirely proprietary. Users must trust vendors regarding the absence of vulnerabilities or intentional backdoors.

Additional problems include manufacturer-imposed Wi-Fi whitelist restrictions, blocked boot-device selection, and automatic firmware updates that cannot be rolled back. These behaviors have been documented on devices from several vendors, notably HP.

What GNU Boot Provides

GNU Boot is a ready-to-flash firmware image built exclusively from free software components. The hardware-initialization layer is supplied by coreboot, while the bootloader is typically GRUB or SeaBIOS. The project was founded in 2022 by Denis Karikli and Adrien Bourma after a community split from Libreboot, which began accepting binary blobs to increase hardware compatibility. GNU Boot follows strict GNU criteria that forbid any non-free code or build tools.

Comparison with Related Projects

coreboot offers broad device support but often requires closed blobs for video initialization or Management Engine components on many platforms. Libreboot supplies pre-built images and simpler installation procedures yet permits proprietary modules for wider hardware coverage. GNU Boot rejects such compromises, resulting in a narrower but fully free set of supported systems.

Currently Supported Hardware

  • ThinkPad X200, X200s, X200 Tablet, T400, T500, X60 series
  • Early Apple models: MacBook 1.1, 2.1 and iMac 5,2
  • AMD Family 15h boards such as KGPE-D16 and KCMA-D8
  • Selected desktop boards including GA-G41M-ES2L and D945GCLF
  • Limited experimental server configurations

Newer platforms after 2013–2014 are generally unsupported because Intel Boot Guard and equivalent AMD mechanisms verify firmware signatures before execution, and open-source memory initialization code does not exist for recent chipsets.

While widespread adoption of fully free firmware remains distant, initiatives such as Google’s use of coreboot in Chromebooks and offerings from certain Linux-focused laptop vendors demonstrate growing interest. If demand increases, manufacturers may begin designing boards with open firmware in mind.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Privacy & Surveillance

Maximizing iPhone Privacy: Essential Settings to Enable, Disable, and Verify Immediately
Top 10 Secure DNS Servers for Privacy, Threat Blocking and Ad Filtering in 2026
WebRTC IP Leaks Explained: Why Disabling the Protocol Harms Anonymity in Anti-Detect Browsers