The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Install/BootLoader"
(Marked this version for translation) |
|||
| Line 2: | Line 2: | ||
{{InstallPart|boot loader configuration}} | {{InstallPart|boot loader configuration}} | ||
</noinclude><translate> | </noinclude><translate> | ||
=== Installing a Bootloader === | === Installing a Bootloader === <!--T:1--> | ||
<!--T:2--> | |||
These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school). As of boot-update-1.7.2, now in Portage, the steps are very similar. | These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school). As of boot-update-1.7.2, now in Portage, the steps are very similar. | ||
<!--T:3--> | |||
First, emerge <code>boot-update</code>. This will also cause <code>grub-2</code> and {{c|efibootmgr}} to be merged, since they are dependencies: | First, emerge <code>boot-update</code>. This will also cause <code>grub-2</code> and {{c|efibootmgr}} to be merged, since they are dependencies: | ||
<!--T:4--> | |||
<console> | <console> | ||
(chroot) # ##i##emerge boot-update | (chroot) # ##i##emerge boot-update | ||
</console> | </console> | ||
<!--T:5--> | |||
Then, edit <code>/etc/boot.conf</code> using {{c|nano}} and specify "<code>Funtoo Linux genkernel</code>" as the <code>default</code> setting at the top of the file, replacing <code>"Funtoo Linux"</code>. | Then, edit <code>/etc/boot.conf</code> using {{c|nano}} and specify "<code>Funtoo Linux genkernel</code>" as the <code>default</code> setting at the top of the file, replacing <code>"Funtoo Linux"</code>. | ||
<!--T:6--> | |||
<code>/etc/boot.conf</code> should now look like this: | <code>/etc/boot.conf</code> should now look like this: | ||
<!--T:7--> | |||
{{file|name=/etc/boot.conf|body= | {{file|name=/etc/boot.conf|body= | ||
boot { | boot { | ||
| Line 23: | Line 29: | ||
} | } | ||
<!--T:8--> | |||
"Funtoo Linux" { | "Funtoo Linux" { | ||
kernel bzImage[-v] | kernel bzImage[-v] | ||
} | } | ||
<!--T:9--> | |||
"Funtoo Linux genkernel" { | "Funtoo Linux genkernel" { | ||
kernel kernel[-v] | kernel kernel[-v] | ||
| Line 33: | Line 41: | ||
} | } | ||
<!--T:10--> | |||
"Funtoo Linux better-initramfs" { | "Funtoo Linux better-initramfs" { | ||
kernel vmlinuz[-v] | kernel vmlinuz[-v] | ||
| Line 39: | Line 48: | ||
}} | }} | ||
<!--T:11--> | |||
If you are booting a custom or non-default kernel, please read <code>man boot.conf</code> for information on the various options available to you. | If you are booting a custom or non-default kernel, please read <code>man boot.conf</code> for information on the various options available to you. | ||
==== Old School (BIOS) MBR ==== | ==== Old School (BIOS) MBR ==== <!--T:12--> | ||
<!--T:13--> | |||
When using "old school" BIOS booting, run the following command to install GRUB to your MBR, and generate the {{c|/boot/grub/grub.cfg}} configuration file that GRUB will use for booting: | When using "old school" BIOS booting, run the following command to install GRUB to your MBR, and generate the {{c|/boot/grub/grub.cfg}} configuration file that GRUB will use for booting: | ||
<!--T:14--> | |||
<console> | <console> | ||
(chroot) # ##i##grub-install --target=i386-pc --no-floppy /dev/sda | (chroot) # ##i##grub-install --target=i386-pc --no-floppy /dev/sda | ||
| Line 50: | Line 62: | ||
</console> | </console> | ||
==== New School (UEFI) Boot Entry ==== | ==== New School (UEFI) Boot Entry ==== <!--T:15--> | ||
<!--T:16--> | |||
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. | 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. | ||
<!--T:17--> | |||
For x86-64bit systems: | For x86-64bit systems: | ||
<!--T:18--> | |||
<console> | <console> | ||
(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 | ||
| Line 61: | Line 76: | ||
</console> | </console> | ||
<!--T:19--> | |||
For x86-32bit systems: | For x86-32bit systems: | ||
<!--T:20--> | |||
<console> | <console> | ||
(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 | ||
| Line 68: | Line 85: | ||
</console> | </console> | ||
==== First Boot, and in the future... ==== | ==== First Boot, and in the future... ==== <!--T:21--> | ||
<!--T:22--> | |||
OK -- you are ready to boot! | OK -- you are ready to boot! | ||
<!--T:23--> | |||
You only need to run <code>grub-install</code> when you first install Funtoo Linux, but you need to re-run <code>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 <code>grub-install</code> when you first install Funtoo Linux, but you need to re-run <code>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. | ||
</translate> | </translate> | ||
Revision as of 04:26, July 14, 2015
This is a template that is used as part of the Installation instructions which covers: boot loader configuration. Templates are being used to allow multiple variant install guides that use most of the same re-usable parts.
Installing a Bootloader
These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school). As of boot-update-1.7.2, now in Portage, the steps are very similar.
First, emerge boot-update. This will also cause grub-2 and efibootmgr to be merged, since they are dependencies:
(chroot) # emerge boot-update
Then, edit /etc/boot.conf using nano and specify "Funtoo Linux genkernel" as the default setting at the top of the file, replacing "Funtoo Linux".
/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
}
"Funtoo Linux better-initramfs" {
kernel vmlinuz[-v]
initrd /initramfs.cpio.gz
}
If you are booting a custom or non-default kernel, please read man boot.conf for information on the various options available to you.
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) # 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) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda (chroot) # boot-update
For x86-32bit systems:
(chroot) # grub-install --target=i386-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda (chroot) # boot-update
First Boot, and in the future...
OK -- you are ready to boot!
You only need to run grub-install when you first install Funtoo Linux, but you need to re-run 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.