Unified Extensible Firmware Interface

From Wikipedia, the free encyclopedia

UEFI Logo

Extensible Firmware Interface's position in the software stack.

The Unified Extensible Firmware Interface (UEFI) (pronounced as an initialism U-E-F-I or like "unify" without the n) is a specification that defines a software interface between an operating system and platform firmware. UEFI is meant to replace the Basic Input/Output System (BIOS) firmware interface, present in all IBM PC-compatible personal computers.[1][2] In practice, most UEFI images provide legacy support for BIOS services. UEFI can support remote diagnostics and repair of computers, even without another operating system.[3] The original EFI (Extensible Firmware Interface) specification was developed by Intel. Some of its practices and data formats mirror ones from Windows.[4][5] In 2005, UEFI deprecated EFI 1.10 (final release of EFI). The UEFI specification is managed by the Unified EFI Forum.
Contents
[hide]

1 History 2 Advantages

3 Compatibility

o o

3.1 Processor compatibility 3.2 Disk device compatibility

4 Features

3.2.1 Protective MBR 3.2.2 Linux 3.2.3 Microsoft Windows

4.1 Services

o o o o

4.1.1 Variable services 4.1.2 Time services

4.2 Protocols 4.3 Device drivers 4.4 Graphics features 4.5 Booting

o o o

4.5.1 UEFI booting 4.5.2 CSM booting 4.5.3 Network booting 4.5.4 Secure boot

4.6 Compatibility Support Module 4.7 The UEFI shell 4.8 Extensions

5 Implementation and adoption

o o o o

5.1 Intel EFI 5.2 Platforms using EFI/UEFI 5.3 Operating systems 5.4 Use of UEFI with virtualization

6 Applications development 7 Criticism

o o

7.1 Secure boot 7.2 Firmware issues

8 See also 9 References 10 Further reading 11 External links

History[edit]

The original motivation for EFI came during early development of the first Intel HP Itanium systems in the mid-1990s. BIOS limitations (such as 16-bit processor mode, 1 MB addressable space and PC AT hardware) were unacceptable for the larger server platforms Itanium was targeting.[6] The effort to address these concerns was initially called Intel Boot Initiative, which began in 1998[7] and was later renamed EFI.[8][9] In July 2005, Intel ceased development of the EFI spec at version 1.10, and contributed it to the Unified EFI Forum, which has evolved the specification as the Unified Extensible Firmware Interface (UEFI). The original EFI spec remains owned by Intel, which exclusively provides licenses for EFI-based products, but the UEFI specification is owned by the Forum.[6][10] Version 2.1 of the UEFI (Unified Extensible Firmware Interface) specification was released on 7 January 2007. It added cryptography, network authentication and the User Interface Architecture (Human Interface Infrastructure in UEFI). The current UEFI specification, version 2.4, was approved in July 2013.

Advantages[edit]

Interaction between the EFI boot manager and EFI drivers

The interface defined by the EFI specification includes data tables that contain platform information, and boot and runtime services that are available to the OS loader and OS. UEFI firmware provides several technical advantages over a traditional BIOS system:[11]

Ability to boot from large disks (over 2 TiB) with a GUID Partition Table, GPT.[12][13] CPU-independent architecture[12] CPU-independent drivers[12]

Flexible pre-OS environment, including network capability Modular design

Compatibility[edit]
Processor compatibility[edit]
As of version 2.3, processor bindings exist for Itanium, x86, x86-64 and ARM. Only little-endian processors can be supported.[14] In May 2013, the UEFI Forum announced that it had produced a proof-of-concept boot environment with UEFI on the 64-bit ARMv8platform.[15] A normal PC BIOS is limited to a 16-bit processor mode and 1 MB of addressable space due to the design being based on the IBM 5150, which used the 16-bit Intel 8088.[6][16] In comparison, the UEFI processor mode can be either 32-bit (x86-32, ARM) or 64-bit (x86-64 and Itanium).[6][17] 64-bit UEFI understands long mode, which allows applications in the pre-boot execution environment to have direct access to all of the memory using 64-bit addressing.[18] UEFI requires the firmware and operating system loader (or kernel) to be size-matched; for example, a 64bit UEFI implementation can only load a 64-bit UEFI operating system boot loader or kernel. After the system transitions from "Boot Services" to "Runtime Services", the operating system kernel takes over. At this point, the kernel can change processor modes if it desires, but this bars usage of the runtime services (unless the kernel switches back again).[19]:sections 2.3.2 and 2.3.4

Disk device compatibility[edit]

See also: GPT: Operating systems support In addition to the standard PC disk partition scheme, which uses a master boot record (MBR), UEFI works with a new partitioning scheme: GUID Partition Table (GPT). GPT is free from many of the limitations of MBR. In particular, the MBR limits on the number and size of disk partitions (up to 4 primary partitions per disk, up to 2 TiB (2 240 bytes) per disk) are relaxed.[20] GPT allows for a maximum disk and partition size of 8 ZiB (8 270 bytes).[20][21] The UEFI specification explicitly requires support for FAT32 for EFI System partitions (ESPs), and FAT16 or FAT12 for removable media;[19]:section 12.3 specific implementations may support other file systems.

