Lesson 1: Motherboard as the Compatibility Map

Core path: 42 minutes

A motherboard is not just the big board everything plugs into.

For a technician, it is the compatibility map for the whole system.

Before you buy a processor, RAM kit, storage device, expansion card, or case, the board tells you what can actually work together.

Start with form factor

Common desktop motherboard form factors include:

• ATX — larger board, more expansion room;
• Micro-ATX — smaller, often fewer slots;
• Mini-ITX — compact, limited expansion.

The board must fit the case, but physical fit is only the first check.

A component can fit physically and still be incompatible electrically, logically, or at the firmware level.

Read the board like a technician

Identify these major areas:

• CPU socket;
• DIMM slots for RAM;
• PCIe expansion slots;
• M.2 storage slots;
• SATA ports;
• 24-pin motherboard power connector;
• CPU power connector;
• front-panel headers;
• USB headers;
• fan headers;
• firmware/CMOS battery area.

The exact layout changes between boards, but the functions stay recognizable.

Compatibility has layers

Use this sequence whenever you evaluate a part:

1. Physical compatibility — does it fit the socket, slot, connector, and case?
2. Electrical compatibility — does the interface provide the correct signaling and power?
3. Firmware/platform compatibility — does the board firmware support the component?
4. System compatibility — will the whole configuration work together within power, cooling, and performance limits?

That is why "it plugs in" is not enough.

BIOS/UEFI is part of the compatibility map

Firmware settings can change whether a system boots, exposes a device, or enables a security/virtualization feature.

At A+ technician depth, recognize settings such as:

• boot order/options;
• USB permissions;
• Secure Boot;
• virtualization support;
• TPM-related security features;
• fan control and temperature monitoring;
• boot password;
• BIOS/UEFI setup password.

A technician should document the baseline before changing firmware settings. Changing several firmware options at once destroys useful evidence.

TPM and HSM are not the same thing

A TPM is a platform security component commonly integrated into or associated with the local system and used by features such as measured/trusted boot and encryption key protection.

A hardware security module (HSM) is a dedicated device/service class designed to protect and perform operations with cryptographic keys, typically at organizational/service scale.

For this course, the distinction is recognition-level:

TPM is tied closely to one platform. HSM is a broader dedicated cryptographic key-protection device/service category.

Example: the wrong CPU

A processor may look similar to another model but use a different socket generation.

If the CPU socket and motherboard do not match, stop there. Do not force the component.

Technician rule:

If a part requires pressure beyond the normal installation mechanism, re-check orientation and compatibility before doing anything else.

Student action

Create a motherboard inspection record with these columns:

Add at least four more interfaces or firmware settings.

Evidence checkpoint

You are ready to move on when you can explain why these are different statements:

• "The component fits."
• "The component is compatible."
• "The firmware exposes/configures it correctly."
• "The system is configured securely for the required job."

Those are different claims, and technicians need evidence for each one.