Note

The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.

Difference between revisions of "Install/Bootloader"

From Funtoo
Jump to navigation Jump to search
Line 24: Line 24:
== boot.conf Configuration ==
== 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:
=== NVIDIA Graphics Card Users ===
 
If you have NVIDIA graphics and plan to set up a graphical environment, you have a couple of choices when it comes to graphics drivers -- the proprietary NVIDIA drivers provided by NVIDIA corporation itself, or the Open Source Nouveau drivers. If you don't know which to choose, we recommend starting with the proprietary NVIDIA drivers first for optimal performance on a wider range of hardware.
 
;If preparing your system for proprietary NVIDIA graphics: It is safe to leave the {{c|nomodeset}} parameter in {{c|/etc/boot.conf}} as the proprietary drivers handle setting the graphics mode themselves. However, you will need to ''blacklist the nouveau modules'' so they do not load upon boot. See [[Package:NVIDIA_Linux_Display_Drivers|the NVIDIA Linux Display Drivers page]] for information on how to get these drivers set up.
 
If you are planning to use Nouveau, {{c|nomodeset}} should be should be removed as explained below in the '''Other Graphics Cards''' section.
 
=== Other Graphics Cards ===
 
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 HiDPI (4K+) displays''': when the kernel automatically changes graphics modes, the console font can be tiny and unreadable.
Line 32: Line 44:


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 ''will need to remove it'', run {{c|ego boot update}} and reboot before they set up X or Wayland. Otherwise, X will not be able to initialize the display.
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 ''will need to remove it'', run {{c|ego boot update}} and reboot before they set up X or Wayland. Otherwise, X will not be able to initialize the display.
{{Important|Make a mental note -- most users will want to ''remove'' the {{c|nomodeset}} option from {{c|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 {{c|nomodeset}} option ''must be removed'' prior to setting up a graphical environment or X will not start.''' Remember to run {{c|ego boot update}} after removing the option, and then reboot prior to configuring X. Also note that if you are using a 4K or higher resolution display, your console text may become very small after enabling kernel mode setting.}}


<!--T:199-->
<!--T:199-->
Line 53: Line 63:
kernel kernel[-v]
kernel kernel[-v]
initrd initramfs[-v]
initrd initramfs[-v]
        # IMPORTANT: Most users -- remember to REMOVE nomodeset below!
params += real_root=auto rootfstype=auto nomodeset
params += real_root=auto rootfstype=auto nomodeset
}
}
Line 113: Line 126:


<!--T:213-->
<!--T:213-->
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}} 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 upon your next reboot.
</translate>
</translate>
<noinclude>{{InstallNavigation|num=14|prev=Kernel|next=Network|align=right}}</noinclude>
<noinclude>{{InstallNavigation|num=14|prev=Kernel|next=Network|align=right}}</noinclude>

Revision as of 02:30, October 8, 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

NVIDIA Graphics Card Users

If you have NVIDIA graphics and plan to set up a graphical environment, you have a couple of choices when it comes to graphics drivers -- the proprietary NVIDIA drivers provided by NVIDIA corporation itself, or the Open Source Nouveau drivers. If you don't know which to choose, we recommend starting with the proprietary NVIDIA drivers first for optimal performance on a wider range of hardware.

If preparing your system for proprietary NVIDIA graphics
It is safe to leave the nomodeset parameter in /etc/boot.conf as the proprietary drivers handle setting the graphics mode themselves. However, you will need to blacklist the nouveau modules so they do not load upon boot. See the NVIDIA Linux Display Drivers page for information on how to get these drivers set up.

If you are planning to use Nouveau, nomodeset should be should be removed as explained below in the Other Graphics Cards section.

Other Graphics Cards

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. Otherwise, X will not be able to initialize the display.

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

        # IMPORTANT: Most users -- remember to REMOVE nomodeset below!

	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 upon your next reboot.

Install Guide, Chapter 14 < Prev Next >
Retrieved from "https://www.funtoo.org/index.php?title=Install/Bootloader&oldid=29304"