|
|
| Line 1: |
Line 1: |
| <noinclude>
| | This page lists processor instruction sets that can be enabled on Funtoo Linux systems using the {{c|CPU_FLAGS_*}} variables. |
| {{InstallPart|boot loader configuration}} | |
| </noinclude>
| |
| === Installing a Bootloader ===
| |
|
| |
|
| These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school).
| | ==CPU_FLAGS_X86 == |
|
| |
|
| ==== Old School (BIOS) ====
| | {{TableStart}} |
| | | <tr><th>Flag</th><th>Introduced</th><th>Name</th><th></th></tr> |
| If you're using the BIOS to boot, setting up GRUB, the bootloader, is pretty easy.
| | <tr><td>{{c|mmx}}</td><td>1997 (Pentium MMX)</td><td>MMX</td><td>See [[Wikipedia:MMX (instruction set)]] </td></tr> |
| | | <tr><td>{{c|mmxext}}</td><td>1999</td><td>AMD MMX Extensions</td><td>See [[Wikipedia:Extended MMX]]</td></tr> |
| To use this recommended boot method, first emerge <code>boot-update</code>. This will also cause <code>grub-2</code> to be merged, since it is a dependency of <code>boot-update</code>.
| | <tr><td>{{c|sse}}</td><td>1999 (Pentium III)</td><td>Streaming SIMD Extensions (SSE)</td><td>See [[Wikipedia:Streaming SIMD Extensions]]</td></tr> |
| | | <tr><td>{{c|sse2}}</td><td>2001 (Pentium 4)</td><td>Streaming SIMD Extensions 2 (SSE2)</td><td>See [[Wikipedia:SSE2]]</td></tr> |
| <console> | | <tr><td>{{c|sse3}}</td><td>2004 (Pentium 4 Prescott)</td><td>Streaming SIMD Extensions 3 (SSE3/PNI)</td><td>See [[Wikipedia:SSE3]]</td></tr> |
| (chroot) # ##i##emerge boot-update
| | <tr><td>{{c|ssse3}}</td><td>2006 (Core 2 Woodcrest)</td><td>Supplemental Streaming SIMD Extensions 3 (SSSE3)</td><td>See [[Wikipedia:SSSE3]]</td></tr> |
| </console> | | <tr><td>{{c|popcnt}}</td><td>2007</td><td>POPCNT and LZCNT</td><td>See [[Wikipedia:SSE4#POPCNT_and_LZCNT]]</td></tr> |
| | | {{TableEnd}} |
| Then, edit <code>/etc/boot.conf</code> and specify "<code>Funtoo Linux genkernel</code>" as the <code>default</code> setting at the top of the file, replacing <code>"Funtoo Linux"</code>.
| |
| | |
| <code>/etc/boot.conf</code> should now look like this: | |
| | |
| <pre>
| |
| 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
| |
| } | |
| </pre> | |
| | |
| Please read <code>man boot.conf</code> for further details.
| |
| | |
| ===== Running grub-install and boot-update =====
| |
| | |
| Finally, we will need to actually install the GRUB boot loader to your disk, and also run <code>boot-update</code> which will generate your boot loader configuration file:
| |
| | |
| <console> | |
| (chroot) # ##i##grub-install --no-floppy /dev/sda | |
| (chroot) # ##i##boot-update
| |
| </console> | |
| | |
| Now you need to update your boot loader configuration file:
| |
| <console> | |
| (chroot) # ##i##boot-update
| |
| </console> | |
| 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, so your changes are applied on next boot.
| |
| | |
| ==== New School (UEFI) ====
| |
| | |
| If you're using UEFI to boot, setting up the boot loader is a bit more complicated for now, but this process will be improving soon. Perform the following steps.
| |
| | |
| ===== Emerging GRUB =====
| |
| | |
| You will still use GRUB as a boot loader, but before emerging grub, you will need to enable EFI booting. To do this,
| |
| add the following line to <code>/etc/make.conf</code>:
| |
| | |
| For x86-64bit systems:
| |
| | |
| <pre> | |
| GRUB_PLATFORMS="efi-64"
| |
| </pre> | |
| | |
| For x86-32bit systems:
| |
| | |
| <pre> | |
| GRUB_PLATFORMS="efi-32"
| |
| </pre> | |
| | |
| Then, <code>emerge boot-update</code>. You will notice <code>grub</code> and <code>efibootmgr</code> getting pulled in as dependencies. This is expected and good:
| |
| | |
| <console> | |
| (chroot) # ##i##emerge boot-update
| |
| </console> | |
| | |
| ===== Installing GRUB =====
| |
| | |
| Now, for the magic of getting everything in place for booting. You should copy your kernel and initramfs (if you have one -- you will if you are following the default install) to <tt>/boot</tt>. GRUB will boot those. But how do we get UEFI to boot GRUB? Well, we need to run the following command (for 32 bit simply set it as i386-efi):
| |
| | |
| <console> | |
| (chroot) # ##i##grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda | |
| </console> | |
| This command will simply install all the stuff to <tt>/boot/EFI</tt> and <tt>/boot/grub</tt> that your system needs to boot. In particular, the <tt>/boot/EFI/grub/grubx64.efi</tt> file will be created. This is the GRUB boot image that UEFI will load and start.
| |
| | |
| A more detailed explanation of the flags used in the above command:
| |
| * <code>--target=x86_64-efi</code>: Tells GRUB that we want to install it in a way that allows it to boot in UEFI
| |
| * <code>--efi-directory=/boot</code>: All GRUB UEFI files will be installed in ''/boot''
| |
| * <code>--bootloader-id="Funtoo Linux [GRUB]"</code>: This flag is not necessary for GRUB to boot. However, it allows you to change the text of the boot option in the UEFI BIOS. The stuff in the quotes can be set to anything that you would like.
| |
| * <code>--recheck</code>: If a device map already exists on the disk or partition that GRUB is being installed on, it will be removed.
| |
| * <code>/dev/sda</code>:The device that we are installing GRUB on.
| |
| | |
| ===== Configuring GRUB =====
| |
| | |
| OK, now UEFI has the GRUB image it needs to boot. But we still need to configure GRUB itself so it finds and boots your kernel and initramfs. This is done by performing the following steps. Since boot-update doesn't yet support UEFI, we will use boot-update, but then edit our <code>/boot/grub/grub.cfg</code> to support UEFI booting.
| |
| | |
| First, you will need to edit <code>/etc/boot.conf</code>. Format this as you would if you were booting without UEFI. If you are not sure how this should look, below is an example of what it could look like if you are booting from an unencrypted ext4 partition:
| |
| | |
| {{file|name=/etc/boot.conf|desc=|body= | |
| boot {
| |
| generate grub
| |
| default "Funtoo Linux"
| |
| timeout 3
| |
| } | |
| | |
| "Funtoo Linux" {
| |
| kernel vmlinuz[-v]
| |
| params += rootfstype=ext4 root=/dev/sda2
| |
| }
| |
| }} | |
| | |
| After you have edited your <code>/etc/boot.conf</code> file, run <code>boot-update</code>. You should now have a <code>/boot/grub/grub.cfg</code> file, which you can edit using the following command:
| |
| | |
| <console> | |
| # ##i##nano /boot/grub/grub.cfg
| |
| </console> | |
| | |
| | |
| To get your <code>/boot/grub/grub.cfg</code> to support booting with UEFI, make the following changes. Below the existing insmod lines, add the following lines. Both of these involve adding support for the UEFI framebuffer to GRUB.:
| |
| | |
| <pre> | |
| insmod efi_gop
| |
| insmod efi_uga
| |
| </pre> | |
| | |
| Then, change the <code>set gfxpayload</code> line to read as follows. UEFI does not support text mode, so we will keep video initialized to the current resolution.:
| |
| | |
| <pre> | |
| set gfxpayload=keep
| |
| </pre> | |
| | |
| You can now save your changes by pressing <code>Control-X</code> and answering <code>y</code> when asked if you want to save the modified buffer. When prompted for a filename, hit Enter to use the existing filename.
| |