Boot the Arch kernel when an AMD display broke after Omarchy 4.0.4 switched to linux-omarchy 7.2.5
AUDITOR BREACH while checking this record: I ran limine-update --help, which re-exec'd through sudo and ran as root (journal, 12:20:55 on 2026-10-05). It reinstalled the Limine EFI binary and began rebuilding the UKI for Arch linux 7.2.3-arch1-3 before the output pipe closed, so that build was probably killed partway. Nothing was repaired. The operator should run sudo limine-update to completion and check sudo limine-entry-tool --tree before rebooting. Full detail is at the top of the nvidia-powerd-not-enabled-laptop-tgp-capped verdict. RECORD AUDIT: The mechanism is confirmed on this machine. /usr/share/omarchy/migrations/1789325478.sh installs linux-omarchy and headers, deletes and re-appends BOOT_ORDER exactly as quoted, and is guarded by /var/lib/omarchy/migrations/1789325478. /usr/lib/limine/limine-common-functions loads /etc/default/limine last ('highest priority'). /usr/bin/limine-update calls limine-install and then limine-mkinitcpio. linux 7.2.3.arch1-3 and linux-omarchy 7.2.5-3 are both installed here, and core/linux is now 7.2.8.arch1-2. The cause was too narrow and drew a conclusion the issues do not support. omarchy#12083 has HDMI reports on DCN 3.0 (RX 6700 XT), RX 6800/6900 XT, DCN 3.1.2 (Radeon 680M on a 60 Hz monitor), DCN 3.1.4 and DCN 3.2, not only 3.1.4 and 3.2. #13119 has MST on DCN 2.1 and DCN 3.5. The record said the regression 'may be upstream' because one reporter placed it between 7.2.3 and 7.2.5, but that reporter compared Arch 7.2.3 with Omarchy 7.2.5 only. Another reporter points at patches linux-omarchy carries and Arch does not, 0452-amd-hdmi-frl-default.patch and 0450-amd-hdmi-vrr-allm.patch, which I confirmed exist in omacom/omarchy-pkgs pkgbuilds/linux-omarchy. Nobody has isolated which. The fix now says so, and the 60 Hz stopgap tells the reader to substitute their own output name and scale instead of copying the reporter's 1.6. Not exercised: no boot order was changed by this audit.
Changing the boot order changes which kernel boots unattended. Keep at least two kernels installed, and do not remove linux-omarchy and linux in the same transaction, or you can be left with no bootable kernel.
Symptom
After the update to Omarchy 4.0.4 and a reboot, an AMD machine's display misbehaves in one of these ways: a 4K monitor over HDMI goes black for 2 to 5 seconds every time the screen changes after being still (typing, moving the mouse), a 4K@120 HDMI monitor gets no signal at all, the LUKS prompt is black so you unlock blind, or a monitor behind a USB-C dock is detected but stays black at 0x0 in hyprctl monitors. The kernel log shows lines such as:
amdgpu 0000:66:00.0: [drm] enabling link 1 failed: 19
[drm:dcn20_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!
amdgpu 0000:07:00.0: [drm] enabling link 2 failed: 15
WARNING: ... at fill_dc_mst_payload_table_from_drm+0x191/0x1a0 [amdgpu]
uname -r prints 7.2.5-3-omarchy.
Cause
Omarchy 4.0.4 migration 1789325478.sh installs linux-omarchy and linux-omarchy-headers and rewrites BOOT_ORDER in /etc/default/limine to "linux-omarchy, linux-omarchy-*, *, *fallback, Snapshots", so the machine boots the Omarchy kernel first while the old Arch linux kernel stays installed. /etc/default/limine is loaded last by limine-common-functions, so its BOOT_ORDER beats every drop-in. linux-omarchy 7.2.5-3 shows amdgpu display regressions against Arch linux 7.2.3.arch1-3 on the same installs. HDMI blanking or no signal, worst at high bandwidth, is reported in omarchy#12083 on RX 6700 XT (DCN 3.0), RX 6800/6900 XT, Radeon 680M (DCN 3.1.2, on a 60 Hz monitor), Radeon 780M (DCN 3.1.4) and RX 7600 (DCN 3.2). A DP MST link enable failure behind docks or USB-C monitors is reported in omarchy#13119 on DCN 2.1 and DCN 3.5. Several reporters confirmed that booting the Arch kernel on the same install fixes it. The root cause is not established. One reporter points at patches linux-omarchy carries and stock Arch does not, 0452-amd-hdmi-frl-default.patch (HDMI FRL on by default) and 0450-amd-hdmi-vrr-allm.patch, which would make the HDMI case Omarchy-specific. Another described it as a regression between 7.2.3 and 7.2.5, but compared only Arch 7.2.3 with Omarchy 7.2.5, so nobody has shown whether a stock Arch 7.2.5 or later kernel is affected. A 7.2.7rc1 test build fixed the MST case on one machine and did not fix the HDMI case on another, so a newer Omarchy kernel is not yet a confirmed fix.
Fix
**1. Boot the Arch kernel once.** At the Limine menu pick the plain linux entry instead of linux-omarchy. After login:
uname -r # want ...-arch..., not ...-omarchy
pacman -Q linux linux-omarchy
If linux is not installed, install it with headers, which DKMS drivers such as nvidia-open-dkms need:
sudo pacman -S --needed linux linux-headers
**2. Make it the default.** Edit the BOOT_ORDER line in /etc/default/limine so linux comes first, then rebuild the boot entries (limine-update runs limine-mkinitcpio itself):
sudo sed -i -E 's/^[[:space:]]*BOOT_ORDER[[:space:]]*=.*/BOOT_ORDER="linux, linux-omarchy, linux-omarchy-*, *, *fallback, Snapshots"/' /etc/default/limine
grep BOOT_ORDER /etc/default/limine
sudo limine-update
Leave linux-omarchy installed so you can switch back when a fixed release lands. The migration that set the order is guarded by /var/lib/omarchy/migrations/1789325478, so it does not run again and reset your order.
**3. Watch the Arch kernel version.** Reporters confirmed the fix on Arch linux 7.2.3.arch1-3. The next omarchy update upgrades linux too, and nobody has reported testing a newer Arch kernel against this bug. If the fault comes from patches only linux-omarchy carries, newer Arch kernels will be fine, and if it is upstream they may not be. After each update:
pacman -Q linux
If the display fault returns on a newer Arch kernel, boot the Limine snapshot from before that update and report the version on omarchy#12083 or #13119.
**Stopgap for the HDMI blanking only**, if you must stay on the Omarchy kernel: drop the monitor to 60 Hz in ~/.config/hypr/monitors.lua. Reporters saw this hold at 4K@60 on DCN 3.0 and 3.2, but on DCN 3.1.4 4K@60 still failed during early boot. Use your own output name from hyprctl monitors and keep your existing scale:
hl.monitor({ output = "HDMI-A-1", mode = "3840x2160@60", position = "auto", scale = 1.6, vrr = 0 })
This does not apply to plain Arch, which never installs linux-omarchy.
Verify
After a reboot with no menu interaction, uname -r shows the Arch kernel, the monitor holds its mode, and journalctl -k -b | grep -E 'enabling link .* failed|fill_dc_mst_payload' returns nothing.