Protective MBR[edit]
The first sector of a GPT disk is reserved for protective MBR, which is a legal MBR data structure that defines a single partition of type0xEE. On disks smaller than 2 TiB, this partition should span the entire disk; on larger disks, it should be 2 TiB in size. The idea is to protect the GPT disk from damage by GPTunaware disk utilities when such tools look at the disk, they see a legacy MBR disk with no free space.[21]

Linux[edit]

See also: EFI System partition and Linux Support for GPT in Linux is enabled by turning on the option CONFIG_EFI_PARTITION (EFI GUID Partition Support) during kernel configuration.[22] This option allows Linux to recognize and use GPT disks after the system firmware passes control over the system to Linux. For reverse compatibility, Linux can use GPT disks in BIOS-based systems for both data storage and booting, as both GRUB 2 and Linux are GPT-aware. Such a setup is usually referred to as BIOSGPT.[23] As GPT incorporates the protective MBR, a BIOS-based computer can boot from a GPT disk using GPT-aware boot loader stored in the protective MBR's bootstrap code area.[21] In case of GRUB, such a configuration requires a BIOS Boot partition for GRUB to embed its second-stage code due to absence of the post-MBR gap in GPT partitioned disks (which is taken over by the GPT's Primary Header and Primary Partition Table). Commonly 1 MiB in size, this partition is of type 0xEF and it is used by GRUB only in BIOS-GPT setups. From the GRUB's perspective, no such partition type exists in case of MBR partitioning. This partition is not required if the system is UEFI based, as there is no such embedding of the secondstage code in that case.[13][21][23] UEFI systems can access GPT disks and directly boot from them, simplifying things and allowing UEFI boot methods for Linux. Booting Linux from GPT disks on UEFI systems involves creation of an EFI System partition (ESP), which contains UEFI applications such as bootloaders, operating system kernels, and utility software.[24][25][26] Such a setup is usually referred to as UEFI-GPT, while ESP is recommended to be at least 512 MiB in size and formatted with a FAT32 filesystem for maximum compatibility.[21][23][27] For backwards compatibility, most of the UEFI implementations also support booting from MBR-partitioned disks, through the Compatibility Support Module (CSM) which provides legacy BIOS compatibility. [28] In that case, booting Linux on UEFI systems is the same as on legacy BIOS-based systems.

Microsoft Windows[edit]
The 64-bit versions of Microsoft Windows Vista[29] and later, 32-bit versions of Windows 8, and the Itanium versions of Windows XP and Server 2003 can boot from disks with a partition size larger than 2 TiB.

Features[edit]
Services[edit]
EFI defines two types of services: boot services and runtime services. Boot services are only available while the firmware owns the platform (before the ExitBootServices call). Boot services include text and graphical consoles on various devices, and bus, block and file services. Runtime services are still accessible while the operating system is running; they include services such as date, time and NVRAM access. In addition, the Graphics Output Protocol (GOP) provides limited runtime services support. The operating system is permitted to directly write to the framebuffer provided by GOP during runtime mode. However, the ability to change video modes is lost after transitioning to runtime services mode until the OS graphics driver is loaded.

Variable services[edit]
UEFI variables provide a way to store data, in particular non-volatile data, that is shared between platform firmware and operating systems or UEFI applications. Variable namespaces are identified by GUIDs, and variables are key/value pairs. For example, variables can be used to keep crash messages in NVRAM after a crash for the operating system to retrieve after a reboot.[30]

Time services[edit]
UEFI provides device-independent time services. Time services include support for timezone and daylight saving fields, which allow the hardware real-time clock to be set to local time or UTC.[31] On machines using a PC-AT real-time clock, the clock still has to be set to local time for compatibility with BIOS-based Windows.[5]

Protocols[edit]
EFI defines protocols as set of software interfaces used for communication between two binary modules. All EFI drivers must provide services to others via protocols.

Device drivers[edit]
In addition to standard architecture-specific device drivers, the EFI specification provides for a processorindependent device driverenvironment, called EFI Byte Code or EBC. System firmware is required by the UEFI specification to carry an interpreter for any EBC images that reside in or are loaded into the environment. In that sense, EBC is similar to Open Firmware, the hardware-independent firmware used in PowerPC-based Apple Macintosh and Sun Microsystems SPARC computers, among others. Some architecture-specific (non-EBC) EFI device driver types can have interfaces for use from the operating system. This allows the OS to rely on EFI for basic graphics and network functions until OS specific drivers are loaded.

Graphics features[edit]
The EFI specification defined a UGA (Universal Graphic Adapter) protocol as a way to support deviceindependent graphics. UEFI did not include UGA and replaced it with GOP (Graphics Output Protocol), with the explicit goal of removing VGA hardware dependencies. The two are similar. UEFI 2.1 defined a "Human Interface Infrastructure" (HII) to manage user input, localized strings, fonts, and forms (in the HTML sense). These enable OEMs or IBVs to design graphical interfaces for pre-boot configuration. UEFI itself does not define a user interface. Most early UEFI implementations were console-based, but as early as 2007 some implementations featured a graphical user interface.[32]

Booting[edit]
UEFI booting[edit]

