Skip to content

Firmware for the Turing Pi 2 that boots a new image on trial and takes it back if the board does not come back right. Upstream stopped in February 2025.

The Firmware page: the running slot, the image the board can fall back to, and when the gate last promoted one.

Updates that undo themselves

Upstream promotes a new image the moment it boots, which proves the kernel started and nothing else. Here it boots on trial and is kept only if the board comes back right. It has said no once, on purpose, to a tampered image — in about 35 seconds.

26updates taken on this board
1rolled back by the board itself
0trips to the rack
How the gate decides →
The board's own Dashboard, naming the firmware, daemon and interface it is running.
Read off the board on 2026-09-12, not counted by hand.
Update without touching your nodes

Upstream power-cycles all four compute modules to update the management computer beside them. This fork leaves their rails alone, so patching the board that manages your cluster does not take the cluster down.

0modules power-cycled by a BMC update
0cluster nodes lost, measured
48 sfor the board itself to come back
What upstream does instead →
The four compute modules on the Power Control page, powered and counted in uptime, across a BMC upgrade.
Every module exactly as it was, uptime unbroken.
One page over every board

Every board on one page, and none of them exposed

Section titled “Every board on one page, and none of them exposed”

A board that can reflash four computers should not face the internet. One page inside the cluster drives them all, with every control a board has, and it holds no credential of its own.

1hostname for the whole estate
11pages per board, the same ones the board serves
0credentials held by the page
Why a board is never exposed →
Both boards on one page, each answering for itself.
A board that is down costs you its card and nothing else.
Fresh, and fixed

Upstream's last release was v2.1.0, in February 2025, on a kernel that is not a longterm release and a Buildroot that is end of life. This fork tracks both, and has taken out six named faults — including the one that killed this board twice in a day.

6.12.109kernel, against upstream's 6.8
142releases across four components
7faults still open, each with a ticket
Every row, with its measurement →
The Dashboard's Software card: kernel, daemon, interface and firmware, each a version you can check against a release.
What the board says it is running, every part of it checkable.
What's new
Just shipped

Firmware v2.44.0: Flashing names what is in the way.

Everything that changed →Follow by feed →
Decided by vote

7 things are planned and 18 votes have been cast. Leading: A hardware watchdog, so a hung daemon does not mean a trip to the rack.

Vote on what comes next →Propose something →

Last updated: