Eric Ihli

Here is the log from a failed boot. As far as I can tell, rEFInd finishes its work. So I'm going to assume this has something to do with how I'm creating the kernel image and initrd. I'll move this discussion to a forum related to linux rather than rEFInd-specific but will post one more update here if/when I have a resolution. ==========Launching 'Boot EFI\Pentoo\vmlinuz-5.12.2-pentoo-x86_64 from BOOT '========== 22:13:31 - Getting EFI variable 'PreviousBoot' from disk 22:13:31 - Loading file 'PreviousBoot'...

This was not related to rEFInd. Rebuilt kernel and initrd with genkernel --clean --install --mountboot --microcode --keymap --lvm --kernel-config=/proc/config.gz --luks --gpg all. (I think some of those arguments weren't necessary) Then boot params crypt_root=UUID=<uuid> rw quiet root=UUID=<uuid> and all is well.

Oh, something that might help me troubleshoot this would be if I could find a way to keep rEFInd logs around after the failed boot attempt. Since rEFInd freezes, I have to hold down the power button to re-power the machine. When it boots up again and I boot into a working system, the log file only contains info from the most recent boot. I lose all the info from the boot that caused the freeze. I see the option to set log_level but I haven't found an option to do log rotation. I just had the idea...

Here is a photo of the error that flashes for a tiny fraction of a second before I get kicked back to a completely frozen rEFInd screen. Searching the web for "buffer too small" "efi stub" "exit_boot" "failed" doesn't reveal much to me. My load options from a slightly customized refind_linux.conf are `"Boot with standard options" "crypt_root=UUID=e5088221-bee0-4bfa-95ac-613e416a9254 rw quiet root=UUID=4321806b-4196-410c-9a8f-ba732518102f" I have a practically identical Manjaro kernel/initrd image...

Here is a photo of the error that flashes for a tiny fraction of a second before I get kicked back to a completely frozen rEFInd screen. Searching the web for "buffer too small" "efi stub" "exit_boot" "failed" doesn't reveal much to me. My load options from a slightly customized refind_linux.conf are `"Boot with standard options" "crypt_root=UUID=e5088221-bee0-4bfa-95ac-613e416a9254 rw quiet root=UUID=4321806b-4196-410c-9a8f-ba732518102f" I have a practically identical Manjaro kernel/initrd image...

Update: I recreated refind_linux.conf using the mkrlconf script and the kernel found with auto-scan works! But now... I realize Manjaro embedded the crypto_keyfile.bin in initramfs defeating the point of encryption (https://wiki.archlinux.org/title/dm-crypt/Device_encryption#With_a_keyfile_embedded_in_the_initramfs). But I at least made progress and have a direction to go. Thanks! Update #2: For the archives Got it working with the manual config using options copied straight from the refind-linux.conf...

Update: I recreated refind_linux.conf using the mkrlconf script and the kernel found with auto-scan works! But now... I realize Manjaro embedded the crypto_keyfile.bin in initramfs defeating the point of encryption (https://wiki.archlinux.org/title/dm-crypt/Device_encryption#With_a_keyfile_embedded_in_the_initramfs). But I at least made progress and have a direction to go. Thanks! Thanks for the notes. I ran into the filesystem drivers problem but solved that. Here's an thought that might be the...

Thanks for the notes. I ran into the filesystem drivers problem but solved that. Here's an thought that might be the issue that's not directly related to rEFInd config but I would be super appreciative of any thoughts. During the install of my Linux flavor, I didn't specify a separate /boot partition. So originally, /boot was encrypted on the same partition as everything else. My attempted solution was to create a FAT32 partition after linux was already installed and then copy all of the files from...