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

(Difference between pages)
 
 
Line 1: Line 1:
{{Note|This material has been integrated into the main [[Funtoo Linux Installation]] guide, so please look at that guide if you are installing Funtoo Linux. Editors: this page still contains some good content that we might want to move over there.}}
+
{{#widget:YouTube16x9|playlist=PL2YVrx9jFJOewYI7f15FahwLOZlFCRqjZ|autoplay=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.
+
{{#ask: [[Category:News]] [[Publication Status::Published]]
 
+
|
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.
+
| order=descending
 
+
| sort=Publication Date
== What Are We Doing? ==
+
| format=feed
 
+
| page=full
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.
+
| title=Funtoo Linux News
 
+
| description=Latest Funtoo Linux news
== First Steps ==
+
|type=atom
 
+
| limit=20
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.
+
 
+
{{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.}}
+
 
+
== 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>
+
 
+
== 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'':
+
{{#get_web_data:url=http://build.funtoo.org/index.xml|format=xml|use xpath|data=builds=/subarches/subarch[@name='amd64-bulldozer']/@builds}}
 +
;Builds: {{#external_value:builds}}
  
{{kernelop|title=Device Drivers,Graphics support,Frame buffer Devices|desc=
+
asdflk asdlfk asdlf alsdf lasd flasd flasd flasd flasd flasd flasd flas dflasd flasdl flasdf lasdfl alsdf lasdf lasdflafsd la sdf
    [*]   Simple framebuffer support
+
<div style="align: center;">
}}
+
[[{{#show: Organization:Brownrice Internet| ?Logo|link=none}}|350px|class=img-orglogo|link=Organization:Brownrice Internet]]<br/>
 +
[[Organization:Brownrice Internet|Learn about Funtoo-friendly organization: Brownrice Internet]]</div>
 +
asdflk asdlfk asdlf alsdf lasd flasd flasd flasd flasd flasd flasd flas dflasd flasdl flasdf lasdfl alsdf lasdf lasdflafsd la sdf
 +
{{fullurl:News:The Many Builds of Funtoo Linux}}
 +
{{#widget:AddThis}}
  
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.
+
I like the {{f|/etc/make.conf}} file, which can also be referred to as {{f|/etc/portage/make.conf}}. It is a groovy file. Another cool file is {{f|/etc/fstab}}.
=== Grub method ===
+
  
==== Unmask Grub 2.02_beta2 ====
+
=== make.conf mentions ===
  
Unmask the latest version of GRUB by placing this in your <code>/etc/portage/package.unmask</code>:
+
{{#ask: [[Mentions file::make.conf]]
 
+
| format=category
<pre>
+
sys-boot/grub
+
</pre>
+
 
+
The 2.00 version of GRUB has known issues with UEFI booting. Using 2.02 is essential for having this boot method work reliably.
+
 
+
==== 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 --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>. If you check your <code>/boot/grub/grub.cfg</code> now, you should see something like this:
+
{{console|body=
 
+
# ##i##bluetoothctl
{{file|name=/boot/grub/grub.cfg|desc=|body=
+
[##g##NEW##!g##] Controller 00:02:72:C9:62:65 antec [default]
set timeout=3
+
##bl##[bluetooth]##!bl###power on
 
+
Changing power on succeeded
  insmod part_gpt
+
##bl##[bluetooth]##!bl### ##i##agent on
  insmod fat
+
Agent registered
  set root=(hostdisk//dev/sda,gpt1)
+
##bl##[bluetooth]##!bl### ##i##scan on
  search --no-floppy --fs-uuid --set 3CFD-6884
+
Discovery started
if loadfont /grub/unifont.pf2; then
+
##bl##[bluetooth]##!bl### ##i##devices
  set gfxmode=text
+
Device 00:1F:20:3D:1E:75 Logitech K760
  insmod gfxterm
+
##bl##[bluetooth]##!bl### ##i##pair 00:1F:20:3D:1E:75
  insmod vbe
+
Attempting to pair with 00:1F:20:3D:1E:75
  terminal_output gfxterm
+
[##y##CHG##!y##] Device 00:1F:20:3D:1E:75 Connected: yes
fi
+
##r##[agent]##!r## Passkey: 454358
 
+
##r##[agent]##!r## Passkey: ##i##4##!i##54358
set menu_color_normal=cyan/blue
+
##r##[agent]##!r## Passkey: ##i##45##!i##4358
set menu_color_highlight=blue/cyan
+
##r##[agent]##!r## Passkey: ##i##454##!i##358
 
+
##r##[agent]##!r## Passkey: ##i##4543##!i##58
menuentry "Funtoo Linux - vmlinuz-3.16.3" {
+
##r##[agent]##!r## Passkey: ##i##45435##!i##8
  insmod part_gpt
+
##r##[agent]##!r## Passkey: ##i##454358##!i##
  insmod fat
+
[##y##CHG##!y##] Device 00:1F:20:3D:1E:75 Paired: yes
  set root=(hostdisk//dev/sda,gpt1)
+
Pairing successful
  search --no-floppy --fs-uuid --set 3CFD-6884
+
[##y##CHG##!y##] Device 00:1F:20:3D:1E:75 Connected: no
  linux /vmlinuz-3.16.3 video=uvesafb:1920x1080-32,mtrr:3,ywrap rootfstype=ext4 root=/dev/sda2
+
##bl##[bluetooth]##!bl### ##i##connect 00:1F:20:3D:1E:75
  set gfxpayload=text
+
Attempting to connect to 00:1F:20:3D:1E:75
}
+
[##y##CHG##!y##] Device 00:1F:20:3D:1E:75 Connected: yes
set default=0
+
Connection successful
 +
##bl##[bluetooth]##!bl### ##i##quit
 +
[##r##DEL##!r##] Controller 00:02:72:C9:62:65 antec [default]
 +
#
 
}}
 
}}
 
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
 
  insmod fat
 
  insmod efi_gop
 
  insmod efi_uga
 
  set root=(hostdisk//dev/sda,gpt1)
 
  search --no-floppy --fs-uuid --set 3CFD-6884
 
if loadfont /grub/unifont.pf2; then
 
  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>.
 
 
=== 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 01:46, February 17, 2015

RSS


Builds
1,2,3,4,5,6

asdflk asdlfk asdlf alsdf lasd flasd flasd flasd flasd flasd flasd flas dflasd flasdl flasdf lasdfl alsdf lasdf lasdflafsd la sdf

asdflk asdlfk asdlf alsdf lasd flasd flasd flasd flasd flasd flasd flas dflasd flasdl flasdf lasdfl alsdf lasdf lasdflafsd la sdf http://www.funtoo.org/News:The_Many_Builds_of_Funtoo_Linux

I like the /etc/make.conf file, which can also be referred to as /etc/portage/make.conf. It is a groovy file. Another cool file is /etc/fstab.

make.conf mentions


# bluetoothctl 
[NEW] Controller 00:02:72:C9:62:65 antec [default]
[bluetooth]#power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# scan on
Discovery started
[bluetooth]# devices
Device 00:1F:20:3D:1E:75 Logitech K760
[bluetooth]# pair 00:1F:20:3D:1E:75
Attempting to pair with 00:1F:20:3D:1E:75
[CHG] Device 00:1F:20:3D:1E:75 Connected: yes
[agent] Passkey: 454358
[agent] Passkey: 454358
[agent] Passkey: 454358
[agent] Passkey: 454358
[agent] Passkey: 454358
[agent] Passkey: 454358
[agent] Passkey: 454358
[CHG] Device 00:1F:20:3D:1E:75 Paired: yes
Pairing successful
[CHG] Device 00:1F:20:3D:1E:75 Connected: no
[bluetooth]# connect 00:1F:20:3D:1E:75
Attempting to connect to 00:1F:20:3D:1E:75
[CHG] Device 00:1F:20:3D:1E:75 Connected: yes
Connection successful
[bluetooth]# quit
[DEL] Controller 00:02:72:C9:62:65 antec [default]
#