Escolar Documentos
Profissional Documentos
Cultura Documentos
Fedora 14 ( codename Laughlin) is probably the first version of Fedora which is likely to be
installed on a significant number of UEFI-enabled hardware platforms. However, you cannot do a
UEFI-install from the standard Fedora 14 distribution media such a DVD as you would on a legacy
BIOS-based platform. You have use one of a number of alternative installation procedures.
In this post I will describe three ways to do an UEFI install of 64-bit Fedora 14 on a 64-bit
ly
Intel-based UEFI-enabled platform. There is no technical reason that an UEFI install should not
work on 64-bit AMD platforms but I have not tested such a configuration. Since Fedora 14 is not
on
yet officially released as I write this post, I used the Fedora 14 RC1 candidate images for testing
purposes but I do not think anything major relating to UEFI-installs will change prior to the formal
release of Fedora 14 in a few days.
se
Although Fedora had rudimentary support for EFI/UEFI since at least Fedora 9, no mention of
such support was included in the associated Installation Guides. With Fedora 14, this has changed.
The Fedora 14 Installation Guide describes how to make a minimal UEFI boot image in section
lu
3.3.1 and discusses UEFI installs in section 7.1. You should read these sections of the Installation
Guide before attempting your own install. Note however that UEFI installation of 32-bit Fedora 14
is not supported. There is no technical reason why this could not be done; it would appear to be
a
simply a business decision as was the decision not to make the standard Fedora 14 distribution
media dual bootable like Red Hat Enterprise Linux 6 and some other GNU/Linux distributions.
nn
Method 1
o
This method uses the 64-bit Fedora 14 netinst.iso image. The output of the dumpet utility shows
that this image has two bootable entries.
rs
pe
# dumpet -i Fedora-14-x86_64-netinst.iso
Validation Entry:
Header Indicator: 0x01 (Validation Entry)
PlatformId: 0x00 (80x86)
ID: ""
r
Checksum: 0x55aa
Fo
Platform ID 0×00 is for legacy BIOS platforms and platform ID 0xEF is for EFI/UEFI platforms.
This image is a complete installation media which uses the Internet to retrieve the various
packages it needs to perform the user-specified installation of the Fedora 14 distribution. The
contents of this image are:
# cd /media/Fedora14
# ls -Ral
.:
total 12
dr-xr-xr-x. 5 fpm fpm 2048 Oct 12 19:35 .
ly
drwxr-xr-x. 3 root root 4096 Oct 29 14:42 ..
dr-xr-xr-x. 3 fpm fpm 2048 Oct 12 19:35 EFI
drwxr-sr-x. 3 fpm fpm 2048 Oct 12 19:34 images
on
drwxr-sr-x. 2 fpm fpm 2048 Oct 12 19:34 isolinux
./EFI:
total 6
dr-xr-xr-x. 3 fpm fpm 2048 Oct 12 19:35 .
se
dr-xr-xr-x. 5 fpm fpm 2048 Oct 12 19:35 ..
drwxr-xr-x. 2 fpm fpm 2048 Oct 12 19:34 BOOT
./EFI/BOOT:
lu
total 72
drwxr-xr-x. 2 fpm fpm 2048 Oct 12 19:34 .
dr-xr-xr-x. 3 fpm fpm 2048 Oct 12 19:35 ..
a
-r--r--r--. 1 fpm fpm 168 Oct 12 19:34 BOOTX64.conf
-rw-r--r--. 1 fpm fpm 68392 Sep 13 12:05 splash.xpm.gz
nn
./images:
total 187525
o
./images/pxeboot:
total 34991
r
./isolinux:
total 36246
drwxr-sr-x. 2 fpm fpm 2048 Oct 12 19:34 .
dr-xr-xr-x. 5 fpm fpm 2048 Oct 12 19:35 ..
-r--r--r--. 1 fpm fpm 2048 Oct 12 19:35 boot.cat
-rw-r--r--. 1 fpm fpm 84 Oct 12 19:34 boot.msg
-r--r--r--. 1 fpm fpm 142 Oct 12 19:34 grub.conf
-rw-r--r--. 2 fpm fpm 32043809 Oct 12 19:34 initrd.img
-r--r--r--. 1 fpm fpm 24576 Oct 12 19:34 isolinux.bin
-r--r--r--. 1 fpm fpm 1023 Oct 12 19:34 isolinux.cfg
-r--r--r--. 1 fpm fpm 165080 Oct 12 19:34 memtest
-r--r--r--. 1 fpm fpm 462737 Oct 12 19:34 splash.jpg
-r--r--r--. 1 fpm fpm 462737 Oct 12 19:34 syslinux-vesa-splash.jpg
-r--r--r--. 1 fpm fpm 2451 Oct 12 19:35 TRANS.TBL
-r--r--r--. 1 fpm fpm 162860 Oct 12 19:34 vesamenu.c32
The size of the image is only approximately 220Mb. Either create a bootable DVD or USB stick. I
recommend the USB stick option as it is the faster of the two to do.
Here is how to use the dd utility to create a bootable USB stick (disk) assuming that /dev/sdb
points to the USB stick and netinst.iso is in the current directory. By the way, assume that
anything previously on the USB stick will be overwritten and lost – so back up anything valuable
on the USB stick.
# dd if=./Fedora-14-x86_64-netinst.iso of=/dev/sdb
ly
Insert this USB stick into your UEFI platform and select the USB stick to boot from using your
UEFI boot manager. The installation will proceed as normal. During the installation you will need
on
to configure a network interface so that the required RPMs for the Fedora 14 distribution can be
downloaded over the Internet.
Method 2
se
This method requires you to download the entire 64-bit Fedora 14 release and burn the ISO onto a
(bootable) DVD. Next mount the DVD and cd to the images subdirectory. Plug in a suitable USB
lu
stick and use the dd utility to write efidisk.img to the USB stick. As before, assume that anything
previously on the USB stick will be overwritten and lost.
a
# cd /media/Fedora\ 14\ x86_64\ DVD/images
nn
# ls -al efidisk.img
-rw-r--r--. 1 fpm fpm 36349952 Oct 21 14:29 efidisk.img
# dd if=./efidisk.img of=/dev/sdb
o
70996+0 records in
70996+0 records out
rs
# gdisk /dev/sdb
pe
GPT: present
.:
total 22
drwxr-xr-x. 3 root root 16384 Dec 31 1969 .
dr-xr-xr-x. 24 root root 4096 Oct 29 10:02 ..
drwxr-xr-x. 3 root root 2048 Oct 21 18:29 EFI
./EFI:
total 20
drwxr-xr-x. 3 root root 2048 Oct 21 18:29 .
drwxr-xr-x. 3 root root 16384 Dec 31 1969 ..
drwxr-xr-x. 2 root root 2048 Oct 21 18:29 BOOT
./EFI/BOOT:
total 35302
drwxr-xr-x. 2 root root 2048 Oct 21 18:29 .
drwxr-xr-x. 3 root root 2048 Oct 21 18:29 ..
ly
-rwxr-xr-x. 1 root root 156 Oct 21 18:29 BOOTX64.conf
-rwxr-xr-x. 1 root root 242985 Oct 21 18:29 BOOTX64.efi
-rwxr-xr-x. 1 root root 32045806 Oct 21 18:29 initrd.img
on
-rwxr-xr-x. 1 root root 68392 Oct 21 18:29 splash.xpm.gz
-rwxr-xr-x. 1 root root 3782016 Oct 21 18:29 vmlinuz
As you can see from the above a small ESP named EFI System Partition is created on the USB
se
stick. It contains the absolute minimum number of files to UEFI-boot a Fedora 14 image. Well, it
could be slightly smaller if they skipped the Legacy GRUB graphic image, i.e. spash.xpm.gz.
Because it is removable media, UEFI understands that BOOTX64.efi is the image to load.
lu
Insert this USB stick into your UEFI platform and select the USB stick to boot from using your
UEFI boot manager. The installation will proceed as normal. As before you will need to configure a
a
network interface so that the required RPMs for the Fedora 14 distribution can be downloaded
over the Internet.
nn
Method 3
If you have a Fedora 14 distribution DVD but poor Internet connectivity, you can still UEFI install
o
Fedora 14. Make a minimal install on a USB stick as described in Method 2. On your UEFI
rs
platform, place the DVD in your DVD drive and insert/attach the USB stick. From your UEFI boot
manager, select the USB stick and boot from it. During installation do not configure a network
interface or select any additional software repositories. A “Found local Installation Media” will be
pe
displayed and Anaconda will retrieve the required RPMs from the what it calls the “Installation
Repo” i.e the Fedora 14 DVD.
r
Fo
ly
on
se
lu
Now that I have described the above methods for UEFI installing Fedora 14, let us examine the
a
UEFI-specific artifacts created by the Fedora 14 install process. When UEFI-installed, Fedora 14
partitions a disk using GPT (GUID Partition Table) rather than using a MBR. For example, here is
nn
the default GPT created by Fedora 14 when the distribution was installed on a single 500Gb disk.
o
# df
rs
# parted /dev/sda
Fo
# gdisk /dev/sda
GPT fdisk (gdisk) version 0.6.8
ly
1 2048 411647 200.0 MiB EF00
2 411648 1435647 500.0 MiB 0700
3 1435648 976773119 465.1 GiB 0700
on
Command (? for help): c
Partition number (1-3): 1
Enter name: ESP
se
Command (? for help): x
MBR partitions:
Number Boot Start (sector) Length (sectors) Type
rs
1 1 976773167 0xEE
The GPT protective partition starts at sector 0, i.e. it precedes partition number 1, and covers the
entire area of the disk used by three GPT partitions. Partition 1 is the EFI System Partition (ESP).
r
The ESP is mounted on /boot/efi. Here is listing of the contents of the ESP.
Fo
# cd /boot/efi
# ls -alR
.:
total 26
drwx------. 3 root root 16384 Dec 31 1969 .
dr-xr-xr-x. 5 root root 1024 Oct 28 18:26 ..
drwx------. 4 root root 4096 Oct 28 22:36 EFI
./EFI:
total 28
drwx------. 4 root root 4096 Oct 28 22:36 .
drwx------. 3 root root 16384 Dec 31 1969 ..
drwx------. 2 root root 4096 Oct 28 18:27 redhat
./EFI/redhat:
total 252
The loadable image for the UEFI booting service is /EFI/redhat/grub.efi. This is a modified version
of GRUB Legacy which a UEFI loader can load.
According to section 3.4.1.2 of the current version (2.3) of the UEFI specification:
ly
For Fedora 14, that FilePath is /EFI/redhat/grub.efi. It would be nice if this were mentioned
on
somewhere in the Fedora 14 install documentation.
se
If for whatever reason, all the Boot#### variables referenced in the BootOrder
variable point to devices that are not present, the boot devices have timed out, the
lu
specific boot file does not exist, or there is no valid boot variable, default boot
processing may optionally occur.
a
All the UEFI platforms I have encountered to date support such default boot processing. In the
nn
case of an X86_64 platform the system firmware will attempt to load the image
/EFI/BOOT/BOOTX64.EFI. For this reason, as a backup boot mechanism, I usually create a
…/EFI/BOOT directory and copy the …/EFI/redhat/grub.efi and …/EFI/redhat/grub.conf files into
o
By the way the Fedora 14 install does not create an EFI volume label for the EFI System Partition.
If you wish, you can easily add one from an EFI shell if one is available to you.
pe
A number of utilities do not work after a UEFI install of Fedora 14. For example fdisk does not
Fo
work with GPT disks. In fairness, it does display a message to that effect. Many people use parted
which does understand GPT but I prefer to use the gdisk utility. Also
System/Administration/Bootloader (/usr/share/system-config-boot/system-config-boot.py) fails with
a /boot/grub/grub.conf not found error. This script needs to be modified so that it knows to edit
/boot/efi/EFI/redhat/grub.conf when an ESP exists.
Please let me know if you discover other interesting methods of UEFI booting Fedora 14 or any
other commands and utilities that exhibit failures due to a UEFI install.