4.2 Understanding Computer Hardware

Understanding Computer Hardware

Linux runs on physical (or virtualized) hardware. Objective 4.2 expects familiarity with the components that make up desktop and server computers—not electronics engineering. Know what each part does, how storage is divided, how Linux names disks under /dev, and why drivers matter.

Partial list from the official objectives: motherboards, processors, power supplies, optical drives, peripherals; hard drives, solid state disks and partitions, /dev/sd*; and drivers.

Core building blocks

The motherboard is the traffic hub. The CPU plugs into a socket and talks to RAM through memory channels designed into the board. Storage devices attach via SATA, NVMe, or USB bridges wired to controllers on the board. Expansion slots (PCIe and similar) accept graphics cards, RAID controllers, or additional network cards. If the motherboard fails, the whole system usually fails even when disks and PSUs are healthy.

The PSU is easy to underestimate. Servers and workstations with many disks and GPUs need higher wattage and reliable connectors. When a machine randomly reboots under load, hardware technicians often check power before blaming the OS.

Optical drives matter historically for installing media and for archival discs. Many cloud VMs have no optical hardware at all; physical desktops may still include one or rely on USB optical drives. On the exam, treat “optical” as CD/DVD-class removable optical media hardware.

Peripherals are everything that extends the computer for humans or for I/O: input devices, printers, scanners, external disks. Linux must load an appropriate driver (kernel module or userspace support) before many peripherals become usable.

Storage: HDD, SSD, and partitions

An HDD stores data magnetically on rotating platters; an SSD stores data in flash chips. Both appear to the OS as block devices once the controller and driver initialize them. You typically partition a disk before installing filesystems: for example, a small boot partition, a root filesystem, and maybe a separate /home. Partitioning lets you isolate data, choose different filesystem types, and reinstall the OS without wiping user files when layouts are planned carefully.

Virtual machines still present virtual disks that look like HDDs/SSDs to the guest; the same partition ideas apply.

Linux disk names: /dev/sd*

Linux represents many devices as special files under /dev. Traditional SCSI, SATA, and USB mass-storage disks commonly appear as:

The letters increment (a, b, c…) for successive disks; partition numbers append to the disk name. Essentials highlights /dev/sd* because it is the classic pattern in learning materials. Modern NVMe devices often use names like /dev/nvme0n1 instead—useful to know in practice—but when an exam item mentions /dev/sda1, think “first partition of the first sd disk.”

Never confuse the device node (/dev/sda) with a mounted directory (/mnt/data). The device is the raw disk; after you create a filesystem and mount it, you access files through a path in the directory tree.

Drivers: software that unlocks hardware

A driver is software—often a kernel module—that teaches the OS how to communicate with a specific device. Without a working network driver, the NIC may power on but never pass packets. Without a printer driver (or a compatible driverless protocol), print jobs stall.

On Linux, many drivers ship with the kernel and load automatically when hardware is detected. Others come from distribution packages or, less ideally, proprietary vendor blobs. Virtual machines use paravirtual or emulated devices with well-supported drivers; bare metal may need firmware files under paths such as those used by linux-firmware packages.

Symptoms of driver problems: device missing from lsusb/lspci visibility tools (when available), network interface not appearing, blank screens on unsupported GPUs, or USB gadgets that show power but no functionality. Essentials-level response: understand that hardware alone is not enough—the kernel needs matching driver support.

How the pieces fit for an Essentials candidate

Picture a server build: motherboard + CPU + RAM + PSU + SSD. You connect a USB keyboard (peripheral) for the installer, boot an ISO from USB or optical media, partition /dev/sda, install Linux, and confirm the NIC driver brings up networking. Each buzzword in 4.2 maps to a step in that story.

Cloud instances hide the motherboard and PSU behind the hypervisor, but the guest still sees virtual CPUs, virtual disks (/dev/sd* or similar), and needs drivers for virtio or emulated devices. The vocabulary remains the same.

Exam traps to avoid

• Treating /dev/sda as a folder of files instead of a block device node
• Assuming every disk is still named /dev/hd* (old IDE naming)—Essentials emphasizes /dev/sd*
• Forgetting that partitions are numbered (sda1, sda2)
• Believing drivers are optional “extras” rather than required for many devices
• Confusing optical drives with SSDs—optical is disc media; SSD is solid-state primary storage

Master the table of components, the HDD/SSD/partition distinction, the /dev/sd* pattern, and the purpose of drivers, and objective 4.2 becomes a straightforward vocabulary section.