What Is Coreboot and How Does It Relate to Libreboot?

Coreboot is free, open source boot firmware that initialises a computer's hardware and then hands control to a separate program called a payload, which boots your operating system. Libreboot is not a fork of coreboot — it is a coreboot distribution, in the same way Debian is a Linux distribution. In practice this means Libreboot takes coreboot, adds a set of payloads and build tooling, and ships it as a ready-to-flash image for specific Intel/AMD x86 and ARM motherboards. If you want to understand the mechanism, learn coreboot. If you want firmware you can install on supported hardware without assembling it yourself, a distribution like Libreboot is usually the practical route.

What coreboot actually does

Boot firmware runs before your OS. On most machines that job is done by a proprietary BIOS/UEFI. Coreboot replaces that layer with free software and splits the work in two:

1. Hardware initialisation — coreboot sets up the memory controller, CPU and peripherals so the machine is usable.
2. Payload handoff — coreboot then jumps to a payload stored in the boot flash, and the payload boots the operating system.

This split is the key idea. Coreboot itself is not a bootloader and does not present a boot menu on its own; that is the payload's job.

The coreboot-plus-payload model

Because coreboot only initialises hardware, what you actually see at boot depends on which payload is included. Common payloads include:

A single firmware image can bundle several of these and let you pick one at boot time. That is exactly the design Libreboot uses: it incorporates GRUB and SeaBIOS payloads on x86/x86_64 Intel/AMD boards, a U-Boot UEFI payload on ARM64 boards, and enables an x86/x86_64 EDK2 UEFI payload by default on most boards.

Why Libreboot is a distribution, not a fork

The distinction matters when you are deciding what to install.

• A fork takes the original project's code and develops it separately, diverging over time.
• A distribution packages an upstream project — coreboot — together with payloads, configuration and build tooling, and releases it as a usable product.

Libreboot states plainly that it is not a fork of coreboot. It provides coreboot for machine initialisation, then jumps to a payload in the boot flash. The value it adds is making coreboot easy to use for people who are not firmware developers: preconfigured images, a defined set of payloads, and documentation.

What hardware and operating systems are supported

Libreboot targets specific Intel/AMD x86 and ARM-based motherboards, including laptops and desktops. Linux, BSD and Windows are all described as well-supported, with the EDK2 UEFI payload being what makes near-universal booting possible on x86.

The word to note is specific. Coreboot and its distributions support a defined list of boards, not arbitrary hardware. Before planning an install, confirm your exact motherboard or laptop model is supported — this is the single most common blocker.

Choosing coreboot directly vs. a distribution

Both paths use the same underlying firmware. The difference is how much work you take on.

Choose coreboot directly if:

• You want to build from source and control every configuration choice.
• Your board is supported by coreboot but not by any distribution.
• You are developing or porting firmware and need upstream code.

Choose a distribution like Libreboot if:

• You want a prebuilt image for a supported board.
• You want multiple payloads bundled and selectable at boot without assembling them yourself.
• You value continued firmware updates that let you keep using existing hardware.

For most people replacing a proprietary BIOS on a supported machine, the distribution route removes the build step entirely. Libreboot also notes that preinstalled hardware and preinstallation services are available from Minifree Ltd on select hardware, and that sales fund the project — worth knowing if you would rather buy a ready machine than flash one yourself.

Practical next steps

1. Check support first. Look up your exact board in the distribution's supported hardware list. No match means no install.
2. Decide source vs. prebuilt. If you are not building from source, use a released image rather than assembling coreboot and payloads manually.
3. Pick your payload. For Linux/BSD, GRUB or SeaBIOS; for Windows or broad compatibility on x86, the EDK2 UEFI payload; for ARM64, U-Boot.
4. Verify after flashing. Confirm the machine initialises, the payload menu appears, and your OS boots — that sequence proves both halves of the coreboot-plus-payload model are working.

The mental model to keep: coreboot is the engine that wakes the hardware; the payload is what actually starts your operating system; and Libreboot is one convenient way of getting both onto a supported machine.