You are not logged in.

#1 2013-02-14 04:43:42

donniezazen
Member
From: Salt Lake City
Registered: 2011-06-24
Posts: 671
Website

[SOLVED] Help Setting up rEFInd

Hello,

I am trying to setup rEFInd to work with kernels I have installed (core and mainline). I am getting error Error: Not Found While Loading vmllinuz-linux. Here is some back ground.

Directory and File Tree

ls -R /boot
/boot:
efi  initramfs-linux-fallback.img  initramfs-linux.img  initramfs-linux-mainline.img  refind_linux.conf  vmlinuz-linux  vmlinuz-linux-mainline

/boot/efi:
EFI

/boot/efi/EFI:
arch  refind

/boot/efi/EFI/arch:
initramfs-arch-fallback.img  initramfs-arch.img  refind_linux.conf  vmlinuz-arch.efi

/boot/efi/EFI/refind:
icons  refind.conf  refind_x64.efi

/boot/efi/EFI/refind/icons:
***All Icon Files***

refind_linux.com in /boot/efi/EFI/arch and /boot

cat refind_linux.conf
"Boot to X"			"root=PARTUUID=53677820-f114-456b-9b2e-6ca2a07f2c36 ro rootfstype=ext4 systemd.unit=graphical.target"
"Boot to Console"		"root=PARTUUID=53677820-f114-456b-9b2e-6ca2a07f2c36 ro rootfstype=ext4 systemd.unit=multi-user.target"

/boot/efi/EFI/refind/refind.conf Relevant part is below. Here is the full file.

menuentry "Arch Linux Core Kernel" {
    icon /EFI/refind/icons/os_arch.icns
    loader /boot/vmlinuz-linux
    initrd /boot/initramfs-linux.img
    options "root=PARTUUID=53677820-f114-456b-9b2e-6ca2a07f2c36 rootfstype=ext4 systemd.unit=graphical.target"
    ostype Linux
    graphics off
}

menuentry "Arch Linux Core Kernel Fallback" {
    icon /EFI/refind/icons/os_arch.icns
    loader /boot/vmlinuz-linux
    initrd /boot/initramfs-linux-fallback.img
    options "root=PARTUUID=53677820-f114-456b-9b2e-6ca2a07f2c36 rootfstype=ext4 systemd.unit=graphical.target"
    ostype Linux
    graphics off
}

My understanding is refind-efi 0.6.5 and above can detect kernel files in /boot and doesn't require it to be renamed with extension .efi. Currently, I am able to boot through /boot/efi/EFI/arch but that shouldn't be required anymore and should be safe to remove once I can get refind to work. What am I doing wrong in refind.conf that it isn't able to find vmlinuz-linux.

Source:- https://wiki.archlinux.org/index.php/UEFI_Bootloaders

Thanks.

UPDATE:- Reading and tinkering solved all my confusions. More details are in this thread.

Last edited by donniezazen (2013-04-04 06:56:15)

Offline

#2 2013-02-14 09:33:46

swordfish
Member
Registered: 2012-01-14
Posts: 160

Re: [SOLVED] Help Setting up rEFInd

Haven't tried it myself, so it's just kind of a "best guess". The wiki says:

Note: As of refind-efi 0.6.5-1, refind can auto-detect kernels in /boot, if there are UEFI drivers for the filesystem used by /boot partition (or / partition if no separate /boot is used) in the ESP, and are loaded by rEFInd. To enable rEFInd to detect and load the drivers and /boot kernels you must enable the appropriate options in refind.conf (mainly mention the PATH for the drivers location in the ESP) and also copy your refind_linux.conf to /boot/refind_linux.conf .

So, I assume, you have to copy the ext4 drivers to your ESP and uncomment the line

#scan_driver_dirs EFI/tools/drivers,drivers

in your refind.conf.


