Jump to: navigation, search


2,433 bytes added, 11 months ago
Marked this version for translation
=== boot.conf Configuration === <!--T:218-->
(%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 ==== NVIDIA Graphics Card Users ==== <!--T:219--> <!--T:220-->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. <!--T:221-->;If using 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, if youwill need to ''blacklist the nouveau modules''re 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. <!--T:222-->;If using memtest86+ Nouveau...: {{c|nomodeset}} should be ''should be removed'' as explained in the '''Other Graphics Cards''' section below. ==== Other Graphics Cards ==== <!--T:223--> <!--T:224-->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 entry kernel from changing graphics modes at boot. This option is in {{c|/etc/boot.conf }} by default for a couple of good reasons: <!--T:225-->* '''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.  <!--T:226-->Disabling mode setting is therefore a good, safe option for initial installs of Funtoo Linux, but most users will ''want to avoid errorsremove this option.'' <!--T:227-->This is because essentially all graphics drivers (the big exception being the proprietary NVIDIA drivers) rely on mode setting to set the graphics mode of your display. So most users ''will need to remove it'', and run {{c|ego boot update}} and reboot before they set up X or Wayland. Otherwise, X will not be able to initialize the display. Of course, you can also choose to remove it now and then you won't need to remember to remove it later :)
"Funtoo Linux" {
kernel bzImage[-v]
"Funtoo Linux genkernel" {
kernel kernel[-v]
initrd initramfs[-v]
  <!--T:230--># IMPORTANT: Most users -- remember to REMOVE nomodeset below!  <!--T:231-->params += real_root=auto rootfstype=autonomodeset
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.
=== Intel Microcode ===<!--T:232-->
{{c|ego boot}} will ensure that you have the most recent Intel CPU microcode installed on your system if you emerge the
following packages:
# %chroot% ##i##emerge intel-microcode iucode_tool
This is not necessary for AMD systems.
(%chroot) # % ##i##grub-install --target=i386-pc --no-floppy /dev/sda(%chroot) # % ##i##ego boot update
(%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##ego boot update
(%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##ego boot update
You only need to run <code>{{c|grub-install</code> }} when you first install Funtoo Linux, but you need to re-run <code>{{c|ego boot update</code> }} every time you modify your <code>{{c|/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 upon your next time you reboot.
Bureaucrats, Administrators, wiki-admins, wiki-staff

Navigation menu