Difference between pages "UEFI Install Guide" and "Test"

(Difference between pages)
m
 
 
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.
+
{{#gravatar_md5:drobbins@funtoo.org}}
  
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.
+
{{#Widget:NewsDisplay|user=Drobbins|gravatar_url=http://www.gravatar.com/avatar/7490f23fe709b41d3be4f79549a679f8?s=80&d=retro&r=g|title=This is a news item!| body=
 +
blahasl adslfkas flasf lasdfksad lfasdlkf dsalfk dslfkasd lfdsakf als sadlfdsal f}} [[Read more...]]
 +
{{#Widget:NewsDisplay|user=Drobbins|gravatar_url=http://www.gravatar.com/avatar/7490f23fe709b41d3be4f79549a679f8?s=80&d=retro&r=g|title=This is a news item!| body=
 +
blahasl adslfkas flasf lasdfksad lfasdlkf dsalfk dslfkasd lfdsakf als sadlfdsal f}}
  
== What Are We Doing? ==
+
== News Items ==
  
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.
+
{{#ask: [[Category:News]] [[Publication Status::Published]]
 
+
| ?Publication Date
== First Steps ==
+
| ?News Category
 
+
| ?Summary
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.
+
| ?Author
 
+
| ?Gravatar MD5
{{fancynote|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.}}
+
| order=descending
 
+
| sort=Publication Date
== Partitioning ==
+
| format=template
 
+
| template=NewsDisplay
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>.
+
| limit=10
 
+
<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>
+
 
+
== Kernel ==
+
 
+
=== VFAT ===
+
 
+
Make sure you add VFAT support to your kernel if you are building it manually.
+
 
+
=== EFI Framebuffer ===
+
 
+
If you have the following option enabled in your kernel, then uvesafb and efifb will not be able to detect the framebuffer:
+
 
+
{{kernelop|title=Bus options (PCI etc.)|desc=
+
    [*] Mark VGA/VBE/EFI FB as generic system framebuffer (NEW)
+
 
}}
 
}}
  
If you have that option enabled, ''you must also enable'':
+
== Other Stuff ==
  
{{kernelop|title=Device Drivers,Graphics support,Frame buffer Devices|desc=
+
{{Package|sys-apps/portage}}
    [*]  Simple framebuffer support
+
}}
+
  
This is the preferred method of using the EFI framebuffer, the efifb and uvesafb drivers will be used as a fallback if the above is not compatible.
+
== Badabing ==
  
== Boot Loader ==
+
{{#ask: [[Category:People]]
=== EFI Stub method ===
+
| limit=20
Instead of bothering with the installation of GRUB, you can consider using the UEFI firmware of your computer to boot your kernel.
+
| order=random
 
+
| format=template
==== Kernel Configuration ====
+
| template=GravatarDisplay
To prepare your kernel to boot with EFI stub, make sure that the following options are built in to your kernel:
+
| link=none
{{kernelop|title=Processor type and features|desc=
+
| searchlabel=
[*] EFI runtime service support
+
[*]    EFI stub support
+
[ ]        EFI mixed-mode support
+
 
+
[*] Built-in kernel command line
+
(kernel options that you want to pass go here)
+
 
}}
 
}}
{{note|Commands that you would normally pass, such as, <code>video{{=}}uvesafb:1920x1080-32,mtrr:3,ywrap</code>, should be put here. In other words, anything that you would normally add to <code>/etc/boot.conf</code> after <code>params +{{=}}</code> should be added to the built-in kernel command line as well.}}
 
  
{{important|You should specifiy the position of your rootfs here. For example: <code>root{{=}}/dev/sdb1</code>.}}
+
== Table test ==
 +
<div class="table-responsive"><table class="table"><tr><td>Hello</td></tr><tr><td>Hello</td></tr><tr><td>Hello</td></tr></table></div>
  
If your system requires an initramfs to boot, do not worry, you can build that in to the kernel. One thing that you should know, however, is that the kernel only takes plaintext and <code>.cpio</code> files for initramfs source files. Therefore, if you use an application to generate an initramfs for you, make sure that it does not use gzip compression. To build better-initramfs-bin without gzip compression, disable the gzip use flag for the package:
+
== Testing error on Show ==
{{file|name=/etc/portage/package.usr|desc= |body=
+
sys-kernel/better-initramfs-bin -gzip
+
}}
+
then emerge better-initramfs:
+
<console>
+
###i## emerge better-initramfs-bin
+
</console>
+
If you check in your <code>/boot</code> directory, you should see a file called <code>initramfs.cpio</code>. See below to include this file in your kernel.
+
{{kernelop|title=General setup|desc=
+
[*] Initial RAM filesystem and RAM disk (initramfs/initrd) support
+
(/path/to/initramfs/file.cpio)
+
For better-initramfs-bin:
+
(/boot/initramfs.cpio)
+
}}
+
  
==== Building and installing the kernel ====
+
* {{#show:User:JanZhou|?full name}}
After you have configured your kernel, build it, install it to <code>/boot</code>, and then create a copy of the image to store in the EFI boot directory:
+
* {{#show:User:Drobbins|?full name}}
<console>
+
###i## pwd
+
/usr/src/linux
+
###i## make -jn
+
###i## make -jn install modules_install
+
###i## mkdir -vp /boot/EFI/Boot
+
###i## cp -v /boot/vmlinuz-x.x.x /boot/EFI/Boot/bootx64.efi
+
</console>
+
When you have finished all of this, you should be able to reboot and enjoy yor new Funtoo system!
+
  
=== Grub method ===
 
==== 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,
+
{{DISPLAYTITLE:Bob Boblaw}}
add the following line to <tt>/etc/portage/make.conf</tt>:
+
[[Category:Test]]
  
<pre>
+
Adding some text
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.
+
== Testing External Data ==
  
==== 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:
+
{{#get_web_data:url=http://auth.funtoo.org:9093/static/members.xml|format=xml|use xpath|data=ircnick=/members/user/ircnick,fullname=/members/user/fullname}}
  
<console>
+
{{#display_external_table:template=MemberDisplay|data=ircnick,fullname}}
# ##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:
+
Daniel Robbins:drobbins:bdfl
* <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 ====
+
{{file|name=foobar|lang=python|desc=foobarosity|body=
 
+
import system
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>. If you check your <code>/boot/grub/grub.cfg</code> now, you should see something like this:  
+
{{file|name=/etc/foo.conf|desc=My foo.conf file|body=
 +
# /etc/host.conf:
 +
# $Header: /var/cvsroot/gentoo/src/patchsets/glibc/extra/etc/host.conf,v 1.1 2006/09/29 23:52:23 vapier Exp $
  
{{file|name=/boot/grub/grub.cfg|desc=|body=
+
# The  file /etc/host.conf contains configuration information specific to
set timeout=3
+
# the resolver library.  It should contain one configuration keyword  per
 +
# line,  followed by appropriate configuration information.  The keywords
 +
# recognized are order, trim, mdns, multi, nospoof, spoof, and reorder.
  
  insmod part_gpt
 
  insmod fat
 
  set root=(hostdisk//dev/sda,gpt1)
 
  search --no-floppy --fs-uuid --set 3CFD-6884
 
if loadfont /grub/unifont.pf2; then
 
  set gfxmode=text
 
  insmod gfxterm
 
  insmod vbe
 
  terminal_output gfxterm
 
fi
 
  
set menu_color_normal=cyan/blue
 
set menu_color_highlight=blue/cyan
 
  
menuentry "Funtoo Linux - vmlinuz-3.16.3" {
+
# This keyword specifies how host lookups are to be performed. It
  insmod part_gpt
+
# should be followed by one or more lookup methods, separated by
  insmod fat
+
# commas. Valid methods are bind, hosts, and nis.
  set root=(hostdisk//dev/sda,gpt1)
+
#
  search --no-floppy --fs-uuid --set 3CFD-6884
+
order hosts, bind
  linux /vmlinuz-3.16.3 video=uvesafb:1920x1080-32,mtrr:3,ywrap rootfstype=ext4 root=/dev/sda2
+
  set gfxpayload=text
+
}
+
set default=0
+
}}
+
  
To get your <code>/boot/grub/grub.cfg</code> to support booting with UEFI, make your <code>/boot/grub/grub.cfg</code> look like this:
 
{{file|name=/boot/grub/grub.cfg|desc=|body=
 
set timeout=3
 
  
  insmod part_gpt
+
# Valid  values are on and off.  If set to on, the resolv+ library
  insmod fat
+
# will return all valid addresses for a host that appears  in  the
  insmod efi_gop
+
# /etc/hosts  file,  instead  of  only  the first. This is off by
  insmod efi_uga
+
# default, as it may cause a substantial performance loss at sites
  set root=(hostdisk//dev/sda,gpt1)
+
# with large hosts files.
  search --no-floppy --fs-uuid --set 3CFD-6884
+
#
if loadfont /grub/unifont.pf2; then
+
multi on
  set gfxmode=auto
+
  insmod gfxterm
+
  insmod vbe
+
  terminal_output gfxterm
+
fi
+
 
+
set menu_color_normal=cyan/blue
+
set menu_color_highlight=blue/cyan
+
 
+
menuentry "Funtoo Linux - vmlinuz-3.16.3" {
+
  insmod part_gpt
+
  insmod fat
+
  set root=(hostdisk//dev/sda,gpt1)
+
  search --no-floppy --fs-uuid --set 3CFD-6884
+
  linux /vmlinuz-3.16.3 video=uvesafb:1920x1080-32,mtrr:3,ywrap rootfstype=ext4 root=/dev/sda2
+
  set gfxpayload=keep
+
}
+
set default=0
+
 
}}
 
}}
 
The lines that we have added and altered do the following:
 
* <code>insmod efi_gop</code> and <code>insmod efi_uga</code>: Both of these involve adding support for the UEFI framebuffer to GRUB.
 
* <code>set gfxmode=auto</code>: Instead of having the GRUB boot option screen being displayed at the smallest resolution possible, changing this to auto will make it fit the resolution of your display.
 
 
== 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: <code>grub:NAME of you hard drive</code>
 
* On some systems, installing the packages that are required for UEFI booting with any gcc later than a 4.x.x release may lead to a black screen after the GRUB screen. To fix this, before you begin installing any packages on your system, emerge =gcc-4.6.4-r2 and proceed with the installation as usual. Remember to switch your compiler back to the version of gcc that came with your system after you have finished installing. To do this, use <code>gcc-config 2</code>. This problem can also be fixed by following the [[Efi Stub guide]] instead of the GRUB one.
 
 
=== 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.
 
 
[[Category:HOWTO]]
 

Revision as of 02:34, October 20, 2014

7490f23fe709b41d3be4f79549a679f8

Drobbins

This is a news item!

blahasl adslfkas flasf lasdfksad lfasdlkf dsalfk dslfkasd lfdsakf als sadlfdsal f
Read more...
Drobbins

This is a news item!

blahasl adslfkas flasf lasdfksad lfasdlkf dsalfk dslfkasd lfdsakf als sadlfdsal f

News Items

er:Dantrell|Dantrell]]

ws:Testing GNOME 3.14|Testing GNOME 3.14]]

GNOME 3.14 is now available in Funtoo, masked for testing. Help us test it!
22 October 2014 by er:Dantrell|Dantrell]]
er:Drobbins|Drobbins]]

ws:Boot-update-1.7.0 released, masked for testing|Boot-update-1.7.0 released, masked for testing]]

This new version of boot-update contains serial terminal support and lilo fixes.
16 October 2014 by er:Drobbins|Drobbins]]

Other Stuff

Portage (Funtoo)

Badabing

User:TaotetekUser:BrantgurgaUser:PantharUser:ThediamondsaintUser:MerlindouUser:PlatanusUser:JobbeUser:BladewingUser:ShellUser:CoffnixUser:NetigerUser:HappyUser:JamesB192User:HlaubeUser:JdkcnUser:ThiagowfxUser:KittenGNUUser:PYRATSUser:BazzleUser:Camtt

Table test

Hello
Hello
Hello

Testing error on Show

  • Daniel Robbins

Adding some text

Testing External Data

Daniel Robbins:drobbins:bdfl

foobar: foobarosity (python source code)
import system
/etc/foo.conf: My foo.conf file
# /etc/host.conf:
# $Header: /var/cvsroot/gentoo/src/patchsets/glibc/extra/etc/host.conf,v 1.1 2006/09/29 23:52:23 vapier Exp $

# The  file /etc/host.conf contains configuration information specific to
# the resolver library.  It should contain one configuration keyword  per
# line,  followed by appropriate configuration information.  The keywords
# recognized are order, trim, mdns, multi, nospoof, spoof, and reorder.



# This keyword specifies how host lookups are to be performed. It
# should be followed by one or more lookup methods, separated by
# commas.  Valid methods are bind, hosts, and nis.
#
order hosts, bind


# Valid  values are on and off.  If set to on, the resolv+ library
# will return all valid addresses for a host that appears  in  the
# /etc/hosts  file,  instead  of  only  the first.  This is off by
# default, as it may cause a substantial performance loss at sites
# with large hosts files.
#
multi on