Skip to content

BMC-UI

The web interface the board serves.

Newest release v3.19.0, 17 in total. Every entry is the release note as published on GitHub, fetched by just refresh-changelog — not written here, so the two cannot disagree.

v3.19.0 — 10 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.19.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.18.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.18.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.17.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.17.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.16.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.16.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.15.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.15.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.14.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.14.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.13.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.13.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.12.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.12.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.11.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.11.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.10.1 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.10.1.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.10.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.10.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.9.3 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.9.3.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.9.2 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.9.2.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.9.1 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.9.1.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.9.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.9.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.8.0 — 09 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.8.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.

v3.7.0 — 08 September 2026

BMC-UI built from the hive branch of this fork, for the Turing Pi 2 BMC firmware build to consume.

Not a Turing Pi release. bmc-ui-v3.7.0.tar.gz unpacks to dist/, which is what lands in /srv/bmcd/www/.

Verify with:

sha256sum -c SHA256SUMS

SHA256SUMS lists bare filenames, so run it from the directory holding the tarball.