Difference between revisions of "Talk:UEFI Bootloaders"

From ArchWiki
Jump to: navigation, search
(Incorrect instructions: new section)
(Incorrect instructions)
Line 8: Line 8:
 
''"Note: As of refind-efi 0.6.5, refind now automatically detects kernels in /boot. They do not have to be renamed to have a .efi extension either. Hence, the following sync scripts aren't needed if using refind."''
 
''"Note: As of refind-efi 0.6.5, refind now automatically detects kernels in /boot. They do not have to be renamed to have a .efi extension either. Hence, the following sync scripts aren't needed if using refind."''
  
But how it is possible for rEFInd to scan the /boot directory? When booting rEFInd, only the dirs inside \EFI are readable for rEFInd. I have tested this and I confirm that rEFInd can't scan /boot until it is mounted by fstab. (the actual booting process)
+
But how it is possible for rEFInd to scan the /boot directory? When booting rEFInd, only the dirs inside \EFI are readable for rEFInd. I have tested this and I confirm that rEFInd can't scan /boot until it is mounted by fstab. (the actual booting process). The sync scripts seems to be needed, to successfully boot Arch.
  
  

Revision as of 11:15, 28 January 2013

Incorrect instructions

Hi,

I have already posted some information on the Forums, but since this is the way to go, I'm posting my thoughts here.

The Wiki's says the following about rEFInd: "Note: As of refind-efi 0.6.5, refind now automatically detects kernels in /boot. They do not have to be renamed to have a .efi extension either. Hence, the following sync scripts aren't needed if using refind."

But how it is possible for rEFInd to scan the /boot directory? When booting rEFInd, only the dirs inside \EFI are readable for rEFInd. I have tested this and I confirm that rEFInd can't scan /boot until it is mounted by fstab. (the actual booting process). The sync scripts seems to be needed, to successfully boot Arch.


As for Systemd Automation script, I find the following line a little bit weird: cp -r /usr/{share/refind/*,lib/refind/*$arch*} $refind_dir/ && ## update bin and dirs

Should it not be: cp -r {/usr/share/refind/*,/lib/refind/refind_x*$arch*.efi} $refind_dir/ && ## update bin and dirs ? Only the file refind_x*ARCH*, is needed for the /lib directory.


Also I would like to see instructions how to add a custom boot entry (if needed/other location). They are documented inside rEFInd, but not on the Wiki. menuentry "Arch Linux" {

   icon /EFI/refind/icons/os_arch.icns
   loader /EFI/arch/vmlinuz-arch.efi
   initrd /EFI/arch/initramfs-arch.img
   options "root=PARTUUID=xx rootfstype=ext4 ro add_efi_memmap systemd.unit=graphical.target"

}

menuentry "Arch Linux Fallback" {

   icon /EFI/refind/icons/os_arch.icns
   loader /EFI/arch/vmlinuz-arch.efi
   initrd /EFI/arch/initramfs-arch-fallback.img
   options "root=PARTUUID=xx rootfstype=ext4 ro add_efi_memmap systemd.unit=multi-user.target"

}


Thanks

Beta990 (talk) 11:11, 28 January 2013 (UTC)