Touchscreen is not working

[avficus]

Hi all.

Mint fan here. My third PC with Linux Mint, regardless I'm not skilled to solve issues.

So, my third PC has a touchscreen and I'm keen to get it to work and use it e.g. for surfing web and use it as standing as A-form with some specific applications.

I have tried help guides from
viewtopic.php?p=2161780&hilit=mssl1680& ... 6#p2161780
viewtopic.php?t=345520
viewtopic.php?t=358364
And section 1 from here https://wiki.archlinux.org/title/Touchscreen

Only change what happened was one line more when launching command "xinput". New line with "xinput" was "silead_ts" under "Virtual Core Pointer".
I also run "xinput test 9" for "silead_ts". Nothing happened.
I also run "dmesg | grep -i i2c" and "modprobe Silead", see two screenshots below.

Results of "xinput" and "dmesg | grep -i i2c".

Result of "modprobe Silead".

UEFI lists e.g. "Sliead" (wrong written in UEFI?) and Goodix and few more displays.
I have multi-boot system. "Sliead" is chosen in UEFI and in Windows touchscreen works.
Some notes of Windows HID-compliant touch screen Properties: KMDF Minidriver for Touch I2C Device, MSSL1680.

In addition I also tried Kernel 6.1, not helped. Touchpad was restless and blinking with that version.

Situation now, after I resetted changes back with Timeshift:

Code: Select all

~$ inxi -Fxxxrz
System:
  Kernel: 5.15.0-73-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop Mobo: N/A model: N/A serial: <superuser required>
    UEFI: American Megatrends v: CC-BI-13.3-Y116GRX200-GF56A-218-C
    date: 06/23/2021
Battery:
  ID-1: BAT0 charge: 21.8 Wh (58.9%) condition: 37.0/37.0 Wh (100.0%)
    volts: 7.6 min: N/A model: WB SR 1 WB Lion Battery type: Li-ion
    serial: <filter> status: Discharging