The UEFI specification defines a "boot manager", a firmware policy engine that is in charge of loading the operating system loader and all necessary drivers. The boot configuration is controlled by a set of global NVRAM variables, including boot variables that indicate the paths to the loaders. Operating system loaders are a class of the UEFI applications. As such, they are stored as files on a file system that can be accessed by the firmware, called EFI System partition (ESP). UEFI defines a specific version of FAT, which encompasses FAT32 file systems on ESPs, and FAT16 and FAT12 on removable media.[19]:section 12.3 Supported partition table schemes include MBR andGPT, as well as El Torito volumes on optical disks.[19]:section 2.6.2 UEFI does not rely on a boot sector, although ESP provides space for it as part of the backwards compatibility.[28] UEFI booting from GPT disks is commonly called UEFI-GPT. Boot loaders can also be automatically detected by the UEFI firmwares, to enable booting from removable devices. Auto-detection relies on a standardized file path to the operating system loader, depending on the actual architecture to boot. Format of the file path is defined as <EFI_SYSTEM_PARTITION>/BOOT/BOOT<MACHINE_TYPE_SHORT_NAME>.EFI, e.g. /efi/BOOT/BOOTX64.EFI.[19] It is common for UEFI firmware to include a user interface to the boot manager, to allow the user to select and load the operating system among the possible options.

CSM booting[edit]
For backwards compatibility, most of the UEFI implementations on PC-class machines also support booting in legacy BIOS mode from MBR-partitioned disks, through the Compatibility Support Module (CSM) which provides legacy BIOS compatibility. In that scenario, booting is performed in the same way as on legacy BIOS-based systems, by ignoring the partition table and relying on the content of a boot sector.[28] BIOS booting from MBR-partitioned disks is commonly called BIOS-MBR, regardless of it being performed on UEFI or legacy BIOS-based systems. As a side note, booting legacy BIOS-based systems from GPT disks is also possible, and it is commonly calledBIOS-GPT. Despite the fact MBR partition tables are required to be fully supported within the UEFI specification,[19] some UEFI firmwares immediately switch to the BIOS-based CSM booting depending on the type of boot disk's partition table, thus preventing UEFI booting to be performed from EFI System partitions on MBR-partitioned disks.[28] Such a scheme is commonly called UEFI-MBR.

Network booting[edit]
UEFI specification includes support for booting over network through the Preboot eXecution Environment (PXE). Underlying network protocols include Internet Protocol (IPv4 and IPv6), User Datagram Protocol (UDP), Dynamic Host Configuration Protocol (DHCP) andTrivial File Transfer Protocol (TFTP).[19][33]

Included is also support for boot images remotely stored on storage area networks (SANs), with Internet Small Computer System Interface (iSCSI) and Fibre Channel over Ethernet (FCoE) as supported protocols for accessing the SANs.[19][34][35]

Secure boot[edit]
The UEFI 2.2 specification adds a protocol known as Secure boot, which can secure the boot process by preventing the loading of drivers or OS loaders that are not signed with an acceptable digital signature. When secure boot is enabled, it is initially placed in "setup" mode, which allows a public key known as the "Platform key" (PK) to be written to the firmware. Once the key is written, secure boot enters "User" mode, where only drivers and loaders signed with the platform key can be loaded by the firmware. Additional "Key Exchange Keys" (KEK) can be added to a database stored in memory to allow other certificates to be used, but they must still have a connection to the private portion of the Platform key.[36] Secure boot can also be placed in "Custom" mode, where additional public keys can be added to the system that do not match the private key.[37] Secure boot is supported by Windows 8, Windows Server 2012, and selected Linux distributions.

Compatibility Support Module[edit]

The Compatibility Support Module (CSM) is a component of the UEFI firmware that provides legacy BIOS compatibility by emulating a BIOS environment, allowing legacy operating systems and some option ROMs that do not support UEFI to still be used.[38] CSM also provides required legacy System Management Mode (SMM) functionality, called CompatibilitySmm, as an addition to features provided by the UEFI SMM. This is optional, and highly chipset and/or platform specific. An example of such a legacy SMM functionality is providing USB legacy support for keyboard and mouse, by emulating their classic PS/2 counterparts.[38]

The UEFI shell[edit]

UEFI provides a shell environment, which can be used to execute other UEFI applications, including UEFI boot loaders.[26] Apart from that, commands available in the UEFI shell can be used for obtaining various other information about the system or the firmware like getting the memory map (memmap), modifying boot manager variables (bcfg), running partitioning programs (diskpart), loading UEFI drivers, editing text files (edit) etc.[39][40][41] Source code for an UEFI shell can be downloaded from the Intel's TianoCore UDK2010 / EDK2 SourceForge project.[42] Shell v2 works best in UEFI 2.3+ systems and is recommended over the shell v1 in those systems. Shell v1 should work in all UEFI systems.[39][43][44] Methods used for launching UEFI shell depend on the manufacturer and model of the system motherboard. Some of them already provide a direct option in firmware setup for launching, e.g. compiled x86-64 version of the shell needs to be made available as<EFI_SYSTEM_PARTITION>/SHELLX64.EFI. Some other systems have an already embedded UEFI shell which can be launched by appropriate key press

combinations.[45][46] For other systems, the solution is either creating an appropriate USB flash drive or adding manually (bcfg) a boot option associated with the compiled version of shell.[41][45][47][48]

