You are not logged in.
Wiki says:
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 I can't get it to work. That is, I delete /boot/efi/EFI/arch/*.{img,efi}, but it doesn't find the files (initramfs-linux-fallback.img, initramfs-linux.img, vmlinuz-linux) in /boot. Am I doing it wrong? Also I can't see anything like this in changelog. I have refind-efi 0.6.11-1.
Last edited by x-yuri (2013-06-12 23:53:07)
Offline
Make sure you also copied the refind drivers to the efi partition so that it can read the partition with the kernels.
Offline
Diaz is correct; you need an EFI driver for your root (or /boot, if it's separate) partition. Also, rEFInd has been scanning inside the directory called "boot" since at least version 0.2.7, and I believe earlier than that. (I'd need to dig into the source code to be sure.) I've just edited the wiki to correct the version number and add a note that an EFI driver is required.
Offline
I've copied the drivers onto UEFISYS partition (I've put refind into EFI/boot so that VirtualBox would automatically run refind):
// booted from arch live cd
# ls -R
.:
EFI/
./EFI:
arch/ boot/ tools/
./EFI/arch:
refind_linux.conf*
./EFI/boot:
bootx64.efi* icons/ refind.conf*
./EFI/boot/icons:
arrow_left.icns* os_freebsd.icns* os_refind.icns*
arrow_right.icns* os_freedos.icns* os_refit.icns*
boot_linux.icns* os_gentoo.icns* os_slackware.icns*
boot_win.icns* os_gummiboot.icns* os_suse.icns*
func_about.icns* os_haiku.icns* os_ubuntu.icns*
func_exit.icns* os_hwtest.icns* os_unknown.icns*
func_firmware.icns* os_kubuntu.icns* os_win.icns*
func_reset.icns* os_legacy.icns* tool_apple_rescue.icns*
func_shutdown.icns* os_linux.icns* tool_mok_tool.icns*
os_altlinux.icns* os_linuxmint.icns* tool_part.icns*
os_arch.icns* os_lubuntu.icns* tool_shell.icns*
os_centos.icns* os_mac.icns* transparent.icns*
os_chrome.icns* os_mandriva.icns* vol_external.icns*
os_debian.icns* os_netbsd.icns* vol_internal.icns*
os_ecomstation.icns* os_openbsd.icns* vol_optical.icns*
os_fatdog.icns* os_opensuse.icns*
os_fedora.icns* os_redhat.icns*
./EFI/tools:
drivers/
./EFI/tools/drivers:
ext2_x64.efi* ext4_x64.efi* hfs_x64.efi* iso9660_x64.efi* reiserfs_x64.efi*
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 30G 0 disk
├─sda1 8:1 0 512M 0 part /mnt/boot/efi
├─sda2 8:2 0 100M 0 part /mnt/boot
└─sda3 8:3 0 29.4G 0 part
└─VolGroup00-lvolroot (dm-1)
254:1 0 29.4G 0 lvm /mnt
...With no result though, refind displays no options for booting OS.
Offline
And then I've renamed boot -> refind and run refind_x64.efi from UEFI shell:
# ls -R
.:
EFI/
./EFI:
arch/ refind/ tools/
./EFI/arch:
refind_linux.conf*
./EFI/refind:
icons/ refind.conf* refind_x64.efi*
./EFI/refind/icons:
arrow_left.icns* os_freebsd.icns* os_refind.icns*
arrow_right.icns* os_freedos.icns* os_refit.icns*
boot_linux.icns* os_gentoo.icns* os_slackware.icns*
boot_win.icns* os_gummiboot.icns* os_suse.icns*
func_about.icns* os_haiku.icns* os_ubuntu.icns*
func_exit.icns* os_hwtest.icns* os_unknown.icns*
func_firmware.icns* os_kubuntu.icns* os_win.icns*
func_reset.icns* os_legacy.icns* tool_apple_rescue.icns*
func_shutdown.icns* os_linux.icns* tool_mok_tool.icns*
os_altlinux.icns* os_linuxmint.icns* tool_part.icns*
os_arch.icns* os_lubuntu.icns* tool_shell.icns*
os_centos.icns* os_mac.icns* transparent.icns*
os_chrome.icns* os_mandriva.icns* vol_external.icns*
os_debian.icns* os_netbsd.icns* vol_internal.icns*
os_ecomstation.icns* os_openbsd.icns* vol_optical.icns*
os_fatdog.icns* os_opensuse.icns*
os_fedora.icns* os_redhat.icns*
./EFI/tools:
drivers/
./EFI/tools/drivers:
ext2_x64.efi* ext4_x64.efi* hfs_x64.efi* iso9660_x64.efi* reiserfs_x64.efi*Nevertheless with the same result.
Offline
I see, either one needs to put drivers into EFI\refind\drivers{,_<arch>} directory, or specify path to them:
# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#
#scan_driver_dirs EFI/tools/drivers,drivers
Offline
Fixed wiki.
Offline
Don't forget to makr your thread here as [Solved].
Offline