Fix AMD screen flickering white/grey when plugging in a monitor
I checked the single cited source, https://wiki.archlinux.org/title/AMDGPU, by fetching its raw wikitext. It does support the symptom and the parameter: the section "Screen flickering white/gray" says verbatim that when you change resolution or connect to an external monitor and the screen flickers or stays white, you should add amdgpu.sg_display=0 as a kernel parameter. So the source stands and I removed nothing. The cause also holds, and I confirmed it against the driver rather than the wiki: drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c at tag v7.1 documents sg_display as "Disable S/G (scatter/gather) display (i.e., display from system memory). This option is only relevant on APUs", with int amdgpu_sg_display = -1; /* auto */, so the parameter still exists on the kernel this corpus targets and 0 is the documented way to turn it off. What was wrong is the fix and the danger, both of which describe a machine Omarchy 4 is not. I confirmed on this workstation (omarchy 4.0.2-1, kernel 7.1.9-arch1-2) that /etc/default/grub does not exist and no grub package is installed, so the GRUB sed recipe is dead advice for the omarchy tag, and /boot/limine.conf is regenerated on every kernel transaction so the Limine line the record gives is silently discarded. The real path is a drop-in under /etc/limine-entry-tool.d/ using +=, which I verified from the installed /etc/limine-entry-tool.conf template ("+= appends parameters ... Commonly used in drop-in configs: /etc/limine-entry-tool.d/*.conf", "= replaces") and from the Limine Arch wiki page, and which agrees with the existing corpus record limine-kernel-parameters-not-applying-omarchy. I read /etc/limine-entry-tool.d/omarchy-defaults.conf on this machine and fetched the same file at upstream tag v4.0.3 (published 2026-09-08, the newest tag), and the two are identical, so this is still true on the current release. The old danger was also wrong in substance: it claimed the recovery is to press e at the boot menu, which is not Limine's documented key, and it ignored that a bare = in the drop-in silently deletes initramfs_async=0 and leaves an encrypted machine at an unthemed text prompt with no desktop. NOT EXERCISED: this workstation has an NVIDIA GeForce RTX 3090 and no amdgpu module is loaded (/sys/module/amdgpu does not exist), so nothing about the AMD behaviour was tested here. The parameter's effect is taken from the kernel source and the wiki, not from a reproduction, and I did not run limine-mkinitcpio or limine-update on this machine.
amdgpu.sg_display=0 itself is low risk. It only stops the display engine scanning out of system memory on an APU, and the cost is that the driver must keep framebuffers in carved-out VRAM, which can fail under memory pressure on a small-carveout APU.
The risk is the drop-in. Writing KERNEL_CMDLINE[default]= instead of +=, or naming the file so it sorts before omarchy-defaults.conf, throws Omarchy's own defaults away, including initramfs_async=0. The comment in the packaged file says that parameter is what stops plymouthd exiting on kernel 7.1, so an encrypted machine falls back to an unthemed text LUKS prompt or sits there with no graphical session. limine-mkinitcpio rewrites the UKI on the ESP, so run df -h /boot first, because a full ESP produces a truncated image that will not boot. Recovery is the Limine snapshot entry or editing the command line in the Limine boot menu, and Omarchy's Direct Boot (omarchy-setup-direct-boot) bypasses that menu entirely, so do not enable Direct Boot while you are still testing kernel parameters.
Symptom
On an AMD APU laptop, the screen flickers white or grey, or stays white, when changing resolution, plugging in an external monitor, or waking a display.
Cause
A bug in the amdgpu 'scatter-gather display' path, which lets the display engine scan out from system memory on APUs.
Fix
Add the kernel parameter amdgpu.sg_display=0.
**On Omarchy 4 the parameter goes in a Limine drop-in, not in a bootloader config.** There is no /etc/default/grub (no grub package is installed), and editing /boot/limine.conf is discarded, because Omarchy boots a Unified Kernel Image with the command line baked into the .efi and regenerates /boot/limine.conf on every kernel transaction. Write your own drop-in whose filename sorts after Omarchy's omarchy-defaults.conf, and always use += so you append instead of replacing Omarchy's own defaults:
sudo tee /etc/limine-entry-tool.d/zz-local.conf >/dev/null <<'EOF'
# `+=` appends. A bare `=` REPLACES Omarchy's defaults and drops
# quiet/splash/initramfs_async=0.
KERNEL_CMDLINE[default]+=" amdgpu.sg_display=0"
EOF
sudo limine-mkinitcpio
sudo limine-update
sudo reboot
The full mechanism, including how to test a parameter once from the Limine boot menu without writing anything to disk, is in the record limine-kernel-parameters-not-applying-omarchy.
**On other Arch-based systems:**
- Limine, with or without a UKI: the same
/etc/limine-entry-tool.d/*.confdrop-in, thensudo limine-update - systemd-boot: append it to the
optionsline in/boot/loader/entries/*.conf - GRUB:
sudo sed -i 's/^GRUB_CMDLINE_LINUX_DEFAULT="/&amdgpu.sg_display=0 /' /etc/default/grub
sudo grub-mkconfig -o /boot/grub/grub.cfg
Reboot.
Verify
cat /proc/cmdline contains amdgpu.sg_display=0, and on Omarchy it must still contain Omarchy's own defaults (quiet splash loglevel=0 ... initramfs_async=0). If those defaults are missing, your drop-in used a bare = or sorts before omarchy-defaults.conf.
cat /sys/module/amdgpu/parameters/sg_display # 0 once applied, -1 is the auto default
Then hot-plug the external monitor or change resolution and confirm the screen no longer flashes white.
Sources
- https://wiki.archlinux.org/title/AMDGPU
- https://wiki.archlinux.org/title/Limine
- https://github.com/torvalds/linux/blob/v7.1/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
- https://github.com/torvalds/linux/blob/v7.1/drivers/gpu/drm/amd/include/amd_shared.h
- https://github.com/omacom/omarchy/blob/v4.0.3/etc/limine-entry-tool.d/omarchy-defaults.conf