Arch_x64 on Thinkpad Edge E520 (Intel Core i5, 4 GB RAM, 128 GB Crucial M4 SSD) + ITX-Desktop (Asrock H77M-ITX, Intel Core i3-2120T, 8GB RAM, 64 GB Samsung 830 SSD)

Offline

#3 2013-02-14 09:42:52

the.ridikulus.rat
Member
From: Indiana, USA
Registered: 2011-10-04
Posts: 765

Re: [SOLVED] Help Setting up rEFInd

See my rEFInd config files below, they are self-explanatory:

/boot/efi/EFI/refind/refind.conf

#
# refind.conf
# Configuration file for the rEFInd boot menu
#

# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout).
#
timeout 3

# Hide user interface elements for personal preference or to increase
# security:
#  banner      - the rEFInd title banner (built-in or loaded via "banner")
#  label       - boot option text label in the menu
#  singleuser  - remove the submenu options to boot Mac OS X in single-user
#                or verbose modes; affects ONLY MacOS X
#  safemode    - remove the submenu option to boot Mac OS X in "safe mode"
#  hwtest      - the submenu option to run Apple's hardware test
#  arrows      - scroll arrows on the OS selection tag line
#  hints       - brief command summary in the menu
#  editor      - the options editor (+, F2, or Insert on boot options menu)
#  all         - all of the above
# Default is none of these (all elements active)
#
#hideui singleuser
#hideui all

# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Default is "icons".
#
#icons_dir myicons

# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
#
#banner hostname.bmp
#banner mybanner.png

# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
#
# Like the banner option above, these options take a filename of an
# uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#
#selection_big   selection-big.bmp
#selection_small selection-small.bmp

# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#
#font myfont.png

# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#
#textonly
textonly

# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#
#textmode 2
textmode 1024

# Set the screen's video resolution. Pass this option either:
#  * two values, corresponding to the X and Y resolutions
#  * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#
#resolution 1024 768
#resolution 3
resolution 1366 768

# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except OS X. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
#   osx     - Mac OS X
#   linux   - A Linux kernel with EFI stub loader
#   elilo   - The ELILO boot loader
#   grub    - The GRUB (Legacy or 2) boot loader
#   windows - Microsoft Windows
# Default value: osx
#
#use_graphics_for osx,linux

# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
#  shell           - the EFI shell (requires external program; see rEFInd
#                    documentation for details)
#  gptsync         - the (dangerous) gptsync.efi utility (requires external
#                    program; see rEFInd documentation for details)
#  apple_recovery  - boots the Apple Recovery HD partition, if present
#  mok_tool        - makes available the Machine Owner Key (MOK) maintenance
#                    tool, MokManager.efi, used on Secure Boot systems
#  about           - an "about this program" option
#  exit            - a tag to exit from rEFInd
#  shutdown        - shuts down the computer (a bug causes this to reboot
#                    EFI systems)
#  reboot          - a tag to reboot the computer
# Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
#
#showtools shell, mok_tool, about, reboot, exit
showtools mok_tool,about,reboot,shutdown,exit

# 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
scan_driver_dirs EFI/tools/drivers_x64

# Which types of boot loaders to search, and in what order to display them:
#  internal      - internal EFI disk-based boot loaders
#  external      - external EFI disk-based boot loaders
#  optical       - EFI optical discs (CD, DVD, etc.)
#  hdbios        - BIOS disk-based boot loaders
#  biosexternal  - BIOS external boot loaders (USB, eSATA, etc.)
#  cd            - BIOS optical-disc boot loaders
#  manual        - use stanzas later in this configuration file
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#
#scanfor internal,external,optical,manual
# scanfor manual,internal,external,optical,hdbios,biosexternal,cd
scanfor manual,internal,external,optical

# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#
#scan_delay 5
scan_delay 0

# When scanning volumes for EFI boot loaders, rEFInd always looks for
# Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#
#also_scan_dirs boot,ESP2:EFI/linux/kernels
# also_scan_dirs UEFISYS:EFI/arch/arch_linux_core,UEFISYS:EFI/arch/arch_linux_mainline

