Difference between pages "Extlinux" and "Install/BootLoader"

(Difference between pages)
(manual extlinux.conf)
 
(Emerging GRUB)
 
Line 1: Line 1:
== What is ExtLinux? ==
+
<noinclude>
 +
{{InstallPart|boot loader configuration}}
 +
</noinclude>
 +
=== Installing a Bootloader ===
  
ExtLinux is a simple and modern systemloader bundled with the syslinux tools. Installation is simple and fast, and thanks to our CoreTeam member Slashbeast the configuration is easily automated.
+
These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school).
  
= Installing ExtLinux for funtoo =
+
==== Old School (BIOS) ====
  
Installing ExtLinux for funtoo is known to work and supported too. If you like to try it just emerge syslinux
+
If you're using the BIOS to boot, setting up GRUB, the bootloader, is pretty easy.
 +
 
 +
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>.
  
 
<console>
 
<console>
# ##i##emerge syslinux
+
(chroot) # ##i##emerge boot-update
 
</console>
 
</console>
  
with that you have the complete syslinux tools installed. Another helpful tool you should merge with syslinux is slashbeast's lazykernel tool, so let us merge it too:
+
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>.
  
<console>
+
<code>/etc/boot.conf</code> should now look like this:
# ##i##emerge lazykernel
+
</console>
+
  
== Installing extlinux ==
+
<pre>
 +
boot {
 +
generate grub
 +
default "Funtoo Linux genkernel"
 +
timeout 3
 +
}
  
to install extlinux just follow these steps:
+
"Funtoo Linux" {
 +
kernel bzImage[-v]
 +
}
  
<console>
+
"Funtoo Linux genkernel" {
# ##i##install -d /boot/extlinux
+
kernel kernel[-v]
# ##i##extlinux --install /boot/extlinux
+
initrd initramfs[-v]
</console>
+
params += real_root=auto
 +
}
  
the next steps are different depending if you use an MBR or GPT setup and the HDD you installed on and want to boot from. Let us now for general take /dev/sda as your boot device.
+
"Funtoo Linux better-initramfs" {
 +
kernel vmlinuz[-v]
 +
initrd /initramfs.cpio.gz
 +
}
 +
</pre>
  
=== MBR ===
+
Please read <code>man boot.conf</code> for further details.
  
If you set up your disk with MBR partition scheme just do the next steps:
+
===== 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>
 
<console>
# ##i##dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/mbr.bin of=/dev/sda
+
(chroot) # ##i##grub-install --no-floppy /dev/sda
# ##i##cp /usr/share/syslinux/menu.c32 /boot/extlinux/
+
(chroot) # ##i##boot-update
# ##i##cp /usr/share/syslinux/libutil.c32 /boot/extlinux/
+
# ##i##touch /boot/extlinux/extlinux.conf
+
 
</console>
 
</console>
  
=== GPT ===
+
Now you need to update your boot loader configuration file:
 
+
 
<console>
 
<console>
# ##i##sgdisk /dev/sda --attributes=1:set:2
+
(chroot) # ##i##boot-update
# ##i##sgdisk /dev/sda --attributes=1:show
+
1:2:1 (legacy BIOS bootable)
+
# ##i##dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/gptmbr.bin of=/dev/sda
+
# ##i##cp /usr/share/syslinux/menu.c32 /boot/extlinux/
+
# ##i##cp /usr/share/syslinux/libutil.c32 /boot/extlinux/
+
# ##i##touch /boot/extlinux/extlinux.conf
+
 
</console>
 
</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.
  
== Setting up the Kernel ==
+
==== New School (UEFI) ====
  
Now if you followed our advice to install lazykernel we have a pretty nice way to solve all the setup with a bit of prework and finish it then. If not you should go to the manual part. :)
+
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.
  
=== lazykernel way ===
+
===== Emerging GRUB =====
  
Edit <tt>/etc/lazykernel.conf</tt>:
+
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>:
  
{{file|name=/etc/lazykernel.conf|desc= |body=
+
For x86-64bit systems:
# After configuring, hash or remove line below.
+
#CONFIGUREFIRST
+
  
# Number of the kernels to keep so `lazykernel clean` will not propose to remove them. Default: 3
+
<pre>
keep_kernels=5
+
GRUB_PLATFORMS="efi-64"
 +
</pre>
  
# Sort kernels by 'version' (biggest version first) or by 'mtime' (latest images first). Default: mtime
+
For x86-32bit systems:
# Sorting by version may fail and 3.3.0-rc2 will be marked as newer than 3.3.0.
+
#sort_by='version'
+
sort_by=mtime
+
  
# The name for menu entry.
+
<pre>
menu_entry_name="Funtoo Linux"
+
GRUB_PLATFORMS="efi-32"
 +
</pre>
  
# Specify what initramfs image to use, if any. (Optional)
+
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:
initramfs='initramfs.cpio.gz'
+
  
# Append kernel params, usualy you use it to specify rootfs device, but you can use it to pass switches to initramfs as well.
+
<console>
kernel_params="rootfstype=ext4 luks enc_root=/dev/sdb3 lvm root=/dev/mapper/vg-root uswsusp resume=/dev/mapper/vg-swap"
+
(chroot) # ##i##emerge boot-update
}}
+
</console>
  