Extensions[edit]
Extensions to EFI can be loaded from virtually any non-volatile storage device attached to the computer. For example, an original equipment manufacturer (OEM) can distribute systems with an EFI partition on the hard drive, which would add additional functions to the standard EFI firmware stored on the motherboard's ROM.

Implementation and adoption[edit]

Intel EFI[edit]
Intel's implementation of EFI is the Intel Platform Innovation Framework, codenamed "Tiano." Tiano runs on Intel's XScale, Itanium andIA-32 processors, and is proprietary software, although a portion of the code has been released under the BSD license or Eclipse Public License (EPL) as TianoCore. TianoCore can be used as a payload for coreboot.[49] Phoenix Technologies' implementations of UEFI include its SecureCore and SecureCore Tiano products.[50] American Megatrendsoffers its own UEFI implementation known as Aptio,[51] while Insyde Software offers InsydeH2O, its own implementation of Tiano.[52]

Platforms using EFI/UEFI[edit]

Intel's first Itanium workstations and servers, released in 2000, implemented EFI 1.02. Hewlett-Packard's first Itanium 2 systems, released in 2002, implemented EFI 1.10; they were able to boot Windows, Linux, FreeBSDand HP-UX; OpenVMS added UEFI capability in June, 2003. In January 2006, Apple Inc. shipped its first Intel-based Macintosh computers. These systems used EFI instead of Open Firmware, which had been used on its previous PowerPC-based systems.[53] On 5 April 2006, Apple first released Boot Camp, which produces a Windows drivers disk and a non-destructive partitioning tool to allow the installation of Windows XP or Vista without requiring a reinstallation of Mac OS X. A firmware update was also released that added BIOS compatibility to its EFI implementation. Subsequent Macintosh models shipped with the newer firmware.[54] During 2005, more than one million Intel systems shipped with Intel's implementation of UEFI.[55] New mobile, desktop and server products, using Intel's implementation of UEFI, started shipping in 2006. For instance, boards that use the Intel 945 chipset series use Intel's UEFI implementation. Since 2005, EFI has also been implemented on non-PC architectures, such as embedded systems based on XScale cores.[55] The EDK (EFI Developer Kit) includes an NT32 target, which allows EFI firmware and EFI applications to run within a Windowsapplication. But no direct hardware access is allowed by EDK NT32. This means only a subset of EFI application and drivers can be executed at the EDK NT32 target.

In 2008, more x86-64 systems adopted UEFI. While many of these systems still allow booting only the BIOS-based OSes via the Compatibility Support Module (CSM) (thus not appearing to the user to be UEFIbased), other systems started to allow booting UEFI-based OSes. For example, IBM x3450 server, MSI motherboards with ClickBIOS, all HP EliteBook Notebook and Tablet PCs, newer HP Compaq Notebook PCs (e.g., 6730b, 6735b, etc.). In 2009, IBM shipped System x machines (x3550 M2, x3650 M2, iDataPlex dx360 M2) and BladeCenter HS22 with UEFI capability. Dell shipped PowerEdge T610, R610, R710, M610 and M710 servers with UEFI capability. More commercially available systems are mentioned in a UEFI whitepaper.[56] In 2011, major vendors (such as ASRock, Asus, Gigabyte, and MSI) launched several consumer-based motherboards using the Intel 6-series LGA 1155 chipset and AMD 9 Series AM3+ chipsets with UEFI.[57] With the release of Windows 8 in October 2012, Microsoft's certification requirements now require that computers include firmware that implements the UEFI specification. Furthermore, if the computer supports the "Connected Standby" feature of Windows 8 (which allows devices to have power management comparable to smartphones, with an almost instantaneous return from standby mode), then the firmware is not permitted to contain a Compatibility Support Module (CSM). As such, systems that support Connected Standby are incapable of booting Legacy BIOS operating systems.[58][59]

Operating systems[edit]
An operating system that can be booted from a (U)EFI is called a (U)EFI-aware OS, defined by (U)EFI specification. Here the termbooted from a (U)EFI means directly booting the system using a (U)EFI OS loader stored on any storage device. The default location for the operating system loader is <EFI_SYSTEM_PARTITION>/BOOT/BOOT<MACHINE_TYPE_SHORT_NAME>.EFI, where short name of the machine type can be IA32, X64, IA64, ARM or AA64.[19] Some operating systems vendors may have their own boot loaders. They may also change the default boot location.

The Linux kernel has been able to use EFI at boot time since early 2000,[60] using the elilo EFI boot loader or, more recently, EFI versions of GRUB.[61] Grub+Linux also supports booting from a GUID partition table without UEFI.[13] The distribution Ubuntu added support for UEFI secure boot as of version 12.10.[62] Further, the Linux kernel can be compiled with the option to run as an EFI bootloader on its own through the EFI bootstub feature.

HP-UX has used (U)EFI as its boot mechanism on IA-64 systems since 2002. HP OpenVMS has used (U)EFI on IA-64 since its initial evaluation release in December 2003, and for production releases since January 2005.[63]

Apple uses EFI for its line of Intel-based Macs. Mac OS X v10.4 Tiger and Mac OS X v10.5 Leopard implement EFI v1.10 in 32-bit mode even on newer 64-bit CPUs, but full support arrived with Mac OS X v10.8 Mountain Lion.[64]

