Kevin Tindall - 2020-06-07

I created the following manual stanza in my refind.conf:

menuentry "Arch Linux Zen" {
    icon     /EFI/refind/icons/os_arch.png
    volume   "stuff"
    loader   /arch_root/boot/vmlinuz-linux-zen
    initrd   /arch_root/boot/initramfs-linux-zen.img 
    options  "root=LABEL=stuff rootflags=subvol=arch_root rw rootfstype=btrfs add_efi_memmap initrd=\arch_root\boot\intel-ucode.img nomodeset"
    submenuentry "Boot using fallback initramfs" {
        initrd /arch_root/boot/initramfs-linux-zen-fallback.img
    }
}

The initrd option on line 4 of the stanza does not appear in the command line for "Boot using default options". I can view the boot command line by pressing <tab> and using the arrow keys to view the entire line. Only the intel-ucode initrd option appears. I at least have a workaround that lets me boot when I manually type out the linux-zen initrd option. Oddly enough, the initrd option form the fallback submenuentry does appear on that command line (again, viewing the entry by pressing <tab> + arrow keys).</tab></tab>

I have already tried adding it to options, which works for booting default, but adds extra options that I have to erase manually when booting the fallback entry. Basically, I am trying to avoid any workarounds that require manually editing the command line. btrfs could be interferring here; however, I don't suspect that is the case since I can boot just fine when the initrd option is part of the boot command line.

Is the order of the keywords in a manual stanza important? What can I do here to make the initrd option be a part of the boot command line while avoiding manual editing during boots?