When a laptop keyboard stops working, the keyboard itself is the usual culprit — keyboards are cheap, exposed and frequently soaked in coffee. But not always. A damaged connector, a corroded trace, a missing pull-up or a failed embedded controller produce exactly the same symptom, and a new keyboard will not fix any of them. This guide explains how the keyboard is read by the board and how to tell a keyboard fault from a board fault.
How a laptop reads its keyboard
Most laptop keyboards are a matrix: a grid of rows and columns, with each key sitting at an intersection. Pressing a key connects one row to one column. The scanning chip — almost always the embedded controller (EC) — drives the scan lines one at a time and reads the sense lines to see which intersection is closed.
| Line group | Typical names | Direction |
|---|---|---|
| Scan (output) lines | KSO0… KSO15 or similar | Driven by the EC |
| Sense (input) lines | KSI0… KSI7 or similar | Read by the EC, with pull-up resistors |
The keyboard connects through a flat flex cable to a connector on the board. Between the connector and the EC there may be series resistors, and the sense lines have pull-ups to an always-on rail. The structure is described in the glossary under keyboard matrix.
Some laptops use a different design — a separate keyboard microcontroller that talks to the system over I²C or USB. The checks below still apply to the connector and cable; the scanning chip is simply different.
Step 1: separate keyboard faults from board faults
| Test | Result | Points to |
|---|---|---|
| External USB keyboard | Works | Internal keyboard, cable, connector or EC scanning |
| External USB keyboard | Does not work | Software, BIOS or USB, not the internal keyboard |
| Keys work in BIOS setup | Yes | Driver or operating-system issue |
| A known-good keyboard | Works | The original keyboard |
| A known-good keyboard | Same fault | The board |
A known-good keyboard is the strongest test. If one is not available, the patterns of failed keys give useful clues.
Patterns of failed keys
- Whole keyboard dead — cable not seated, connector damage, EC not scanning, or the keyboard's flex badly damaged.
- A group of keys in a line or pattern dead — one scan or sense line broken. Keys sharing a line in the matrix fail together, even though they are not neighbours on the keyboard.
- Single key dead — almost always the keyboard itself.
- Keys typing on their own or repeating — a short between lines, usually liquid on the keyboard membrane or corrosion on the connector.
Step 2: inspect the connector and cable
The keyboard connector is a common failure point:
- Latch not closed or the cable not fully inserted — re-seat carefully.
- Cracked or bent contacts on the connector, sometimes after a keyboard replacement.
- Corrosion — keyboards are on top of the board, and liquid spills often reach the connector first.
- Torn flex cable — check the contact fingers and the fold where the cable bends.
Clean corrosion with isopropyl alcohol and a soft brush, then inspect under magnification. A connector with broken contacts should be replaced. Connector types are covered under fpc connector.
Step 3: measure the lines
On a powered board
With the keyboard disconnected and the laptop on, the sense lines should sit at their pull-up voltage — usually the always-on 3.3 V rail or similar, but check the schematic. A sense line at zero means it is shorted to ground, its pull-up resistor is open, or the EC pin is damaged.
The scan lines change state rapidly while the EC scans; a meter shows an in-between average or nothing useful. Do not draw conclusions from their DC readings.
On an unpowered board
Diode mode gives a fingerprint of each line:
- Disconnect the keyboard and all power.
- Measure each scan and sense line at the connector to ground in diode mode.
- Compare lines within each group.
Healthy lines of the same type read close to each other. An OL among normal-looking neighbours means the path is interrupted somewhere between connector and EC — typically corrosion, a cracked via or a series resistor that has gone open or fallen off. A value close to zero means that line has a short to ground. The technique is explained in Using Diode Mode Values from Boardview Files.
Continuity to the EC
For a suspect line, check continuity from the connector pin to the EC pin, following the net in the boardview, through any series resistors. A break shows where the corrosion or damage is. The method is covered in Continuity Testing: Finding Breaks in Traces, Cables and Connectors.
Step 4: liquid damage
Keyboard faults and liquid damage go together. Even when the spill reached only the keyboard, liquid often runs through to the board near the keyboard connector. Look for:
- green or white residue on connector pins and nearby resistors;
- corroded vias around the connector;
- damaged pull-up resistors on the sense lines.
Clean the area thoroughly, then repeat the line measurements. The full routine is in Laptop Liquid Damage Repair: What to Check First.
Step 5: the embedded controller
If the connector, cable and lines are all fine and a known-good keyboard still does not work, the EC may be at fault:
- EC firmware — a corrupted EC firmware can stop keyboard scanning while the laptop otherwise works. On some boards the EC firmware lives in the BIOS chip; reflashing a correct BIOS can fix it.
- EC damage — a liquid- or ESD-damaged EC may scan only some lines, or none. Replacing an EC is possible but needs programming and careful work.
The EC's other jobs — power button, charging, fans — give clues. If those work, the EC is alive, and the problem is more likely in its keyboard pins or the paths to them. The EC is described in the glossary under embedded controller.
The keyboard backlight
The backlight is a separate circuit: a supply (often with its own fuse), an enable or PWM signal, and LEDs in the keyboard. A working keyboard with a dead backlight is a different fault, usually a blown fuse caused by liquid in the keyboard.
Example: half the keys dead after a small spill
A laptop's keyboard types most letters, but a scattered set of keys — including some numbers, letters and a function key — do nothing. A known-good keyboard shows the same pattern, so the board is at fault. In the schematic, all the dead keys share one sense line. With the board unpowered, that line reads OL in diode mode at the connector while its neighbours read normally. Following the net in the boardview, the series resistor between the connector and the EC is green with corrosion and reads open. A new resistor restores the line, and every key works.
FAQ
How do I know if it is the keyboard or the motherboard?
Try a known-good keyboard. If the same keys fail, the board is at fault; if the new keyboard works, replace the original.
Why do non-adjacent keys fail together?
They share a row or column in the matrix. One broken line disables every key on it, no matter where those keys sit on the keyboard.
Can a BIOS update fix a dead keyboard?
Sometimes, if the EC firmware was corrupted and is restored by the update. Physical damage will not be fixed by firmware.
Why are keys typing by themselves?
Usually a short between matrix lines from liquid on the membrane or corrosion on the connector. Disconnect the keyboard — if it stops, the keyboard is at fault.
Is it safe to clean the keyboard connector with alcohol?
Yes, with isopropyl alcohol of high purity, a soft brush and enough time to dry before power is applied.
Bottom line
Use an external keyboard and a known-good keyboard to separate keyboard faults from board faults. On the board, inspect the connector, check the sense lines' pull-up voltages, compare all lines in diode mode, and follow any odd line back to the EC. Liquid damage near the connector is the most common board-level cause.