The Itanium versions of Windows 2000 (Advanced Server Limited Edition and Datacenter Server Limited Edition) implemented EFI 1.10 in 2002. MS Windows Server 2003 for IA-64, MS Windows XP

64-bit Edition and Windows 2000 Advanced Server Limited Edition, all of which are for the Intel Itanium family of processors, implement EFI, a requirement of the platform through the DIG64specification.[65]

Microsoft introduced UEFI for x86-64 Windows operating systems with Windows Server 2008 and Windows Vista Service Pack 1 so the 64-bit versions of Windows 7 are compatible with EFI. 32-bit UEFI was originally not supported since vendors did not have any interest in producing native 32-bit UEFI firmware because of the mainstream status of 64-bit computing.[66] Windows 8 includes further optimizations for UEFI systems, including a faster startup, 32-bit support, and secure boot support.[67][68] There do appear to be some issues with Windows 7 machines not properly supporting the use of MBR as data disks as per Microsoft's own implementation specifications [citation needed]. The typical behavior is a refusal to recognize the presence of any operating system to boot from.

On March 5, 2013, the FreeBSD Foundation awarded a grant to a developer seeking to add UEFI support to the FreeBSD kernel and bootloader.[69]

Oracle Solaris 11.1 and later support UEFI boot for x86 systems with UEFI firmware version 2.1 or later. GRUB 2 is used as the boot loader on x86.[70]

Use of UEFI with virtualization[edit]

HP Integrity Virtual Machines provides UEFI boot on HP Integrity Servers. It also provides a virtualized UEFI environment for the guest UEFI-aware OSes.

Intel hosts an Open Virtual Machine Firmware project on SourceForge.[71] VMware Fusion 3 software for Mac OS X can boot Mac OS X Server virtual machines using EFI. VirtualBox has implemented UEFI since 3.1,[72] but limited to Unix/Linux operating systems (does not work with Windows Vista x64 and Windows 7 x64).[73][74]

QEMU can be used with the Open Virtual Machine Firmware (OVMF) provided by TianoCore. The VMware ESXi version 5 hypervisor, part of VMware vSphere, supports virtualized EFI as an alternative to BIOS inside a virtual machine.

Second generation of the Microsoft Hyper-V virtual machine supports virtualized UEFI.[citation needed]

Applications development[edit]
EDK2 Application Development Kit (EADK) makes it possible to use standard C library functionalities within UEFI applications. EADK can be downloaded from the Intel's TianoCore UDK2010 / EDK2 SourceForge project. Even a port of the Python interpreter is made available as an UEFI application by using the EADK.[75] A minimalistic "Hello world" C program written using EADK looks similar to its usual C counterpart: #include <Uefi.h> #include <Library/UefiLib.h> #include <Library/ShellCEntryLib.h> INTN EFIAPI ShellAppMain(IN UINTN Argc, IN CHAR16 **Argv)

{ Print(L"hello, world\n"); return(0); }

Criticism[edit]
Numerous digital rights activitists have protested against UEFI. Ronald G. Minnich, a co-author of coreboot, and Cory Doctorow, a digital rights activist, have criticized EFI as an attempt to remove the ability of the user to truly control the computer.[76][77] It does not solve any of the BIOS's long-standing problems of requiring two different driversone for the firmware and one for the operating systemfor most hardware.[78] The open-source project, TianoCore,[79] provides the UEFI interfaces. TianoCore lacks the specialized drivers that initialize chipset functions, which are instead provided by Coreboot, of which TianoCore is one of many payload options. The development of Coreboot requires cooperation from chipset manufacturers to provide the specifications needed to develop initialization drivers.

Secure boot[edit]
See also: Windows 8: Secure boot and Hardware restrictions: Secure boot In 2011, Microsoft announced that computers certified to run its Windows 8 operating system had to ship with secure boot enabledusing a Microsoft private key. Following the announcement, the company was accused by critics and free software/open source advocates (including the Free Software Foundation) of trying to use the secure boot functionality of UEFI to hinder or outright preventthe installation of alternative operating systems such as Linux. Microsoft denied that the secure boot requirement was intended to serve as a form of lock-in, and clarified its requirements by stating that systems certified for Windows 8 must allow secure boot to enter custom mode or be disabled, but not on systems using the ARM architecture.[37][80] Other developers raised concerns about the legal and practical issues of implementing support for secure boot on Linux systems in general. Former Red Hat developer Matthew Garrett noted that conditions in the GNU General Public License version 3 may prevent the use of the GRUB bootloader without a distribution's developer disclosing the private key (however, the Free Software Foundationhas since clarified its position, assuring that the responsibility to make keys available was held by the hardware manufacturer),[62] and that it would also be difficult for advanced users to build custom kernels that could function with secure boot enabled without self-signing them.[80] Other developers suggested that signed builds of Linux with another key could be provided, but noted that it would be difficult to persuade OEMs to ship their computers with the required key alongside the Microsoft key.[2] Several major Linux distributions have developed different implementations for secure boot. Matthew Garrett himself developed a minimal bootloader known as shim; a pre-compiled, signed bootloader that allows the user to individually trust keys provided by distributors.[81] Ubuntu 12.10 uses an older version of shim pre-configured for use with Canonical's own key that only verifies the bootloader and allows unsigned

