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.