Boot hangs on the splash screen and the LUKS passphrase prompt never appears
Confirmed on this machine (omarchy-settings 4.0.2-1, plymouth 26.134.222-2, limine-mkinitcpio-hook 1.37.1-1): the quoted HOOKS line is byte-identical to /etc/mkinitcpio.conf.d/omarchy_hooks.conf, Omarchy 4 uses the udev-based encrypt hook (not sd-encrypt) with cryptdevice= in /etc/default/limine and in the running /proc/cmdline, the vconsole.conf Latin-layout bundling is in the same file, and initramfs_async=0 with the kernel 7.1 race comment is verbatim in /etc/limine-entry-tool.d/omarchy-defaults.conf and present in /proc/cmdline. pacman -Ql plymouth lists only hooks/plymouth, install/plymouth and install/plymouth-shutdown, so plymouth-encrypt is not an Arch hook, and mkinitcpio's wording is verbatim "Hook 'X' cannot be found" (/usr/lib/initcpio/functions:1244). The Arch Plymouth page still says plymouth goes before encrypt or sd-encrypt, still documents SimpleDRM by default on UEFI with the docked-laptop warning, plymouth.use-simpledrm=0, plymouth.enable=0 disablehooks=plymouth and plymouth.debug, and the Dm-crypt/System_configuration troubleshooting section is the origin of the 'swallow the password prompt' wording. The drop-in mechanism holds: /usr/lib/limine/limine-common-functions loads /usr/share/limine-entry-tool.d, /etc/limine-entry-tool.conf, /etc/limine-entry-tool.d/*.conf, then /etc/default/limine, the local /etc/default/limine uses +=, and limine-mkinitcpio re-embeds the cmdline via limine-entry-tool --get-cmdline before --add-uki. The one-off Limine edit holds too: menu.c opens the entry editor on e/E, the entry tool writes a cmdline: line, CONFIG.md says the editor defaults to enabled unless a config hash is enrolled or Secure Boot is active, ENABLE_ENROLL_LIMINE_CONFIG is unset on Omarchy 4 and sbctl is not installed, and systemd-stub only refuses a load-options cmdline under Secure Boot. Two things were wrong. First, the cause's mechanism: /usr/lib/initcpio/hooks/encrypt only calls plymouth ask-for-password when plymouth --ping succeeds, so a plymouth hook ordered after encrypt gives a plain text prompt, not a hang, and splash with no plymouth in the initramfs cannot swallow anything because plymouthd is not running. The hang the symptom describes comes from plymouthd running but unable to draw (no early KMS driver, SimpleDRM on a dark output, or the kernel 7.1 race), which is what the Arch dm-crypt page's 'use the correct modules' means. Cause rewritten, and the Omarchy 4 angle added: omarchy_hooks.conf drops kms on NVIDIA-only machines and relies on nvidia.conf early-loading nvidia_drm. Second, the theme-reset block: plymouth-set-default-theme -R runs /usr/lib/plymouth/plymouth-update-initrd, which is bare mkinitcpio -P, and /etc/mkinitcpio.d is empty on Omarchy 4 so that cannot rebuild the UKI. omarchy-refresh-plymouth already runs plymouth-set-default-theme omarchy followed by limine-mkinitcpio and refuses to run under sudo, so on Omarchy it is the only command needed. NOT exercised: no boot was performed, no Limine edit, no rebuild, and the Manjaro plymouth-encrypt origin was not re-fetched (the Manjaro GitLab raw URL returned nothing), so that sentence rests on the previous audit. GitHub issue search was unavailable to this token, so no Omarchy issue was checked for this record.
Editing HOOKS wrongly is how people make a machine unbootable. Dropping encrypt/sd-encrypt means nothing can unlock the root device, and dropping filesystems or block means it cannot be found. Change one thing, rebuild, read the output, and keep a fallback entry or a bootable snapshot available before you reboot. plymouth.enable=0 is safe as a one-off boot parameter but leaves you with a plain text prompt. Do not make it permanent if you also removed the plymouth hook, or you lose the themed prompt entirely. Never disable the passphrase prompt to "get past" this.
Symptom
The machine reaches the Omarchy/Arch boot splash (or a black screen with a spinner) and stops there forever. No Enter passphrase for /dev/nvme0n1p2: prompt, no cursor. Typing the passphrase blind and pressing Enter sometimes works, which is the giveaway. Pressing Esc shows nothing useful. Variants after editing the initramfs config:
==> ERROR: Hook 'plymouth-encrypt' cannot be found
==> ERROR: Hook 'plymouth' cannot be found
On a docked laptop the prompt may be drawn on an external monitor that is still asleep.
Cause
The encrypt hook asks for the passphrase in one of two ways. If plymouthd is already running in the initramfs (plymouth --ping succeeds) it hands the prompt to plymouth ask-for-password, which draws it on the splash and pipes what you type to cryptsetup. Otherwise it prints A password is required to access the root volume: as plain text. The hang happens in the first case when plymouthd is running but cannot draw: the initramfs has no early KMS driver for the GPU, or plymouth is on SimpleDRM and the output it chose is dark. The prompt is invisible but input still works, which is why typing the passphrase blind sometimes gets you in. This is what the Arch dm-crypt page means by "use the correct modules or Plymouth will swallow the password prompt".
On Omarchy 4 the hook order is fixed by the package-owned /etc/mkinitcpio.conf.d/omarchy_hooks.conf (plymouth right after udev, encrypt later, not sd-encrypt), so a wrong order only occurs when someone overrides HOOKS in /etc/mkinitcpio.conf or another drop-in. Even then the result is an unthemed text prompt rather than a deadlock, because plymouthd is not running yet when encrypt asks. The same file drops the kms hook on machines where NVIDIA owns every display controller and relies on /etc/mkinitcpio.conf.d/nvidia.conf early-loading nvidia_drm, so on those machines a missing nvidia module means no display driver at all at the prompt. Omarchy also ships initramfs_async=0 because kernel 7.1 unpacks the initramfs asynchronously, plymouthd exits when it cannot read /proc/cmdline, and encrypted boots fall back to a text prompt.
Two related traps: plymouth-encrypt is not a hook on Arch at all (the plymouth package ships only /usr/lib/initcpio/hooks/plymouth, and the name is a deprecated Manjaro alias for encrypt), so guides recommending it make every rebuild fail with Hook 'plymouth-encrypt' cannot be found. And plymouth defaults to SimpleDRM on UEFI, which does not light up secondary monitors, so a docked laptop can show the prompt on a dark screen.
Fix
**Get in first.** At the boot menu, edit the entry and disable plymouth for one boot. Limine: press e on the entry and edit the cmdline: line (the editor is on by default. Omarchy does not enrol a config hash or set up Secure Boot, either of which would disable it and make the cmdline embedded in the UKI non-overridable). GRUB: press e, edit the linux line, Ctrl+X:
plymouth.enable=0 disablehooks=plymouth
Remove quiet and splash from the same line so you can see the prompt. The text A password is required to access the root volume: should now appear.
**Fix the hook order.** plymouth must come after udev (or systemd) and *before* encrypt/sd-encrypt, otherwise you get an unthemed text prompt. This is Omarchy 4's shipped order, in the package-owned /etc/mkinitcpio.conf.d/omarchy_hooks.conf, so on Omarchy check that nothing in /etc/mkinitcpio.conf or another drop-in overrides it:
HOOKS=(base udev plymouth keyboard autodetect microcode modconf kms keymap consolefont block encrypt filesystems fsck btrfs-overlayfs)
On plain Arch, edit /etc/mkinitcpio.conf to the same shape:
HOOKS=(base udev plymouth autodetect microcode modconf kms keyboard keymap consolefont block encrypt filesystems fsck)
If you copied plymouth-encrypt from another distro's guide, replace it with plain encrypt. It does not exist on Arch.
**Rebuild and read the output.** On Omarchy the entries are unified kernel images and /etc/mkinitcpio.d is empty, so mkinitcpio -P stops with No presets found and never touches what boots:
sudo limine-mkinitcpio # Omarchy 4 / Limine + UKI
# plain Arch:
sudo mkinitcpio -P
There must be no Hook '...' cannot be found.
**Docked laptop / external monitor.** Make plymouth use the real GPU driver instead of the UEFI framebuffer so all outputs come up:
plymouth.use-simpledrm=0
**Keyboard layout at the prompt.** If the passphrase is rejected rather than absent, the initramfs is using us layout. Omarchy bundles /etc/vconsole.conf into the image automatically for Latin layouts. On plain Arch add it yourself:
# /etc/mkinitcpio.conf.d/99-local.conf
FILES+=(/etc/vconsole.conf)
**Debug what plymouth is doing** by adding plymouth.debug to the command line and reading /var/log/plymouth-debug.log after you get in.
**Make a parameter permanent on Omarchy** (do not edit the generated /boot/limine.conf). Drop-ins under /etc/limine-entry-tool.d/ are read before /etc/default/limine, and Omarchy's /etc/default/limine appends with +=, so a drop-in survives:
sudo tee /etc/limine-entry-tool.d/99-local.conf >/dev/null <<'EOF'
KERNEL_CMDLINE[default]+=" plymouth.use-simpledrm=0"
EOF
sudo limine-mkinitcpio
Note that Omarchy already ships initramfs_async=0 in /etc/limine-entry-tool.d/omarchy-defaults.conf to work around a kernel 7.1 race in which plymouthd exits before it can read /proc/cmdline, dropping encrypted boots to an unthemed text prompt. If your booted cat /proc/cmdline is missing it, your boot image predates that default and sudo limine-mkinitcpio regenerates it.
If the splash is merely ugly rather than broken, reset the theme instead of disabling plymouth. On Omarchy run this as your user, not under sudo (it refuses otherwise). It republishes the packaged theme, runs plymouth-set-default-theme omarchy and then limine-mkinitcpio:
omarchy-refresh-plymouth
On plain Arch:
sudo plymouth-set-default-theme -R <theme>
Do not use plymouth-set-default-theme -R on Omarchy: its rebuild step is bare mkinitcpio -P, which has no presets to run there.
Verify
After rebuilding, sudo limine-mkinitcpio (or mkinitcpio -P) reports no missing hooks. On the next boot the themed passphrase prompt appears and accepts input. cat /proc/cmdline contains the parameters you added.
Sources
- https://wiki.archlinux.org/title/Plymouth
- https://wiki.archlinux.org/title/Dm-crypt/System_configuration
- https://github.com/basecamp/omarchy/blob/quattro/etc/mkinitcpio.conf.d/omarchy_hooks.conf
- https://github.com/basecamp/omarchy/blob/quattro/etc/limine-entry-tool.d/omarchy-defaults.conf
- https://archlinux.org/packages/extra/x86_64/plymouth/files/
- https://gitlab.manjaro.org/packages/extra/plymouth/-/blob/master/PKGBUILD
- https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio
- https://wiki.archlinux.org/title/Kernel_parameters
- https://github.com/limine-bootloader/limine/blob/trunk/CONFIG.md
- https://github.com/limine-bootloader/limine/blob/trunk/common/menu.c
- https://github.com/systemd/systemd/blob/main/man/systemd-stub.xml