Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-3136GitHub issuePublicReceived

How to Persistently Add Custom DSDT and Kernel Command Line Arguments?

Reported by ameeno · filed Oct 1, 2025Closed upstream on 2025-11-03 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

How to Persistently Add Custom DSDT and Kernel Command Line Arguments?revision 1 · captured 2026-10-04 11:35 UTC via poll

What correction or addition do we need?

Hello!

First off, thank you for the great Omarchy project. I've used it to set up my system, and it's been a fantastic experience.

I'm writing to ask for guidance on the recommended way to make some system-specific customizations persistent. My laptop requires a custom ACPI table (DSDT) to enable deep sleep, which is a common issue for many modern devices on Linux.

I have successfully managed to get everything working perfectly with the following manual steps:

  1. Created a Custom DSDT: I compiled a patched dsdt.aml to fix my sleep issues.
  1. Placed the ACPI Override: I placed the file in the correct location for the mkinitcpio hook:
    sudo mkdir -p /etc/initcpio/acpi_override
    sudo cp dsdt.aml /etc/initcpio/acpi_override/
  1. Enabled the `mkinitcpio` Hook: I added the hook by creating a drop-in config file at /etc/mkinitcpio.conf.d/zzz_omarchy_hooks.conf with the following content, which adds acpi_override to the HOOKS array:
    # Add custom hook for ACPI override
    HOOKS+=(acpi_override)
  1. Added Kernel Parameter: I manually edited /boot/limine.conf and added mem_sleep_default=deep to the CMDLINE for my kernel entry.

After running sudo mkinitcpio -P, the system works perfectly. My custom DSDT is loaded, and deep sleep is now the default and functional.

My Question

My main concern is ensuring these changes are persistent and "update-proof" within the Omarchy ecosystem.

  1. Kernel Command Line: Manually editing /boot/limine.conf feels temporary. I suspect this file might be regenerated (and my changes lost) during a kernel update or when a script is run. What is the official Omarchy method for permanently adding kernel parameters so they persist across rebuilds? Is there a file like /etc/kernel/cmdline or a default config that should be modified?
  1. `mkinitcpio` Hooks: Is using a drop-in file in /etc/mkinitcpio.conf.d/ the correct and recommended way to add a hook like acpi_override? I want to make sure this customization is safe from being overwritten by future project updates.

To summarize, I'm looking for the official, persistent method to:
* Add a kernel parameter (mem_sleep_default=deep).
* Ensure a custom mkinitcpio hook (acpi_override) is always included.

Thank you for your time and for this excellent project. Any guidance you can provide would be greatly appreciated

View raw text
### What correction or addition do we need?

Hello!

First off, thank you for the great Omarchy project. I've used it to set up my system, and it's been a fantastic experience.

I'm writing to ask for guidance on the recommended way to make some system-specific customizations persistent. My laptop requires a custom ACPI table (`DSDT`) to enable `deep` sleep, which is a common issue for many modern devices on Linux.

I have successfully managed to get everything working perfectly with the following manual steps:

1.  **Created a Custom DSDT:** I compiled a patched `dsdt.aml` to fix my sleep issues.

2.  **Placed the ACPI Override:** I placed the file in the correct location for the `mkinitcpio` hook:
    ```bash
    sudo mkdir -p /etc/initcpio/acpi_override
    sudo cp dsdt.aml /etc/initcpio/acpi_override/
    ```

3.  **Enabled the `mkinitcpio` Hook:** I added the hook by creating a drop-in config file at `/etc/mkinitcpio.conf.d/zzz_omarchy_hooks.conf` with the following content, which adds `acpi_override` to the HOOKS array:
    ```
    # Add custom hook for ACPI override
    HOOKS+=(acpi_override)
    ```

4.  **Added Kernel Parameter:** I manually edited `/boot/limine.conf` and added `mem_sleep_default=deep` to the `CMDLINE` for my kernel entry.

After running `sudo mkinitcpio -P`, the system works perfectly. My custom DSDT is loaded, and deep sleep is now the default and functional.

### My Question

My main concern is ensuring these changes are **persistent and "update-proof"** within the Omarchy ecosystem.

1.  **Kernel Command Line:** Manually editing `/boot/limine.conf` feels temporary. I suspect this file might be regenerated (and my changes lost) during a kernel update or when a script is run. What is the official Omarchy method for permanently adding kernel parameters so they persist across rebuilds? Is there a file like `/etc/kernel/cmdline` or a default config that should be modified?

2.  **`mkinitcpio` Hooks:** Is using a drop-in file in `/etc/mkinitcpio.conf.d/` the correct and recommended way to add a hook like `acpi_override`? I want to make sure this customization is safe from being overwritten by future project updates.

To summarize, I'm looking for the official, persistent method to:
*   Add a kernel parameter (`mem_sleep_default=deep`).
*   Ensure a custom `mkinitcpio` hook (`acpi_override`) is always included.

Thank you for your time and for this excellent project. Any guidance you can provide would be greatly appreciated

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.