Skip to content

Firmware v2.41.0

Pins bmcd 2.38.4 and BMC-UI 4.0.1; tpi stays at 1.10.0. One fix, from a reader on the Turing Pi Discord.

Firmware v2.41.0, 6 October 2026 — the first image to carry bmcd 2.38.4, BMC-UI 4.0.1. Every item below is the repository's own changelog entry, taken apart; the whole entry is a click away under each one.

Fixed

  • After an upgrade the browser could keep running the old interface. A reader upgraded to v2.40.0 and saw the upgrade page report a problem, the password page appear, and the nodes shown as off, until they cleared their browser's cache.

    The whole entry

    The board served its web pages without saying how long a browser may keep them, so browsers kept the old page by their own guess, and when that old page asked for its files, which the new firmware no longer has, the board answered with the new page instead of "not found". The old interface ran half-broken against the new board.

    bmcd 2.38.4 tells the browser to check the page on every visit (cheaply, with an ETag), lets it keep the numbered files under /assets/ for a year, and answers a missing file with "not found". BMC-UI 4.0.1 reloads itself once when one of its files fails to load, so a browser holding an old copy lands on the current interface, and shows a Reload button rather than looping if that is not enough. The fleet's web server gets the same rules.

    Upgrading from v2.40.0 or older: your browser may still hold the old page once more after this upgrade, because that old page was cached under the old rules. If anything looks wrong, reload the page once (Ctrl+Shift+R, or Cmd+Shift+R on a Mac). From this version on, upgrades do not need that.

  • After an upgrade the browser could keep running the old interface, and the page then broke: a password-change page, nodes shown as off, a failed upgrade flow, until the browser cache was cleared. The daemon sent index.html with no cache instruction, so browsers guessed how long to keep it (a fraction of its age, hours or days) and never asked again. bmcd 2.38.4

    The whole entry

    The old page then asked for script files the new firmware no longer has, and was answered with the web page itself instead of a script, which the browser refuses to run. Now index.html is always checked again (a cheap "unchanged" answer when it is), the built files under /assets/ are kept for a year because their names change with their content, and a file under /assets/ that does not exist answers 404 rather than the web page. Pages such as /power-control still open the interface on a reload, and the API is untouched. Reported by a reader on the Turing Pi Discord.

  • A browser that kept an old copy of the interface now rescues itself after an upgrade. A reader on the Turing Pi Discord upgraded to firmware v2.40.0 and found the upgrade page, the password page and the node list broken, with nodes shown as off, until they cleared the browser's cache. BMC-UI 4.0.1

    The whole entry

    The browser had kept the old page, which asked for files the new firmware no longer has. When a page piece fails to load, the interface now reloads itself once, which fetches the current page, and carries on where you were. If the reload does not help, it does not try again and a banner says the interface was updated and offers a Reload button, in all six languages. This covers the board, the fleet and the demo. A page already stuck in a browser from before this release cannot do this itself; one reload of the page (or clearing the cache) gets it onto this version once.

  • The fleet's web server tells browsers what to keep. The page itself is now revalidated on every visit, so a new release shows up without clearing anything; the numbered files under /assets/ are cached for a year, with one clear instruction instead of two; and a file that is not there is a plain "not found" rather than the page. BMC-UI 4.0.1

    The whole entry

    (The board's own server is fixed separately, in bmcd.)

Every release of the firmware · the roadmap · follow by feed