'''Unified Extensible Firmware Interface''' (or UEFI for short) is a new type of firmware that was initially designed by Intel (known as EFI then) mainly for its Itanium based systems. It introduces new ways of booting an OS that is distinct from the commonly used "MBR boot code" method followed for BIOS systems. It started as Intel's EFI in versions 1.x and then a group of companies called the UEFI Forum took over its development from which it was called Unified EFI starting with version 2.0 . As of 23 May 2012, UEFI Specification 2.3.1 is the most recent version.

+

'''Unified Extensible Firmware Interface''' (or UEFI for short) is a new type of firmware that was initially designed by Intel (known as EFI then) mainly for its Itanium based systems. It introduces new ways of booting an OS that is distinct from the commonly used "MBR boot code" method followed for BIOS systems. It started as Intel's EFI in versions 1.x and then a group of companies called the UEFI Forum took over its development from which it was called Unified EFI starting with version 2.0 . As of 24 July 2013, UEFI Specification 2.4 (released July 11, 2013) is the most recent version.

{{Note|Unless specified as EFI 1.x , EFI and UEFI terms are used interchangeably to denote UEFI 2.x firmware. Also unless stated explicitly, these instructions are general and some of them may not work or may be different in Macs. Apple's EFI implementation is neither a EFI 1.x version nor UEFI 2.x version but mixes up both. This kind of firmware does not fall under any one UEFI Specification version and therefore it is not a standard UEFI firmware.}}

{{Note|Unless specified as EFI 1.x , EFI and UEFI terms are used interchangeably to denote UEFI 2.x firmware. Also unless stated explicitly, these instructions are general and some of them may not work or may be different in Macs. Apple's EFI implementation is neither a EFI 1.x version nor UEFI 2.x version but mixes up both. This kind of firmware does not fall under any one UEFI Specification version and therefore it is not a standard UEFI firmware.}}

−

== Booting an OS using BIOS ==

+

Before understanding UEFI, it is important to understand how the pre-UEFI (BIOS) systems boot. This is explained in subsequent sections.

−

A BIOS or Basic Input-Output System is the very first program that is executed once the system is switched on. After all the hardware has been initialized and the POST operation has completed, the BIOS executes the first boot code in the first device in the device booting list.

+

= BIOS =

−

If the list starts with a CD/DVD drive, then the El-Torito entry in the CD/DVD is executed. This is how bootable CD/DVD works. If the list starts with a HDD, then BIOS executes the very first 440 bytes MBR boot code. The boot code then chainloads or bootstraps a much larger and complex bootloader which then loads the OS.

+

A BIOS or Basic Input-Output System is the very first program (firmware) that is executed once the system is switched on. In most cases it is stored in a flash memory in the motherboard itself and independent of the system storage.

−

Basically, the BIOS does not know how to read a partition table or filesystem. All it does is initialize the hardware, then load and run the 440-byte boot code.

# BIOS launches the first 440 bytes (MBR boot code region) of the first disk in the BIOS disk order

+

# The MBR boot code then takes control from BIOS and launches its next stage code (if any) (mostly bootloader code)

+

# The launched (2nd stage) code (actual bootloader) then reads its support and config files

+

# Based on the data in its config files, the bootloader loads the kernel and initramfs into system memory (RAM) and launches the kernel

+

+

== Multibooting in BIOS ==

Since very little can be achieved by a program that fits into the 440-byte boot code area, multi-booting using BIOS requires a multi-boot capable bootloader (multi-boot refers to booting multiple operating systems, not to booting a kernel in the Multiboot format specified by the GRUB developers). So usually a common bootloader like [[GRUB]] or [[Syslinux]] or [[LILO]] would be loaded by the BIOS, and it would load an operating system by either chain-loading or directly loading the kernel.

Since very little can be achieved by a program that fits into the 440-byte boot code area, multi-booting using BIOS requires a multi-boot capable bootloader (multi-boot refers to booting multiple operating systems, not to booting a kernel in the Multiboot format specified by the GRUB developers). So usually a common bootloader like [[GRUB]] or [[Syslinux]] or [[LILO]] would be loaded by the BIOS, and it would load an operating system by either chain-loading or directly loading the kernel.

−

== Booting an OS using UEFI ==

+

= UEFI =

−

UEFI firmware does not support booting through the above mentioned method which is the only way supported by BIOS. UEFI has support for reading both the partition table as well as understanding filesystems.

+

UEFI has support for reading both the partition table as well as understanding filesystems. Hence it is not limited by 440 byte code limitation (MBR boot code) as in BIOS systems. It does not use the MBR boot code at all.

The commonly used UEFI firmwares support both MBR and GPT partition table. EFI in Apple-Intel Macs are known to also support Apple Partition Map besides MBR and GPT. Most UEFI firmwares have support for accessing FAT12 (floppy disks), FAT16 and FAT32 filesystems in HDDs and ISO9660 (and UDF) in CD/DVDs. EFI in Apple-Intel Macs can access HFS/HFS+ filesystems also apart from the mentioned ones.

The commonly used UEFI firmwares support both MBR and GPT partition table. EFI in Apple-Intel Macs are known to also support Apple Partition Map besides MBR and GPT. Most UEFI firmwares have support for accessing FAT12 (floppy disks), FAT16 and FAT32 filesystems in HDDs and ISO9660 (and UDF) in CD/DVDs. EFI in Apple-Intel Macs can access HFS/HFS+ filesystems also apart from the mentioned ones.

−

UEFI does not launch any boot code in the MBR whether it exists or not. Instead it uses a special partition in the partition table called ''EFI SYSTEM PARTITION'' in which files required to be launched by the firmware are stored. Each vendor can store its files under {{ic|<EFI SYSTEM PARTITION>/EFI/<VENDOR NAME>/}} folder and can use the firmware or its shell (UEFI shell) to launch the boot program. An EFI System Partition is usually formatted as FAT32.

+

UEFI does not launch any boot code in the MBR whether it exists or not. Instead it uses a special partition in the partition table called '''EFI SYSTEM PARTITION''' in which files required to be launched by the firmware are stored. Each vendor can store its files under {{ic|<EFI SYSTEM PARTITION>/EFI/<VENDOR NAME>/}} folder and can use the firmware or its shell (UEFI shell) to launch the boot program. An EFI System Partition is usually formatted as FAT32 (mostly) or FAT16

+

+

Under UEFI, every program whether it is an OS loader or a utility (e.g. a memory testing app or recovery tool), should be a UEFI Application corresponding to the EFI firmware bitness/architecture. The vast majority of UEFI firmwares, including recent Apple Macs, use x86_64 EFI firmware. The only known devices that use IA32 (32-bit) EFI are older (pre 2008) Apple Macs, some recent Intel Cloverfield ultrabooks and some older Intel Server boards are known to operate on Intel EFI 1.10 firmware

−

{{Note|On some UEFI systems the only possible way to launch UEFI application on boot (if it doesn't have custom entry in UEFI boot menu) is to put it in this fixed location: {{ic|<EFI SYSTEM PARTITION>/EFI/boot/bootx64.efi}} (for 64-bit x86 system)}}

+

An x86_64 EFI firmware does not include support for launching 32-bit EFI apps (unlike x86_64 Linux and Windows versions which include such support). Therefore the UEFI application must be compiled for that specific firmware processor bitness/architecture.

−

Under UEFI, every program whether it is an OS loader or a utility (e.g. a memory testing app or recovery tool), should be a UEFI Application corresponding to the EFI firmware architecture. The vast majority of UEFI firmwares, including recent Apple Macs, use x86_64 EFI firmware. The only known devices that use i386 EFI are older (pre 2008) Apple Macs.

# Firmware then reads its Boot Manager data to determine which UEFI application to be launched and from where (i.e. from which disk and partition).

+

# Firmware then launches the UEFI application as defined in the boot entry in the firmware's boot manager.

+

# The launched UEFI application may launch another application (in case of UEFI Shell or a boot manager like rEFInd) or the kernel and initramfs (in case of a bootloader like GRUB) depending on how the UEFI application was configured.

−

An x86_64 EFI firmware does not include support for launching 32-bit EFI apps unlike x86_64 Linux and Windows versions which include such support. Therefore the bootloader must be compiled for that specific architecture.

+

{{Note|On some UEFI systems the only possible way to launch UEFI application on boot (if it doesn't have custom entry in UEFI boot menu) is to put it in this fixed location: {{ic|<EFI SYSTEM PARTITION>/EFI/boot/bootx64.efi}} (for 64-bit x86 system)}}

−

=== Multibooting on UEFI ===

+

== Multibooting in UEFI ==

−

Since each OS or vendor can maintain its own files within the EFI SYSTEM PARTITION without affecting the other, multi-booting using UEFI is just a matter of launching a different UEFI application corresponding to the particular OS's bootloader. This removes the need for relying on chainloading mechanisms of one bootloader to load another to switch OSes.

+

Since each OS or vendor can maintain its own files within the EFI System Partition without affecting the other, multi-booting using UEFI is just a matter of launching a different UEFI application corresponding to the particular OS's bootloader. This removes the need for relying on chainloading mechanisms of one bootloader to load another to switch OSes.

−

==== Multibooting Windows and Linux ====

+

=== Booting Microsoft Windows ===

−

64-bit Windows Vista (SP1+), Windows 7 and Windows 8 versions support booting using UEFI firmware. These Windows versions support either UEFI-GPT booting or BIOS-MBR booting. 32-bit Windows versions only support BIOS-MBR booting. See http://support.microsoft.com/kb/2581408 for more info.

+

64-bit Windows Vista (SP1+), Windows 7 and Windows 8 versions support booting using x86_64 EFI firmware. Windows forces type of partitioning depending on the firmware used, i.e. if Windows is booted in UEFI mode, it can be installed only to a GPT disk. If the Windows is booted in Legacy BIOS mode, it can be installed only to a MBR disk. This is a limitation enforced by Windows installer. Thus Windows supports either UEFI-GPT boot or BIOS-MBR boot only, not UEFI-MBR or BIOS-GPT boot.

−

This limitation does not exist in Linux Kernel but rather depends on the bootloader used. For the sake of Windows UEFI booting, the Linux bootloader used should also be installed in UEFI-GPT mode if booting from the same disk.

+

This limitation is not enforced by Linux kernel itself, but rather depends on how the bootloader is configured. However this Windows limitation should be considered if the user wishes to boot Windows and Linux from the same disk, since setting up the bootloader itself depends on the firmware type and disk partitioning used. In case of Windows and Linux dual boot in the same disk, it is advisable to follow the method used by Windows, either go for UEFI-GPT boot or BIOS-MBR boot only, not the other two cases.

32-bit Windows versions only support BIOS-MBR booting. So, in case of Linux and 32-bit Windows booting from the same disk, the disk can use only MBR. See http://support.microsoft.com/kb/2581408 for more info.

−

== Boot Process under UEFI ==

+

== Detecting UEFI Firmware bitness ==

−

# System switched on - Power On Self Test, or POST process.

+

=== Non Macs ===

−

# UEFI firmware is loaded.

−

# Firmware reads its Boot Manager to determine which UEFI application to be launched and from where (ie. from which disk and partition).

−

# Firmware launches the UEFI application from the FAT32 formatted UEFISYS partition as defined in the boot entry in the firmware's boot manager.

−

# UEFI application may launch another application (in case of UEFI Shell or a boot manager like rEFInd) or the kernel and initramfs (in case of a bootloader like GRUB) depending on how the UEFI application was configured.

−

== Detecting UEFI Firmware Arch ==

+

Check whether the dir {{ic|/sys/firmware/efi}} exists, if it exists it means the kernel has booted in EFI mode. In that case the UEFI bitness is same as kernel bitness. (ie. i686 or x86_64)

−

If you have a non-Mac UEFI system, then you most likely have a x86_64 (aka 64-bit) UEFI 2.x firmware. A few known x86_64 UEFI 2.x firmwares are Phoenix SecureCore Tiano, AMI Aptio and Insyde H2O.

To find out the arch of the efi firmware in a Mac, type the following into the terminal:

+

To find out the arch of the efi firmware in a Mac, type the following into the Mac OS X terminal:

+

ioreg -l -p IODeviceTree | grep firmware-abi

ioreg -l -p IODeviceTree | grep firmware-abi

−

If the command returns EFI32 then it is i386 EFI 1.x firmware. If it returns EFI64 then it is x86_64 EFI 1.x firmware. Macs do not have UEFI 2.x firmware as Apple's EFI implementation is not fully compliant with UEFI Specification.

−

== UEFI Support in Linux Kernel ==

+

If the command returns EFI32 then it is IA32 (32-bit) EFI firmware. If it returns EFI64 then it is x86_64 EFI firmware. Most of the Macs do not have UEFI 2.x firmware as Apple's EFI implementation is not fully compliant with UEFI 2.x Specification.

+

+

== UEFI Variables ==

+

+

UEFI defines variables through which an operating system can interact with the firmware. UEFI Boot Variables are used by the boot-loader and used by the OS only for early system start-up. UEFI Runtime Variables allow an OS to manage certain settings of the firmware like the UEFI Boot Manager or managing the keys for UEFI Secure Boot Protocol etc.

UEFI Runtime Variables Support (efivarfs filesystem - {{ic|/sys/firmware/efi/efivars}}). This option is important as this is required to manipulate UEFI Runtime Variables using tools like {{ic|/usr/bin/gummiboot}}. '''Efivarfs''' is recommended over '''efivars sysfs''' interface (described below). The below config option has been added in kernel 3.10 and above.

+

UEFI Runtime Variables Support ('''efivarfs''' filesystem - {{ic|/sys/firmware/efi/efivars}}). This option is important as this is required to manipulate UEFI Runtime Variables using tools like {{ic|/usr/bin/efibootmgr}}. The below config option has been added in kernel 3.10 and above.

CONFIG_EFIVAR_FS=y

CONFIG_EFIVAR_FS=y

−

UEFI Runtime Variables Support ('''efivars sysfs''' interface - {{ic|/sys/firmware/efi/vars}}). This option is important as this is required to manipulate UEFI Runtime Variables using tools like {{ic|efibootmgr}}.

+

UEFI Runtime Variables Support ('''efivars sysfs''' interface - {{ic|/sys/firmware/efi/vars}}). This option should be disabled if all the userspace tools support '''efivarfs'''.

−

−

CONFIG_EFI_VARS=m

−

CONFIG_EFI_VARS_PSTORE=m

−

CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE=y

−

−

{{Note|For Linux to access UEFI Runtime Services, the UEFI Firmware processor architecture and the Linux kernel processor architecture must match. This is independent of the bootloader used.}}

−

{{Note|If the UEFI Firmware arch and Linux Kernel arch are different, then the "'''noefi'''" kernel parameter must be used to avoid the kernel panic and boot successfully. The "noefi" option instructs the kernel not to access the UEFI Runtime Services.}}

# efivarfs (efivarfs kernel module, /sys/firmware/efi/efivars) that was designed to overcome the limitations of sysfs-efivars interface

+

# Old sysfs-efivars interface (efivars kernel module, /sys/firmware/efi/vars) which has been disabled in from linux-3.11 (in Arch pkg)

−

UEFI defines variables through which an operating system can interact with the firmware. UEFI Boot Variables are used by the boot-loader and used by the OS only for early system start-up. UEFI Runtime Variables allow an OS to manage certain settings of the firmware like the UEFI Boot Manager or managing the keys for UEFI Secure Boot Protocol etc.

+

efivarfs was introduced in kernel 3.8 and most of its bugs were ironed out in kernel 3.10 .

−

{{Note|The below steps will not work if the system has been booted in BIOS mode and will not work if the UEFI processor architecture does not match the kernel one, i.e. x86_64 UEFI + x86 32-bit Kernel and vice-versa config will not work. This is true only for efivars kernel module and efibootmgr step. The other steps (ie. upto setting up <UEFISYS>/EFI/arch/refind/{refindx64.efi,refind.conf} ) can be done even in BIOS/Legacy boot mode.}}

+

Running both sysfs-efivars and efivarfs can create inconsistencies in EFI variables data in the kernel and is discouraged. Going forward efivarfs is the recommended way for tools to interact with kernel reg EFI variables. All the uefi variables related tools in official repos support '''efivarfs''' as of 18-September-2013.

−

Access to UEFI Runtime services is provided by "efivars" kernel module which is enabled through the {{ic|<nowiki>CONFIG_EFI_VARS=y</nowiki>}} kernel config option. This module exposes the variables under the directory {{ic|/sys/firmware/efi/vars}} (for kernels >=3.8 through {{ic|/sys/firmware/efi/efivars}}). One way to check whether the system has booted in UEFI boot mode is to check for the existence of {{ic|/sys/firmware/efi/vars}} (and in kernels >=3.8 for {{ic|/sys/firmware/efi/efivars}})directory with contents similar to :

# Kernel should be booted in EFI mode (via EFISTUB or any EFI bootloader, not via BIOS/CSM or Apple's "bootcamp" which is also BIOS/CSM)

−

AcpiGlobalVariable-af9ffd67-ec10-488a-9dfc-6cbf5ee22c2e

+

# EFI Runtime Services in the kernel SHOULD NOT be disabled via kernel cmdline, i.e. "noefi" kernel parameter SHOULD NOT be used.

−

BGRTLogoIndex-9da5909e-ef5e-4851-8715-bf9e22b7a600

+

# If any userspace tool is unable to modify efi variables data, check for existence of {{ic|/sys/firmware/efi/efivars/dump-*}} files. If they exist, delete them, reboot and retry again.

−

BmEssentialVariableNames-0b7646a4-6b44-4332-8588-c8998117f2ef

+

# If the above step does not fix the issue, try booting with{{ic|efi_no_storage_paranoia}} kernel parameter to disable kernel efi variable storage space check that may prevent writing/modification of efi variables.

−

Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0002-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0005-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0006-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0007-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0008-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0009-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot000A-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot000B-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot000C-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot000D-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot000E-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot000F-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0010-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0011-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0012-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0013-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0014-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0015-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0016-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0017-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Boot0018-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

BootOrderDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

BuildDate-e5bbf7be-2417-499b-97db-39f4896391bc

−

BuildTime-e5bbf7be-2417-499b-97db-39f4896391bc

−

ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

CpuProtocolSetupVar-7d4adce1-930d-40c7-9cd2-6d2148413dc7

−

db-d719b2cb-3d3a-4596-a3bc-dad00e67656f

−

dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f

−

DIAGSPLSHSCRN-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

DptfProtocolSetupVar-1054354b-b543-4dfe-558b-a7ad6351c9d8

−

ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

FirmwarePerformanceDataTable-9dab39a4-3f8a-47ac-80c3-400729332c81

−

HDDPWD-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

iFfsData-f9f0b131-f346-4f16-80dd-f941072b3a7d

−

KEK-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Key0000-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Key0001-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Key0002-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Key0003-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Key0004-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Key0005-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

Key0006-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

LastBootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

LBC-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBL-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOL-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0001-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0002-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0003-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0004-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0005-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0006-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0007-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0008-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0009-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP000A-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP000B-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP000C-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP000D-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP000E-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP000F-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0010-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0011-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0012-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0013-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0014-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0015-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0016-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0017-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LBOP0018-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LenovoConfig-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LenovoFlashScratch1-67c3208e-4fcb-498f-9729-0760bb4109a7

−

LenovoHiddenSetting-1827cfc7-4e61-4273-b796-d35f4b0c88fc

−

LenovoScratchData-67c3208e-4fcb-498f-9729-0760bb4109a7

−

LenovoSecurityConfig-a2c1808f-0d4f-4cc9-a619-d1e641d39d49

−

LenovoSystemConfig-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LKOP0000-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LKOP0001-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LKOP0002-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LKOP0003-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LKOP0004-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LKOP0005-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LKOP0006-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

LoaderDeviceIdentifier-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LoaderDevicePartUUID-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LoaderEntriesAuto-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LoaderEntrySelected-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LoaderFirmwareInfo-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LoaderFirmwareType-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LoaderImageIdentifier-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LoaderInfo-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LoaderTimeExecUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LoaderTimeInitUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LoaderTimeMenuUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f

−

LocalSecurityVars-47355e9f-0857-45e1-8a6f-a4f5eda89a77

−

LWO-2a4dc6b7-41f5-45dd-b46f-2dd334c1cf65

−

MailBoxQ-67c3208e-4fcb-498f-9729-0760bb4109a7

−

MeBiosExtensionSetup-1bad711c-d451-4241-b1f3-8537812e0c70

−

MemoryTypeInformation-4c19049f-4137-4dd3-9c10-8b97a83ffdfa

−

MemoryTypeInformationBackup-4c19049f-4137-4dd3-9c10-8b97a83ffdfa

−

MemRestoreVariable-608dc793-15de-4a7f-a0c5-6c29beaf5d23

−

MTC-eb704011-1402-11d3-8e77-00a0c969723b

−

OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

PbaStatusVar-0ec1a7f5-4904-40a0-8eab-4bcc4666da45

−

PchInit-e6c2f70a-b604-4877-85ba-deec89e117eb

−

PchS3Peim-e6c2f70a-b604-4877-85ba-deec89e117eb

−

PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

PlatformOpRomSetup-65827a61-99e2-4f07-a7aa-0b1f98edad39

−

ProtectedBootOptions-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

PwdStatusVar-3e72b3ad-2b91-424a-ad73-c3270e91ed88

−

SaPegData-c4975200-64f1-4fb6-9773-f6a9f89d985e

−

SaPpiSetupVar-7da81437-866b-4143-8e08-a25c6ef0fa5b

−

SaProtocolSetupVar-34f73d4d-963e-4c65-b3b3-515e720175d6

−

SctHotkey-4650c401-93f1-4aeb-b87d-c8204c047dec

−

SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

SecureBootOption-955b9041-133a-4bcf-90d1-97e1693c0e30

−

Setup-4dfbbaab-1392-4fde-abb8-c41cc5ad7d5d

−

SetupHotKey-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

SimpleBootFlag-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

SMBIOSELOG000-c3eeae98-23bf-412b-ab60-efcbb48e1534

−

SMBIOSELOGNUMBER-c3eeae98-23bf-412b-ab60-efcbb48e1534

−

SMBIOSMEMSIZE-c3eeae98-23bf-412b-ab60-efcbb48e1534

−

TcgSetup-753ab903-444c-41f8-a235-569e8341147e

−

Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8c

−

TpmAcpiData-6403753b-abde-4da2-aa11-6983ef2a7a69

−

TpmSaveState-5e724c0c-5c03-4543-bcb6-c1e23de24136

−

The UEFI Runtime Variables will not be exposed to the OS if you have used "noefi" kernel parameter in the boot-loader menu. This parameter instructs the kernel to completely ignore UEFI Runtime Services.

+

{{Note|{{ic|efi_no_storage_paranoia}} should only be used when needed and should not be left as a normal boot option. The effect of this kernel command line parameter turns off a safeguard that was put in place to help avoid the bricking of machines when the NVRAM gets too full.}}

−

=== Userspace Tools ===

+

=== Inconsistency between efivarfs and sysfs-efivars ===

−

There are few tools that can access/modify the UEFI variables, namely

+

Both sysfs-efivars and efivarfs can run simultaneously, but this can cause inconsistency between sysfs-efivars data and efivarfs data, especially if data in both are simultaneously modified. See https://lkml.org/lkml/2013/4/16/473 for more info. Therefore it is advisable to use enable only one interface at a time and disable the other one.

{{Note|From core/linux-3.11 onwards efivars and efi_pstore modules are no longer compiled (this change in only in Arch kernel, upstream has not removed sysfs-efivars code). Only efivarfs is supported from core/linux-3.11 onwards in Arch.}}

{{Note|The below commands should be run BEFORE '''chroot''', if any.}}

−

{{Warning|Using {{ic|efibootmgr}} in Apple Macs will brick the firmware and may need reflash of the motherboard ROM. There have been bug reports regarding this in Ubuntu/Launchpad bug tracker. Use bless command alone in case of Macs. Experimental "bless" utility for Linux by Fedora developers - {{AUR|mactel-boot}}.}}

+

# umount /sys/firmware/efi/efivars

+

# modprobe -r efivars

−

{{Note|{{ic|efibootmgr}} command will work only if you have booted the system in UEFI mode itself, since it '''requires access to UEFI Runtime Variables''' which are '''available only in UEFI boot mode''' (with "noefi" kernel parameter NOT being used). Otherwise the message {{ic|Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables}} is shown.}}

+

# modprobe efivarfs

+

# mount -t efivarfs efivarfs /sys/firmware/efi/efivars

−

{{Note| If you are unable to use {{ic|efibootmgr}}, some UEFI BIOSes allow users to directly manage uefi boot options from within the BIOS. For example, some ASUS BIOSes have a "Add New Boot Option" choice which enables you to select a local EFI system partition and manually enter the EFI stub location. (for example '\EFI\refind\refind_x64.efi')}}

{{Note|If {{ic|efibootmgr}} fails to create the boot entry, check for existence of {{ic|/sys/firmware/efi/efivars/dump-*}} files, if they exist, delete them, reboot and retry {{ic|efibootmgr}} again. If even this fails, retry {{ic|efibootmgr}} after booting with {{ic|efi_no_storage_paranoia}} kernel parameter.}}

+

Verify by running {{ic|efivars -l}}. If efivar fails to list the uefi variables, check whether all the conditions in [[#Requirements_for_UEFI_Variables_support_to_work_properly]] are met.

−

{{Note|If {{ic|efibootmgr}} completely fails to work in your system, you can reboot into UEFI Shell v2 and use {{ic|bcfg}} command to create a boot entry for the bootloader.}}

+

==== Switch to sysfs-efivars ====

−

Initially the user may be required to manually launch the boot-loader from the firmware itself (using maybe the UEFI Shell) if the UEFI boot-loader was installed when the system is booted in BIOS mode. Then {{ic|efibootmgr}} should be run to make the UEFI boot-loader entry as the default entry in the UEFI Boot Manager.

+

{{Note|The below commands should be run BEFORE '''chroot''', if any.}}

−

To use efibootmgr, first load the 'efivars' kernel module (if compiled as a external module):

+

# umount /sys/firmware/efi/efivars

+

# modprobe -r efivars

# modprobe efivars

# modprobe efivars

−

If you get '''no such device found''' error for this command, that means you have not booted in UEFI mode or due to some reason the kernel is unable to access UEFI Runtime Variables (noefi?).

+

Verify by running {{ic|efivars -l}}. If efivar fails to list the uefi variables, check whether all the conditions in [[#Requirements_for_UEFI_Variables_support_to_work_properly]] are met.

−

Verify whether there are files in ''/sys/firmware/efi/vars/'' (and ''/sys/firmware/efi/efivars/'' for kernel >=3.8) directory. This directory and its contents are created by "efivars" kernel module and it will exist only if you have booted in UEFI mode, without the "noefi" kernel parameter.

+

= Userspace Tools =

−

If ''/sys/firmware/efi/vars/'' directory is empty or does not exist, then {{ic|efibootmgr}} command will not work. If you are unable to make the ISO/CD/DVD/USB boot in UEFI mode try [[#Create_UEFI_bootable_USB_from_ISO]].

+

There are few tools that can access/modify the UEFI variables, namely

−

{{Note| The below commands use {{Pkg|refind-efi}} boot-loader as example.}}

# '''efibootmgr''' - Tool to manipulate UEFI Firmware Boot Manager Settings. Upstream (linuxdell)efibootmgr code does not support efivarfs. A fork of efibootmgr by Fedora's Peter Jones (vathpela) supports both efivarfs and sysfs-efivars. It is currently used in official core/{{Pkg|efibootmgr}} pkg and AUR pkg {{AUR|efibootmgr-pjones-git}} - https://github.com/vathpela/efibootmgr/tree/libefivars

Assume the boot-loader file to be launched is {{ic|/boot/efi/EFI/refind/refind_x64.efi}}. {{ic|/boot/efi/EFI/refind/refind_x64.efi}} can be split up as {{ic|/boot/efi}} and {{ic|/EFI/refind/refind_x64.efi}}, wherein {{ic|/boot/efi}} is the mountpoint of the EFI System Partition, which is assumed to be {{ic|/dev/sdXY}} (here X and Y are just placeholders for the actual values - eg:- in {{ic|/dev/sda1}} , X=a Y=1).

+

=== efibootmgr ===

−

To determine the actual device path for the UEFI System Partition (should be in the form {{ic|/dev/sdXY}}), try :

+

{{Warning|Using {{ic|efibootmgr}} in Apple Macs may brick the firmware and may need reflash of the motherboard ROM. There have been bug reports regarding this in Ubuntu/Launchpad bug tracker. Use bless command alone in case of Macs. Experimental "bless" utility for Linux by Fedora developers - {{AUR|mactel-boot}}.}}

+

+

{{Note|If {{ic|efibootmgr}} completely fails to work in your system, you can reboot into UEFI Shell v2 and use {{ic|bcfg}} command to create a boot entry for the bootloader.}}

+

+

{{Note| If you are unable to use {{ic|efibootmgr}}, some UEFI BIOSes allow users to directly manage uefi boot options from within the BIOS. For example, some ASUS BIOSes have a "Add New Boot Option" choice which enables you to select a local EFI System Partition and manually enter the EFI stub location. (for example '\EFI\refind\refind_x64.efi')}}

{{Note|Upstream efibootmgr http://linux.dell.com/git/efibootmgr.git does not support efivarfs. However vathpela's efibootmgr supports efivarfs and is currently used in official efibootmgr pkg. sysfs-efivars is also completely disabled in official Arch kernel and it supports only efivarfs. This section is written with the assumtion that you are using only efivarfs and vathpela's efibootmgr.}}

+

+

Assuming the boot-loader file to be launched is {{ic|/boot/efi/EFI/refind/refind_x64.efi}}, {{ic|/boot/efi/EFI/refind/refind_x64.efi}} can be split up as {{ic|/boot/efi}} and {{ic|/EFI/refind/refind_x64.efi}}, wherein {{ic|/boot/efi}} is the mountpoint of the EFI System Partition, which is assumed to be {{ic|/dev/sdXY}} (here X and Y are just placeholders for the actual values - eg:- in {{ic|/dev/sda1}} , X==a Y==1).

+

+

To determine the actual device path for the EFI System Partition (assuming mountpoint {{ic|/boot/efi}} for example) (should be in the form {{ic|/dev/sdXY}}), try :

# findmnt /boot/efi

# findmnt /boot/efi

TARGET SOURCE FSTYPE OPTIONS

TARGET SOURCE FSTYPE OPTIONS

/boot/efi /dev/sdXY vfat rw,flush,tz=UTC

/boot/efi /dev/sdXY vfat rw,flush,tz=UTC

+

+

Verify that uefi variables support in kernel is working properly by running:

+

+

# efivar -l

+

+

If efivar lists the uefi variables without any error, then you can proceed. If not, check whether all the conditions in [[#Requirements_for_UEFI_Variables_support_to_work_properly]] are met.

{{Note|1=UEFI uses backward slash {{ic|\}} as path separator (similar to Windows paths), but the {{Pkg|efibootmgr}}-0.6.0-3 and above pkgs support passing unix-style paths with forward-slash {{ic|/}} as path-separator for the {{ic|-l}} option. Efibootmgr internally converts {{ic|/}} to {{ic|\}} before encoding the loader path. The relevant commit that added this feature to efibootmgr is http://linux.dell.com/cgi-bin/cgit.cgi/efibootmgr.git/commit/?id=f38f4aaad1dfa677918e417c9faa6e3286411378 .}}

+

{{Note|1=UEFI uses backward slash {{ic|\}} as path separator (similar to Windows paths), but the official {{Pkg|efibootmgr}} pkg support passing unix-style paths with forward-slash {{ic|/}} as path-separator for the {{ic|-l}} option. Efibootmgr internally converts {{ic|/}} to {{ic|\}} before encoding the loader path. The relevant git commit that incorporated this feature in efibootmgr is http://linux.dell.com/cgi-bin/cgit.cgi/efibootmgr.git/commit/?id=f38f4aaad1dfa677918e417c9faa6e3286411378 .}}

In the above command {{ic|/boot/efi/EFI/refind/refind_x64.efi}} translates to {{ic|/boot/efi}} and {{ic|/EFI/refind/refind_x64.efi}} which in turn translate to drive {{ic|/dev/sdX}} -> partition {{ic|Y}} -> file {{ic|/EFI/refind/refind_x64.efi}}.

In the above command {{ic|/boot/efi/EFI/refind/refind_x64.efi}} translates to {{ic|/boot/efi}} and {{ic|/EFI/refind/refind_x64.efi}} which in turn translate to drive {{ic|/dev/sdX}} -> partition {{ic|Y}} -> file {{ic|/EFI/refind/refind_x64.efi}}.

Line 324:

Line 373:

FAT32 filesystem is case-insensitive since it does not use UTF-8 encoding by default. In that case the firmware uses capital 'EFI' instead of small 'efi', therefore using {{ic|\EFI\refind\refindx64.efi}} or {{ic|\efi\refind\refind_x64.efi}} does not matter (this will change if the filesystem encoding is UTF-8).

FAT32 filesystem is case-insensitive since it does not use UTF-8 encoding by default. In that case the firmware uses capital 'EFI' instead of small 'efi', therefore using {{ic|\EFI\refind\refindx64.efi}} or {{ic|\efi\refind\refind_x64.efi}} does not matter (this will change if the filesystem encoding is UTF-8).

−

== Linux Bootloaders for UEFI ==

+

= UEFI Bootloaders =

−

−

See [[UEFI Bootloaders]].

−

== EFI System Partition ==

+

See [[UEFI Bootloaders]] for the main article.

−

{{Note|UEFI System Partition and EFI System Partition (ESP) are same, the terminologies are used interchangeably in some places.}}

+

= EFI System Partition =

{{Note|The ESP should be accessible by the UEFI firmware, which cannot read LVM and software RAID systems.}}

{{Note|The ESP should be accessible by the UEFI firmware, which cannot read LVM and software RAID systems.}}

−

{{Note|Setting "boot" flag in parted in a MBR partition marks that partition as active, while the same "boot" flag in a GPT partition marks that partition as "UEFI System Partition".}}

+

{{Note|Setting "boot" flag in parted in a MBR partition marks that partition as active, while the same "boot" flag in a GPT partition marks that partition as "EFI System Partition".}}

The EFI System Partition needs to be formatted with a FAT32 filesystem (non-FAT filesystems like ext2/3/4, reiserfs, NTFS, UDF etc. are not supported). Although ESPs with size >=100 MiB and formatted as FAT32 are allowed by Microsoft Windows and many Linux distros, Microsoft documentation specifies that the minimum partition/volume size for FAT32 is 512 MiB. Therefore an ESP should be at least 512 MiB size for maximum compatibility. If you are using Linux EFISTUB booting, then you need to make sure there is adequate space available for keeping the Kernel and Initramfs files in the ESP.

The EFI System Partition needs to be formatted with a FAT32 filesystem (non-FAT filesystems like ext2/3/4, reiserfs, NTFS, UDF etc. are not supported). Although ESPs with size >=100 MiB and formatted as FAT32 are allowed by Microsoft Windows and many Linux distros, Microsoft documentation specifies that the minimum partition/volume size for FAT32 is 512 MiB. Therefore an ESP should be at least 512 MiB size for maximum compatibility. If you are using Linux EFISTUB booting, then you need to make sure there is adequate space available for keeping the Kernel and Initramfs files in the ESP.

Line 340:

Line 387:

It is recommended to use always GPT for UEFI boot as some UEFI firmwares do not allow UEFI-MBR boot.

It is recommended to use always GPT for UEFI boot as some UEFI firmwares do not allow UEFI-MBR boot.

−

=== For GPT partitioned disks ===

+

== GPT partitioned disks ==

+

Two choices:

Two choices:

+

* Using GNU Parted/GParted: Create a FAT32 partition. Set "boot" flag on for that partition.

* Using GNU Parted/GParted: Create a FAT32 partition. Set "boot" flag on for that partition.

* Using GPT fdisk (aka gdisk): Create a partition with partition type {{ic|ef00}}. Then format that partition as FAT32 using {{ic|mkfs.vfat -F32 /dev/<THAT_PARTITION>}}

* Using GPT fdisk (aka gdisk): Create a partition with partition type {{ic|ef00}}. Then format that partition as FAT32 using {{ic|mkfs.vfat -F32 /dev/<THAT_PARTITION>}}

−

=== For MBR partitioned disks ===

+

If you get the message <code>WARNING: Not enough clusters for a 32 bit FAT!</code>, reduce cluster size with <code>mkfs.vfat -s2 -F32 ...</code> or <code>-s1</code>, otherwise the partition may be unreadable by UEFI.

+

+

== MBR partitioned disks ==

+

Two choices:

Two choices:

+

* Using GNU Parted/GParted: Create FAT32 partition. Change the type code of that partition to {{ic|0xEF}} using fdisk, cfdisk or sfdisk.

* Using GNU Parted/GParted: Create FAT32 partition. Change the type code of that partition to {{ic|0xEF}} using fdisk, cfdisk or sfdisk.

* Using fdisk: Create a partition with partition type {{ic|0xEF}}. Then format that partition as FAT32 using {{ic|mkfs.vfat -F32 /dev/<THAT_PARTITION>}}

* Using fdisk: Create a partition with partition type {{ic|0xEF}}. Then format that partition as FAT32 using {{ic|mkfs.vfat -F32 /dev/<THAT_PARTITION>}}

−

== UEFI Shell ==

+

= UEFI Shell =

−

The UEFI Shell is a shell/terminal for the firmware which allows launching uefi applications which include uefi bootloaders. Apart from that, the shell can also be used to obtain various other information about the system or the firmware like memory map (memmap), modifying boot manager variables (bcfg), running partitioning programs (diskpart), loading uefi drivers, editing text files (edit), hexedit etc.

+

The UEFI Shell is a shell/terminal for the firmware which allows launching uefi applications which include uefi bootloaders. Apart from that, the shell can also be used to obtain various other information about the system or the firmware like memory map (memmap), modifyiang boot manager variables (bcfg), running partitioning programs (diskpart), loading uefi drivers, editing text files (edit), hexedit etc.

Shell 2.0 works only in UEFI 2.3+ systems and is recommended over Shell 1.0 in those systems. Shell 1.0 should work in all UEFI systems irrespective of the spec. version the firmware follows. More info at [http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=ShellPkg ShellPkg] and [http://sourceforge.net/mailarchive/message.php?msg_id=28690732 this mail]

+

Shell v2 works best in UEFI 2.3+ systems and is recommended over Shell v1 in those systems. Shell v1 should work in all UEFI systems irrespective of the spec. version the firmware follows. More info at [http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=ShellPkg ShellPkg] and [http://sourceforge.net/mailarchive/message.php?msg_id=28690732 this mail]

−

=== Launching UEFI Shell ===

+

== Launching UEFI Shell ==

−

Few Asus and other AMI Aptio x86_64 UEFI firmware based motherboards (from Sandy Bridge onwards) provide an option called {{ic|"Launch EFI Shell from filesystem device"}} . For those motherboards, download the x86_64 UEFI Shell and copy it to your UEFI SYSTEM PARTITION as {{ic|<UEFI_SYSTEM_PARTITION>/shellx64.efi}} (mostly {{ic|/boot/efi/shellx64.efi}}) .

+

Few Asus and other AMI Aptio x86_64 UEFI firmware based motherboards (from Sandy Bridge onwards) provide an option called {{ic|"Launch EFI Shell from filesystem device"}} . For those motherboards, download the x86_64 UEFI Shell and copy it to your EFI System Partition as {{ic|<EFI_SYSTEM_PARTITION>/shellx64.efi}} (mostly {{ic|/boot/efi/shellx64.efi}}) .

Systems with Phoenix SecureCore Tiano UEFI firmware are known to have embedded UEFI Shell which can be launched using either F6, F11 or F12 key.

Systems with Phoenix SecureCore Tiano UEFI firmware are known to have embedded UEFI Shell which can be launched using either F6, F11 or F12 key.

Line 373:

Line 427:

{{Note|If you are unable to launch UEFI Shell from the firmware directly using any of the above mentioned methods, create a FAT32 USB pen drive with Shell.efi copied as (USB)/efi/boot/bootx64.efi . This USB should come up in the firmware boot menu. Launching this option will launch the UEFI Shell for you.}}

{{Note|If you are unable to launch UEFI Shell from the firmware directly using any of the above mentioned methods, create a FAT32 USB pen drive with Shell.efi copied as (USB)/efi/boot/bootx64.efi . This USB should come up in the firmware boot menu. Launching this option will launch the UEFI Shell for you.}}

More info at http://software.intel.com/en-us/articles/efi-shells-and-scripting/

More info at http://software.intel.com/en-us/articles/efi-shells-and-scripting/

−

==== bcfg ====

+

=== bcfg ===

BCFG command is used to modify the UEFI NVRAM entries, which allow the user to change the boot entries or driver options. This command is described in detail in page 83 (Section 5.3) of "UEFI Shell Specification 2.0" pdf document.

BCFG command is used to modify the UEFI NVRAM entries, which allow the user to change the boot entries or driver options. This command is described in detail in page 83 (Section 5.3) of "UEFI Shell Specification 2.0" pdf document.

Line 395:

Line 449:

Shell> bcfg boot add 3 fs0:\EFI\refind\refind_x64.efi "rEFInd"

Shell> bcfg boot add 3 fs0:\EFI\refind\refind_x64.efi "rEFInd"

−

where fs0: is the mapping corresponding to the UEFI System Partition and fs0:\EFI\refind\refind_x64.efi is the file to be launched.

+

where fs0: is the mapping corresponding to the EFI System Partition and fs0:\EFI\refind\refind_x64.efi is the file to be launched.

To remove the 4th boot option

To remove the 4th boot option

Line 413:

Line 467:

Shell> bcfg -? -v -b

Shell> bcfg -? -v -b

−

==== edit ====

+

=== edit ===

EDIT command provides a basic text editor with an interface similar to nano text editor, but slightly less functional. It handles UTF-8 encoding and takes care or LF vs CRLF line endings.

EDIT command provides a basic text editor with an interface similar to nano text editor, but slightly less functional. It handles UTF-8 encoding and takes care or LF vs CRLF line endings.

−

To edit, for example rEFInd's refind.conf in the UEFI System Partition (fs0: in the firmware)

+

To edit, for example rEFInd's refind.conf in the EFI System Partition (fs0: in the firmware)

Shell> fs0:

Shell> fs0:

Line 425:

Line 479:

Type {{ic|Ctrl-E}} for help.

Type {{ic|Ctrl-E}} for help.

−

== Hardware Compatibility ==

+

= UEFI Linux Hardware Compatibility =

−

Main page [[HCL/Firmwares/UEFI]]

+

See [[HCL/Firmwares/UEFI]] for the main article.

+

+

= UEFI Bootable Media =

== Create UEFI bootable USB from ISO ==

== Create UEFI bootable USB from ISO ==

Line 442:

Line 498:

* Then create a FAT32 filesystem in the partition on the USB (unmount before if necessary) with LABEL as used in the Archiso configuration. Obtain the label from {{ic|/mnt/iso/loader/entries/archiso-x86_64.conf}}; this is used by the {{ic|archiso}} hook in initramfs to identify the udev path to the installation media. {{ic|mkfs.vfat}} is part of package {{Pkg|dosfstools}}. {{Note|The filesystem should be either FAT32 (recommended), FAT16, or FAT12.}}

* Then create a FAT32 filesystem in the partition on the USB (unmount before if necessary) with LABEL as used in the Archiso configuration. Obtain the label from {{ic|/mnt/iso/loader/entries/archiso-x86_64.conf}}; this is used by the {{ic|archiso}} hook in initramfs to identify the udev path to the installation media. {{ic|mkfs.vfat}} is part of package {{Pkg|dosfstools}}. {{Note|The filesystem should be either FAT32 (recommended), FAT16, or FAT12.}}

* Mount the newly created FAT32 USB partition, and copy the contents of the installation media to the USB media.

* Mount the newly created FAT32 USB partition, and copy the contents of the installation media to the USB media.

Line 450:

Line 506:

# sync

# sync

# umount /mnt/{usb,iso}

# umount /mnt/{usb,iso}

−

−

=== Fixing errors ===

−

−

If you find the error: ''"No loader found. Configuration files in /loader/entries/*.conf are needed."'' First, try to convert filenames in /loader/entries/ to lower case. A possible fix is to use a different uefi bootloader to the included one, gummiboot.

−

−

Download [https://www.archlinux.org/packages/extra/any/refind-efi/download/ refind-efi pkg] and extract the file {{ic|/usr/lib/refind/refind_x64.efi}} from within the package to {{ic|(USB)/EFI/boot/bootx64.efi}} (overwrite or rename any existing {{ic|(USB)/EFI/boot/bootx64.efi}} file).

−

−

Then copy this text to {{ic|EFI/boot/refind.conf}}. Take care that the label in the Arch menu section ({{ic|ARCH_201304}} here) matches that of your usb's.

−

−

{{hc|refind.conf|<nowiki>

−

timeout 5

−

textonly

−

−

showtools about,reboot,shutdown,exit

−

# scan_driver_dirs EFI/tools/drivers_x64

−

scanfor manual,internal,external,optical

−

−

scan_delay 1

−

dont_scan_dirs EFI/boot

−

−

max_tags 0

−

default_selection "Arch Linux Archiso x86_64 UEFI USB"

−

−

menuentry "Arch Linux Archiso x86_64 UEFI USB" {

−

loader /arch/boot/x86_64/vmlinuz

−

initrd /arch/boot/x86_64/archiso.img

−

ostype Linux

−

graphics off

−

options "archisobasedir=arch archisolabel=ARCH_201304 add_efi_memmap"

−

}

−

−

menuentry "UEFI x86_64 Shell v2" {

−

loader /EFI/shellx64_v2.efi

−

graphics off

−

}

−

−

menuentry "UEFI x86_64 Shell v1" {

−

loader /EFI/shellx64_v1.efi

−

graphics off

−

}

−

</nowiki>}}

−

−

You should now be able to successfully boot, and you can choose which EFI you'd like to load.

== Remove UEFI boot support from ISO ==

== Remove UEFI boot support from ISO ==

Line 519:

Line 532:

Burn {{ic|~/archiso.iso}} to optical media and proceed with installation normally.

Burn {{ic|~/archiso.iso}} to optical media and proceed with installation normally.

−

== QEMU with OVMF ==

+

= Testing UEFI in systems without native support =

−

OVMF [http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=OVMF] is a project to enable UEFI support for Virtual Machines. OVMF contains a sample UEFI firmware for QEMU and KVM.

+

== OVMF for Virtual Machines ==

−

You can build OVMF from AUR {{Aur|ovmf-svn}} and use it like this:

+

OVMF [http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=OVMF] is a tianocore project to enable UEFI support for Virtual Machines. OVMF contains a sample UEFI firmware for QEMU.

−

qemu-system-x86_64 -bios /usr/share/ovmf/bios.bin ...

+

You can build OVMF (with Secure Boot support) from AUR {{AUR|ovmf-svn}} and run it as follows:

−

For OVMF with Secure Boot support, use the PKGBUILD from https://bitbucket.org/the_ridikulus_rat/ovmf-tianocore-edk2-pkgbuild/src to build it and run it as follows:

DUET is a tianocore project that enables chainloading a full UEFI environment from a BIOS system, in a way similar to BIOS OS booting. This method is being discussed extensively in http://www.insanelymac.com/forum/topic/186440-linux-and-windows-uefi-boot-using-tianocore-duet-firmware/ . Pre-build DUET images can be downloaded from one of the repos at https://gitorious.org/tianocore_uefi_duet_builds . Specific instructions for setting up DUET is available at https://gitorious.org/tianocore_uefi_duet_builds/tianocore_uefi_duet_installer/blobs/raw/master/Migle_BootDuet_INSTALL.txt .

+

+

You can also try http://sourceforge.net/projects/cloverefiboot/ which provides modified DUET images that may contain some system specific fixes and is more frequently updated compared to the gitorious repos.

+

+

= Troubleshooting =

+

+

== Windows 7 won't boot in UEFI Mode ==

−

=== Windows 7 won't boot in UEFI Mode ===

If you have installed Windows to a different harddisk with GPT partitioning and still have a MBR partitioned harddisk in your computer, then it is possible that the UEFI BIOS is starting it's CSM support (for booting MBR partitions) and therefor Windows won't boot. To solve this merge your MBR harddisk to GPT partitioning or disable the SATA port where the MBR harddisk is plugged in or unplug the SATA connector from this harddisk.

If you have installed Windows to a different harddisk with GPT partitioning and still have a MBR partitioned harddisk in your computer, then it is possible that the UEFI BIOS is starting it's CSM support (for booting MBR partitions) and therefor Windows won't boot. To solve this merge your MBR harddisk to GPT partitioning or disable the SATA port where the MBR harddisk is plugged in or unplug the SATA connector from this harddisk.

Unified Extensible Firmware Interface (or UEFI for short) is a new type of firmware that was initially designed by Intel (known as EFI then) mainly for its Itanium based systems. It introduces new ways of booting an OS that is distinct from the commonly used "MBR boot code" method followed for BIOS systems. It started as Intel's EFI in versions 1.x and then a group of companies called the UEFI Forum took over its development from which it was called Unified EFI starting with version 2.0 . As of 24 July 2013, UEFI Specification 2.4 (released July 11, 2013) is the most recent version.

Note: Unless specified as EFI 1.x , EFI and UEFI terms are used interchangeably to denote UEFI 2.x firmware. Also unless stated explicitly, these instructions are general and some of them may not work or may be different in Macs. Apple's EFI implementation is neither a EFI 1.x version nor UEFI 2.x version but mixes up both. This kind of firmware does not fall under any one UEFI Specification version and therefore it is not a standard UEFI firmware.

Before understanding UEFI, it is important to understand how the pre-UEFI (BIOS) systems boot. This is explained in subsequent sections.

BIOS

A BIOS or Basic Input-Output System is the very first program (firmware) that is executed once the system is switched on. In most cases it is stored in a flash memory in the motherboard itself and independent of the system storage.

Boot Process under BIOS

BIOS launches the first 440 bytes (MBR boot code region) of the first disk in the BIOS disk order

The MBR boot code then takes control from BIOS and launches its next stage code (if any) (mostly bootloader code)

The launched (2nd stage) code (actual bootloader) then reads its support and config files

Based on the data in its config files, the bootloader loads the kernel and initramfs into system memory (RAM) and launches the kernel

Multibooting in BIOS

Since very little can be achieved by a program that fits into the 440-byte boot code area, multi-booting using BIOS requires a multi-boot capable bootloader (multi-boot refers to booting multiple operating systems, not to booting a kernel in the Multiboot format specified by the GRUB developers). So usually a common bootloader like GRUB or Syslinux or LILO would be loaded by the BIOS, and it would load an operating system by either chain-loading or directly loading the kernel.

UEFI

UEFI has support for reading both the partition table as well as understanding filesystems. Hence it is not limited by 440 byte code limitation (MBR boot code) as in BIOS systems. It does not use the MBR boot code at all.

The commonly used UEFI firmwares support both MBR and GPT partition table. EFI in Apple-Intel Macs are known to also support Apple Partition Map besides MBR and GPT. Most UEFI firmwares have support for accessing FAT12 (floppy disks), FAT16 and FAT32 filesystems in HDDs and ISO9660 (and UDF) in CD/DVDs. EFI in Apple-Intel Macs can access HFS/HFS+ filesystems also apart from the mentioned ones.

UEFI does not launch any boot code in the MBR whether it exists or not. Instead it uses a special partition in the partition table called EFI SYSTEM PARTITION in which files required to be launched by the firmware are stored. Each vendor can store its files under <EFI SYSTEM PARTITION>/EFI/<VENDOR NAME>/ folder and can use the firmware or its shell (UEFI shell) to launch the boot program. An EFI System Partition is usually formatted as FAT32 (mostly) or FAT16

Under UEFI, every program whether it is an OS loader or a utility (e.g. a memory testing app or recovery tool), should be a UEFI Application corresponding to the EFI firmware bitness/architecture. The vast majority of UEFI firmwares, including recent Apple Macs, use x86_64 EFI firmware. The only known devices that use IA32 (32-bit) EFI are older (pre 2008) Apple Macs, some recent Intel Cloverfield ultrabooks and some older Intel Server boards are known to operate on Intel EFI 1.10 firmware

An x86_64 EFI firmware does not include support for launching 32-bit EFI apps (unlike x86_64 Linux and Windows versions which include such support). Therefore the UEFI application must be compiled for that specific firmware processor bitness/architecture.

Boot Process under UEFI

Firmware then reads its Boot Manager data to determine which UEFI application to be launched and from where (i.e. from which disk and partition).

Firmware then launches the UEFI application as defined in the boot entry in the firmware's boot manager.

The launched UEFI application may launch another application (in case of UEFI Shell or a boot manager like rEFInd) or the kernel and initramfs (in case of a bootloader like GRUB) depending on how the UEFI application was configured.

Note: On some UEFI systems the only possible way to launch UEFI application on boot (if it doesn't have custom entry in UEFI boot menu) is to put it in this fixed location: <EFI SYSTEM PARTITION>/EFI/boot/bootx64.efi (for 64-bit x86 system)

Multibooting in UEFI

Since each OS or vendor can maintain its own files within the EFI System Partition without affecting the other, multi-booting using UEFI is just a matter of launching a different UEFI application corresponding to the particular OS's bootloader. This removes the need for relying on chainloading mechanisms of one bootloader to load another to switch OSes.

Booting Microsoft Windows

64-bit Windows Vista (SP1+), Windows 7 and Windows 8 versions support booting using x86_64 EFI firmware. Windows forces type of partitioning depending on the firmware used, i.e. if Windows is booted in UEFI mode, it can be installed only to a GPT disk. If the Windows is booted in Legacy BIOS mode, it can be installed only to a MBR disk. This is a limitation enforced by Windows installer. Thus Windows supports either UEFI-GPT boot or BIOS-MBR boot only, not UEFI-MBR or BIOS-GPT boot.

This limitation is not enforced by Linux kernel itself, but rather depends on how the bootloader is configured. However this Windows limitation should be considered if the user wishes to boot Windows and Linux from the same disk, since setting up the bootloader itself depends on the firmware type and disk partitioning used. In case of Windows and Linux dual boot in the same disk, it is advisable to follow the method used by Windows, either go for UEFI-GPT boot or BIOS-MBR boot only, not the other two cases.

32-bit Windows versions only support BIOS-MBR booting. So, in case of Linux and 32-bit Windows booting from the same disk, the disk can use only MBR. See http://support.microsoft.com/kb/2581408 for more info.

Detecting UEFI Firmware bitness

Non Macs

Check whether the dir /sys/firmware/efi exists, if it exists it means the kernel has booted in EFI mode. In that case the UEFI bitness is same as kernel bitness. (ie. i686 or x86_64)

Apple Macs

To find out the arch of the efi firmware in a Mac, type the following into the Mac OS X terminal:

ioreg -l -p IODeviceTree | grep firmware-abi

If the command returns EFI32 then it is IA32 (32-bit) EFI firmware. If it returns EFI64 then it is x86_64 EFI firmware. Most of the Macs do not have UEFI 2.x firmware as Apple's EFI implementation is not fully compliant with UEFI 2.x Specification.

UEFI Variables

UEFI defines variables through which an operating system can interact with the firmware. UEFI Boot Variables are used by the boot-loader and used by the OS only for early system start-up. UEFI Runtime Variables allow an OS to manage certain settings of the firmware like the UEFI Boot Manager or managing the keys for UEFI Secure Boot Protocol etc.

Linux Kernel Config options for UEFI

UEFI Runtime Variables Support (efivarfs filesystem - /sys/firmware/efi/efivars). This option is important as this is required to manipulate UEFI Runtime Variables using tools like /usr/bin/efibootmgr. The below config option has been added in kernel 3.10 and above.

CONFIG_EFIVAR_FS=y

UEFI Runtime Variables Support (efivars sysfs interface - /sys/firmware/efi/vars). This option should be disabled if all the userspace tools support efivarfs.

UEFI Variables Support in Kernel

efivarfs (efivarfs kernel module, /sys/firmware/efi/efivars) that was designed to overcome the limitations of sysfs-efivars interface

Old sysfs-efivars interface (efivars kernel module, /sys/firmware/efi/vars) which has been disabled in from linux-3.11 (in Arch pkg)

efivarfs was introduced in kernel 3.8 and most of its bugs were ironed out in kernel 3.10 .

Running both sysfs-efivars and efivarfs can create inconsistencies in EFI variables data in the kernel and is discouraged. Going forward efivarfs is the recommended way for tools to interact with kernel reg EFI variables. All the uefi variables related tools in official repos support efivarfs as of 18-September-2013.

Requirements for UEFI Variables support to work properly

EFI Runtime Services support should be present in the kernel (CONFIG_EFI=y).

Kernel should be booted in EFI mode (via EFISTUB or any EFI bootloader, not via BIOS/CSM or Apple's "bootcamp" which is also BIOS/CSM)

EFI Runtime Services in the kernel SHOULD NOT be disabled via kernel cmdline, i.e. "noefi" kernel parameter SHOULD NOT be used.

If any userspace tool is unable to modify efi variables data, check for existence of /sys/firmware/efi/efivars/dump-* files. If they exist, delete them, reboot and retry again.

If the above step does not fix the issue, try booting withefi_no_storage_paranoia kernel parameter to disable kernel efi variable storage space check that may prevent writing/modification of efi variables.

Note:efi_no_storage_paranoia should only be used when needed and should not be left as a normal boot option. The effect of this kernel command line parameter turns off a safeguard that was put in place to help avoid the bricking of machines when the NVRAM gets too full.

Inconsistency between efivarfs and sysfs-efivars

Both sysfs-efivars and efivarfs can run simultaneously, but this can cause inconsistency between sysfs-efivars data and efivarfs data, especially if data in both are simultaneously modified. See https://lkml.org/lkml/2013/4/16/473 for more info. Therefore it is advisable to use enable only one interface at a time and disable the other one.

Note: From core/linux-3.11 onwards efivars and efi_pstore modules are no longer compiled (this change in only in Arch kernel, upstream has not removed sysfs-efivars code). Only efivarfs is supported from core/linux-3.11 onwards in Arch.

efibootmgr

Warning: Using efibootmgr in Apple Macs may brick the firmware and may need reflash of the motherboard ROM. There have been bug reports regarding this in Ubuntu/Launchpad bug tracker. Use bless command alone in case of Macs. Experimental "bless" utility for Linux by Fedora developers - mactel-bootAUR.

Note: If efibootmgr completely fails to work in your system, you can reboot into UEFI Shell v2 and use bcfg command to create a boot entry for the bootloader.

Note: If you are unable to use efibootmgr, some UEFI BIOSes allow users to directly manage uefi boot options from within the BIOS. For example, some ASUS BIOSes have a "Add New Boot Option" choice which enables you to select a local EFI System Partition and manually enter the EFI stub location. (for example '\EFI\refind\refind_x64.efi')

Note: Upstream efibootmgr http://linux.dell.com/git/efibootmgr.git does not support efivarfs. However vathpela's efibootmgr supports efivarfs and is currently used in official efibootmgr pkg. sysfs-efivars is also completely disabled in official Arch kernel and it supports only efivarfs. This section is written with the assumtion that you are using only efivarfs and vathpela's efibootmgr.

Assuming the boot-loader file to be launched is /boot/efi/EFI/refind/refind_x64.efi, /boot/efi/EFI/refind/refind_x64.efi can be split up as /boot/efi and /EFI/refind/refind_x64.efi, wherein /boot/efi is the mountpoint of the EFI System Partition, which is assumed to be /dev/sdXY (here X and Y are just placeholders for the actual values - eg:- in /dev/sda1 , X==a Y==1).

To determine the actual device path for the EFI System Partition (assuming mountpoint /boot/efi for example) (should be in the form /dev/sdXY), try :

In the above command /boot/efi/EFI/refind/refind_x64.efi translates to /boot/efi and /EFI/refind/refind_x64.efi which in turn translate to drive /dev/sdX -> partition Y -> file /EFI/refind/refind_x64.efi.

The 'label' is the name of the menu entry shown in the UEFI boot menu. This name is user's choice and does not affect the booting of the system. More info can be obtained from efibootmgr GIT README .

FAT32 filesystem is case-insensitive since it does not use UTF-8 encoding by default. In that case the firmware uses capital 'EFI' instead of small 'efi', therefore using \EFI\refind\refindx64.efi or \efi\refind\refind_x64.efi does not matter (this will change if the filesystem encoding is UTF-8).

UEFI Bootloaders

EFI System Partition

Note: The ESP should be accessible by the UEFI firmware, which cannot read LVM and software RAID systems.

Note: Setting "boot" flag in parted in a MBR partition marks that partition as active, while the same "boot" flag in a GPT partition marks that partition as "EFI System Partition".

The EFI System Partition needs to be formatted with a FAT32 filesystem (non-FAT filesystems like ext2/3/4, reiserfs, NTFS, UDF etc. are not supported). Although ESPs with size >=100 MiB and formatted as FAT32 are allowed by Microsoft Windows and many Linux distros, Microsoft documentation specifies that the minimum partition/volume size for FAT32 is 512 MiB. Therefore an ESP should be at least 512 MiB size for maximum compatibility. If you are using Linux EFISTUB booting, then you need to make sure there is adequate space available for keeping the Kernel and Initramfs files in the ESP.

It is recommended to use always GPT for UEFI boot as some UEFI firmwares do not allow UEFI-MBR boot.

GPT partitioned disks

Two choices:

Using GNU Parted/GParted: Create a FAT32 partition. Set "boot" flag on for that partition.

Using GPT fdisk (aka gdisk): Create a partition with partition type ef00. Then format that partition as FAT32 using mkfs.vfat -F32 /dev/<THAT_PARTITION>

If you get the message WARNING: Not enough clusters for a 32 bit FAT!, reduce cluster size with mkfs.vfat -s2 -F32 ... or -s1, otherwise the partition may be unreadable by UEFI.

MBR partitioned disks

Two choices:

Using GNU Parted/GParted: Create FAT32 partition. Change the type code of that partition to 0xEF using fdisk, cfdisk or sfdisk.

Using fdisk: Create a partition with partition type 0xEF. Then format that partition as FAT32 using mkfs.vfat -F32 /dev/<THAT_PARTITION>

UEFI Shell

The UEFI Shell is a shell/terminal for the firmware which allows launching uefi applications which include uefi bootloaders. Apart from that, the shell can also be used to obtain various other information about the system or the firmware like memory map (memmap), modifyiang boot manager variables (bcfg), running partitioning programs (diskpart), loading uefi drivers, editing text files (edit), hexedit etc.

Shell v2 works best in UEFI 2.3+ systems and is recommended over Shell v1 in those systems. Shell v1 should work in all UEFI systems irrespective of the spec. version the firmware follows. More info at ShellPkg and this mail

Launching UEFI Shell

Few Asus and other AMI Aptio x86_64 UEFI firmware based motherboards (from Sandy Bridge onwards) provide an option called "Launch EFI Shell from filesystem device" . For those motherboards, download the x86_64 UEFI Shell and copy it to your EFI System Partition as <EFI_SYSTEM_PARTITION>/shellx64.efi (mostly /boot/efi/shellx64.efi) .

Systems with Phoenix SecureCore Tiano UEFI firmware are known to have embedded UEFI Shell which can be launched using either F6, F11 or F12 key.

Note: If you are unable to launch UEFI Shell from the firmware directly using any of the above mentioned methods, create a FAT32 USB pen drive with Shell.efi copied as (USB)/efi/boot/bootx64.efi . This USB should come up in the firmware boot menu. Launching this option will launch the UEFI Shell for you.

Important UEFI Shell Commands

UEFI Shell commands usually support -b option which makes output pause after each page. map lists recognized filesystems (fs0, ...) and data storage devices (blk0, ...). Run help -b to list available commands.

bcfg

BCFG command is used to modify the UEFI NVRAM entries, which allow the user to change the boot entries or driver options. This command is described in detail in page 83 (Section 5.3) of "UEFI Shell Specification 2.0" pdf document.

Note: Users are recommended to try bcfg only if efibootmgr fails to create working boot entries in their system.

Note: UEFI Shell v1 official binary does not support bcfg command. You can download a modified UEFI Shell v2 binary which may work in UEFI pre-2.3 firmwares.

To dump a list of current boot entries -

Shell> bcfg boot dump -v

To add a boot menu entry for rEFInd (for example) as 4th (numbering starts from zero) option in the boot menu

Shell> bcfg boot add 3 fs0:\EFI\refind\refind_x64.efi "rEFInd"

where fs0: is the mapping corresponding to the EFI System Partition and fs0:\EFI\refind\refind_x64.efi is the file to be launched.

To remove the 4th boot option

Shell> bcfg boot rm 3

To move the boot option #3 to #0 (i.e. 1st or the default entry in the UEFI Boot menu)

Shell> bcfg boot mv 3 0

For bcfg help text

Shell> help bcfg -v -b

or

Shell> bcfg -? -v -b

edit

EDIT command provides a basic text editor with an interface similar to nano text editor, but slightly less functional. It handles UTF-8 encoding and takes care or LF vs CRLF line endings.

To edit, for example rEFInd's refind.conf in the EFI System Partition (fs0: in the firmware)

UEFI Linux Hardware Compatibility

UEFI Bootable Media

Create UEFI bootable USB from ISO

Note: The instructions below are specifically for Archiso/official media; Archboot preparation is identical, with this refind.conf instead of the one mentioned below (which is for Archiso) and without the filesystem label requirement.

Then create a FAT32 filesystem in the partition on the USB (unmount before if necessary) with LABEL as used in the Archiso configuration. Obtain the label from /mnt/iso/loader/entries/archiso-x86_64.conf; this is used by the archiso hook in initramfs to identify the udev path to the installation media. mkfs.vfat is part of package dosfstools.

Note: The filesystem should be either FAT32 (recommended), FAT16, or FAT12.

Remove UEFI boot support from ISO

Warning: In the event that UEFI+isohybrid El Torito/MBR really causes problems, it would be better to just UEFI boot using the USB stick instructions in the previous section

Most of the 32-bit EFI Macs and some 64-bit EFI Macs refuse to boot from a UEFI(X64)+BIOS bootable CD/DVD. If one wishes to proceed with the installation using optical media, it might be necessary to remove UEFI support first.

Mount the official installation media and obtain the archisolabel as shown in the previous section.

Troubleshooting

Windows 7 won't boot in UEFI Mode

If you have installed Windows to a different harddisk with GPT partitioning and still have a MBR partitioned harddisk in your computer, then it is possible that the UEFI BIOS is starting it's CSM support (for booting MBR partitions) and therefor Windows won't boot. To solve this merge your MBR harddisk to GPT partitioning or disable the SATA port where the MBR harddisk is plugged in or unplug the SATA connector from this harddisk.