Canoeboot 20231107 released!

Leah Rowe in GNU Leah Mode™

7 November 2023

Return to index

Article published by: Leah Rowe in GNU Leah Mode™

Date of publication: 7 November 2023


This new release, Canoeboot 20231107, released today 7 November 2023, is based on the recent Libreboot 20231106 release. The previous release was Canoeboot 20231103, released on 3 November 2023. Today’s release has focused on minor bug fixes, plus tweaks to the GRUB payload. It imports certain fixes from the Libreboot 20231106 release, relative to Libreboot 20231101.

Canoeboot provides boot firmware for supported x86/ARM machines, starting a bootloader that then loads your operating system. It replaces proprietary BIOS/UEFI firmware on x86 machines, and provides an improved configuration on ARM-based chromebooks supported (U-Boot bootloader, instead of Google’s depthcharge bootloader). On x86 machines, the GRUB and SeaBIOS coreboot payloads are officially supported, provided in varying configurations per machine. It provides an automated build system for the configuration and installation of coreboot ROM images, making coreboot easier to use for non-technical people. You can find the list of supported hardware in Canoeboot documentation.

Canoeboot’s main benefit is higher boot speed, better security and more customisation options compared to most proprietary firmware. As a libre software project, the code can be audited, and coreboot does regularly audit code. The other main benefit is freedom to study, adapt and share the code, a freedom denied by most boot firmware, but not Canoeboot! Booting Linux/BSD is also well supported.

Work done since last release

This is largely a bugfix release. Most notably, boot issues on GM45 thinkpads present in the 20231103 release have been resolved.

Dell E6400 on its own tree

Canoeboot contains a DDR2 raminit patch for Dell Latitude E6400, that increases reliability on coldboot, but it negatively affects other GM45 machines that use DDR3 RAM instead.

This board is no longer provided by coreboot/default. Instead, it is provided by coreboot/dell, and the offending patch has been moved there, along with other required patches.

This means that the Dell Latitude E6400 still works, and quite reliably, but the patch for it will not impact other boards. In some special circumstances, Canoeboot 20231103 randomly crashed or rebooted with certain memory modules, when using on GM45 ThinkPads (ROM images for those machines were then deleted from those release archives). Today’s Canoeboot release solves that problem, so these machines can be used reliably once again (and ROM images are provided, in this Canoeboot 20231107 release).

Coreboot, GRUB, U-Boot and SeaBIOS revisions

Canoeboot 20231107 and 20231103 are both based on these revisions:

Several other fixes and tweaks have been made, in addition to this and the E6400 patch mentioned above.

Build system tweaks

These changes were made:

The following additional commits were picked, which are present in Libreboot’s Git repository after the Libreboot 20231106 release upon which Canoeboot 20231107 is based:

c4d90087 add grub mods: diskfilter,hashsum,loadenv,setjmp
d0d6decb re-add grub modules: f2fs, json, read, scsi, sleep
86608721 nvmutil: print usage
f12f5c3a nvmutil: fix makefile

This is a very conservative changelog, because this is largely a bugfix release.

Hardware supported in this release

All of the following are believed to boot, but if you have any issues, please contact the Canoeboot project. They are:

Servers (AMD, x86)

Desktops (AMD, Intel, x86)

Laptops (Intel, x86)

Laptops (ARM, with U-Boot payload)


You can find this release on the downloads page. At the time of this announcement, some of the rsync mirrors may not have it yet, so please check another one if your favourite one doesn’t have it.


Update on 12 November 2023:

This file was also overlooked, and is still present in the release tarball:

This has now been removed, in the Canoeboot git repository (cbmk.git), and this file will absent, in the next release after Canoeboot 20231107. Thanks go to Denis Carikli who reported this. The patch to fix it is here:

This fix will be present in the next release.

Markdown file for this page:

Subscribe to RSS for this site

Site map

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