Chromebook Marasov: Touchpad detected but not working (PIXA2342) – Fix
I ran into an issue with a fresh CachyOS installation on a Chromebook Marasov.
Symptoms
The touchpad was detected correctly by the kernel:
PIXA2342:00 093A:200D Touchpad
The device was also correctly classified as a touchpad:
ID_INPUT=1
ID_INPUT_TOUCHPAD=1
ID_INPUT_TOUCHPAD_INTEGRATION=internal
KDE Plasma detected the touchpad and showed it in the settings.
evtest also reported touch and multitouch events correctly.
However:
- Cursor did not move
- Tap-to-click did not work
- Clicking did not work
- Gestures did not work
In short: the touchpad was fully detected but completely unusable.
Diagnosis
The following tests confirmed that the hardware and kernel driver were working correctly:
sudo evtest /dev/input/event6
Touch events, pressure values and multitouch coordinates were reported correctly.
This suggests that the issue is not hardware-related and occurs somewhere in the libinput layer.
Workaround / Fix
Create the following file:
sudo mkdir -p /etc/libinput
sudo nano /etc/libinput/local-overrides.quirks
Contents:
[PIXA Touchpad]
MatchName=*PIXA*Touchpad*
AttrResolutionHint=31x31
AttrPressureRange=10:8
Reboot the system:
sudo reboot
After reboot the touchpad worked normally:
- Cursor movement works
- Tap-to-click works
- Physical click works
- Gestures work
System Information
Chromebook: Marasov
Touchpad: PIXA2342:00 093A:200D
Kernel: 7.0.11-1-cachyos
Desktop: KDE Plasma (Wayland)
Notes
The workaround was inspired by a similar Chromebook touchpad fix originally posted on the Chrultrabook forum for ELAN devices.
For my PIXA2342 touchpad, simply adapting the quirk to match the PIXA device resolved the issue completely.
It might be worth considering adding a proper libinput quirk upstream for PIXA2342 touchpads so that this works out of the box.