OMEN ACPI Toolkit v2.4.0

v2.4.0 improves the toolkit's procedural readability, documentation and release checks without changing the validated ACPI behaviour.

Highlights

• Clears a successfully resumed workflow's pending marker while preserving it when the resumed operation fails, preventing stale RESUME notices.
• Refactors the Bash and Python workflow code into clearer procedural sections, names, constants and explicit dispatch.
• Rewrites the README around the problem, validated scope, safe first run and recovery limit.
• Adds docs/code-overview.md with component, privilege, state and ownership boundaries.
• Clarifies project authorship, validation responsibility and the independent-review boundary.
• Consolidates bounded archive handling in the repository-only NVDE audit tool and extends its self-test.
• Adds the NVDE self-test and reference-machine constant consistency to the repository suite.
• Keeps current v2.2.0 and v2.3.0 stock-recovery snapshots trusted when their existing integrity and identity checks pass.

Validation

The S5-only and Combined transformers, AML round-trip verifiers, normalized patches and transformation fixtures are identical to v2.3.0. Their generated outputs are byte-identical for the reference fixture, so the v2.3.0 hardware observations remain the applicable baseline and no additional physical boot or shutdown cycle was required.

The complete local suite, the pending-workflow regression, Pyright, markdownlint, strict manifest verification, updater verify-only checks and two independent reproducible archive builds passed. GitHub Actions passed on both the release commit and the v2.4.0 tag.

An incompatible ACPI override can cause boot failure, data loss, instability, abnormal thermal behaviour, battery drain or the need for manual recovery. Keep the stock entries and read README.md and LICENSE before use.

Verify omen-acpi-toolkit-v2.4.0.tar.gz.sha256 before extraction, then run sha256sum -c SHA256SUMS inside the archive. After any kernel, initramfs or Limine update, run omen-acpi refresh all before booting a managed entry.

OMEN ACPI Toolkit v2.3.0

v2.3.0 adds an independent, refreshable Limine lifecycle for the primary CachyOS standard and LTS kernels while leaving every stock entry available.

Highlights

• Detects linux-cachyos, linux-cachyos-lts, or both from the current stock Limine configuration.
• Creates separate S5-only and Combined entries for each detected primary kernel.
• Reuses the stock kernel and ordered initramfs/module paths, prepending one small variant-specific ACPI early CPIO instead of freezing kernel copies.
• Adds omen-acpi refresh all to reconcile kernel additions, removals, initramfs changes and Limine updates idempotently.
• Migrates recognized v2.2.0 single-kernel managed state without rebuilding the already verified AML.
• Preserves historical OMEN entries inside Limine snapshot hierarchies without treating them as active duplicates.
• Reports the running kernel, standard/LTS entry state, NVIDIA modules and Combined BF01/WQBZ diagnostics.
• Keeps stock recovery, uninstall ownership checks and fail-closed transaction protections compatible with the multi-kernel layout.

The S5-only and Combined ACPI transformations are unchanged and remain byte-for-byte equivalent to the v2.1.11 validated baseline for the same stock DSDT.

On the validated reference machine, both standard and LTS entries for S5-only and Combined reported current; Combined was active on linux-cachyos-lts 6.18.42-1 with an exact managed AML hash and valid stock recovery. S5-only on LTS has not been boot-tested and is not claimed as runtime-validated. No non-reference hardware is physically validated.

An incompatible ACPI override can cause boot failure, data loss, instability, abnormal thermal behaviour, battery drain or the need for manual recovery. Keep the stock entries and read README.md and LICENSE before use.

Verify omen-acpi-toolkit-v2.3.0.tar.gz.sha256 before extraction, then run sha256sum -c SHA256SUMS inside the archive. After any kernel, initramfs or Limine update, run omen-acpi refresh all before booting a managed entry.

OMEN ACPI Toolkit v2.2.0

v2.2.0 adds a process-local, explicit opt-in for a different but readable DMI identity. The user acknowledges the risks and chooses to proceed; opt-in is neither compatibility nor support. The ACPI transformations are unchanged from v2.1.11.

The target remains CachyOS with mkinitcpio and Limine. It provides independent S5-only and Combined entries while preserving the stock entry. Only OMEN Gaming Laptop 16-ap0xxx, board 8E35, BIOS F.13 has been physically validated. No non-reference hardware has been physically validated. All structural, compilation, AML, boot, GPU, kernel, initramfs, Limine, ownership, transaction and rollback checks remain mandatory, so an opted-in system may be rejected.

For the same stock DSDT, reference S5-only and Combined AML outputs are byte-for-byte identical to v2.1.11. Physical boot and shutdown validation was performed historically with v2.1.11; v2.2.0's opt-in paths have automated coverage only, which is not hardware validation.

