A dead touchpad is usually a setting, a driver or a cable — but not always. Touchpads connect to the board through a thin flex cable and talk to the system over one of a few interfaces, each with its own supply, pull-ups and control lines. When software and settings are ruled out, those few signals are quick to check. This guide covers the order that finds the cause fastest, from the keyboard shortcut that disables the touchpad to the interrupt line on the board.
Step 1: rule out settings and software
- Touchpad toggle — many laptops have a function key or a double-tap corner that disables the touchpad.
- Operating-system settings — touchpad switched off, or disabled when a mouse is connected.
- Firmware setting — some laptops can disable the touchpad, or switch its mode, in the BIOS.
- Driver — check the device list for the touchpad or an unknown HID device with an error.
- External mouse — if it works, the system is fine and the fault is specific to the touchpad.
A touchpad that works in the firmware setup screen (on laptops where the setup supports pointing devices) but not in the operating system has a driver problem, not a hardware one.
How a touchpad connects
| Interface | Typical on | Signals |
|---|---|---|
| I²C-HID | Most recent laptops | I²C clock and data, an interrupt line, supply |
| PS/2 | Older laptops | Clock and data to the EC |
| SMBus-based | Some designs, often alongside PS/2 | SMBus clock and data |
| USB | A few designs | D+ and D−, supply |
The interface is described under i2c hid and the bus under i2c. The schematic's touchpad connector page shows which one your board uses.
Step 2: the flex cable
The touchpad's flex cable is short, thin and often routed under the battery or around the keyboard:
- reseat it at both ends, making sure the connector latches are closed;
- inspect it for creases, tears and burnt or corroded contacts;
- check each conductor end to end with continuity, as described in Continuity Testing: Finding Breaks in Traces, Cables and Connectors.
Many touchpad faults after a battery or keyboard replacement are simply a cable not fully inserted. Connector types are described under fpc connector.
Step 3: touchpad power
With the laptop on, measure the touchpad's supply pin at the board connector — usually 3.3 V, sometimes switched by the EC or a load switch. If it is missing:
- check the source rail;
- check any fuse or ferrite bead on the line;
- with power removed, check the supply to ground for a short; a liquid-damaged touchpad can short its own supply.
Step 4: bus pull-ups
I²C, SMBus and PS/2 lines all need pull-up resistors. With the laptop on and the touchpad connected:
- the clock and data lines should sit at the pull-up voltage when idle;
- a line stuck at zero means a short, a damaged pin, or a missing pull-up supply;
- a line at an intermediate voltage suggests leakage, often from corrosion.
With power removed, compare the clock and data lines in diode mode; they usually read similarly.
Step 5: the interrupt line
I²C-HID touchpads tell the system that they have new data by pulling an interrupt line. If the interrupt line is open or stuck, the touchpad may be detected but never respond, or respond erratically. Check that the line has its pull-up and reaches the chipset or EC pin shown in the schematic.
Step 6: liquid damage
Touchpads sit under the palm rest, where spills often run. Corrosion on the touchpad's own circuit board, the cable contacts or the board connector is common. Clean all three, then repeat the checks. The connector area on the board often shares the spill with the keyboard connector; check that too, as described in Laptop Keyboard Not Working: Board-Level Causes.
Seeing bus activity
A multimeter shows only average levels on bus lines. While the touchpad is being used, an active I²C or PS/2 line may read slightly below its idle pull-up voltage, but the difference is small. An oscilloscope or an inexpensive logic analyser shows clearly whether the clock toggles and whether the touchpad answers. If the system's side sends clock pulses and the data line never responds, the touchpad or its cable is at fault; if no clock appears at all, look at the host side — the chipset, the EC, or the driver.
Convertibles and thin laptops
On convertible and very thin laptops, the touchpad may share a cable with the keyboard or connect through a small daughterboard. It may also be disabled automatically when the screen folds into tablet mode, based on a sensor reading. A touchpad that works only in some positions points at that sensor or its settings, not at the touchpad itself.
Step 7: the touchpad module
If power, bus lines and interrupt are correct at the board connector and the cable is good, the touchpad module itself is the likely fault. A known-good module of the same part number confirms it. Some touchpads are bonded into the palm rest; replacement may mean a whole top case.
Firmware for touchpads
Touchpad modules often run their own firmware, and the laptop manufacturer occasionally releases updates for them. A touchpad that behaves erratically — jumping pointer, phantom clicks — on an otherwise healthy board may benefit from such an update or a driver change. Check the manufacturer's support page for the model before replacing a module that tests fine electrically.
Buttons
Separate touchpad buttons may connect through the same cable or their own. If the pointer moves but clicks do not register, check the button switches and their lines; if clicks work but the pointer does not move, the sensor side is at fault.
Quick reference
| Finding | Likely cause |
|---|---|
| Works after toggle key or setting change | Disabled by setting |
| Device missing, supply present, bus lines normal | Cable, module |
| Supply missing | Source rail, fuse, switch, short |
| Clock or data stuck low | Short, damaged pin, missing pull-up supply |
| Detected but not responding | Interrupt line, driver |
Example: touchpad gone after a battery replacement
After a battery replacement, a laptop's touchpad stopped working; an external mouse works. The operating system shows no touchpad device at all. The touchpad cable runs under the battery. With the battery removed again, the cable's board-end connector shows the cable inserted at a slight angle with the latch half closed. Reseating it fully and closing the latch brings the touchpad back. No board work was needed.
FAQ
Why did my touchpad stop after a repair?
Most often the flex cable is not fully inserted or the latch is open. Reseat it first.
How do I know which interface my touchpad uses?
The schematic's touchpad connector page shows the signals: I²C, PS/2, SMBus or USB.
Can liquid kill a touchpad?
Yes. The touchpad, its cable or the board connector can corrode. Clean all three.
The pointer moves but clicks do not work. Why?
The buttons or their lines are faulty; the sensor itself works.
Is the touchpad part of the keyboard?
Usually not; it has its own cable. But both often sit near each other and share spill damage.
Bottom line
Rule out toggles, settings and drivers first. Then reseat and test the flex cable, check the touchpad's supply, the bus pull-ups and the interrupt line at the board connector, and clean any corrosion. If all of that is correct, the touchpad module is the likely culprit.