# `[2026-09-24]` pfi-gx10 "power on after AC loss" — UEFI patch applied, NOT validated

pfi-gx10 (ASUS Ascent GX10, BIOS `GX10DGX.0105.2026.0505.1153`, no BMC) stayed
off after the NH3 outage. With Prime's approval (after the permission
classifier first refused it as externally-sourced firmware code), bytes 3–4
of the 81-byte UEFI var `Setup-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9` were
changed `0x1d,0x00 → 0x1c,0x01` via `efivar -w`; readback shows exactly those
two bytes changed. Recipe: community tool `Fheodoor01/DGX-Spark---Power-on-boot-`
(diff-derived from a power-on unit vs a stay-off unit; author-verified on
GX10DGX.0103/.0104). **Byte 3's meaning is unknown**; the resulting pair
matches factory power-on units.

**Original saved twice:** `/var/lib/efi-setup-backup/Setup-ec87d643-20260924-pre-poweron.bin`
on the box and `servers/pfi-gx10/efi-Setup-ec87d643-20260924-pre-poweron.bin`
(sha256 `6d6f6f77…`, raw incl. the 4-byte attr header). Revert procedure in
`servers/pfi-gx10/README.md`. Commit `e5197a3`.

⚠⚠ **An OS shutdown is NOT a test of this setting.** It means "start when
power RETURNS after a cut"; a `poweroff` is supposed to stay off by design.
The tool's README claims the two are indistinguishable — false here. I
trusted it and ran two poweroff "tests" (1421, and 1435 after the reboot the
README says the firmware needs); both stayed off, each costing Prime a trip to
the button, and both prove nothing. Prime called it out directly.

**Status:** the box is OFF (the 1435 shutdown) with the patch in place, and
Prime left NH3. **He will pull and restore AC on 2026-09-25.** Comes up alone
→ works; drop "NOT YET VALIDATED" from the README. Stays off → he presses the
button, revert from the backup, and set it in firmware via a PiKVM (he intends
to add one with ATX control, which also covers remote power-on regardless).

**Validated 2026-09-25 (Prime, relayed by Miranda 1333):** Prime replugged AC and
the box came up by itself at 1108:54 PT, with no button press. The patch works.