LLMpediaThe first transparent, open encyclopedia generated by LLMs

BIOS

Generated by DeepSeek V3.2
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: HP EliteBook Hop 4
Expansion Funnel Raw 65 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted65
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
BIOS
NameBIOS
InventorGary Kildall
Introduced1975
RelatedUEFI, CP/M, IBM PC

BIOS. The Basic Input/Output System is a fundamental firmware interface embedded on a computer's motherboard. It initializes and tests the system hardware during the booting process, a sequence known as the Power-On Self-Test. This firmware provides a consistent set of low-level services for the operating system and applications, acting as an intermediary between the hardware and software layers of a personal computer.

Overview

Residing on a non-volatile ROM chip, typically flash memory, this firmware is the first code executed when a computer is powered on. Its primary role is to initialize critical components like the central processing unit, memory controller, and storage devices. The interface establishes a basic hardware abstraction layer, allowing the operating system to interact with peripherals like the keyboard, display adapter, and hard disk drive without needing precise details of the hardware. This abstraction was crucial for the standardization and proliferation of the IBM PC compatible market, enabling software to run on a wide variety of machines from manufacturers like Compaq, Dell, and HP.

History

The conceptual foundation was laid by Gary Kildall for his CP/M operating system in the mid-1970s, where he coined the term. The implementation familiar in modern PCs originated with the original IBM PC released in 1981, designed by a team led by Don Estridge. Early versions were stored on mask ROM chips, making updates impossible without physical replacement. As the IBM PC AT and clones from companies like Phoenix Technologies and Award Software dominated the market, the firmware became a de facto standard. The transition to EEPROM and later flash memory in the 1990s, championed by Intel, allowed users to perform updates via software, a process known as "flashing."

Function

Upon system startup, it performs the Power-On Self-Test, checking the integrity of the RAM, CPU, and other essential subsystems. It then locates, initializes, and catalogs available boot devices such as hard drives, optical disc drives, or USB flash drives according to a user-defined order. After identifying a valid boot device with a master boot record, it loads the first sector of code into memory and hands control over to the operating system loader, such as the Windows Boot Manager or GRUB. It also provides runtime services for the OS through software interrupts, handling basic screen output and disk access.

Configuration

Users can modify hardware settings by entering a setup utility, typically accessed by pressing a key like Delete or F2 during the initial boot sequence. This interface, often called the "CMOS Setup" due to its historical reliance on CMOS battery-backed memory, allows adjustment of parameters for the CPU, memory timings, and boot order. It also enables configuration of integrated peripherals like the SATA controller, USB ports, and legacy ISA support. Changes are saved to the non-volatile memory and applied each time the system starts.

Security

Traditional implementations had limited security features, making systems vulnerable to rootkit infections like CIH or Mebromi. To address this, capabilities like a boot password and validation of firmware integrity were introduced. The Trusted Platform Module can be integrated to provide a hardware-based root of trust for secure measurements during the booting process. Despite these measures, vulnerabilities such as Cold boot attack and exploits detailed by researchers at Black Hat conferences have demonstrated persistent risks, prompting the development of more secure firmware architectures.

UEFI replacement

The Unified Extensible Firmware Interface, developed initially by Intel for its Itanium architecture, is the modern successor. Adopted widely by the Unified EFI Forum, a consortium including Microsoft, Apple Inc., and AMD, UEFI addresses limitations such as disk partition size restrictions and a cumbersome text-mode interface. It features a graphical setup, faster boot times, support for Secure Boot to prevent unauthorized operating system loaders, and a modular design that allows for network capabilities. Modern computers from vendors like Lenovo and ASUS now ship with UEFI firmware, though it often includes a Compatibility Support Module to emulate the legacy interface for older software.