Week 01 · lesson
Lesson 4: Firmware, POST, and the Boot Path
A computer can have every major component installed and still fail before the operating system ever starts.
That is why technicians need to understand the boot path.
Power-on is a sequence
A simplified startup path looks like this:
- system receives power;
- motherboard firmware starts;
- POST checks essential hardware;
- firmware identifies bootable devices;
- the selected boot device is handed control;
- the operating system begins loading.
If the machine never reaches Step 6, reinstalling an operating system is probably not your first move.
BIOS and UEFI
Legacy systems use BIOS. Modern systems generally use UEFI.
UEFI provides a more capable firmware environment and commonly supports features such as:
- graphical setup interfaces;
- GPT boot disks;
- Secure Boot;
- modern hardware configuration;
- boot-order management;
- hardware monitoring.
Do not randomly change firmware settings during a lab. Record the original state first.
POST
POST means Power-On Self-Test.
POST checks whether enough essential hardware is functioning for the startup process to continue.
Possible evidence includes:
- vendor logo or firmware screen;
- diagnostic LEDs;
- beep codes;
- text error messages;
- fan behavior;
- drive detection;
- memory count;
- absence of video output.
Different manufacturers implement diagnostics differently, so documentation matters.
Lab: observe without changing
Using an approved classroom computer or firmware screenshot set, record:
- firmware type when identifiable;
- system date/time;
- detected CPU;
- installed memory;
- detected storage;
- boot order;
- Secure Boot state if visible;
- hardware-monitor readings if available.
Do not change a setting unless the lab specifically tells you to.
Scenario: powers on, no operating system
Suppose the system reaches firmware, detects the CPU and memory, but shows no bootable device.
What does that evidence eliminate?
It makes a total motherboard or CPU failure less likely because firmware is already executing.
What becomes more relevant?
- storage detection;
- boot order;
- damaged or missing bootloader;
- failed drive;
- disconnected drive;
- incompatible firmware mode.
The symptom narrows the path.
Scenario: no POST video
Now suppose the machine powers on but never displays firmware output.
Start earlier in the chain.
Check:
- monitor power and input;
- display cable;
- correct video output;
- diagnostic LEDs or beep codes;
- RAM seating;
- GPU seating and power if installed;
- CPU power connection.
Do not jump straight to replacing the motherboard.
Evidence checkpoint
By the end of the lesson, you should be able to explain where firmware and POST fit in the startup path and use startup evidence to decide whether a failure likely occurs before or after the operating-system boot stage.
Tomorrow you put the week together in a service-ticket challenge.
System process animation
From power button to operating system
Step through the startup boundaries in order so a boot failure is located before a repair is attempted.Technician question: At which boundary does the observed evidence stop?
Read it. Prove it.