Difference between pages "UEFI Install Guide" and "Kernel Seeds"

(Difference between pages)
(Mention /sys/firmware/efi)
 
(Created page with "This page is intended to house the new Kernel Seeds page. Here's what Duncan and I think is a good idea: * kernel-seeds.org redirects to this page. * This page has some nice...")
 
Line 1: Line 1:
This tutorial will show you how to install Funtoo on a UEFI system. UEFI, also known as the [[Wikipedia:Unified Extensible Firmware Interface|Unified Extensible Firmware Interface]], is a new firmware interface that is used on some newer computers as a replacement for the traditional PC BIOS. It has an integrated boot loader, so setting up booting is different.
+
This page is intended to house the new Kernel Seeds page.
  
This tutorial is meant to be an "overlay" over the Regular Funtoo Installation. Follow the normal installation and only follow steps in this tutorial when dealing with partitioning and configuring the boot loader (GRUB). All steps are otherwise identical to the regular installation process.
+
Here's what Duncan and I think is a good idea:
  
== What Are We Doing? ==
+
* kernel-seeds.org redirects to this page.
 +
* This page has some nice, special graphics on it to differentiate it from the other Funtoo Wiki pages.
 +
* This page begins with a short history of Kernel Seeds, giving credit to Pappy and talking about its role in the Gentoo community.
 +
* Following this, a short introduction to the concepts behind kernel seeds will be written from scratch.
 +
* Existing content will be converted and edited and stored as subpages (ie. Kernel_Seeds/Working_With_Kernel_Seeds)
 +
* The latest .config files (3.9.9 era) will be moved to a git repository to allow community maintenance. The older versions will be archived.
  
This guide will show you how to set up your UEFI system to load the GRUB boot loader, which will then load your Funtoo Linux kernel and initramfs. This is the "UEFI + GRUB" method as described on the [[Boot Methods]] page.
+
This will allow the pages to be maintained by interested users, and allow good integration with the rest of the Funtoo wiki, while maintaining its distinctiveness with its own look.
 
+
== First Steps ==
+
 
+
To install Funtoo Linux on a UEFI system, first you need to boot SysRescueCD in UEFI mode. To do this, enable UEFI in your BIOS, and if necessary disable legacy booting. After some fiddling, you should be able to boot SysRescueCD and get a black and white text menu instead of the traditional aqua/cyan-colored menu. The black and white menu indicates that you booted SysRescueCD in UEFI mode. Once you've accomplished this, you're ready to continue with your Funtoo Linux installation and partition your drive. See below for details.
+
 
+
'''If the <tt>/sys/firmware/efi</tt> directory exists, then you have successfully booted in EFI mode and will be able to configure your Funtoo system to boot in EFI mode. If the directory doesn't exist, fix this first. It is a requirement for setting up EFI booting.'''
+
 
+
== Partitioning ==
+
 
+
To set up your partitions for UEFI booting, you will create a ~500MB FAT32 partition on <tt>/dev/sda1</tt>, and set it to type <tt>EF00</tt> using <tt>gdisk</tt>.
+
 
+
<console>
+
Command: ##i##n ↵
+
Partition Number: ##i##1 ↵
+
First sector: ##i##↵
+
Last sector: ##i##+500M ↵
+
Hex Code: ##i##EF00
+
</console>
+
 
+
This partition will serve as your Funtoo <tt>/boot</tt> filesystem as well as the partition that the UEFI firmware can read to load GRUB. Then you will set up swap on <tt>/dev/sda2</tt> and your root filesystem on <tt>/dev/sda3</tt>. To create the FAT32 filesystem, type:
+
 
+
<console>
+
# ##i##mkfs.vfat -F 32 /dev/sda1
+
</console>
+
 
+
Your <tt>/etc/fstab</tt> entry for this filesystem will also differ, and will look like this:
+
 
+
<pre>
+
/dev/sda1 /boot vfat noatime 1 2
+
</pre>
+
 
+
Make sure you add VFAT support to your kernel if you are building it manually.
+
 
+
== Boot Loader ==
+
 
+
=== 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 <tt>/etc/portage/make.conf</tt>:
+
 
+
<pre>
+
GRUB_PLATFORMS="efi-64"
+
</pre>
+
 
+
Then, <tt>emerge grub</tt>. You will notice <tt>efibootmgr</tt> getting pulled in as a dependency. This is expected and good.
+
 
+
=== 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:
+
 
+
<console>
+
# ##i##grub-install --target=x86_64-efi --efi-directory=/boot /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.
+
=== 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 not use boot-update directly and will create a <tt>/boot/grub/grub.cfg</tt> file manually that looks like this:
+
 
+
<pre>
+
set timeout=3
+
set gfxmode=auto
+
insmod efi_gop
+
insmod efi_uga
+
 
+
menuentry "Funtoo Linux genkernel - kernel-debian-sources-x86_64-3.2.35-2" { 
+
    insmod part_gpt
+
    insmod fat 
+
    set root=(hostdisk//dev/sda,gpt1) 
+
    search --no-floppy --fs-uuid --set __REPLACE_UUID_OF_SDA1__
+
    linux /kernel-debian-sources-x86_64-3.2.35-2 real_root=/dev/sda3
+
    initrd /initramfs-debian-sources-x86_64-3.2.35-2 
+
    set gfxpayload=keep
+
}
+
set default=0
+
</pre>
+
 
+
Note the <tt>search</tt> line where it says <tt>__REPLACE_UUID_OF_SDA1__</tt> above. You will need to run <tt>blkid /dev/sda1</tt> and use the UUID value that is displayed. For example, on my system, I need to use <tt>C34B-19CF</tt>. You can also change the <tt>menuentry</tt> line text in quotes to say whatever you want, and the <tt>linux</tt> and <tt>initrd</tt> lines should reference your kernel versions in <tt>/boot</tt>. As above, use the path <tt>/</tt> instead of <tt>/boot</tt> as the path should be relative to the root of the VFAT filesystem.
+
 
+
== Known Issues ==
+
With pure UEFI boot mode, with legacy mode disabled, following error expected:
+
* video driver not supported, boot hangs, hard reboot required.
+
Choose UEFI first, next legacy driver. It depends on motherboard vendor and efi bios version.
+
In UEFI bios choose grub option, if your succeeded with above guide, additional menu should appear in Boot Menu, otherwise it boots into EFI shell:
+
* grub:NAME of you hard drive
+
 
+
=== Done! ===
+
 
+
Remember to follow all other steps in the regular Funtoo Install Guide. Assuming you did everything correctly, your system should now boot via UEFI! We will be adding UEFI support to boot-update soon to make this process easier.
+

Revision as of 00:06, 10 April 2014

This page is intended to house the new Kernel Seeds page.

Here's what Duncan and I think is a good idea:

  • kernel-seeds.org redirects to this page.
  • This page has some nice, special graphics on it to differentiate it from the other Funtoo Wiki pages.
  • This page begins with a short history of Kernel Seeds, giving credit to Pappy and talking about its role in the Gentoo community.
  • Following this, a short introduction to the concepts behind kernel seeds will be written from scratch.
  • Existing content will be converted and edited and stored as subpages (ie. Kernel_Seeds/Working_With_Kernel_Seeds)
  • The latest .config files (3.9.9 era) will be moved to a git repository to allow community maintenance. The older versions will be archived.

This will allow the pages to be maintained by interested users, and allow good integration with the rest of the Funtoo wiki, while maintaining its distinctiveness with its own look.