Difference between pages "UEFI Install Guide" and "Compare Forked Packages To Gentoo"

From Funtoo
(Difference between pages)
Jump to: navigation, search
(Configuring GRUB)
 
(How To Help)
 
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.
+
== Description ==
  
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.
+
Funtoo Linux has a number of forked packages, and sometimes these packages can get out-of-date relative to Gentoo Linux. Periodically, we need to update ebuilds in Funtoo Linux so that they are current. To make this task easier, we have an automated script that compares versions of forked ebuilds in Funtoo Linux to those in Gentoo Linux.
  
== What Are We Doing? ==
+
Here's how it works: Below, you can see a list of all ebuilds in Gentoo Linux that have higher version numbers than those in Funtoo Linux. This list is updated ''hourly''.
 +
{{#get_web_data:url=http://ports.funtoo.org/my.json|format=json|data=fcx8664=fcx8664}}
 +
== Funtoo / Gentoo Comparison (funtoo-current, x86-64bit) ==
 +
 +
{{#arraymaptemplate:{{#external_value:fcx8664}}|PkgCompareDisplay|,||}}
  
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.
+
Some of these ebuilds may be intentionally kept at earlier versions, although in general, we want to update ebuilds to the most recent version that works reliably. Note that rev parts of ebuilds ("<tt>-rX</tt>") are not considered in version comparisons, since sometimes Gentoo and Funtoo revisions are not analogous.
  
== First Steps ==
+
== How To Help ==
  
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.
+
Here's how you can help: If you see an package above that appears to be out-of-date, and you believe we should update to a newer version, [http://bugs.funtoo.org open a bug] on the Funtoo bug tracker. We can look into the ebuild and will give you feedback on whether we feel a new version of the ebuild should be added.
  
== Partitioning ==
+
If there is some consensus that it should be updated, you can also help with the update process. [https://github.com/funtoo/funtoo-overlay funtoo-overlay on GitHub] and working on updating the ebuild yourself. Reference your commits in a bug report on our bug tracker. If you are going to help with ebuild writing, it's important to first familiarize yourself with why we forked the ebuild in the first place. The best way to dig up information on the history of the forked Funtoo package is to type "<tt>git log .</tt>" in the ebuild directory. This will show log information for the package only, and you can look at the history of the ebuild.
  
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>.  
+
When updating ebuilds, we do want to look at Gentoo's most recent changes. Some of our ebuilds are mild variations of Gentoo's ebuilds, while others are complete rewrites. In general, we like to make our work as easy as possible, so we don't want to duplicate work. We'll change stuff if there is a good reason to do so. We want to make the process of updating ebuilds as easy as possible, while keeping added functionality or bug fixes that have been added on the Funtoo side.
  
<console>
+
[[Category:Activity]]
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 05:06, 29 September 2013

Description

Funtoo Linux has a number of forked packages, and sometimes these packages can get out-of-date relative to Gentoo Linux. Periodically, we need to update ebuilds in Funtoo Linux so that they are current. To make this task easier, we have an automated script that compares versions of forked ebuilds in Funtoo Linux to those in Gentoo Linux.

Here's how it works: Below, you can see a list of all ebuilds in Gentoo Linux that have higher version numbers than those in Funtoo Linux. This list is updated hourly.

Funtoo / Gentoo Comparison (funtoo-current, x86-64bit)

  • sys-libs/glibc 2.19 > 2.18-r1
  • sys-libs/timezone-data 2014b > 2013g
  • sys-libs/pam 1.1.8 > 1.1.6-r4
  • app-admin/system-config-printer-gnome 1.4.3-r1 > 1.3.12
  • app-admin/eselect 1.4.1 > 1.3.8
  • app-admin/salt 2014.1.2 > 2014.1.1
  • app-admin/system-config-printer-common 1.4.3 > 1.3.12
  • sys-boot/grub 9999-r1 > 2.00-r7
  • net-misc/networkmanager 0.9.8.8 > 0.9.8.2-r2
  • net-misc/bfgminer 3.10.0 > 3.8.1
  • net-misc/x2goserver 4.0.1.15 > 4.0.1.6
  • net-dns/avahi 0.6.31-r4 > 0.6.30-r4
  • net-dns/dnsmasq 2.69 > 2.66
  • sys-firmware/ipxe 1.0.0_p20130925 > 1.0.0_p20130624-r1
  • app-shells/bash 4.2_p47 > 4.2_p45-r1
  • sys-apps/pciutils 3.2.1 > 3.2.0
  • sys-apps/gptfdisk 0.8.10 > 0.8.8
  • sys-apps/man-db 2.6.7.1 > 2.6.5
  • sys-apps/hwids 20140317 > 20140103
  • sys-apps/kmod 17 > 15-r1
  • sys-apps/gawk 4.1.1 > 4.1.0
  • sys-apps/coreutils 8.22 > 8.21
  • sys-apps/openrc 0.12.4 > 0.12.3-r2
  • sys-apps/iproute2 3.14.0 > 3.11.0
  • sys-apps/busybox 1.22.1 > 1.21.1
  • sys-apps/util-linux 2.24.1-r2 > 2.23.2-r1
  • app-portage/eix 0.30.1 > 0.29.6
  • app-portage/portage-utils 0.53 > 0.21-r1
  • sys-cluster/ploop 1.11 > 1.10
  • virtual/jdk 1.8.0 > 1.7.0
  • virtual/jre 1.8.0 > 1.7.0
  • x11-wm/icewm 1.3.8 > 1.3.7-r2
  • mail-mta/postfix 2.12_pre20140406 > 2.10.2
  • net-wireless/hostapd 2.1 > 2.0
  • dev-java/oracle-jdk-bin 1.8.0.0 > 1.7.0.55
  • dev-java/oracle-jre-bin 1.8.0.0 > 1.7.0.51
  • sys-kernel/linux-headers 3.14 > 3.13
  • sys-kernel/genkernel 3.4.49.1 > 3.4.40.7-r2
  • media-libs/libgphoto2 2.5.3.1 > 2.5.2-r1
  • sys-devel/binutils 2.24-r2 > 2.23.2
  • sys-power/upower 0.9.23-r2 > 0.9.20-r1
  • app-office/libreoffice-bin 4.1.4.2 > 4.1.3.2
  • net-analyzer/munin 2.0.19-r1 > 2.0.14
  • dev-util/valgrind 3.9.0 > 3.8.1-r2
  • app-vim/gentoo-syntax 20130619 > 20120916
  • app-misc/screenfetch 3.2.2 > 3.0.5
  • app-misc/ca-certificates 20140223.3.16-r1 > 20140223.3.15.5
  • www-servers/nginx 1.5.13 > 1.5.11
  • sys-fs/eudev 1.6 > 1.5.3
  • sys-fs/udisks 2.1.3 > 2.0.0
  • sys-fs/udev 212-r1 > 204
  • sys-fs/lvm2 2.02.105-r2 > 2.02.103
  • dev-lang/perl 5.18.2 > 5.18.1
  • x11-drivers/ati-drivers 14.3_beta > 13.12
  • sys-auth/pambase 20140313 > 20120417
  • www-client/google-chrome 34.0.1847.116_p1 > 33.0.1750.152_p1

Some of these ebuilds may be intentionally kept at earlier versions, although in general, we want to update ebuilds to the most recent version that works reliably. Note that rev parts of ebuilds ("-rX") are not considered in version comparisons, since sometimes Gentoo and Funtoo revisions are not analogous.

How To Help

Here's how you can help: If you see an package above that appears to be out-of-date, and you believe we should update to a newer version, open a bug on the Funtoo bug tracker. We can look into the ebuild and will give you feedback on whether we feel a new version of the ebuild should be added.

If there is some consensus that it should be updated, you can also help with the update process. funtoo-overlay on GitHub and working on updating the ebuild yourself. Reference your commits in a bug report on our bug tracker. If you are going to help with ebuild writing, it's important to first familiarize yourself with why we forked the ebuild in the first place. The best way to dig up information on the history of the forked Funtoo package is to type "git log ." in the ebuild directory. This will show log information for the package only, and you can look at the history of the ebuild.

When updating ebuilds, we do want to look at Gentoo's most recent changes. Some of our ebuilds are mild variations of Gentoo's ebuilds, while others are complete rewrites. In general, we like to make our work as easy as possible, so we don't want to duplicate work. We'll change stuff if there is a good reason to do so. We want to make the process of updating ebuilds as easy as possible, while keeping added functionality or bug fixes that have been added on the Funtoo side.