Kernel parameters do not stick on Omarchy 4 because /boot/limine.conf is generated
This is the strongest record of the batch and every Omarchy-4-specific claim held up under direct inspection. I read etc/limine-entry-tool.d/omarchy-defaults.conf on quattro: it contains exactly KERNEL_CMDLINE[default]+=" quiet splash loglevel=0 systemd.show_status=false rd.udev.log_level=0 vt.global_cursor_default=0" plus a separate KERNEL_CMDLINE[default]+=" initramfs_async=0", and CUSTOM_UKI_NAME="omarchy", matching the record's quote and the /boot/EFI/Linux/omarchy*.efi path. Omarchy's default/limine/limine.conf really does hold only theming and menu options (interface_branding, term_palette, default_entry, hash_mismatch_panic), confirming 'anything you type into it is discarded'. The priority claim is confirmed by limine-entry-tool's own shipped config comments: drop-ins are /etc/limine-entry-tool.d/*.conf where += appends and = replaces, with the explicit note "/etc/default/limine overrides any drop-in configs, so += is recommended there", and "If unset, the tool will try to read them from '/etc/kernel/cmdline' or '/proc/cmdline'". The record's three-tier ordering is right. bin/omarchy-refresh-limine does precisely what the record says: mv /boot/limine.conf to .bak, cp the packaged default, then limine-update and limine-snapper-sync. bin/omarchy-setup-direct-boot does create an 'Omarchy' efibootmgr entry pointing straight at the UKI. Limine CONFIG.md confirms editor_enabled "Defaults to yes" and that per-entry cmdline is a real option (so a menu-time test does reach a UKI via LoadOptions, with Secure Boot off). Two cosmetic nits that do not change the verdict: the sources list cites default/limine/default.conf but the file on quattro is default/limine/limine.conf, and the sudo tee heredoc truncates zz-local.conf, so a reader adding a second parameter later should use tee -a or sudoedit.
A bad kernel parameter is a failure to boot. Test it in the Limine editor before writing a drop-in. Using KERNEL_CMDLINE[default]= instead of +=, or naming your file so it sorts *before* omarchy-defaults.conf, silently drops Omarchy's initramfs_async=0, which the packaged comment says is what keeps Plymouth alive at the LUKS prompt. An encrypted machine then falls back to an unthemed text prompt or hangs. limine-mkinitcpio rewrites the UKI on the ESP: run df -h /boot first, because a full ESP produces a truncated, unbootable image. If you enabled Secure Boot with ENABLE_ENROLL_LIMINE_CONFIG=yes, modifying limine.conf without re-enrolling the checksum makes the machine refuse to boot even after you disable Secure Boot. Keep an unsigned fallback loader. Recovery for all of the above is the Limine snapshot entry, so do not enable Direct Boot until you are done experimenting.
Symptom
Every GPU fix you find says "add amdgpu.dcdebugmask=0x10 (or nvidia_drm.modeset=1, i915.force_probe=…, nomodeset) to your kernel command line", but Omarchy has no /etc/default/grub. You edit /boot/limine.conf, reboot, and cat /proc/cmdline does not show the parameter, or it works once and is silently reverted by the next omarchy update or kernel upgrade.
Cause
Omarchy 4 does not hand-maintain /boot/limine.conf. It boots a **Unified Kernel Image** at /boot/EFI/Linux/omarchy*.efi, built by limine-mkinitcpio and registered by limine-entry-tool. /boot/limine.conf holds only theming and menu options and is regenerated from configuration on every kernel/limine transaction, so anything you type into it is discarded. Worse, with a UKI the command line is *baked into the .efi image*, so even a correct limine.conf edit could not change it.
The real sources of the command line, in increasing priority:
/etc/kernel/cmdline(the generic default when nothing else is set),- drop-ins in
/etc/limine-entry-tool.d/*.conf, read in lexical filename order, /etc/default/limine, which the Arch wiki notes has the **highest** priority and overrides all drop-ins.
Omarchy ships its own drop-in, /etc/limine-entry-tool.d/omarchy-defaults.conf, containing quiet splash loglevel=0 systemd.show_status=false rd.udev.log_level=0 vt.global_cursor_default=0 plus initramfs_async=0. That file is package-owned: editing it means your changes turn into .pacnew conflicts on the next update.
Fix
**Put your parameters in your own drop-in whose filename sorts after Omarchy's**, and always use += so you append rather than replace:
sudo tee /etc/limine-entry-tool.d/zz-local.conf >/dev/null <<'EOF'
# Local kernel parameters.
# `+=` appends to what earlier drop-ins set. A bare `=` REPLACES them and will
# wipe Omarchy's quiet/splash/initramfs_async defaults.
KERNEL_CMDLINE[default]+=" amdgpu.dcdebugmask=0x10"
EOF
# rebuild the UKI/initramfs, then regenerate the Limine boot entries
sudo limine-mkinitcpio
sudo limine-update
sudo reboot
After reboot:
cat /proc/cmdline
**Variants:**
# only for a specific kernel entry (matches the boot menu entry name)
KERNEL_CMDLINE[linux-lts]+=" nvidia_drm.modeset=1"
# only for the fallback entry
KERNEL_CMDLINE[fallback]+=" nomodeset"
**Test a parameter once, without persisting anything:** at the Limine boot menu select the entry and open Limine's editor (the key hints are printed in the menu's help line, and editor_enabled defaults to yes), edit the command line, and boot. Nothing is written to disk. If Omarchy's *Direct Boot* is enabled (omarchy-setup-direct-boot adds an Omarchy EFI entry that jumps straight to the UKI), the Limine menu is bypassed entirely. Pick Limine from the firmware boot menu (usually F12/F8/Esc) to get it back.
**If you already clobbered /boot/limine.conf,** restore the packaged one:
omarchy-refresh-limine
# moves your file to /boot/limine.conf.bak, copies the packaged default,
# then runs `limine-update` and `limine-snapper-sync`
**On other Arch-based distros using Limine (e.g. CachyOS):** the same mechanism applies: /etc/default/limine and /etc/limine-entry-tool.d/, then limine-mkinitcpio (or limine-dracut) and limine-update. On GRUB systems it is GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub plus sudo grub-mkconfig -o /boot/grub/grub.cfg.
Verify
cat /proc/cmdline contains both your parameter and Omarchy's defaults (quiet splash loglevel=0 … initramfs_async=0). sudo limine-list shows the entries. For a module parameter, cat /sys/module/<module>/parameters/<param> reflects the new value.
Sources
- https://wiki.archlinux.org/title/Limine
- https://github.com/basecamp/omarchy/blob/quattro/etc/limine-entry-tool.d/omarchy-defaults.conf
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-refresh-limine
- https://github.com/basecamp/omarchy/blob/quattro/bin/omarchy-setup-direct-boot
- https://github.com/basecamp/omarchy/blob/quattro/default/limine/default.conf
- https://github.com/limine-bootloader/limine/blob/trunk/CONFIG.md