BIOS

BIOS
Jud McCranie · CC BY-SA 4.0 · source
Name	BIOS
Caption	Basic Input/Output System
Developer	Intel Corporation, American Megatrends, Phoenix Technologies, Award Software International
Released	1975
Latest release version	Legacy and UEFI variants
Operating system	MS-DOS, Microsoft Windows, Linux kernel, FreeBSD
Type	Firmware
License	Proprietary and open implementations

BIOS

The Basic Input/Output System is low-level firmware that initializes hardware and provides runtime services for operating systems on IBM PC-compatible Personal Computers. It traces roots to firmware in the Intel 8086 era and influenced platforms used by vendors such as IBM, Compaq, Dell, and HP. BIOS functionality bridges bootstrap load from storage devices to kernel handoff used by Microsoft Windows NT, Linux kernel, FreeBSD, and legacy MS-DOS environments.

History

The BIOS concept originated with firmware routines in early microcomputers built around Intel 8080 and Intel 8086 processors, with commercialization propelled by IBM PC introductions and contemporaneous vendors such as Phoenix Technologies and Award Software International. During the 1980s and 1990s, BIOS evolved alongside platform shifts led by Intel Corporation chipset roadmaps, the emergence of Compaq Portable systems, and competitive BIOS firmware licensing among Dell and HP. The late 2000s saw the Unified Extensible Firmware Interface effort backed by Intel Corporation and collaborators, driven by compatibility goals with Microsoft Windows Vista and later Windows 7 certification requirements. Transition events include the publication of boot specifications by consortiums linked to UEFI Forum participants and pressure from hardware makers like Apple Inc. for modern firmware models.

Architecture and Components

BIOS architecture traditionally comprises a power-on self-test routine originating from processor reset vectors, a CMOS-backed configuration area maintained with a battery, and interrupt-driven runtime services callable by software. Key components include POST code sequences implemented for Intel-based platforms, a nonvolatile storage region for configuration settings often maintained by vendors such as American Megatrends, device initialization modules for controllers produced by Intel Corporation and AMD, and boot device selection logic used with SATA and optical media controllers. Supplementary modules provide option ROM support for add-on cards from companies like NVIDIA and Broadcom, while SPI flash chips from suppliers such as Winbond and Micron Technology store firmware images.

Functions and Operation

On power-up, firmware executes a POST sequence that exercises processor registers, system buses on PCI and ISA backplanes, memory controllers per Intel 440BX-era designs, and peripheral interfaces from vendors like Realtek or Intel Corporation. The firmware enumerates hardware, sets up basic DMA and interrupt mappings, and locates a bootloader on storage such as devices conforming to ATA or NVMe protocols. Runtime services expose low-level facilities historically via BIOS interrupts used by legacy software including MS-DOS utilities; modern operating systems typically abandon BIOS calls after kernel initialization in favor of direct device drivers as seen in Linux kernel and Windows NT architectures.

Firmware Interfaces and Standards

Legacy BIOS defined software-visible interrupts and data structures standardized de facto across IBM PC clones, while successor specifications such as the Unified Extensible Firmware Interface were formalized by the UEFI Forum with participation from Intel Corporation, Microsoft Corporation, and Apple Inc.. Standards associated with boot services include support for GUID Partition Table schemes used by Microsoft Corporation and Linux kernel distributions, Secure Boot mechanisms aligned with Trusted Platform Module workflows standardized by Trusted Computing Group, and device driver models that interact with ACPI tables designed by Intel Corporation and Microsoft collaborators. Interoperability initiatives involved vendors like Phoenix Technologies and American Megatrends to provide platform firmware compatible with Windows certification programs.

Security and Vulnerabilities

Firmware is a high-value attack surface targeted by sophisticated threat actors exemplified in incidents affecting enterprise products from major suppliers; vulnerabilities in firmware have enabled persistent compromise across operating system reinstalls and storage replacements. Classes of weaknesses include improper update authentication exploited via supply-chain attacks implicating outsourced firmware development, buffer overflows in option ROM modules, and misconfigurations of Secure Boot bypasses relevant to Microsoft Windows deployment scenarios. Mitigations evolved through cryptographic signing, measured boot attestation with Trusted Platform Module chips, firmware update policies by OEMs such as Dell and HP, and research disclosures at venues attended by security teams from Google and Microsoft.

Implementation Variants and Vendors

Implementations range from legacy BIOS firmware produced by Phoenix Technologies, American Megatrends (AMI), and Award Software International to modern UEFI firmware stacks offered by OEMs such as Dell, HP, Lenovo, and Apple Inc. for x86_64 and ARM-based platforms. Open-source projects like coreboot and Tianocore provide alternative implementations used by communities associated with Chromium OS and server vendors seeking auditable firmware. Hardware partners including Intel Corporation, AMD, NVIDIA, and controller suppliers such as Marvell Technology Group influence firmware features through chipset registers, option ROM interfaces, and update mechanisms.

Troubleshooting and Configuration

Common troubleshooting steps involve checking POST beep codes documented by manufacturers like AMI and Phoenix Technologies, reseating components used in Dell and HP service guides, and restoring CMOS settings with battery replacement procedures referenced in OEM maintenance manuals. Configuration tasks include updating firmware images via vendor utilities provided by Lenovo and Dell, enabling or disabling Secure Boot for Microsoft Windows or alternative operating systems, and adjusting boot order entries to select devices adhering to UEFI or legacy boot conventions. Diagnostic methods also employ external tools from hardware vendors and community projects such as coreboot for image analysis and recovery procedures.

Category:Firmware