Difference between revisions of "Install/Bootloader"

From Funtoo
Jump to navigation Jump to search
(7 intermediate revisions by the same user not shown)
Line 20: Line 20:


<!--T:198-->
<!--T:198-->
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.
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"}}.  


== boot.conf Configuration ==
Most users, particularly those who plan on setting up a graphical environment, will want to eventually remove {{c|nomodeset}} from {{c|params}} in {{f|/etc/make.conf}}. {{c|nomodeset}} prevents the kernel from changing graphics modes at boot. This option is in {{c|/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 {{c|nomodeset}} is a good option to get the initial system up and running, most users are encouraged to remove it before they set up X or Wayland.
{{Important|Make a mental note -- while {{c|nomodeset}} is a safe option for now, most users will want to ''remove'' the {{c|nomodeset}} option from {{c|params}} prior to setting up their graphical environment. But it's generally OK to keep it enabled until Funtoo Linux is fully installed and you have performed your initial reboot into your new system. When it is time to remove this option, simply edit {{c|/etc/boot.conf}}, remove the option, and run {{c|ego boot update}} to update your boot configuration.}}
<!--T:199-->
<!--T:199-->
{{c|/etc/boot.conf}} should now look like this:
{{c|/etc/boot.conf}} should now look like this:
Line 33: Line 45:
}
}


<!--T:201-->
"Funtoo Linux" {
"Funtoo Linux" {
kernel bzImage[-v]
kernel bzImage[-v]
}
}


<!--T:202-->
"Funtoo Linux genkernel" {
"Funtoo Linux genkernel" {
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
}
}
<!--T:217-->
}}
}}



Revision as of 21:45, September 9, 2019

Other languages:
English • ‎Türkçe • ‎español • ‎português do Brasil • ‎русский • ‎中文(中国大陆)‎

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 are encouraged to remove it before they set up X or Wayland.

   Important

Make a mental note -- while nomodeset is a safe option for now, most users will want to remove the nomodeset option from params prior to setting up their graphical environment. But it's generally OK to keep it enabled until Funtoo Linux is fully installed and you have performed your initial reboot into your new system. When it is time to remove this option, simply edit /etc/boot.conf, remove the option, and run ego boot update to update your boot configuration.

/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 >