# Partitions to omit from scans. You must specify a volume by its
# label, which you can obtain in an EFI shell by typing "vol", from
# Linux by typing "blkid /dev/{devicename}", or by examining the
# disk's label in various OSes' file browsers.
# The default is "Recovery HD".
#
#dont_scan_volumes "Recovery HD"

# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory or the EFI/tools directory.
# You can "blacklist" additional directories with this option, which
# takes a list of directory names as options. You might do this to
# keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
# another boot loader or to exclude a directory that holds drivers
# or non-bootloader utilities provided by a hardware manufacturer. If
# a directory is listed both here and in also_scan_dirs, dont_scan_dirs
# takes precedence. Note that this blacklist applies to ALL the
# filesystems that rEFInd scans, not just the ESP, unless you precede
# the directory name by a filesystem name, as in "myvol:EFI/somedir"
# to exclude EFI/somedir from the scan on the myvol volume but not on
# other volumes.
#
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell
dont_scan_dirs UEFISYS:EFI/boot

# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, MokManager.efi is in this blacklist,
# but will show up as a tool if present in certain directories. You
# can control the tools row with the showtools token.
# The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
#
#dont_scan_files shim.efi,MokManager.efi

# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When uncommented, this option causes
# all files in scanned directories with names that begin with "vmlinuz"
# or "bzImage" to be included as loaders, even if they lack ".efi"
# extensions. The drawback to this option is that it can pick up kernels
# that lack EFI stub loader support and other files. Passing this option
# a "0" value causes kernels without ".efi" extensions to NOT be scanned;
# passing it alone or with any other value causes all kernels to be scanned.
# Default is to NOT scan for kernels without ".efi" extensions.
#
scan_all_linux_kernels

# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#
#max_tags 0

# Set the default menu selection.  The available arguments match the
# keyboard accelerators available within rEFInd.  You may select the
# default loader using:
#  - A digit between 1 and 9, in which case the Nth loader in the menu
#    will be the default. 
#  - Any substring that corresponds to a portion of the loader's title
#    (usually the OS's name or boot loader's path).
#
#default_selection 1
default_selection "Arch Linux Core Kernel"

# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#
#include manual.conf

# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
#
#  volume    - identifies the filesystem from which subsequent files
#              are loaded. You can specify the volume by label or by
#              a number followed by a colon (as in "0:" for the first
#              filesystem or "1:" for the second).
#  loader    - identifies the boot loader file
#  initrd    - Specifies an initial RAM disk file
#  icon      - specifies a custom boot loader icon
#  ostype    - OS type code to determine boot options available by
#              pressing Insert. Valid values are "MacOS", "Linux",
#              "Windows", and "XOM". Case-sensitive.
#  graphics  - set to "on" to enable graphics-mode boot (useful
#              mainly for MacOS) or "off" for text-mode boot.
#              Default is auto-detected from loader filename.
#  options   - sets options to be passed to the boot loader; use
#              quotes if more than one option should be passed or
#              if any options use characters that might be changed
#              by rEFInd parsing procedures (=, /, #, or tab).
#  disabled  - use alone or set to "yes" to disable this entry.
#
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.

########################################################################
########################################################################

menuentry "Arch Linux Core Kernel" {
    icon /EFI/refind/icons/os_arch.icns
    volume UEFISYS
    loader /EFI/arch/arch_linux_core/vmlinuz-ARCH-core.efi
    initrd /EFI/arch/arch_linux_core/initramfs-ARCH-core.img
    options "root=PARTUUID=6f44c56d-d5c2-41ca-8c54-873d8dc5e5e3 rootfstype=ext4 gpt loglevel=6 printk.time=y pcie_aspm=force i915.i915_enable_rc6=1 nouveau.nofbaccel=1 add_efi_memmap systemd.unit=graphical.target"
    ostype Linux
    graphics off
}

