Main public logs

Combined display of all available logs of Geekworm Wiki. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).

08:27, 20 May 2026 135.180.174.172 talk performed unknown action "comments/add" on X728-script (X728 V2.5 — two power-on events required after software shutdown (AON / button) This post documents a reproducible behavior on the X728 V2.5 and the test methodology that isolates it to the X728 MCU. My hope is that other V2.5 users can confirm or refute, and that anyone with insight into the MCU's power-on logic can comment. Symptom. After a software shutdown of the Raspberry Pi (via shutdown -h now, or the equivalent x728off/xSoft.sh route), the X728 requires two power-on events to boot...)
08:20, 20 May 2026 135.180.174.172 talk performed unknown action "comments/add" on X728-script (Formatting got messed up....the changes to xPWR.sh should be: gpioset -c "$GPIOCHIP" "$BOOT"=1 & BOOT_PID=$! trap 'kill "$BOOT_PID" 2>/dev/null' EXIT trap 'kill "$BOOT_PID" 2>/dev/null; exit 0' TERM INT)
08:17, 20 May 2026 135.180.174.172 talk performed unknown action "comments/add" on X728-script (Trixie / libgpiod 2.x issues The Trixie-branch xPWR.sh and xSoft.sh updated for libgpiod 2.2.x have a behavioral bug that prevents them from holding GPIO12 and GPIO26 as intended. The scripts run without errors, but the GPIO lines they appear to set are not actually held — the consequences range from the X728 never seeing a "Pi is alive" signal on GPIO12, to GPIO26 being left in an undefined state at shutdown. This post documents the root cause and the corrected scripts. Root cause. Both sc...)