Binary Blob Extermination Policy

Leah Rowe in GNU Leah Mode

10 January 2025


Return to index

Article published by: Leah Rowe in GNU Leah Mode

Date of publication: 10 January 2025

Canoeboot is a wholly Free Software coreboot distro. The page you’re reading now, will attempt to describe how Canoeboot achives this goal, specifically, on a technical level. Some nuance is always present, in any such effort, so it’s critical that users do understand this.

Projects like coreboot are nominally free software, but may still contain some non-free software. Canoeboot takes projects like this and integrates them, with blobs removed; some patching is also done. We can’t support as much hardware because of this, but that’s the point of Canoeboot: to be a pure free software distribution.

Canoeboot, then, is a a much stricter approach to the same problem, of how to provide users with fully free boot firmware. It is strict, to the point of being pedantic, but it provides a viable solution for Free Software purists.

Free as in freedom!

Canoeboot intentionally de-blobs coreboot, which is to say that it does not include binary blobs. The coreboot software otherwise requires binary blobs on some of the systems that it has support for. Canoeboot’s version of coreboot is entirely free, on its consequently reduced set of supported motherboards.

It was decided that a formal policy should be written, because there is quite a bit of nuance that would otherwise not be covered. Canoeboot’s policies in this regard were previously ill defined.

Background information

Canoeboot concerns itself only with what goes in the main boot flash IC, but there are other pieces of firmware to take into consideration, as covered in the Canoeboot FAQ.

Most critical of these are:

Specific binary blobs are also problematic, on most coreboot systems, but they differ per machine. Canoeboot excludes binary blobs in releases, so it only supports a handful of machines from coreboot.

For information about Intel Management Engine and AMD PSP, refer to the FAQ.

So what is Canoeboot’s policy?

Canoeboot follows a very conservative and light touch approach, when it comes to deblobbing coreboot.

Canoeboot only excludes software binary blobs, plus CPU microcode updates. In practise, it is mostly microcode updates that Canoeboot’s build system deletes, along with coreboot Git history so that no traces remain of old revisions; older revisions had many blobs in the main repository, but modern coreboot moved almost all of them to third party submodule repositories..

Non-software blobs are permitted, so long as they are in an easily understood and/or well-documented format. For example, DDR training data is permitted (patterns used during memory controller initialization, specifically training, where the precise timings for the RAM are brute-forced); this is not software.

SPD data stored in the coreboot Git repository is in all cases some format that’s simply more efficient to store as a binary, in a format that is in fact known/understood (see: coreboot source code and data sheets); in many cases, there’s only one correct way to write such data, making even the question of copyright a moot point. Data is data, and code is code; the two are separate.

Non-software blobs must be redistributable under a free license, and must not be encumbered by DRM, or they will not be included in Canoeboot.

Other firmware, such as Embedded Controller firmware, is currently outside the scope of the Canoeboot project, but not due to lack of desire; rather, these are not yet possible on most supported or otherwise capable platforms, at least not with free software. Other examples of firmware outside of the main boot flash is covered in the Canoeboot FAQ.

More detailed insight about microcode

To be clear: it is preferable that microcode be free. The microcode on Intel and AMD systems are non-free. Facts and feelings rarely coincide; the purpose of this section is to spread facts, regardless of the ideological assumptions made by the reader.

The CPU already has microcode burned into mask ROM. The microcode configures logic gates in the CPU, to implement an instruction set, via special decoders which are fixed-function; it is not possible, for example, to implement a RISCV ISA on an otherwise x86 processor. It is only possible for the microcode to implement x86, or broken x86, and the default microcode is almost always broken x86 on Intel/AMD CPUs; it is inevitable, due to the complexity of these processors.

These processors provide a way to supply microcode updates. These updates are volatile, and consequently must be applied during every boot cycle. The updates fix stability/reliability/security bugs, and their absence is technically incorrect, but Canoeboot excludes them anyway, because that is Canoe policy. Examples of where these updates fix bugs: on ASUS KCMA-D8/KGPE-D16 and ThinkPad X200/T400/T500/W500/X200T/X200/R500/X301, the updates make hardware-based virtualization (via kvm) completely stable, where it would otherwise lead to a kernel panic. They allow those same thinkpads to be run with high CPU usage and I/O (RAM usage), without crashing (otherwise, it’s very likely to encounter a kernel panic caused by a Machine Check Exception).

Not including these updates will result in an unstable/undefined state. Intel themselves define which bugs affect which CPUs, and they define workarounds, or provide fixes in microcode. Based on this, software such as the kernel, Linux, can work around those bugs/quirks. Also, upstream versions of Linux can update the microcode at boot time (however, it is recommend still to do it from coreboot, for more stable memory controller initialization or “raminit”). Similar can be said about AMD CPUs.

Here are some examples of where lack of microcode updates affected Canoeboot, forcing Canoeboot to work around changes made upstream in coreboot, changes that were good and made coreboot behave in a more standards-compliant manner as per Intel specifications. Canoeboot had to break coreboot to retain certain other functionalities, on some GM45/ICH9M thinkpads:

https://codeberg.org/canoeboot/cbmk/raw/commit/2d17df9d584719cf6fe2079588a09751d12d071c/config/module/coreboot/default/patches/0054-fix-speedstep-on-x200-t400-Revert-cpu-intel-model_10.patch

https://codeberg.org/canoeboot/cbmk/raw/commit/2d17df9d584719cf6fe2079588a09751d12d071c/config/module/coreboot/default/patches/0055-GM45-type-CPUs-don-t-enable-alternative-SMRR.patch

These patches revert bug fixes in coreboot, fixes that happen to break other functionality but only when microcode updates are excluded. The most technically correct solution is to not apply the above patches, and instead supply microcode updates! However, this would violate Canoeboot’s policy. Canoeboot ships without them, despite these facts - and they are facts. Another example: on AMD Opteron 62xx/42xx CPUs, not including microcode updates may allow code running inside virtual machines to access host memory; microcode updates fix this (63xx/43xx doesn’t have this bug).

The general rule is to assume that your CPU is broken, and not secure, when excluding microcode updates. These updates patch bugs and fix security issues in CPUs, as per errata provided by Intel and AMD. Please consult the errata provided by Intel/AMD for your particular CPU. Please note that the ARM64 CPUs do not use microcode updates, because the logic gates are hard-wired; Intel/AMD CPUs allow to partially reconfigure logic gates via these microcode updates (that’s what the updates do, toggle gates).

It is imperative that users be warned about the facts, regardless of the ideology, due to the very nature of what microcode does. For example if you’re running mission-critical systems and you want to reduce the chance of data corruption, excluding microcode updates is ill advised; yet some people may take the risk. Canoeboot’s purpose is to be a fully free firmware distribution, but we will obviously provide such warnings as it is simply the right thing to do. Be wary of these caveats, when using Canoeboot.

Markdown file for this page: https://canoeboot.org/news/policy.md

Site map

This HTML page was generated by the Canoeboot Static Site Generator.

Canoeboot is discontinued. A new project was created: RBoot project, a fully free UEFI firmware distribution based on coreboot. RBoot is Canoeboot continued under a new name, with the same maintainer. The canoeboot website and release sources shall be preserved for historical purposes.