kernels to be loaded: developers believed this practice of only signing the bootloader is more feasible, since a trusted kernel is only effective at securing user space and not the pre-boot state (which secure boot is designed to protect). This also allows users to build their own kernels and use custom kernel modules as well, without needing to re-configure the system.[62][82][83] Canonical also maintains its own private key to sign installations of Ubuntu pre-loaded on certified OEM computers that run the operating system, and also plans to enforce a secure boot requirement as wellrequiring both a Canonical key and a Microsoft key (for compatibility reasons) to be included in their firmware. Fedora also uses shim, but requires that both the kernel and its modules be signed as well.[82] It has been disputed whether the kernel and its modules must be signed as well; while the UEFI specifications do not require it, Microsoft has asserted that their contractual requirements do, and that it reserves the right to revoke any certificates used to sign code that can be used to compromise the security of the system.[83] In February 2013, another Red Hat developer attempted to submit a patch to the Linux kernel that would allow it to parse Microsoft's authenticode signing using a master X.509 key embedded in PE files signed by Microsoft. However, the proposal was criticized by Linux creator Linus Torvalds, who attacked Red Hat for supporting Microsoft's control over the secure boot infrastructure.[84] On March 26, 2013, the Spanish free software development group Hispalinux filed a formal complaint with the European Commission, contending that Microsoft's secure boot requirements on OEM systems were "obstructive" and anti-competitive.[85] At the Black Hat conference in August 2013, a group of security researchers presented a series of exploits in specific vendor implementations of UEFI that could be used to exploit secure boot.[86]

Firmware issues[edit]
The increased prominence of UEFI firmware in devices has also led to a number of technical issues blamed on their respective implementations.[87] Following the release of Windows 8 in late-2012, it was discovered that certain Lenovo computer models with secure boot had firmware that was hard-coded to only allow executables named "Windows Boot Manager" or "Red Hat Enterprise Linux" to load, regardless of any other setting.[88] Other issues were encountered by several Toshiba laptop models with secure boot that were missing certain certificates required for its proper operation.[87] In January 2013, a bug surrounding the UEFI implementation on some Samsung laptops was publicized, which caused them to bebricked after installing a Linux distribution in UEFI mode. While potential conflicts with a kernel module designed to access system features on Samsung laptops were initially blamed (also prompting kernel maintainers to disable the module on UEFI systems as a safety measure), Matthew Garret uncovered that the bug was actually triggered by storing too many UEFI variables to memory, and that the bug could also be triggered under Windows as well under special conditions. In conclusion, he determined that the offending kernel module had caused kernel message dumps to be written to the firmware, thus triggering the bug.[30][89][90]

See also[edit]

Booting GNU GRUB Master boot record (MBR) GUID Partition Table (GPT) EFI System partition (ESP) BIOS Boot partition Advanced Configuration and Power Interface (ACPI) coreboot Open Firmware OpenBIOS Platform Initialization Specification System Management BIOS (SMBIOS) System Management Mode (SMM) Trusted Platform Module (TPM) Unified EFI Forum

References[edit]
1. Jump up^ Michael Kinney (1 September 2000). "Solving BIOS Boot Issues with EFI" (PDF). pp. 4750. Retrieved 14 September 2010. 2. ^ Jump up to:
a b

"MS denies secure boot will exclude Linux". The Register. 23 September 2011.

Retrieved 24 September 2011. 3. Jump up^ "The 30-year-long Reign of BIOS is Over: Why UEFI W... - Input Output". H30565.www3.hp.com. Retrieved 2012-03-06. 4. 5.
[dead link]

Jump up^ IBM PC Real Time Clock should run in UT. Cl.cam.ac.uk. Retrieved on 2013-10-30. ^ Jump up to:
a b

Matthew Garrett (Jan 19, 2012). "EFI and Linux: the future is here, and it's awful -

Matthew Garrett". linux.conf.au 2012. Retrieved 2 April 2012. 6. ^ Jump up to:

a b c d

"Emulex UEFI Implementation Delivers Industry-leading Features for IBM

Systems" (PDF). Emulex. Retrieved 14 September 2010. 7. Jump up^ Extensible Firmware Interface (EFI) and Unified EFI (UEFI), Intel, archived from the original on 2010-01-05 8. 9. Jump up^ Wei, Dong (2006), "foreword", Beyond BIOS, Intel Press,ISBN 978-0-9743649-0-2 Jump up^ "1.10 Specification overview", Extensible Firmware Interface, Intel

10. Jump up^ About, Unified EFI Forum, "Q: What is the relationship between EFI and UEFI? A: The UEFI specification is based on the EFI 1.10 specification published by Intel with corrections and changes managed by the Unified EFI Forum. Intel still holds the copyright on the EFI 1.10 specification, but has

contributed it to the Forum so that the Forum can evolve it. There will be no future versions of the EFI specification, but customers who license it can still use it under the terms of their license from Intel. The license to the Unified EFI Specification comes from the Forum, not from Intel" 11. Jump up^ "UEFI and Windows". Microsoft. 15 September 2009. Retrieved 14 September 2010. 12. ^ Jump up to:
a b c

Large disk support and features such as Advanced Configuration and Power

Interface (ACPI) and System Management BIOS (SMBIOS) were subsequently implemented in BIOSbased systems. 13. ^ Jump up to:
a b c

