-
-
Notifications
You must be signed in to change notification settings - Fork 1
Bootloader
Kevin P. Wilson edited this page Aug 7, 2024
·
1 revision
<translate>
<languages></languages>
In order for Funtoo Linux to boot, it must detect the boot filesystem, root filesystem and swap. The most reliable way to do this is to use the UUID,
or unique identifier, of the partitions holding these filesystems. We will use these UUID values in the , which we will set up next.
The UUID allows Linux to find the right filesystem, even if it detects the disks differently or you move them around in your computer. Funtoo Linux
uses a Linux kernel and initial RAM disk to boot, and to get everything set up, we need to set up correctly, and then install the
GRUB boot loader -- and there are two different commands for this, depending on whether you are using MBR or UEFI. Then, finally, we run
which is a Funtoo command that configures everything for us.
To see the UUIDs for your existing filesystems, type the following command:
The UUIDs are listed to the left-hand side of the . Use these values for setting up the file, below.
is used by the command which is run when your system boots. Lines in this file inform about filesystems to be mounted and how they should be mounted. In order for the system to boot properly, you must edit and ensure that it reflects the partition configuration you used earlier in the install process. If you can't remember the partition configuration that you used earlier:
controls boot loader configuration in Funtoo and is used by . The default configuration is probably fine for you, so most can skip to the appropriate "GRUB Install" section, later on this page.
Here is what is in the file by default:
If you are booting a custom or non-default kernel, please read for information on the various options available to you.
You will notice after booting that you there will be a boot option in the GRUB menu for a "nomodeset" mode. We don't recommend you use this mode by default but it is available to you for a couple of good reasons:
- For users with HiDPI (4K+) displays, especially laptops: If you have not set up a graphical environment, 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. Use this boot option as a temporary workaround.