You are not logged in.
Hi everybody,
I installed rEFInd on MacOS and created an ext4 partition for Arch Linux. I then installed Arch on the partition skipping the bootloader installation.
rEFInd can now see and run MacOS installation but not the Arch one.
I tried to manually add an entry for Arch but if I use the volume label as identifier, I get the common error:
rEFInd - Booting OS
Starting vmlinuz-linux
Using load options 'ro root=UUID=... initrd=\boot\initramfs-linux.img'
Invalid loader file!
Error: Not Found while loading vmlinuz-linux
* Hit any key to continue *while if I use the unique partition GUID, rEFInd display a blank screen and I'm forced to go to recovery and edit back the refind.config file.
My current Arch entry in refind.config is the following:
# UUID: 9C4B48BE-7F69-47E1-8828-AB21C8AD1AFC
menuentry "Arch Linux" {
icon /EFI/refind/icons/os_arch.png
volume "Arch Linux"
loader /boot/vmlinuz-linux
initrd /boot/initramfs-linux.img
options "root=PARTUUID=9C4B48BE-7F69-47E1-8828-AB21C8AD1AFC rw add_efi_memmap"
submenuentry "Boot using fallback initramfs" {
initrd /boot/initramfs-linux-fallback.img
}
submenuentry "Boot to terminal" {
add_options "systemd.unit=multi-user.target"
}
}I saw lot of similar topic but none of them could help me to fix mine. Thanks to anyone.
Offline
# UUID: 9C4B48BE-7F69-47E1-8828-AB21C8AD1AFC
options "root=PARTUUID=9C4B48BE-7F69-47E1-8828-AB21C8AD1AFC rw add_efi_memmap"
Maybe check first carefully your device ID's and if you're quoting the UUID or the PARTUUID of the device.
Last edited by d_fajardo (2019-08-27 16:59:37)
Offline
# UUID: 9C4B48BE-7F69-47E1-8828-AB21C8AD1AFC
options "root=PARTUUID=9C4B48BE-7F69-47E1-8828-AB21C8AD1AFC rw add_efi_memmap"
Maybe check first carefully your device ID's and if you're quoting the UUID or the PARTUUID of the device.
Thanks for your reply. I checked the device ID and it's the expected one, also i'm not quoting it.
Kernel auto detection is not working as well, I get only the manual entry which is not working.
Offline
Warning: loader and initrd paths are relative to the root of volume. If /boot is a separate partition (e.g. the ESP), the loader and initrd paths would be /vmlinuz-linux and /initramfs-linux.img, respectively.
Did you heed this warning from the rEFInd Wiki? Is the ESP in a separate partition?
Offline
Warning: loader and initrd paths are relative to the root of volume. If /boot is a separate partition (e.g. the ESP), the loader and initrd paths would be /vmlinuz-linux and /initramfs-linux.img, respectively.
Did you heed this warning from the rEFInd Wiki? Is the ESP in a separate partition?
Hi d_fajardo, thanks again for your help. Yes the ESP was in a separate partition. At the end I managed to make rEFInd kernel autodetection working by installing grub-efi on Arch.
Offline
At the end I managed to make rEFInd kernel autodetection working by installing grub-efi on Arch.
Did you have to? Did you try simply updating the paths (i.e. without '/boot')
Offline
At the end I managed to make rEFInd kernel autodetection working by installing grub-efi on Arch.
Did you have to? Did you try simply updating the paths (i.e. without '/boot')
It was the only method I found to make it works. Also, after installing grub started to work both the autodetection that the manual entry I had written.
Offline