Lesson 3: Ports, Cables, and Interfaces

A connector is not just a shape. It tells you what kind of signal, power, or data path the system expects.

That makes ports one of the fastest ways to narrow a hardware problem.

Start with the outside

On a typical desktop, identify these external interfaces when present:

• USB-A;
• USB-C;
• HDMI;
• DisplayPort;
• Ethernet RJ-45;
• 3.5 mm audio;
• legacy VGA or DVI;
• power input.

Do not assume two ports with similar shapes do the same thing.

USB-C is the classic example. The connector shape can carry different capabilities depending on the implementation, including USB data, charging, DisplayPort Alt Mode, or Thunderbolt.

Internal data interfaces

Inside the system, common paths include:

SATA

SATA commonly connects 2.5-inch SSDs, 3.5-inch HDDs, and older optical drives.

A SATA drive normally needs two separate connections:

• SATA data to the motherboard;
• SATA power from the PSU.

A missing data cable and a missing power cable produce different failure paths.

M.2

M.2 describes a form factor and connector family. It does not automatically mean NVMe.

Depending on the device and motherboard, an M.2 drive may use SATA or PCIe/NVMe.

Technician rule:

Never buy or install an M.2 drive based only on the fact that the slot looks right.

Check the motherboard documentation and supported key/protocol.

PCI Express

PCIe connects expansion devices such as GPUs, network adapters, capture cards, and storage controllers.

Slot length and electrical lane support matter. A large x16 slot is commonly used for a GPU, while smaller slots may support other cards.

Power interfaces

Learn the difference between a cable that carries data and a cable that supplies power.

Common internal power connectors include:

• 24-pin ATX motherboard power;
• 4+4 or 8-pin CPU/EPS power;
• GPU auxiliary power;
• SATA power.

A system can have a perfectly connected data path and still fail because the device has no power.

Lab: cable-path diagnosis

For each scenario, identify the most relevant path to inspect first.

Scenario A

A SATA SSD appears physically installed but does not show up in firmware or the operating system.

Inspect both:

• SATA data path;
• SATA power path.

Scenario B

The desktop powers on, but the monitor reports No Signal.

Check:

• monitor power;
• display cable;
• correct monitor input;
• whether the cable is connected to the intended graphics output;
• GPU seating and auxiliary power if a discrete GPU is present.

Scenario C

A front USB port is dead while rear motherboard USB ports work.

That evidence points toward the front-panel port, cable, or internal USB header before it points toward the entire USB subsystem.

Build a port map

Create a labeled port map for one classroom desktop, laptop, or approved visual model.

Your map must include:

• port/interface name;
• typical device connected;
• data, video/audio, network, or power role;
• one compatibility warning;
• one failure symptom.

Do not write "plug goes here." Use technician language.

Evidence checkpoint

By the end of this lesson, you should be able to distinguish major external and internal interfaces, explain the difference between power and data paths, and use connector evidence to narrow a failure.

Next we bring firmware, boot, and POST into the picture.