An incompatible override can cause boot failure, data loss, instability, abnormal thermal behaviour, battery drain or the need for manual recovery. Keep the stock entry and read README.md and LICENSE for risks, recovery, warranty and responsibility.

Verify omen-acpi-toolkit-v2.2.0.tar.gz.sha256 before extraction, then run sha256sum -c SHA256SUMS inside the archive.

Post-release documentation clarification — 8 August 2026

The documentation on main now makes the already validated S5 mechanism more explicit. On the reference firmware, the S5-only transformation sets OMPR = 3 and invokes the firmware's existing PEGP._PS3(), reaching the PG00._OFF() power-resource path when its firmware guards are satisfied.

S5-only was independently sufficient to eliminate the previously observed abnormal post-shutdown heating on the reference machine. The WQBZ / AE_AML_BUFFER_LIMIT bounds correction is a separate firmware issue and is not required for that demonstrated S5 result; the Combined variant simply applies both independent corrections.

This is a documentation clarification only. The v2.2.0 tag, implementation, ACPI transformations, published release assets and their checksums are unchanged.

OMEN ACPI Toolkit v2.1.11

This is a historical release, superseded by the current v2.2.0 release.

v2.1.11 hardens preventive stock recovery at transaction boundaries, improves recovery status and dashboard output, makes release archives reproducible across local time zones, and reorganizes the packaged README and versioned documentation. It still has no opt-in for other hardware.

Physical validation is limited to the HP OMEN MAX 16-ap0006sl with DMI OMEN Gaming Laptop 16-ap0xxx, board 8E35, and BIOS F.13, using CachyOS with mkinitcpio and Limine. The maintainer booted and shut down both S5-only and Combined, returned to the unchanged stock entry, exercised the normal recover-stock route, and removed and recreated the preventive snapshot. The normal entry was not deleted and an emergency recovery entry was not booted. Corruption, failure-injection, destructive and concurrency scenarios were automated fixtures only and do not validate other hardware.

Snapshots created by v2.1.10 are refresh-required and cannot create a trusted recovery entry; refresh from a clean stock boot. Without a usable normal entry or current trusted snapshot, external recovery media is required.

Verify omen-acpi-toolkit-v2.1.11.tar.gz.sha256 before extraction, then run sha256sum -c SHA256SUMS. Read the tag's README.md and LICENSE for risks, recovery, warranty and responsibility.

OMEN ACPI Toolkit v2.1.10

This is a historical release, superseded by the current v2.2.0 release.

v2.1.10 introduces preventive stock-boot recovery. From a verified clean stock boot, it snapshots the normal kernel and ordered initramfs components; if the normal entry later disappears, a verified snapshot can create the reserved zz-omen-acpi-stock-recovery entry without changing Limine's default. It also repairs Guided setup selection and adds a dedicated stock recovery menu.

Recovery, rollback, tamper and concurrency paths at this tag were covered by automated fixtures. The included manual validation plan is explicitly marked “not executed,” so those tests are not physical hardware validation. This version accepts only the HP OMEN MAX 16-ap0006sl identity OMEN Gaming Laptop 16-ap0xxx, board 8E35, BIOS F.13; it has no hardware opt-in.

Migration matters: prepare the snapshot while the normal linux-cachyos entry still exists. Later versions classify a v2.1.10 snapshot as refresh-required, not trusted for recovery-entry creation; refresh it from a clean stock boot. If neither a usable normal entry nor a trusted snapshot exists, external recovery media is required.

Verify omen-acpi-toolkit-v2.1.10.tar.gz.sha256 before extraction, then run sha256sum -c SHA256SUMS. Read the tag's README.md and LICENSE for risks, recovery, warranty and responsibility.

OMEN ACPI Toolkit v2.1.9

This is a historical release, superseded by the current v2.2.0 release.

v2.1.9 improves CLI resilience: failed dashboard actions return to the menu, test mode avoids dependency and boot-state prompts, and status handles an unreadable live DSDT without a traceback. It also adopts GPL-3.0-or-later, expands the public operational and safety documentation, and adds the NVDE analysis. Its ACPI transformations and entry lifecycle are unchanged from v2.1.8.

This release targets CachyOS/Arch with mkinitcpio and Limine on the HP OMEN MAX 16-ap0006sl identity OMEN Gaming Laptop 16-ap0xxx, board 8E35, BIOS F.13. The S5-only shutdown behaviour and Combined WQBZ result documented at this tag were observed on that reference laptop; automated CLI regression tests are not hardware validation. There is no opt-in for other hardware.

At this version, stock return requires an existing normal CachyOS entry; no preventive recovery snapshot is created. If that entry is already missing, use external recovery media.

Verify omen-acpi-toolkit-v2.1.9.tar.gz.sha256 before extraction, then run sha256sum -c SHA256SUMS inside the archive. Read the tag's README.md and LICENSE for risks, recovery, warranty and responsibility.