menuentry "Arch Linux Core Kernel Fallback" {
    icon /EFI/refind/icons/os_arch.icns
    volume UEFISYS
    loader /EFI/arch/arch_linux_core/vmlinuz-ARCH-core.efi
    initrd /EFI/arch/arch_linux_core/initramfs-ARCH-core-fallback.img
    options "root=PARTUUID=6f44c56d-d5c2-41ca-8c54-873d8dc5e5e3 rootfstype=ext4 gpt loglevel=6 printk.time=y pcie_aspm=force i915.i915_enable_rc6=1 nouveau.nofbaccel=1 add_efi_memmap systemd.unit=graphical.target"
    ostype Linux
    graphics off
}

menuentry "Arch Linux Mainline Kernel" {
    icon /EFI/refind/icons/os_arch.icns
    volume UEFISYS
    loader /EFI/arch/arch_linux_mainline/vmlinuz-arch-mainline.efi
    initrd /EFI/arch/arch_linux_mainline/initramfs-arch-mainline.img
    options "root=PARTUUID=6f44c56d-d5c2-41ca-8c54-873d8dc5e5e3 rootfstype=ext4 gpt loglevel=6 printk.time=y pcie_aspm=force i915.i915_enable_rc6=1 nouveau.nofbaccel=1 add_efi_memmap systemd.unit=graphical.target"
    ostype Linux
    graphics off
}

menuentry "Arch Linux Mainline Kernel Fallback" {
    icon /EFI/refind/icons/os_arch.icns
    volume UEFISYS
    loader /EFI/arch/arch_linux_mainline/vmlinuz-arch-mainline.efi
    initrd /EFI/arch/arch_linux_mainline/initramfs-arch-mainline-fallback.img
    options "root=PARTUUID=6f44c56d-d5c2-41ca-8c54-873d8dc5e5e3 rootfstype=ext4 gpt loglevel=6 printk.time=y pcie_aspm=force i915.i915_enable_rc6=1 nouveau.nofbaccel=1 add_efi_memmap systemd.unit=graphical.target"
    ostype Linux
    graphics off
}

menuentry "UEFI x86_64 Shell v2" {
    icon /EFI/refind/icons/tool_shell.icns
    volume UEFISYS
    loader /EFI/tools/shellx64_v2.efi
    graphics off
}

menuentry "UEFI x86_64 Shell v1" {
    icon /EFI/refind/icons/tool_shell.icns
    volume UEFISYS
    loader /EFI/tools/shellx64_v1.efi
    graphics off
}

menuentry "Arch Linux x86_64 Archboot" {
    icon /EFI/refind/icons/os_arch.icns
    volume UEFISYS
    loader /EFI/arch/archboot/vmlinuz_x86_64
    initrd /EFI/arch/archboot/initramfs_x86_64.img
    options "gpt loglevel=7 add_efi_memmap none=UEFI_ARCH_x86_64"
    ostype Linux
    graphics off
}

menuentry "Arch Linux LTS x86_64 Archboot via EFILINUX" {
    icon /EFI/refind/icons/os_arch.icns
    volume UEFISYS
    loader /EFI/efilinux/efilinuxx64.efi
    initrd /EFI/arch/archboot/initramfs_x86_64.img
    options "-f \EFI\arch\archboot\vmlinuz_x86_64_lts gpt loglevel=7 add_efi_memmap none=UEFI_ARCH_x86_64"
    ostype Linux
    graphics off
    disabled
}

########################################################################
########################################################################

# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.

# A sample entry for a Linux 3.3 kernel with its new EFI boot stub
# support on a filesystem called "KERNELS". This entry includes
# Linux-specific boot options and specification of an initial RAM disk.
# Note uses of Linux-style forward slashes, even in the initrd
# specification. Also note that a leading slash is optional in file
# specifications.
menuentry Linux {
	icon EFI/refind/icons/os_linux.icns
	volume KERNELS
	loader bzImage-3.3.0-rc7
	initrd initrd-3.3.0.img
	options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
	disabled
}

# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
	loader /EFI/ubuntu/grubx64.efi
	icon /EFI/refined/icons/os_linux.icns
	disabled
}

# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
	loader \EFI\elilo\elilo.efi
	disabled
}

# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
	loader \EFI\Microsoft\Boot\bootmgfw.efi
	disabled
}

# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
	icon \EFI\refind\icons\os_win.icns
	loader \EFI\tools\shell.efi
	options "fs0:\EFI\tools\launch_windows.nsh"
	disabled
}

# Mac OS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My Mac OS X" {
	icon \EFI\refind\icons\os_mac.icns
	volume "OS X boot"
	loader \System\Library\CoreServices\boot.efi
	disabled
}

/boot/refind_linux.conf

## This file should be present in the same directory as the kernel file(s)
## More info at http://www.rodsbooks.com/refind/linux.html , http://www.rodsbooks.com/efi-bootloaders/efistub.html

"Boot into Graphics mode"    "root=PARTUUID=6f44c56d-d5c2-41ca-8c54-873d8dc5e5e3 rootfstype=ext4 gpt loglevel=6 printk.time=y pcie_aspm=force i915.i915_enable_rc6=1 nouveau.nofbaccel=1 add_efi_memmap systemd.unit=graphical.target initrd=\initramfs-linux-fallback.img initrd=\initramfs-linux-mainline-fallback.img"
"Boot into Terminal mode"    "root=PARTUUID=6f44c56d-d5c2-41ca-8c54-873d8dc5e5e3 rootfstype=ext4 gpt loglevel=6 printk.time=y pcie_aspm=force i915.i915_enable_rc6=1 nouveau.nofbaccel=1 add_efi_memmap systemd.unit=multi-user.target initrd=\initramfs-linux-fallback.img initrd=\initramfs-linux-mainline-fallback.img"
"Boot into Rescue mode"      "root=PARTUUID=6f44c56d-d5c2-41ca-8c54-873d8dc5e5e3 rootfstype=ext4 gpt loglevel=6 printk.time=y pcie_aspm=force i915.i915_enable_rc6=1 nouveau.nofbaccel=1 add_efi_memmap systemd.unit=rescue.target initrd=\initramfs-linux-fallback.img initrd=\initramfs-linux-mainline-fallback.img"

For this you need to have /boot/efi/EFI/tools/drivers_x64/ext4_x64.efi driver, otherwise rEFInd wont be able to read /boot. I have /boot as a separate partition from / root partition. If your /boot is part of root partition, you need to modify the file paths accordingly.

Offline

#4 2013-02-14 16:09:37

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: [SOLVED] Help Setting up rEFInd

donniezazen wrote:

Hello,

I am trying to setup rEFInd to work with kernels I have installed (core and mainline). I am getting error Error: Not Found While Loading vmllinuz-linux.

That error indicates that the file vmlinuz-linux isn't present. Chances are this was generated by your manual boot stanza, which as written requires that the file /boot/vmlinuz-linux be installed on a volume called UEFISYS. Assuming that name is descriptive, this is presumably your ESP, but no such file is present on the ESP.

More broadly speaking, you're at least partially set up for two methods of launching Linux, but I suspect that both of these methods is missing at least one critical element:

  • Manual boot stanzas -- As noted, your current manual boot stanzas refer to files on the UEFISYS volume, but they don't seem to be present (assuming "UEFISYS" is your ESP). You must either copy your kernel and initrd files or specify your root or /boot partition on the "volume" line (and adjust the path if you've got a separate /boot partition).

  • Auto-detection -- rEFInd scans certain locations for boot loaders, including the root (/) directory and the /boot directory of every volume it can read. Thus, it should pick up a Linux kernel in its natural "home" if the EFI can read the appropriate filesystem. This conditional is critical. If your kernel is on an ext4 filesystem, for instance, the EFI can't read it unless you install rEFInd's ext4fs driver. My guess is that you haven't installed such a driver, and so auto-detection is not picking up your kernels and you're only seeing entries for your manual boot stanzas. Installing a suitable filesystem driver will change this if your kernels are in a standard partition (not a RAID or LVM setup) that uses ext2/3/4fs, ReiserFS, or HFS+.

