The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Install/Bootloader
Install Guide: Bootloader
Install Guide, Chapter 14 | < Prev | Next > |
These install instructions show you how to use GRUB to boot using BIOS (legacy) or UEFI.
ego boot update (ego boot
) is installed by default, but GRUB is not, as it is not required for all Funtoo Linux systems (such as containers, for example.) But for booting on bare metal, it is the recommended and best-supported boot loader, so you will need to emerge it:
chroot # emerge -av grub
Next, edit /etc/boot.conf
using nano
and specify "Funtoo Linux genkernel
" as the default
setting at the top of the file, replacing "Funtoo Linux"
.
boot.conf Configuration
Most users, particularly those who plan on setting up a graphical environment, will want to eventually remove nomodeset
from params
in /etc/make.conf
. nomodeset
prevents the kernel from changing graphics modes at boot. This option is in /etc/boot.conf
by default for a couple of good reasons:
- For users with HiDPI (4K+) displays: when the kernel automatically changes graphics modes, the console font can be tiny and unreadable.
- For users with incompatible graphics cards: Some graphics cards don't handle mode setting properly and this can result in a blank screen after reboot.
Disabling mode setting is therefore a good, safe option for initial installs of Funtoo Linux.
However, essentially all graphics drivers (the big exception being the proprietary NVIDIA drivers) require mode setting to be enabled. So while nomodeset
is a good option to get the initial system up and running, most users will need to remove it, run ego boot update
and reboot before they set up X or Wayland.
Make a mental note -- most users will want to remove the nomodeset
option from params
prior to setting up their graphical environment. It is included in the initial install to ensure that virtually all systems boot up with a readable console. But all graphics drivers (with the one exception of the proprietary NVIDIA drivers) REQUIRE mode setting to be enabled, and thus the nomodeset
option must be removed prior to setting up a graphical environment or X will not start. Remember to run ego boot update
after removing the option, and then reboot prior to configuring X.
/etc/boot.conf
should now look like this:
/etc/boot.conf
boot {
generate grub
default "Funtoo Linux genkernel"
timeout 3
}
"Funtoo Linux" {
kernel bzImage[-v]
}
"Funtoo Linux genkernel" {
kernel kernel[-v]
initrd initramfs[-v]
params += real_root=auto rootfstype=auto nomodeset
}
If you are booting a custom or non-default kernel, please read man boot.conf
for information on the various options available to you.
Intel Microcode
ego boot
will ensure that you have the most recent Intel CPU microcode installed on your system if you emerge the
following packages:
chroot # emerge intel-microcode iucode_tool
This is not necessary for AMD systems.
Old School (BIOS) MBR
When using "old school" BIOS booting, run the following command to install GRUB to your MBR, and generate the /boot/grub/grub.cfg
configuration file that GRUB will use for booting:
chroot # grub-install --target=i386-pc --no-floppy /dev/sda chroot # ego boot update
New School (UEFI) Boot Entry
If you're using "new school" UEFI booting, run of the following sets of commands, depending on whether you are installing a 64-bit or 32-bit system. This will add GRUB as a UEFI boot entry.
For x86-64bit systems:
chroot # mount -o remount,rw /sys/firmware/efi/efivars chroot # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda chroot # ego boot update
For x86-32bit systems:
chroot # mount -o remount,rw /sys/firmware/efi/efivars chroot # grub-install --target=i386-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda chroot # ego boot update
First Boot, and in the future...
OK -- you are almost ready to boot!
You only need to run grub-install
when you first install Funtoo Linux, but you need to re-run ego boot update
every time you modify your /etc/boot.conf
file or add new kernels to your system. This will regenerate /boot/grub/grub.cfg
so that you will have new kernels available in your GRUB boot menu, the next time you reboot.
Install Guide, Chapter 14 | < Prev | Next > |