Predictive additive fan-floor governor for ASUS GX10 (Ascent GX10) nodes — the ASUS partner SKU of NVIDIA GB10 / DGX Spark.
Tested on ASUS GX10. The upstream
dgx-spark-fan-controldriver stock-gates its DMI match to NVIDIAP4242(DGX Spark) and Lenovo30KL0005GF(ThinkStation PGX). On an ASUS GX10 it does not load without the includedapply_asus_patch.py/driver-patch/0001-platform-match-asus-gx10.patch. This repo is validated end-to-end on two ASUS GX10 nodes; if you are on an NVIDIA DGX Spark or Lenovo PGX you do not need the patch, but the governor itself has only ever been exercised on ASUS hardware.
Repository: public at https://github.com/chunkyen/spark-fan-governor (Apache-2.0). The driver dependency is GPL-2.0-only and is not redistributed here — see Licence below.
Built 2026-10-02 as a standalone alternative to Spark_Energy_Management's
energy_control service, whose fixed safety contract is unusable on a live
EXL3 deck:
- its guard aborts below 12 GiB MemAvailable (our nodes sit at ~6 GiB with the deck loaded) and above GPU 85 °C (routine bursts reach 86–93 °C);
- neither limit can be raised by configuration — they are deliberately fixed;
- it also arms a 1700 MHz GPU entry ceiling and flips all 20 CPU policies from
performancetoconservativeat start.
D1 keeps the one wanted feature — predictive fan anticipation — and owns exactly one actuator: the additive fan floor. No GPU clocks, no CPU governors, no cpufreq maxima. The floor is a lower clamp only; firmware may always add more cooling.
"D1" = Design 1 — a working label from the carve-out that the public name deliberately does not carry — of three options drawn up when this was carved out of Spark_Energy_Management (October 2026), after the operator asked for just the predictive-fan feature:
- D1 — standalone floor daemon (this project, chosen): a ~100-line
stdlib-only daemon owning only the
dgx_ec_fan_floordevice. Fastest to ship, smallest trust surface, nothing else touched. - D2 — faithful predictive port: SEM's full digital-twin fan policy (load-scaled speed instead of a fixed floor), reusing their read-only collector as a library. More fidelity, but the twin constants are Lenovo-fitted — a prior here, not a calibration. Kept as the upgrade path if the fixed floor ever proves too blunt.
- E — full
energy_controlservice: rejected as a dead end — even with "clocks disabled" via config it still arms the GPU entry ceiling, caps CPU targets by validation, and abort-loops on the fixed memory guard. Making it work means patching their fixed safety contract: a fork, not a config.
| path | what |
|---|---|
fan_governor.py |
the governor (Python 3.12+, stdlib only) |
spark-fan-governor.service |
systemd unit — boot-enabled, Restart=on-failure |
install-module.sh |
installs + boot-persists the EC fan-floor driver |
apply_asus_patch.py |
restores the ASUS GX10 DMI branch in the driver source |
driver-patch/0001-platform-match-asus-gx10.patch |
DMI patch against the pristine upstream driver |
driver-patch/LICENSE-GPL-2.0-upstream-driver |
the upstream driver's licence (GPL-2.0-only) |
This repository's own code (fan_governor.py, the systemd unit, scripts) is
Apache-2.0, matching the licence GitHub attached to this repository.
The driver dependency is not covered by it: dgx_ec_fan_control is
GPL-2.0-only and is not redistributed here. Only a patch against the
pristine upstream source is shipped, and you obtain the source yourself:
- Upstream: https://github.com/christopherowen/dgx-spark-fan-control
- Base commit:
deb2ea1(8 September 2026)
The governor drives a cooling device provided by the kernel module
dgx_ec_fan_control (upstream christopherowen/dgx-spark-fan-control,
GPL-2.0-only, v0.1.3). Its stock DMI gate accepts only NVIDIA P4242; our ASUS
GX10 reports vendor ASUSTeK COMPUTER INC. and product/board GX10, so an
additional branch is required.
driver-patch/0001-platform-match-asus-gx10.patch adds it and is verified to
apply cleanly with patch -p1 against the upstream base commit. It also carries
a Lenovo ThinkStation PGX branch (LENOVO / 30KL0005GF) inherited from the
Spark_Energy_Management copy of this driver (CC BY-NC 4.0); that branch is not
needed on ASUS hardware and can be dropped if you only want the ASUS change.
Historical note: on the machine this was developed on, the originally patched
source had not been preserved — only the compiled module carried the change
(its rodata held ASUSTeK COMPUTER INC., GX10 and an asus_gx10 local while
every .c on disk lacked them). The branch above was recovered from those
strings, and the rebuilt module verified to probe on real hardware: packet
service 0x8003, properties 0x109, FF-A 1.2, capabilities fan0 1260–9000 /
fan1 1890–13500 RPM, floor device registered in automatic state.
srcversion is not a useful integrity check here — it hashes struct
layout, so it is byte-identical between the patched and unpatched builds. Probe
success on real GX10 hardware is the real evidence.
apply_asus_patch.py reproduces the same change in-place if you already have a
driver checkout; the patch file is the canonical form.
State 0 = auto/off, then 2700, 3600, 4500, 5400, 6300, 7200, 8100, 9000,
10125, 11250, 12375, 13500 RPM. fan0 tops out at 9000 RPM (hardware limit);
states 9–12 push fan1 beyond that while fan0 saturates. The governor caps
requests at --max-state 10 (fan1 = 11250 RPM): verified live on a GX10 —
the EC accepted cur_state=10, fan0 held 9000, fan1 ramped 10260 → 11205 RPM
within ~8 s. States 11–12 remain untested.
- Load (GPU power ≥ 30 W and/or util ≥ 40 %, or vLLM queue > 0 when
--queue-urlis set) → floor raised to--load-stateimmediately. Feed-forward by design: the EC's own curve was measured reacting 20+ s late at 79 °C. - Load held → floor held. Load gone → held for
--idle-delay-s, then released to 0 (EC auto). - GPU ≥
--hot-gpu-cor any ACPI zone ≥--hot-acpi-c→--hot-state. Since 2026-10-02 (afternoon):--hot-state 10 --max-state 10— escalation drives fan1 to the 11250 RPM rung (fan0 saturates at its 9000 limit). This followed measured CPU-zone overshoot on gx10b: both 90 °C+ acpitz excursions peaked (92–94.6 °C) with fans already at the state-8 rung, i.e. fan1 had ~2 300 RPM of unused headroom above the old cap. Rationale and trade-off: the overshoot is seconds-scale thermal-mass lag, so state 10 pre-arms more airflow during the climb but does not eliminate the spike; it also trades acoustic headroom — states 11–12 stay reserved. stopalways writes floor 0, so the EC regains full control.
The GB10 has no CPU package sensor. The seven thermal_zone* entries are
all generic acpitz — firmware-defined board regions (SoC vicinity, VRM/power
areas) — and the hottest of them is what the EC watches. nvidia-smi reports
the only die-level silicon reading on the machine: the Blackwell GPU die.
Nothing in Linux measures the CPU complex die directly.
Consequences that shape the governor:
- The ACPI zones read hotter than the GPU die and lead it — measured at 7–17 °C on this hardware (community data agrees: die ~61 °C while a zone read 82.9 °C on our own node). The zones sit on the package heat path the EC protects (~98 °C cutoff), so a zone trip is an early warning of the thing the EC will act on, not a false alarm.
- The two hot trips are therefore deliberately offset:
--hot-gpu-c 80(die, the true silicon figure) and--hot-acpi-c 88(package, the EC signal, raised by roughly the observed die/zone gap so both trips mean the same actual risk). Either alone would miss something: the die is blind to VRM/heat-soak the zones catch; the zones lag a fast die spike the die sensor catches instantly. - A zone trip during pure GPU load is correct, not a false positive. The
Grace CPU and Blackwell GPU share one package and heatsink with no thermal
isolation — GPU power heats the whole package even at 0 % CPU utilisation.
Community threads show the "CPU" (package) zones running 15–20 °C above the
die under GPU-only inference, and hard power-offs where
nvidia-smilooked fine while a zone sat at 92–96 °C. - The old "CPU temperature" label was wrong, not the reading. The zone
number is real board telemetry and worth watching — it is just not CPU-die
temperature, and dashboards should say
Temperature (ACPI)(the Seewhy-dash collector now carriestemperatureLabel/temperatureSourcefor this).
Rule of thumb: GPU die temp + throttle-reason bits answer "is the compute silicon safe"; the hottest ACPI zone answers "is the package heading for the EC limit"; fan RPM answers "is the response adequate". The governor uses each for exactly its own question.
| metric | A (floor 5) | B (EC auto) |
|---|---|---|
| ACPI SoC peak | 85 °C | 86 °C |
| TGPU zone peak | 78 °C | 81 °C |
| GPU die peak | 72 °C | 75 °C |
| fan0 | 6300 held from load start | 3780 → 4320 (late step) |
| throughput | unchanged | unchanged |
A 1–3 °C win at 6300 RPM vs the EC's 3780–4320 RPM. A 35 s burst showed no difference — thermal mass dominates short loads, so the floor pays off over minutes, not showcase bursts.
Node confound: gx10a runs intrinsically hotter than gx10b (+4–7 °C at equal role/load). Always compare role-matched or state the delta explicitly.
sudo systemctl start spark-fan-governor # also starts at boot
sudo systemctl stop spark-fan-governor # floor -> 0, EC auto
journalctl -u spark-fan-governor -f
python3 fan_governor.py --dry-run # no writes, no root neededThe driver is not bundled — get the source, patch it, build it, then
install. The patch in driver-patch/ is verified to apply cleanly against the
upstream base commit.
# 1. driver: clone upstream, apply the ASUS GX10 patch, build
git clone https://github.com/christopherowen/dgx-spark-fan-control
cd dgx-spark-fan-control && git checkout deb2ea1
patch -p1 < /path/to/spark-fan-governor/driver-patch/0001-platform-match-asus-gx10.patch
cd kernel && make && cd ..
# 2. install the module + make it load at boot
sudo DRIVER_KERNEL_DIR=$PWD/kernel bash install-module.sh
# 3. the governor itself
sudo install -d -m 0755 /opt/spark-fan-governor
sudo install -m 0644 fan_governor.py README.md /opt/spark-fan-governor/
sudo install -m 0644 spark-fan-governor.service /etc/systemd/system/
sudo systemctl daemon-reload && sudo systemctl enable --now spark-fan-governorsudo systemctl disable --now spark-fan-governor
sudo rm -rf /opt/spark-fan-governor
sudo rm /etc/systemd/system/spark-fan-governor.service
sudo rm /etc/modules-load.d/dgx-ec-fan.conf
sudo systemctl daemon-reload
# optional: sudo rmmod dgx_ec_fan_controlstop always releases the floor to 0 first. Nothing else on the node is
modified.