Work around AM5 boards that wake instantly even with all ACPI wakeups disabled
The Omarchy/Limine drop-in mechanism is genuine (omarchy-hibernation-setup does exactly echo 'KERNEL_CMDLINE[default]+=" ..."' > /etc/limine-entry-tool.d/<name>.conf then sudo tee -a /etc/default/limine < "$DROP_IN"), but the acpi_osi value is BROKEN as written. kernel-parameters.txt is explicit: "Double-quotes can be used to protect spaces in values, e.g.: param=\"spaces in here\"". The record's echo emits acpi_osi=!Windows 2015 with a bare space, so the kernel parses acpi_osi=!Windows (an _OSI string that does not exist) plus a stray 2015 token. The fix silently does nothing. The quotes must survive into the final cmdline. Also acpi_os_name is name-dropped with no value or guidance, and there is no warning that a bad cmdline baked into a UKI can leave the machine unbootable.
Changing the reported _OSI string alters which ACPI code paths the firmware takes. Fan curves, battery reporting or thermal behaviour can change. Keep a known-good boot entry so you can boot without the parameter.
Symptom
Suspend still ends immediately after disabling every entry in /proc/acpi/wakeup, including GPP0. Seen on Gigabyte B650/B850/X670/X870 and MSI PRO X870E-P WIFI boards.
Cause
The board's ACPI tables take a broken code path when the kernel reports itself as a recent Windows version through the _OSI interface, and the firmware re-arms a wake source the OS cannot see.
Fix
The quotes are load-bearing. acpi_osi=!Windows 2015 without them is parsed as two separate parameters and does nothing.
On Omarchy (Limine + UKI), escape the inner quotes so they land in the generated cmdline:
sudo mkdir -p /etc/limine-entry-tool.d
printf 'KERNEL_CMDLINE[default]+=" acpi_osi=\\"!Windows 2015\\""\n' \
| sudo tee /etc/limine-entry-tool.d/acpi-osi.conf
sudo tee -a /etc/default/limine < /etc/limine-entry-tool.d/acpi-osi.conf
sudo limine-mkinitcpio
After rebooting, verify the parameter actually arrived intact. If you see 2015 as its own token, the quoting was lost:
cat /proc/cmdline
dmesg | grep -i 'ACPI: Added _OSI\|ACPI: Deleted _OSI'
GRUB: GRUB_CMDLINE_LINUX_DEFAULT="... acpi_osi=\"!Windows 2015\"" in /etc/default/grub, then sudo grub-mkconfig -o /boot/grub/grub.cfg. systemd-boot: add acpi_osi="!Windows 2015" to the options line in /boot/loader/entries/*.conf.
Masking an _OSI string changes which ACPI code path the firmware takes for everything, not just wakeup. Backlight, fan and battery control can regress. Test it as a one-off boot-time edit (press e in the Limine/GRUB menu) before making it permanent, and keep a known-good fallback boot entry, since a broken cmdline baked into a UKI is harder to recover from. Try "!Windows 2020", "!Windows 2019" etc. one at a time if 2015 does not help. Drop the vague acpi_os_name mention. It takes a full string (e.g. acpi_os_name="Microsoft Windows NT") and is rarely the right knob here.
Verify
cat /proc/cmdline contains the parameter, and systemctl suspend now stays asleep. dmesg | grep -i _OSI shows the string being masked.