For instance, when replacing the bootloader for rEFInd. This file ussualy works out of the box when it is generated from the same boot session as it is supposed to start. None of the entries contain the initramfs, as it is established automatically at boot. And minimal is contains only the current root device, with the ro argument. Single is the same as default, but with single added. The default entry is based on the current /proc/cmdline. Each entry will show up as an option for each kernel. It is automatically generated in /boot during refind_install or with mkrlconf. Refind_nf should live in the same directory as the kernels. Follow the above naming convention for best results, though more detail can be found in the config file. In order to play nice with icon assertion, the kernel must be stored in EFI/Gentoo.įile names are important to rEFInd, especially for matching kernels with their initramfs. It is possible to store the kernels and initial RAM disks on the ESP, instead of /boot. Either, the initramfs should be named using the same convention, or its name should be specified in refind_nf. However, if a Custom Initramfs is used some care is required. When using tools like Genkernel or Dracut, no additional configuration is required. Provided that refind_nf does not specify an initrd, it is automatically appended to the kernel command line. For example initramfs-5.4.66-gentoo.img matches with initramfs-5.4.66-gentoo.img.
This makes it compatible with (semi-) automatic kernel installation methods such as genkernel -install or make install without further configuration.Īt boot, rEFInd looks for an initial RAM disk that starts with init and ends in a kernel version string. Regardless if /boot is a separate partition or part of the root file system, rEFInd should be able to find a kernel if standard naming convention is used. This installation method can be used as either a permanent setup to create a bootable USB flash drive or install rEFInd on a computer that tends to "forget" its NVRAM settings or as a temporary bootstrap to get the system to boot in EFI mode. Root # refind-install -usedefault /dev/sda Call efibootmgr to set itself as the default boot manager.Install its refind_圆4.efi application and other stuff into the ESP.If not, automount the ESP according to /etc/fstab The rEFInd package comes with the refind-install command. This will require some additional steps when installing the kernel. Only ESP partition, with kernels living in /EFI/Gentoo/.(Provided it is a non-encrypted, non-LVM and one of the above supported filesystems). Seperate ESP partition with /boot part of the root filesystem.(See example in the Kernel image at ESP section).īoot partition configuration is quite flexible. On the filesystems it can read (based on above USE flags), it scans in the following locations : efi or beginning with vmlinuz, bzImage or kernel. See EFI System Partition.įor kernel storage there are multiple options.ĭuring boot, rEFInd can automatically find EFI boot images and Linux kernels. If an ESP does not exist, one needs to be created. Once the rEFInd package has been emerged, a second step is needed to install the binaries to the ESP. The binaries into your EFI System Partition You will need to use the command 'refind-install' to install Root # emerge -ask sys-boot/refind rEFInd has been built and installed into $