{{fancynote| Please make sure to comment out or delete the second line of the config file...else it will spit out an error.}}
+
===== Installing GRUB =====
  
Now let us setup our kernel with lazykernel. If you have a manual kernel just run:
+
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>
 
<console>
# ##i##cd <kernel build dir>
+
(chroot) # ##i##grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda
# ##i##lazykernel auto
+
 
</console>
 
</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.
  
This will generate the modules for you. Copy your kernel form <tt>/usr/src/linux</tt> to <tt>/boot</tt> and generate the <tt>/boot/extlinux/extlinux.conf</tt>. The manual kernel will be the only one supported by lazykernel.
+
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.
  
=== manual extlinux.conf ===
+
===== Configuring GRUB =====
  
For other kernels, like those created by genkernel or by the binary USE-flag you need to edit your config by yourself. Just open <tt>/boot/extlinux/extlinux.conf</tt> in your favorite editor:
+
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.
  
{{file|name=/boot/extlinux/extlinux.conf|desc= |body=
+
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:
TIMEOUT 30
+
UI menu.c32
+
  
MENU TITLE Boot Menu
+
{{file|name=/etc/boot.conf|desc=|body=
MENU COLOR title        1;37;40
+
boot {
MENU COLOR border      30;40
+
        generate grub
MENU COLOR unsel        37;40
+
        default "Funtoo Linux"
 +
        timeout 3
 +
}
  
LABEL funtoo1
+
"Funtoo Linux" {
        MENU LABEL Funtoo Linux KERNEL-VERSION
+
         kernel vmlinuz[-v]
         LINUX /<kernel>
+
         params += rootfstype=ext4 root=/dev/sda2
         INITRD /<initramfs>
+
}
        APPEND rootfstype=ext4 luks enc_root=/dev/sdb3 lvm root=/dev/mapper/vg-root uswsusp resume=/dev/mapper/vg-swap
+
 
}}
 
}}
  
That's all. You are now ready for boot. You can also define several LABELs in that list to have multiple kernel selections to choose from before booting.
+
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>
  
[[Category:HOWTO]]
+
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.

Revision as of 19:48, January 1, 2015


Note

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).

Old School (BIOS)

If you're using the BIOS to boot, setting up GRUB, the bootloader, is pretty easy.

To use this recommended boot method, first emerge boot-update. This will also cause grub-2 to be merged, since it is a dependency of boot-update.

(chroot) # emerge boot-update

Then, edit /etc/boot.conf 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:

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
}

Please read man boot.conf 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 boot-update which will generate your boot loader configuration file:

(chroot) # grub-install --no-floppy /dev/sda
(chroot) # boot-update

Now you need to update your boot loader configuration file:

(chroot) # boot-update

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, 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 /etc/make.conf:

For x86-64bit systems:

GRUB_PLATFORMS="efi-64"

For x86-32bit systems:

GRUB_PLATFORMS="efi-32"

Then, emerge boot-update. You will notice grub and efibootmgr getting pulled in as dependencies. This is expected and good:

(chroot) # emerge boot-update
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 /boot. 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):

(chroot) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda

This command will simply install all the stuff to /boot/EFI and /boot/grub that your system needs to boot. In particular, the /boot/EFI/grub/grubx64.efi 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:

  • --target=x86_64-efi: Tells GRUB that we want to install it in a way that allows it to boot in UEFI
  • --efi-directory=/boot: All GRUB UEFI files will be installed in /boot
  • --bootloader-id="Funtoo Linux [GRUB]": 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.
  • --recheck: If a device map already exists on the disk or partition that GRUB is being installed on, it will be removed.
  • /dev/sda: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 /boot/grub/grub.cfg to support UEFI booting.

First, you will need to edit /etc/boot.conf. 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:

/etc/boot.conf
boot {
        generate grub
        default "Funtoo Linux"
        timeout 3
}

"Funtoo Linux" {
        kernel vmlinuz[-v]
        params += rootfstype=ext4 root=/dev/sda2
}

After you have edited your /etc/boot.conf file, run boot-update. You should now have a /boot/grub/grub.cfg file, which you can edit using the following command:

# nano /boot/grub/grub.cfg


To get your /boot/grub/grub.cfg 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.:

  insmod efi_gop
  insmod efi_uga

Then, change the set gfxpayload line to read as follows. UEFI does not support text mode, so we will keep video initialized to the current resolution.:

  set gfxpayload=keep

You can now save your changes by pressing Control-X and answering y when asked if you want to save the modified buffer. When prompted for a filename, hit Enter to use the existing filename.