In most cases, auto-detection is preferable because it picks up new kernels automatically; however, given the usual Arch naming scheme, either method works. Since rEFInd defaults to doing auto-detection, it's probably still just a little easier to set up, though. In either case, you need to ensure that rEFInd can read the filesystem on which the kernel is stored. You can do this by using drivers or by copying the kernel to the ESP. The latter is easier if you mount the ESP at /boot; but if you're not currently set up that way, you'll need to juggle some files to get that to work.

Offline

#5 2013-02-14 21:45:32

swordfish
Member
Registered: 2012-01-14
Posts: 160

Re: [SOLVED] Help Setting up rEFInd

Sorry for hijacking this thread a little bit, but how do I tell rEFInd to use the "Arch" logo on bootup if I switch to auto-detection?

Background: Out of curiosity I have set my system for auto-detection. This means:

- I have deleted /boot/efi/EFI/arch and moved refind_linux.conf to /boot
- I have created a directory /boot/efi/EFI/tools/drivers_x64 and copied the relevant drivers from /usr/lib/refind/drivers_x64
- I have uncommented the "scan_drivers_dir" line in refind.conf to look for drivers in /EFI/tools/drivers_x64

After a reboot rEFInd shows me now the penguin image as boot option. But I would like to use the Arch logo. How do I tell rEFInd to use it?

Ah, and by the way - do I have to change the nvram entry for rEFInd?


Arch_x64 on Thinkpad Edge E520 (Intel Core i5, 4 GB RAM, 128 GB Crucial M4 SSD) + ITX-Desktop (Asrock H77M-ITX, Intel Core i3-2120T, 8GB RAM, 64 GB Samsung 830 SSD)

Offline

#6 2013-02-14 23:22:29

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 5,670

Re: [SOLVED] Help Setting up rEFInd

You don't need to change the nvram entry unless the refind directory is in a different place which it isn't unless you just didn't mention that. Plus, if that was needed, presumably it wouldn't boot to rEFInd (unless you also have it installed as a backup default).


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | grub2 | systemd | LVM2 on LUKS
Lenovo x121e | Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz GenuineIntel | Intel Centrino Wireless-N 1000 | US keyboard with Euro | 320G 7200 RPM Seagate HDD

Offline

#7 2013-02-15 19:17:29

srs5694
Member
From: Woonsocket, RI
Registered: 2012-11-06
Posts: 719
Website

Re: [SOLVED] Help Setting up rEFInd

swordfish wrote:

Sorry for hijacking this thread a little bit, but how do I tell rEFInd to use the "Arch" logo on bootup if I switch to auto-detection?

See the bulleted list under Hiding and Displaying EFI Boot Loaders in the rEFInd documentation. If you need more guidance on this, please start a new thread.

Offline

#8 2013-02-15 19:54:33

swordfish
Member
Registered: 2012-01-14
Posts: 160

Re: [SOLVED] Help Setting up rEFInd

srs5694 wrote:
swordfish wrote:

Sorry for hijacking this thread a little bit, but how do I tell rEFInd to use the "Arch" logo on bootup if I switch to auto-detection?

See the bulleted list under Hiding and Displaying EFI Boot Loaders in the rEFInd documentation. If you need more guidance on this, please start a new thread.

Ah, great - thanks for the hint wink !!!


Arch_x64 on Thinkpad Edge E520 (Intel Core i5, 4 GB RAM, 128 GB Crucial M4 SSD) + ITX-Desktop (Asrock H77M-ITX, Intel Core i3-2120T, 8GB RAM, 64 GB Samsung 830 SSD)

Offline

Board footer

Powered by FluxBB