GRUB "ran out of memory" loading a large initramfs on AMD Zen 5 laptops
Issue 8629 exists and matches (GRUB out-of-memory on Ryzen AI 9 HX 370 / Strix Point), and the contiguous-low-memory diagnosis is right. Three problems in the fix. COMPRESSION_OPTIONS=(-19) contradicts mkinitcpio.conf(5), which says the setting 'is generally not used. It can be potentially dangerous and may cause invalid images to be generated without any sign of an error'. Telling someone with an already-unbootable machine to set it is the wrong risk. A blanket MODULES=() silently deletes whatever was there, which on Omarchy is the NVIDIA early-KMS list and on other systems may be the forced vfat modules from the /boot/efi record. That can turn a boot-menu failure into an unmountable root. And bootctl install alone gives you systemd-boot with an empty menu: Arch+mkinitcpio does not auto-generate BLS entries, so the machine will boot to a loader with nothing in it.
Switching bootloaders on a machine you cannot currently boot is a one-way trip if it goes wrong. Do it from a chroot with a live USB in hand, and leave the old loader's files on the ESP until the new one is proven.
Symptom
Fresh install (Omarchy 4.0.1 reported, but the failure mode is generic) on an AMD Ryzen AI 9 HX 370 / Strix Point machine such as a Framework 13. The system dies at or just before the boot menu with:
error: ../../grub-core/loader/efi/linux.c:542:grub_cmd_linux: ran out of memory
Disabling Secure Boot, hiding the TPM and shrinking the iGPU allocation all fail to help.
Cause
GRUB must place the initramfs in a contiguous block of physical memory below 4 GB. A 240 MB+ initramfs (typical once NVIDIA/AMD firmware and early KMS modules are bundled) needs more contiguous low memory than the firmware leaves free once Pluton/fTPM reservations and iGPU carve-outs have fragmented that region. Tracked as basecamp/omarchy#8629.
Fix
**Shrink the initramfs.** Boot the fallback/rescue entry or chroot from a live USB, then record what you currently have before changing anything:
grep -h '^MODULES\|^HOOKS\|^COMPRESSION' /etc/mkinitcpio.conf /etc/mkinitcpio.conf.d/*.conf
ls -lh /boot/initramfs-*.img
In /etc/mkinitcpio.conf, set compression explicitly and leave the options alone. mkinitcpio.conf(5) warns COMPRESSION_OPTIONS can produce a silently invalid image:
COMPRESSION="zstd"
# do NOT set COMPRESSION_OPTIONS
Ensure autodetect is present so only in-use modules are packed:
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck)
Remove **only** the GPU early-KMS entries from MODULES. Do not blank the array, other modules there may be load-bearing:
# e.g. MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm vfat) -> MODULES=(vfat)
Rebuild and check:
sudo mkinitcpio -P
ls -lh /boot/initramfs-linux.img # aim well under 150 MB
**Or switch loader.** Limine (Omarchy 2.0+) and systemd-boot load via the EFI stub and have no low-memory allocator constraint. bootctl install only installs the loader. You must also create entries, or you get an empty menu:
sudo bootctl --esp-path=/boot install
sudoedit /boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=UUID=<your-root-uuid> rw
bootctl list # must show the entry BEFORE you reboot
sudo systemctl enable systemd-boot-update.service
sudo efibootmgr -v # then reorder with -o <new>,<old>
Verify
ls -lh /boot/initramfs-linux.img shows a substantially smaller image and the machine reaches the boot menu and boots without the memory error.