When you press the PC's power button, it's not the operating system that wakes up first. Before Windows, Linux, or anything else appears on the screen, a less visible but decisive actor takes the stage. It's the motherboard firmware, what for years we simply called
BIOS and which today, in most modern machines, lives under the name
UEFI.
These components are the bridge between the bare hardware and the software you use every day. Without them, the CPU, RAM, disks, and cards wouldn't even know where to begin. Understanding what they do and why they are so important means looking inside the first seconds of every computer's life, the ones we usually take for granted.
BIOS, the PC Veteran
The acronym BIOS comes from
Basic Input Output System. It is the historical firmware of IBM-compatible PCs, a small piece of software recorded in non-volatile memory on the motherboard. When the machine turns on, the processor starts executing that very code, which has the task of initializing the hardware and preparing the ground for the operating system.
The BIOS runs the POST, Power On Self Test, checks that RAM, CPU, and basic peripherals respond correctly, detects storage units, and sets essential parameters. Then it searches for a boot device following the configured order and reads the bootloader from the disk, historically from the MBR table. Because of this, for years, limitations like disks over 2 TB or certain partition configurations were tied precisely to the nature of the BIOS and its way of communicating with the hardware.
The classic BIOS interface is that blue or gray, text-based screen, invoked by pressing keys like Del, F2, or F10 at startup. There, parameters such as boot order, RAM speed, virtualization support, and any overclocking functions are adjusted. A spartan but crucial environment, which many technicians know almost by heart.
UEFI, the Modern Successor
With the arrival of ever-larger disks, advanced security needs, and new hardware platforms, the BIOS model reached its limit. From this was born
UEFI, Unified Extensible Firmware Interface, standardized by a consortium of companies and detailed on the official website of the
UEFI Forum. In practice, it is the modern successor to the BIOS, although many manufacturers still call it BIOS out of habit.
UEFI is not just a graphical makeover. It is a more modular firmware, designed to manage disks with the GPT partition scheme, to support additional interfaces, extendable drivers, and more flexible boot modes. It allows interfaces with a mouse, multilingual support, and even small apps that run before the operating system, such as diagnostic tools or update utilities.
One of the most discussed functions is
Secure Boot, which allows the firmware to verify the signature of the bootloader and operating system, blocking unauthorized code. Well-configured, it is an important ally in the basic security of machines. Poorly configured, however, it can complicate the life of those installing alternative systems or Linux distributions without following compatibility guidelines.
Many modern motherboards offer a compatibility mode, often called CSM or Legacy, which emulates the behavior of the old BIOS to make operating systems and configurations that don't yet know the UEFI world work. It's a transitional phase that illustrates well the coexistence of old and new in the hardware world.
What Really Happens at Startup
If you look at the boot sequence with a bit of zoom, the movie is quite accurate. At power-on, the power supply brings voltage to the motherboard, the CPU is reset and begins executing the instructions in the firmware, whether BIOS or UEFI. Internal registers are initialized, memory is set up, and fundamental devices are verified.
After completing the POST, the firmware builds an inventory of the available hardware, checks the saved configurations, and moves to the next phase, the search for a bootable device. In a UEFI world, this means locating an EFI partition on one of the disks, loading the bootloader, and passing control to it. From that moment on, the operating system tells the story, but the first chapters have already been written by the firmware.
It is in this phase that seemingly innocuous details, like the disk's position in the boot order or the activation of certain options, decide whether the system boots smoothly or gets stuck on a black screen. That's why, when installing a new system or moving a disk from one machine to another, understanding how BIOS and UEFI interpret the drives is often the difference between a successful boot and hours of attempts.
Why BIOS and UEFI Remain Fundamental
BIOS and UEFI are fundamental for at least three reasons. The first is evident: without them, the hardware doesn't go from dead iron to a functioning machine. They are the ones that initialize controllers, memory, buses, and expose a coherent platform for the operating system to work on.
The second reason concerns the machine's
deep configuration. Power parameters, fan management, virtualization support, RAM XMP profiles, SATA or NVMe modes of the controllers—all pass through the firmware. The decisions made there directly influence performance, stability, and compatibility. Many official manufacturer guides, such as the BIOS and UEFI support pages from
Intel, show well how delicate this level is.
The third concerns security. Firmware access passwords, Secure Boot, blocking boot from unauthorized external devices, CPU microcode updates. All elements that live at the intersection of hardware and software and which, if neglected, leave the front door dangerously ajar.
In a world of polished interfaces and increasingly automatic systems, BIOS and UEFI remain the roughest but indispensable part of the experience. We hardly ever see them, but they are the ones who decide whether a computer can be born, every morning, as a usable machine or remain stuck halfway across the ford.
