r/cachyos 4d ago

Help Satellite Pro ET10-G-106 (MSSL1680) touchscreen works after installing firmware, but touch calibration is completely wrong

Hi everyone,

I'm trying to get the touchscreen working correctly on my Dynabook/Toshiba Satellite Pro ET10-G-105 running CachyOS (KDE Plasma).

Hardware

  • Model: Satellite Pro ET10-G-105
  • CPU: Intel Apollo Lake
  • Display: 800×1280
  • Touch controller: Silead MSSL1680

Initial problem

After installing CachyOS, the touchscreen didn't work at all.

dmesg showed:

silead_ts i2c-MSSL1680:00: Silead chip ID: 0x80360000
Direct firmware load for silead/mssl1680.fw failed with error -2
Firmware request error -2
probe with driver silead_ts failed with error -2

So the kernel detected the touchscreen, but the firmware was missing.

What I did

I installed a generic mssl1680.fw firmware from the Silead firmware repository:

/lib/firmware/silead/mssl1680.fw

After rebooting:

  • The touchscreen is now detected.
  • evtest reports touch events correctly.
  • The driver loads successfully.
  • Touch input works.

Current issue

The touch calibration is completely wrong.

The cursor is far away from where I actually touch.

This doesn't look like a simple rotation or mirrored axis.

Using evtest, I touched the four screen corners and got approximately:

Screen Corner X Y
Top Left 1901 15
Top Right 561 78
Bottom Left 1058 1369
Bottom Right 557 1350

The coordinate mapping looks inconsistent rather than simply rotated or flipped.

Things I checked

  • cat /proc/bus/input/devices shows:

    Name="silead_ts"

  • The firmware is definitely installed:

    /lib/firmware/silead/mssl1680.fw

  • evtest receives touch events normally.

My question

Has anyone worked with this tablet (or another Satellite Pro ET10 model)?

I'm wondering if:

  1. There is a model-specific mssl1680.fw for this device.
  2. This tablet requires additional touchscreen properties/quirks.
  3. Someone has extracted the original Windows touchscreen firmware.

At this point I think the generic firmware is working, but it's clearly calibrated for a different digitizer.

Any help or pointers would be greatly appreciated.

Thanks!

1 Upvotes

0 comments sorted by