Difference between revisions of "Install/Bootloader/en"

From Funtoo
Jump to navigation Jump to search
(Updating to match new version of source page)
(Updating to match new version of source page)
(4 intermediate revisions by the same user not shown)
Line 5: Line 5:


{{InstallNavigation|num=14|prev=Kernel|next=Network}}</noinclude>
{{InstallNavigation|num=14|prev=Kernel|next=Network}}</noinclude>
=== boot.conf Configuration ===


These install instructions show you how to use GRUB to boot using BIOS (legacy) or UEFI.
These install instructions show you how to use GRUB to boot using BIOS (legacy) or UEFI.
Line 11: Line 13:


{{console|body=
{{console|body=
(chroot) ###i## emerge -av grub
%chroot% ##i##emerge -av grub
}}
}}


Next, edit {{c|/etc/boot.conf}} using {{c|nano}} and specify "{{c|Funtoo Linux genkernel}}" as the {{c|default}} setting at the top of the file, replacing {{c|"Funtoo Linux"}}. Also, if you're not using memtest86+ remove the entry in boot.conf to avoid errors.
==== boot.conf ====


{{c|/etc/boot.conf}} should now look like this:
{{c|/etc/boot.conf}} controls boot loader configuration in Funtoo. Here is what is in the file by default:


{{file|name=/etc/boot.conf|body=
{{file|name=/etc/boot.conf|body=
boot {
boot {
generate grub
generate grub
default "Funtoo Linux"  
default "Funtoo Linux"
timeout 3  
timeout 3
}
}


"Funtoo Linux" {
"Funtoo Linux" {
kernel bzImage[-v]
kernel kernel[-v]
initrd initramfs[-v]
params += real_root=auto rootfstype=auto
}
}


"Funtoo Linux genkernel" {
"Funtoo Linux (nomodeset)" {
kernel kernel[-v]
kernel kernel[-v]
initrd initramfs[-v]
initrd initramfs[-v]
params += real_root=auto rootfstype=auto
params += real_root=auto rootfstype=auto nomodeset
}
}
}}


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 ====
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 {{c|nomodeset}} option, simply select that option from the GRUB menu when your system boots.
=== rootwait ===
If you are using a root partition on an {{c|nvme}} device, add the {{c|rootwait}} kernel parameter to force the kernel to wait for it to asynchronously initialize or the kernel will panic on some hardware.
=== Intel Microcode ===
{{c|ego boot}} will ensure that you have the most recent Intel CPU microcode installed on your system if you emerge the following packages. These will be merged for you already if
you are using a desktop stage3:
{{console|body=
%chroot% ##i##emerge -av intel-microcode iucode_tool
}}
}}


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.
This is not necessary for AMD systems.


==== Old School (BIOS) MBR ====
==== Old School (BIOS) MBR ====
Line 44: Line 70:


{{console|body=
{{console|body=
(chroot) # ##i##grub-install --target=i386-pc --no-floppy /dev/sda
%chroot% ##i##grub-install --target=i386-pc --no-floppy /dev/sdX
(chroot) # ##i##ego boot update
%chroot% ##i##ego boot update
}}
}}


Line 55: Line 81:


{{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="Funtoo Linux [GRUB]" --recheck /dev/sda
%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 63: Line 89:


{{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="Funtoo Linux [GRUB]" --recheck /dev/sda
%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 72: Line 98:
OK -- you are almost ready to boot!  
OK -- you are almost ready to boot!  


You only need to run <code>grub-install</code> when you first install Funtoo Linux, but you need to re-run <code>ego boot update</code> every time you modify your <code>/etc/boot.conf</code> file or add new kernels to your system. This will regenerate {{c|/boot/grub/grub.cfg}} so that you will have new kernels available in your GRUB boot menu, the next time you reboot.
You only need to run {{c|grub-install}} when you first install Funtoo Linux, but you need to re-run {{c|ego boot update}} every time you modify your {{c|/etc/boot.conf}}. When you emerge updated kernels, {{c|ego boot update}} will be run automatically as part of the install process. This will regenerate {{c|/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 [https://wiki.archlinux.org/index.php/GRUB#Default/fallback_boot_path default/fallback path]
{{console|body=
%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
}}
 
<noinclude>{{InstallNavigation|num=14|prev=Kernel|next=Network|align=right}}</noinclude>

Revision as of 22:58, October 6, 2022

Other languages:

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.

rootwait

If you are using a root partition on an nvme device, add the rootwait kernel parameter to force the kernel to wait for it to asynchronously initialize or the kernel will panic on some hardware.

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. These will be merged for you already if you are using a desktop stage3:

chroot # emerge -av 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. When you emerge updated kernels, ego boot update will be run automatically as part of the install process. 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 >