Firmware v2.14.0
bmcd v2.19.0 → v2.23.0.
Firmware v2.14.0, 9 September 2026. Every item below is the repository's own changelog entry, taken apart; the whole entry is a click away under each one.
New¶
/etc/default/syslogd¶
Carrying the remote-logging knob documented and deliberately unset (SQU-108).
The whole entry
syslogd -R <host>:<port> sends this board's kernel and daemon logs somewhere that survives a reboot; /var/log is a tmpfs and the overlay is the wrong answer, on a NAND with five free eraseblocks and a workload guaranteed to grow. A default pointing at a host nobody configured would make every boot wait on a DNS lookup.
Changed¶
-
bmcd v2.19.0 → v2.23.0. Four releases:
The whole entry
-
A fan can be held at a step (SQU-170).
opt=set&type=coolingtakesmode=manualto pause the zone's governor andmode=autoto hand the fan back. Until now a written step was returned to the governor's own choice within a poll, which is what made the interface's slider a control that lied. A held fan is taken back above the zone's hottestactivetrip, because this board declares nocriticaltrip and nothing else would intervene. -
A flash targets the module that was asked for (SQU-105). All four modules sit behind one hub on a v2.5 board, and the daemon used to take whichever answered first — a flash of node 2 could write node 1 and report success. The node-to-port mapping is read from this board's own device tree rather than assumed.
-
An audit line per mutating call (SQU-108), naming the action, node, caller, address and outcome, and naming the loopback bypass explicitly when there was no credential at all. Sent to the system log as well as the rotating file, because
/tmpand/var/logare both tmpfs here. -
bmcd_process_threads, the companion to the resident-set metric.
-
-
tpiv1.2.2 → v1.3.0.cooling set --holdand--auto, and a Governor column that says-rather thanrunningon a daemon that does not report it. - BMC-UI v3.14.0 → v3.15.0. The fan slider now sits behind an explicit Override switch, offered only where the daemon reports it can actually hold a step.
Every release of the firmware · the roadmap · follow by feed