OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
power-suspend high occasional DISPUTE

Fix a black screen when resuming from hibernation

archomarchyendeavouroscachyosmanjaronvidiaamdintelmkinitcpiolaptopdesktop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The early-KMS-vs-hibernation-image conflict is a real and correctly diagnosed failure mode, and the LTS-kernel and nvidiafb suggestions are reasonable. The defect is Omarchy-specific and this record explicitly claims to apply to Omarchy: it tells the user to edit MODULES= and HOOKS= in /etc/mkinitcpio.conf, but Omarchy ships /etc/mkinitcpio.conf.d/omarchy_hooks.conf which REASSIGNS HOOKS with = and is read after the main file, so the edit is silently discarded and the user rebuilds an unchanged initramfs. This is the same drop-in precedence trap the omarchy-resume-hook record documents. The example HOOKS array also drops kms while keeping encrypt, which on an encrypted root can leave the LUKS passphrase prompt on a blank screen.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Removing the kms hook loses flicker-free boot and can change console/plymouth behaviour, and on an encrypted root the password prompt may render at a different resolution. A wrong HOOKS array is unbootable, so keep a fallback entry.

Symptom

Resume from hibernate leaves a completely black screen: no console, no TTY, and the machine is otherwise alive (Caps Lock LED toggles, SSH sometimes works). Resuming from ordinary suspend is fine.

Cause

Graphics devices are being initialised inside the initramfs (early KMS / explicit MODULES=) before the hibernation image is restored. The device state set up by the initramfs conflicts with the state recorded in the image. It can also be a kernel regression introduced by an update.

Fix

First check where HOOKS is actually coming from, because on Omarchy the main config is overridden by a drop-in:


grep -h '^\(HOOKS\|MODULES\)' /etc/mkinitcpio.conf /etc/mkinitcpio.conf.d/*.conf

**Arch / EndeavourOS / CachyOS** (no drop-in reassigning HOOKS): edit /etc/mkinitcpio.conf directly:


MODULES=()
HOOKS=(base udev autodetect microcode modconf keyboard keymap consolefont block encrypt resume filesystems fsck)

**Omarchy**: editing /etc/mkinitcpio.conf will NOT take effect. Write a drop-in that sorts last, starting from the array the grep above printed and removing only kms (keep everything else, including any btrfs-overlayfs hook):


sudo tee /etc/mkinitcpio.conf.d/zz_no_early_kms.conf <<'EOF'
MODULES=()
# full array from the grep above, with kms removed
HOOKS=(base udev autodetect microcode modconf keyboard keymap consolefont block encrypt resume filesystems fsck btrfs-overlayfs)
EOF
sudo limine-mkinitcpio

On either distro, rebuild and confirm the result actually changed:


sudo mkinitcpio -P          # sudo limine-mkinitcpio on Omarchy
lsinitcpio -a /boot/initramfs-linux.img | head   # or check the UKI was regenerated

Caveat the record omits: with an encrypted root, removing kms means the LUKS passphrase prompt may render on a black screen on some GPUs, so you are typing blind. Test that you can still unlock before relying on it, and be ready to boot the previous entry.

The LTS-kernel and blacklist nvidiafb suggestions are fine as written. On Omarchy, sudo pacman -S linux-lts linux-lts-headers followed by sudo limine-mkinitcpio generates the extra boot entry for you.

Verify

Hibernate and resume. The desktop reappears. journalctl -b | grep -i 'PM: hibernation' shows a clean restore with no device errors.

Sources

black-screen-on-resume-from-hibernate-early-kms