How To Fix A Touchpad Not Working In Linux (2026)
Your Linux laptop boots fine, but the touchpad does nothing, or it works only some of the time.
This is usually a software or driver problem, and it is often fixable without opening the laptop.
Work through the steps below in order, from the quickest checks to the kernel-level fixes, and expect to spend 15 to 30 minutes.
Which test tells you what is wrong?
Run these three checks first, because the result decides which fix you need.
| Test | If it shows the touchpad | If it does not |
|---|---|---|
sudo dmesg | grep -i touchpad | The kernel found the hardware | Suspect the driver, firmware or a kernel parameter |
sudo libinput list-devices | The desktop input layer can see it | Go to the driver and kernel steps |
sudo libinput debug-events | Events print as you touch the pad, so the settings are the problem | No events means the problem is below libinput, in the kernel driver |
Step 1: check whether the kernel sees the touchpad
Open a terminal with the keyboard (Ctrl+Alt+T on many distributions) and run the commands below.
cat /proc/bus/input/devices | grep -i touchpadsudo dmesg | grep -i touchpad
A line such as SynPS/2 Synaptics TouchPad means the kernel has registered the device.
If nothing appears, the touchpad may be an I2C device that is loaded under a different name, so also try grep -i -E "touchpad|syna|elan" /proc/bus/input/devices.
Step 2: check what libinput sees
Run sudo libinput list-devices and look for your touchpad and its Capabilities line.
Then run sudo libinput debug-events and move a finger across the pad.
If events scroll past, libinput is fine and the cause is a setting or the desktop; if nothing appears, the problem sits at the kernel driver level, so skip ahead to Steps 6 to 8.
The libinput project documents debug-events and libinput record in its bug-reporting guide.
Step 3: make sure the touchpad is not switched off in settings
On Ubuntu 24.04 with GNOME, open Settings, choose Mouse & Keyboard, switch to the Touchpad tab and check that the Touchpad toggle is on.
On KDE Plasma, open System Settings and go to Input Devices, then Touchpad.
On GNOME you can also check the stored value from a terminal.
- See the current value:
gsettings get org.gnome.desktop.peripherals.touchpad send-events - Re-enable the touchpad:
gsettings reset org.gnome.desktop.peripherals.touchpad send-events
The value disabled means the touchpad was turned off on purpose or by accident.
Also look for the “disabled on external mouse” mode in libinput’s configuration options, which silences the pad whenever a USB or wireless mouse is plugged in.
Step 4: rule out a hardware switch or BIOS setting
Some laptops turn the touchpad off with the Fn key plus one of the function keys, so check your laptop manual for the exact combination.
Next, restart and open the BIOS or UEFI setup, using the key your laptop shows at startup (often F2 or Del).
Look for an entry named Internal Pointing Device, Touchpad or Trackpad and make sure it is enabled.
If the BIOS offers an update, read your maker’s notes first, because some touchpad problems come from firmware bugs.
Step 5: use libinput, not the old Synaptics driver
Modern distributions use libinput by default, and the older Synaptics X driver is deprecated.
On Wayland, which is the default on current Ubuntu and Fedora GNOME sessions, libinput is always used, so Xorg driver packages make no difference.
You can see which session you are in with echo $XDG_SESSION_TYPE.
On an X11 session, grep -i "Using input driver" /var/log/Xorg.0.log shows which driver grabbed the touchpad.
Note: xinput only works under X11, so on Wayland it will not list or toggle your touchpad.
If you need persistent X11 settings, a libinput file in /etc/X11/xorg.conf.d/ such as 40-libinput.conf with MatchIsTouchpad "on" and MatchDriver "libinput" is the approach used by current guides.
Step 6: reload the driver if it breaks after suspend
If the touchpad works after boot but dies after the laptop wakes, reload its driver module.
- PS/2 touchpads:
sudo modprobe -r psmouse && sudo modprobe psmouse - I2C touchpads:
sudo modprobe -r i2c_hid_acpithensudo modprobe i2c_hid_acpi
A Framework Laptop 13 owner reported that the I2C reload brought back scrolling and clicks after suspend.
It is not a guaranteed cure, because a Fedora user with a Synaptics SYNA3602 pad found that the same reload did nothing.
Step 7: try a kernel parameter on stubborn laptops
Kernel parameters are added to the GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub, then GRUB must be regenerated the way your distribution documents.
| Parameter | What it does | Reported result |
|---|---|---|
i8042.nopnp=1 | Stops the i8042 driver from using ACPI PnP to find the keyboard and mouse ports | One IdeaPad 5 owner reported a working touchpad after adding it, but was unsure it was permanent |
i8042.noaux | Skips the check for the auxiliary (mouse) port | Listed in the kernel docs; try only if you know why |
i8042.nomux | Skips the check for a multiplexing controller | Listed in the kernel docs; try only if you know why |
The full list is in the kernel’s kernel-parameters documentation.
Warning: do not paste random pci= options from forums, because one user who tried pci=nocrs on a modern UEFI laptop ended up with a system that would not boot.
Step 8: test another kernel or a live USB
Boot a live USB of your distribution and test the touchpad there.
If it works on the live USB, your installed system has a configuration problem; if it fails there too, suspect the kernel or the hardware.
Regressions do happen: on Fedora, one user reported kernel 5.16 working while 5.17.4 and 5.17.5 failed, so booting an older or newer kernel from the GRUB menu is a fair test.
ELAN and newer AMD-based laptops are the models most often reported with compatibility problems, so a recent kernel and updated firmware packages matter most there.
Which fix matches your symptom?
| Symptom | Most likely cause | Try |
|---|---|---|
No touchpad line in dmesg or /proc/bus/input/devices | Driver, firmware or BIOS setting | Steps 4, 7 and 8 |
| Listed by libinput but no events | Kernel driver problem | Steps 6 and 8 |
| Events show but the pointer does not move | Settings or desktop issue | Step 3 |
| Works until a USB mouse is plugged in | Disabled on external mouse mode | Step 3 |
| Dies after suspend | I2C or PS/2 driver not resuming | Step 6 |
xinput shows nothing | You are on Wayland | Step 5 |
What if nothing works?
Save a recording with sudo libinput record and your dmesg output, because the libinput project says a recording is the most useful attachment for a touchpad bug report.
Then report the problem to your distribution or the kernel bug tracker with your laptop model and kernel version from uname -r.
Meanwhile, a USB or Bluetooth mouse keeps you working, and our guide to fixing a slow cursor covers mouse tuning.
Related Linux guides on this site include fixing no sound in Ubuntu and GNOME keyboard shortcuts, which help while the touchpad is down.
In my case on a Toshiba Satellite, the trackpad would automatically scroll back to the top of the page whether it was a webpage, document or terminal when scrolling with trackpad or navigating with page down button. My fix was toggling scroll lock. Must have unintentionally toggled scroll lock off at some point.
My solution for Lenovo notebook to switch touchpad ON/OFF
Pressing “F6” key
I have a strange situation: My touchpad does appear in the input list(ELAN touchpad), but not only do all of the ‘xserver-org-input-‘ commands say “command not” found even when my touchpad is working(after having to reboot my device), but ‘/etc/X11/xorg.conf.d/’ does not have any files in that folder on my device. It’s empty. Even stranger is that when I run the ‘journalctl -b | grep -i’ command, terminal gives no output, even though it’s in the input list as I said earlier. I also tried restarting Drivers with ‘sudo mobprobe -reset mouse’ and then ‘sudo mobprobe mouse’. That command doesn’t look like it works because using it(when my touchpad does work) does not require installing to enable my touchpad(using ‘sudo modprobe mouse’).
I have a strange situation: My touchpad does appear in the input list(ELAN touchpad), but not only do all of the xserver-org-input- commands say “command not” found, even when my touchpad is working(after having to reboot my device), but /etc/X11/xorg.conf.d/ does not have any files in that folder on my device. It’s empty.