"Installation". 3.4 BIOS installation. GNU GRUB. Retrieved 2013-09-25.

14. Jump up^ UEFI specification 2.3.1, section 1.8.1. 15. Jump up^ "New boot firmware a step toward 64-bit Windows RT". PC World. Retrieved 28 October 2013. 16. Jump up^ Hardwidge, Ben (1 June 2010). "LBA explained Solving the 3TB Problem?". bit-tech. Retrieved 18 June 2010. 17. Jump up^ Brian Richardson (10 May 2010). "Ask a BIOS Guy: "Why UEFI"". Intel Architecture Blog. Retrieved 18 June 2010. 18. Jump up^ Gary Simpson. "UEFI Momentum The AMD perspective"(PPTX). AMD. Retrieved 18 June 2010. 19. ^ Jump up to:
a b c d e f g h i

"UEFI Specifications (version 2.4 and older)"(PDF). Unified EFI, Inc. June

2013. Retrieved 2013-09-25. 20. ^ Jump up to: 21. ^ Jump up to:

a b

"FAQ: Drive Partition Limits" (PDF). UEFI Forum. Retrieved 9 June 2010. Roderick W. Smith (2012-07-03). "Make the most of large drives with GPT and

a b c d e

Linux". IBM. Retrieved 2013-09-25. 22. Jump up^ "block/partitions/Kconfig (3.11.1)".CONFIG_EFI_PARTITION (line #247). kernel.org. Retrieved 2013-09-25. 23. ^ Jump up to:
a b c

"GRUB". BIOS systems. Arch Linux. Retrieved 2013-09-25.

[unreliable source?]

24. Jump up^ "GRUB and the boot process on UEFI-based x86 systems". redhat.com. Retrieved 2013-1114. 25. Jump up^ "UEFI Booting 64-bit Redhat Enterprise Linux 6". fpmurphy.com. September 2010. Retrieved 2013-11-14. 26. ^ Jump up to:
a b

"UEFI Bootloaders". Arch Linux. Retrieved 2013-09-25.

[unreliable source?]

27. Jump up^ "Unified Extensible Firmware Interface". EFI System Partition. Arch Linux. Retrieved 201309-25.
[unreliable source?] a b c d

28. ^ Jump up to:

"UEFI system booting from MBR partition table and GRUB legacy". Arch Linux

Forums. June 2012. Retrieved 2013-10-06. 29. Jump up^ For Microsoft Windows Vista (x64), it is possible only if installed from an installation DVD of Microsoft Windows Vista (x64) with its service pack 1 or 2 integrated.

30. ^ Jump up to: 2013.

a b

"Samsung UEFI bug: Notebook bricked from Windows". The H. Retrieved 27 February

31. Jump up^ UEFI specification, section 7.3 32. Jump up^ Intel shows PC booting Windows with UEFI firmware 33. Jump up^ "Red Hat Enterprise Linux 6 Installation Guide". 30.2.2. Configuring PXE boot for EFI. Red Hat. Retrieved 2013-10-09. 34. Jump up^ "UEFI Summit" (PDF). Advances in Pre-OS Networking in UEFI 2.4. Hewlett-Packard. July 2013. Retrieved 2013-10-09. 35. Jump up^ "Storage and Network Convergence Using FCoE and iSCSI" (PDF). IBM. July 2012. Retrieved 2013-10-09. 36. Jump up^ Edge, Jake. "UEFI and "secure boot"". LWN.net. Retrieved 9 September 2012. 37. ^ Jump up to:
a b

"Windows 8 Secure Boot: The Controversy Continues". PC World. Retrieved 9

September 2012. 38. ^ Jump up to:

a b

"Intel Platform Innovation Framework for EFI" (PDF).Compatibility Support Module

Specification (revision 0.97). Intel. 2007-09-04. Retrieved 2013-10-06. 39. ^ Jump up to: 25.
a b

"Unified Extensible Firmware Interface". UEFI Shell. Arch Linux. Retrieved 2013-09-

[unreliable source?]

40. Jump up^ "EFI Shells and Scripting". Intel. Retrieved 2013-09-25. 41. ^ Jump up to:
a b

"UEFI Shell Specification Version 2.0, Errata A" (PDF). Unified EFI, Inc. May 2012.

Retrieved 2013-09-25. 42. Jump up^ "TianoCore on SourceForge". Intel. Retrieved 2013-09-25. 43. Jump up^ "Email Archive: edk2-devel". [edk2] Inclusion of UEFI shell in Linux distro iso. SourceForge. 2012. Retrieved 2013-09-25. 44. Jump up^ "TianoCore on SourceForge". Shell FAQ. Intel. Retrieved 2013-09-25. 45. ^ Jump up to: 2013-09-25.
a b

"Unified Extensible Firmware Interface". Launching UEFI Shell. Arch Linux. Retrieved

[unreliable source?]

