The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Install/Bootloader/tr"
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
Line 87: | Line 87: | ||
<div lang="en" dir="ltr" class="mw-content-ltr"> | <div lang="en" dir="ltr" class="mw-content-ltr"> | ||
{{c|ego boot}} will ensure that you have the most recent Intel CPU microcode installed on your system if you emerge the | {{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 | ||
following packages: | you are using a desktop stage3: | ||
</div> | </div> | ||
<div lang="en" dir="ltr" class="mw-content-ltr"> | <div lang="en" dir="ltr" class="mw-content-ltr"> | ||
{{console|body= | {{console|body= | ||
%chroot% ##i##emerge intel-microcode iucode_tool | %chroot% ##i##emerge -av intel-microcode iucode_tool | ||
}} | }} | ||
</div> | </div> |
Revision as of 22:57, October 6, 2022
Kurulum Kılavuzu: Önyükleyici
Install Guide, Chapter 14 | < Prev | Next > |
boot.conf Configuration
Bu sayfa, BIOS (legacy) veya UEFI kullanarak önyükleme yapmak için GRUB'un nasıl ayarlanması gerektiğini gösterir.
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
}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
"Funtoo Linux" {
kernel kernel[-v]
initrd initramfs[-v]
params += real_root=auto rootfstype=auto
}
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
"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
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 > |