CPU:
  Info: dual core model: Intel Celeron N4020 bits: 64 type: MCP
    smt: <unsupported> arch: Goldmont Plus rev: 8 cache: L1: 112 KiB L2: 4 MiB
  Speed (MHz): avg: 796 min/max: 800/2800 cores: 1: 796 2: 796
    bogomips: 4377
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel GeminiLake [UHD Graphics 600] driver: i915 v: kernel ports:
    active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:3185
    class-ID: 0300
  Device-2: Alcor Micro USB 2.0 Web Camera type: USB driver: uvcvideo
    bus-ID: 1-8:3 chip-ID: 058f:5608 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.7x9.4")
    s-diag: 485mm (19.1")
  Monitor-1: eDP-1 model: LM133LF1L01 res: 1600x900 hz: 60 dpi: 138
    size: 294x165mm (11.6x6.5") diag: 337mm (13.3") modes: 1920x1080
  OpenGL: renderer: Mesa Intel UHD Graphics 600 (GLK 2) v: 4.6 Mesa 22.2.5
    direct render: Yes
Audio:
  Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:0e.0 chip-ID: 8086:3198
    class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-73-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Message: No device data found.
  IF-ID-1: wlx46072418c6ee state: up mac: <filter>
Bluetooth:
  Device-1: Realtek 802.11n WLAN Adapter type: USB driver: btusb,rtw_8723du
    bus-ID: 1-7:2 chip-ID: 0bda:d723 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 4 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
Drives:
  Local Storage: total: 116.48 GiB used: 16.12 GiB (13.8%)
  ID-1: /dev/mmcblk0 vendor: SanDisk model: DA4128 size: 116.48 GiB
    type: SSD serial: <filter> rev: 0x8 scheme: GPT
Partition:
  ID-1: / size: 42.19 GiB used: 16.07 GiB (38.1%) fs: ext4
    dev: /dev/mmcblk0p5
  ID-2: /boot/efi size: 96 MiB used: 56 MiB (58.4%) fs: vfat
    dev: /dev/mmcblk0p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 261.6 MiB (12.8%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 45.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2225 apt: 2217 flatpak: 8
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https://ftp.acc.umu.se/mirror/linuxmint.com/packages vera main upstream import backport
    2: deb http://mirrors.nic.funet.fi/ubuntu jammy main restricted universe multiverse
    3: deb http://mirrors.nic.funet.fi/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://mirrors.nic.funet.fi/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 231 Uptime: 1d 14h 30m wakeups: 9 Memory: 3.65 GiB
  used: 2.75 GiB (75.3%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.3.0 alt: 11/12 Shell: Bash v: 5.1.16 running-in: gnome-terminal
  inxi: 3.3.13

Code: Select all

~$ xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ HTIX5288:00 0911:5288 Mouse             	id=9	[slave  pointer  (2)]
⎜   ↳ HTIX5288:00 0911:5288 Touchpad          	id=10	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Video Bus                               	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ USB 2.0 Web Camera: USB 2.0 Web         	id=8	[slave  keyboard (3)]
    ↳ Intel HID events                        	id=11	[slave  keyboard (3)]
    ↳ Intel HID 5 button array                	id=12	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=13	[slave  keyboard (3)]

Code: Select all

~$ dmesg | grep -i i2c
[ 8971.702881] i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (32/46160)
[ 8971.705950] i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (32/36986)
[ 8971.708949] i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (32/20366)

Command above results a lot of similar lines, but I only pasted three first lines here.

Code: Select all

~$ dmesg | grep Silead

Empty result for command above. At some situation this command gave chip ID number.

Code: Select all

~$ modprobe Silead
modprobe: FATAL: Module Silead not found in directory /lib/modules/5.15.0-73-generic

I hope that someone can help me to get touchscreen working, please.

[SMG]

Only change what happened was one line more when launching command "xinput". New line with "xinput" was "silead_ts" under "Virtual Core Pointer".

Only change what happened when you did what? What change did you make?

If there is more than one setting for the touchscreen, then maybe silead isn't the one you should be using.

Also, if this is a very new laptop, then you need to be using a kernel newer than 5.15.

[avficus]

Hi SMG.

I mean that I followed tips I found and installed Silead mssl1680 firmware. I don't remember which Kernel was in use then.
This Silead firmware is not anymore installed, because I reset computer state with Timeshift.
Should I try install Silead firmware again and boot with Kernel 6.1.0-1013-oem x86_64?

At a moment I have Kernel 6.1.0-1013-oem x86_64 installed, together with 5.15.0-73.
Both works well.

[SMG]

Should I try install Silead firmware again and boot with Kernel 6.1.0-1013-oem x86_64?

I do not see any indication your computer uses Silead so I would not recommend installing firmware for it.

What were the options in the BIOS/UEFI and which one is the current setting? You mentioned Goodix. Maybe that is the setting you should be using? It is hard for me to know because you have not yet told us the brand name of the laptop.

[avficus]

Thank you for your reply.

UEFI menu steps to find select touch panel device:
Chipset -> South cluster configuration -> Touch panel device select
Then there is options:
- Goodix touch device
- Elan tech touch device
- Sliead touch device (wrong written, should be Silead?)
- Focal tech touch device
- None touch device
Now I went all touch panel options through. Tried every option, booted, run inxi (no changes) and Driver Manager (no drivers found). No touch screen.

Touch screen works in Windows.
Windows HID-compliant touch screen Properties:
- General tab: Location: KMDF Minidriver for Touch I2C Device
- Events tab: Information: Device HID\MSSL 1680&Col01\5&19f557a8&0&0000 was migrated.
I thought MSSL 1680 is related to Silead.

This laptop brand and model is Onn. WY133A.
This is unknown brand for me.
I have a doubt that Chuwi could be a same.

[SMG]

UEFI menu steps to find select touch panel device:
Chipset -> South cluster configuration -> Touch panel device select
Then there is options:
- Goodix touch device
- Elan tech touch device
- Sliead touch device (wrong written, should be Silead?)
- Focal tech touch device
- None touch device
Now I went all touch panel options through. Tried every option, booted, run inxi (no changes) and Driver Manager (no drivers found). No touch screen.

Neither inxi or Driver Manager would have the information you need. You need to try those options and then run xinput to see if the touchscreen shows up.

I have no idea why there would be that many options and I have helped people with of all of those except Focal.

I thought MSSL 1680 is related to Silead.

That is the information I found as well. However, that makes it all the more confusing that your system has so many options in the BIOS/UEFI.

[avficus]

I wrote wrong, sorry. I really did run xinput, not inxi, and no changes.

I hope there is something else to try?

[SMG]

Should I try install Silead firmware again and boot with Kernel 6.1.0-1013-oem x86_64?

I didn't notice you posted two different outputs in your first post.

The photos do show silead in xinput. The error message in the photo (silead_ts more touches reported than supported) indicates the current file is being seen, but I've not been able to find information on how to do anything to address the errors.

You can try the newer kernel with the firmware and see if it works or if different error messages happen. (Please do not post photos of terminal output next time. It's easier to reference data posted in code tags.)

[avficus]

So, I run these lines to install Silead firmware. One line at a time.

Code: Select all

cd ~/Downloads && sudo apt-get install -y aria2 unzip
aria2c https://github.com/edward-p/mssl1680-firmware/archive/refs/heads/master.zip
unzip mssl*.zip && cd mssl1680-firmware-master
sudo mkdir /lib/firmware/silead && sudo cp mssl1680.fw /lib/firmware/silead

Then rebooted with 6.1.0 kernel.
Now mouse cursor flashes when moving it. On the screen flashes stripes and bars at times. Right after desktop was loaded, I was almost unable to use mouse or touchpad, because mouse cursor didn't follow my will. Then, after approx. 15 seconds, mouse cursor was easier to move. However, using mouse or touchpad is not easy.
Touchscreen doesn't work.

Here is some command outputs:

Code: Select all

~$ xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ silead_ts                               	id=9	[slave  pointer  (2)]
⎜   ↳ HTIX5288:00 0911:5288 Mouse             	id=10	[slave  pointer  (2)]
⎜   ↳ HTIX5288:00 0911:5288 Touchpad          	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Video Bus                               	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ USB 2.0 Web Camera: USB 2.0 Web         	id=8	[slave  keyboard (3)]
    ↳ Intel HID events                        	id=12	[slave  keyboard (3)]
    ↳ Intel HID 5 button array                	id=13	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=14	[slave  keyboard (3)]

Code: Select all

~$ dmesg | grep -i i2c
[   40.157201] silead_ts i2c-MSSL1680:00: More touches reported then supported 10 > 5
80.414442] i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (32/44110)

Above lines were a lot, but just two different. So I pasted only these two lines, because other were similar.

Code: Select all

~$ dmesg | grep Silead

Above command has no visible output.

Code: Select all

~$ modprobe Silead
modprobe: FATAL: Module Silead not found in directory /lib/modules/6.1.0-1013-oem

Above: I don't know how to place Silead module in right way.

Update:

Code: Select all

~$ dmesg | grep Silead
[    7.740929] silead_ts i2c-MSSL1680:00: Silead chip ID: 0x56810000

Above output came after next reboot.

Mouse cursor is not accurate. It is so bad that it is not possible to File manager safely. Using web browser is possible.

[SMG]

So, I run these lines to install Silead firmware. One line at a time.

Code: Select all

cd ~/Downloads && sudo apt-get install -y aria2 unzip
aria2c https://github.com/edward-p/mssl1680-firmware/archive/refs/heads/master.zip
unzip mssl*.zip && cd mssl1680-firmware-master
sudo mkdir /lib/firmware/silead && sudo cp mssl1680.fw /lib/firmware/silead

Then rebooted with 6.1.0 kernel.

I finally was able to get the right link to find edward-p / mssl1680-firmware repository and found it was archived four years ago.

I see on that page mention of "mouse pointer jumpy" for several versions. I do not know what version you are using (or if it even matters four years later).

Touchscreen doesn't work.

I think you should revert back to your snapshot.

Code: Select all

~$ dmesg | grep -i i2c
[   40.157201] silead_ts i2c-MSSL1680:00: More touches reported then supported 10 > 5
80.414442] i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (32/44110)

Above lines were a lot, but just two different. So I pasted only these two lines, because other were similar.

From my earlier searches, the second line is for the touchpad. It is not for the touchscreen.

I found cases where people were having issues getting the touchscreen to work in Windows which is usually not a good sign for getting it to work in Linux-based distros. Unfortunately, I do not have any other ideas.

Maybe someone else will have some ideas about getting this silead touchscreen to work on Linux Mint.

[avficus]

I see on that page mention of "mouse pointer jumpy" for several versions. I do not know what version you are using (or if it even matters four years later).

I don't know how to check that version. I don't want to search around using file manager with jumpy mouse pointer. But as you said, it may be doesn't matter.

From my earlier searches, the second line is for the touchpad. It is not for the touchscreen.

I agree.

Unfortunately, I do not have any other ideas.

Thank you a lot for trying.

Maybe someone else will have some ideas about getting this silead touchscreen to work on Linux Mint.

I hope so. That would be nice.

[avficus]

I wanted to tell this new information if this could solve something.

This is dual boot system. Today, when I booted into Windows, touchscreen is not working there anymore. Before I installed Mint and tried to get touchscreen working in Mint, it worked in Windows.

I went to Windows Device Manager -> Human Interface Devices -> KMDF HID Minidriver for Touch I2C Device (there is a yellow attention mark/triangle, to indicate problem with a device). I opened device properties.
General tab has following information:
- Manufacturer: Sileadinc.com
- Location: on Intel Serial IO I2C Host Controller - 31B4
- Device status: This device cannot find enough free resources that it can use. (Code 12)
If you want to use this device, you will need to disable one of the other devices on this system.

For me it seems that installing Mint and trying to get touchscreen to work in Mint, has affected to touchscreen settings in Windows.
Could it be possible?
Do you get any ideas, what to do?

[SMG]

For me it seems that installing Mint and trying to get touchscreen to work in Mint, has affected to touchscreen settings in Windows.
Could it be possible?
Do you get any ideas, what to do?

One idea is to research the error message because it is a Windows error message and this is a Linux Mint forum.

Here is Code 12, This device cannot find enough free resources that it can use with possible options you can try to clear your Windows problem.

The operating systems are completely separate. The only common piece is the BIOS/UEFI. If you didn't change anything in the BIOS/UEFI, then this message has nothing to do with you installing Linux Mint.