46. Jump up^ "Basic Instructions for Using EFI for Server Configuration on Intel Server Boards and Intel Server Systems" (PDF).Intel. 2008. Retrieved 2013-09-25. 47. Jump up^ "Unified Extensible Firmware Interface". bcfg. Arch Linux. Retrieved 2013-09-25.
source?] [unreliable source?] [unreliable

48. Jump up^ "GRUB EFI Examples". Asus. Arch Linux. Retrieved 2013-09-25. 49. Jump up^ "TianoCore - coreboot". Retrieved 25 May 2012.

50. Jump up^ "SecureCore Tiano". Phoenix Technologies. Retrieved 14 September 2010. 51. Jump up^ "Aptio: The Complete UEFI Product Solution" (PDF). American Megatrends, Inc. Retrieved 8 January 2011. 52. Jump up^ "InsydeH2O UEFI Framework". Insyde Software Corp. Retrieved 8 January 2011.

53. Jump up^ Apple Computer. "Universal Binary Programming Guidelines, Second Edition: Extensible Firmware Interface (EFI)" 54. Jump up^ Apple's Transition from Open Firmware to Extensible Firmware Interface, mactech, 2007. 55. ^ Jump up to:
a b

"Intel Platform Innovation Framework for UEFI Overview". Intel. Retrieved 14

September 2010. 56. Jump up^ Evaluating UEFI using Commercially Available Platforms and Solutions (PDF), UEFI, 20115 57. Jump up^ Asus P67 Motherboard Preview. 58. Jump up^ Windows Hardware Certification Requirements for Client and Server Systems, Microsoft, 2013-1 59. Jump up^ "Microsoft: All You Need to Know About Windows 8 on ARM". PC Magazine. Retrieved 30 September 2013. 60. Jump up^ Announcement of release 3.5pre1 by maintainer Brett Johnson made on 2004-02-27. 61. Jump up^ EFI version of Grub, Debian GNU/Linux, retrieved 1 May 2008 62. ^ Jump up to:
a b c

"Ubuntu will use GRUB 2 for its Secure Boot implementation". The H Online.

Retrieved 28 October 2012. 63. Jump up^ OpenVMS Release History, HP, retrieved 16 September 2008 64. Jump up^ rEFIt Windows Vista and EFI, SourceForge 65. Jump up^ "Extensible Firmware Interface", Windows Server TechCenter, Microsoft 66. Jump up^ "Unified Extended Firmware Interface support in Windows Vista". Microsoft. 26 October 2006. Retrieved 12 June 2010. "Microsoft determined that vendors would not have any interest in producing native UEFI 32-bit firmware because of the current status of mainstream 64-bit computing and platform costs. Therefore, Microsoft originally did not to ship support for 32-bit UEFI implementations." 67. Jump up^ "Microsoft Touts Incredible Windows 8 Boot Times". Retrieved September 9, 2011. 68. Jump up^ Jon Brodkin (21 September 2011). "Windows 8 secure boot could complicate Linux installs". Ars Technica. Retrieved 23 September 2011. 69. Jump up^ "FreeBSD to get UEFI support". The H. Retrieved 7 March 2013. 70. Jump up^ "Oracle Solaris 11.1 What's New" (PDF). oracle.com. Retrieved 2013-11-04. 71. Jump up^ Open Virtual Machine Firmware, SourceForge 72. Jump up^ 3.1 Changelog, VirtualBox 73. Jump up^ Ticket 7702, VirtualBox 74. Jump up^ "Statement by sr. software engineer at Oracle", Forum, VirtualBox 75. Jump up^ "TianoCore on SourceForge". EDK2 Application Development Kit (EADK). Intel. Retrieved 2013-09-25. 76. Jump up^ "Interview: Ronald G Minnich". Fosdem. 6 February 2007. Retrieved 14 September 2010. 77. Jump up^ Doctorow, Cory (2011-12-27), The Coming War on General Purpose Computation, retrieved 2013-09-25

78. Jump up^ "coreboot (aka LinuxBIOS): The Free/Open-Source x86 Firmware". YouTube. 31 October 2008. Retrieved 14 September 2010. 79. Jump up^ "Welcome", TianoCore, SourceForge 80. ^ Jump up to:
a b

"Is Microsoft Blocking Linux Booting on ARM Hardware?". Compurer World UK.

Retrieved 2012-03-06. 81. Jump up^ "Shimming your way to Linux on Windows 8 PCs". ZDNet. Retrieved 26 February 2013. 82. ^ Jump up to:
a b

"Ubuntu details its UEFI secure boot plans". Linux Weekly News. Retrieved 11

September 2012. 83. ^ Jump up to:

a b

"No Microsoft certificate support in Linux kernel says Torvalds". The H. Retrieved 26

February 2013. 84. Jump up^ "Linus Torvalds: I will not change Linux to "deep-throat Microsoft"". Ars Technica. Retrieved 26 February 2013. 85. Jump up^ "Exclusive: Open software group files complaint against Microsoft to EU". Reuters. 26 March 2013. Retrieved 26 March 2013. 86. Jump up^ "Researchers demo exploits that bypass Windows 8 Secure Boot". IT World. Retrieved 5 August 2013. 87. ^ Jump up to:
a b

"Linux on Windows 8 PCs: Some progress, but still a nuisance". ZDNet. Retrieved 26

February 2013. 88. Jump up^ "Lenovo UEFI Only Wants To Boot Windows, RHEL". Phoronix. Retrieved 26 February 2013. 89. Jump up^ "Linux acquitted in Samsung laptop UEFI deaths". Bit-tech. Retrieved 26 February 2013. 90. Jump up^ "Booting Linux using UEFI can brick Samsung laptops". The H. Retrieved 26 February 20