The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Install/Bootloader"
(add line to quiet down boot messages. still need to figure out disabling initrd scan messages. im going to set this in undead usb by default. the kernel feels like it boots quicker when it doesn't have to think about printing messages.) |
Tag: Rollback |
||
| Line 3: | Line 3: | ||
== Bootloader == <!--T:1--> | == Bootloader == <!--T:1--> | ||
</includeonly><noinclude><languages/> | </includeonly><noinclude><languages/> | ||
= Install Guide: Bootloader = | |||
<!--T:2--> | <!--T:2--> | ||
| Line 51: | Line 51: | ||
<!--T:203--> | <!--T:203--> | ||
If you are booting a custom or non-default kernel, please read {{c|man boot.conf}} for information on the various options available to you. | If you are booting a custom or non-default kernel, please read {{c|man boot.conf}} for information on the various options available to you. | ||
==== nomodeset ==== <!--T:240--> | ==== nomodeset ==== <!--T:240--> | ||
| Line 80: | Line 77: | ||
<!--T:235--> | <!--T:235--> | ||
AMD | This is not necessary for AMD systems. | ||
==== Old School (BIOS) MBR ==== <!--T:204--> | ==== Old School (BIOS) MBR ==== <!--T:204--> | ||
<!--T:205--> | <!--T:205--> | ||
When using "old school" BIOS booting, run the following command to install GRUB to your MBR, and generate the {{c|/boot/grub/grub.cfg}} configuration file that GRUB will use for booting: | |||
<!--T:206--> | <!--T:206--> | ||
{{console|body= | {{console|body= | ||
%chroot% ##i##grub-install --target=i386-pc --no-floppy /dev/ | %chroot% ##i##grub-install --target=i386-pc --no-floppy /dev/sdX | ||
%chroot% ##i##ego boot update | %chroot% ##i##ego boot update | ||
}} | }} | ||
| Line 109: | Line 101: | ||
{{console|body= | {{console|body= | ||
%chroot% ##i##mount -o remount,rw /sys/firmware/efi/efivars | %chroot% ##i##mount -o remount,rw /sys/firmware/efi/efivars | ||
%chroot% ##i##grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=" | %chroot% ##i##grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda | ||
%chroot% ##i##ego boot update | %chroot% ##i##ego boot update | ||
}} | }} | ||
| Line 119: | Line 111: | ||
{{console|body= | {{console|body= | ||
%chroot% ##i##mount -o remount,rw /sys/firmware/efi/efivars | %chroot% ##i##mount -o remount,rw /sys/firmware/efi/efivars | ||
%chroot% ##i##grub-install --target=i386-efi --efi-directory=/boot --bootloader-id=" | %chroot% ##i##grub-install --target=i386-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda | ||
%chroot% ##i##ego boot update | %chroot% ##i##ego boot update | ||
}} | }} | ||
| Line 126: | Line 118: | ||
<!--T:212--> | <!--T:212--> | ||
OK -- you are almost ready to boot! | |||
<!--T:213--> | <!--T:213--> | ||
| Line 134: | Line 124: | ||
==== Post reboot UEFI troubleshooting ==== <!--T:236--> | ==== Post reboot UEFI troubleshooting ==== <!--T:236--> | ||
In case UEFI NVRAM boot entry is missing in BIOS and grub does not start you can try moving an already installed GRUB EFI executable to the [https://wiki.archlinux.org/index.php/GRUB#Default/fallback_boot_path default/fallback path] | In case UEFI NVRAM boot entry is missing in BIOS and grub does not start you can try moving an already installed GRUB EFI executable to the [https://wiki.archlinux.org/index.php/GRUB#Default/fallback_boot_path default/fallback path] | ||
{{console|body= | {{console|body= | ||
%chroot% ##i##mv -v /boot/EFI/ | %chroot% ##i##mv -v '/boot/EFI/Funtoo Linux [GRUB]' /boot/EFI/BOOT | ||
%chroot% ##i##mv -v /boot/EFI/BOOT/grubx64.efi /boot/EFI/BOOT/BOOTX64.EFI | %chroot% ##i##mv -v /boot/EFI/BOOT/grubx64.efi /boot/EFI/BOOT/BOOTX64.EFI | ||
}} | }} | ||
Revision as of 04:39, December 12, 2020
Install Guide: Bootloader
| Install Guide, Chapter 14 | < Prev | Next > |
boot.conf Configuration
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
boot.conf
/etc/boot.conf controls boot loader configuration in Funtoo. Here is what is in the file by default:
/etc/boot.conf boot {
generate grub
default "Funtoo Linux"
timeout 3
}
"Funtoo Linux" {
kernel kernel[-v]
initrd initramfs[-v]
params += real_root=auto rootfstype=auto
}
"Funtoo Linux (nomodeset)" {
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.
nomodeset
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.
To use the nomodeset option, simply select that option from the GRUB menu when your system boots.
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/sdX 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 upon your next reboot.
Post reboot UEFI troubleshooting
In case UEFI NVRAM boot entry is missing in BIOS and grub does not start you can try moving an already installed GRUB EFI executable to the default/fallback path
chroot # mv -v '/boot/EFI/Funtoo Linux [GRUB]' /boot/EFI/BOOT chroot # mv -v /boot/EFI/BOOT/grubx64.efi /boot/EFI/BOOT/BOOTX64.EFI
| Install Guide, Chapter 14 | < Prev | Next > |