[WinBook TW102] Touch inputs not detected

Bug #1874862 reported by Will Ethridge
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

touch inputs are not detected by Ubuntu on this tablet. I'm not sure the touch screen hardware is detected at all by Ubuntu. I tried cat /dev/input/eventX (replacing X with every option listed) and not once got any reaction to touching the screen.

I can provide more information and troubleshooting if asked, I just need to know what to look for.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.5.0-050500-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 13:27:45 2020
DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
InstallationDate: Installed on 2020-01-22 (92 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 0603:0002 Novatek Microelectronics Corp.
 Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M
     |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
         |__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
         |__ Port 2: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
MachineType: MicroElectronics TW102
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-01-26 (88 days ago)
dmi.bios.date: 03/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8.17
dmi.board.asset.tag: Default string
dmi.board.name: H8811C
dmi.board.vendor: EMDOOR
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: EMDOOR
dmi.chassis.version: 1
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1:
dmi.product.family: WinBook
dmi.product.name: TW102
dmi.product.sku: 585497
dmi.product.version: 1
dmi.sys.vendor: MicroElectronics
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Will Ethridge (gamerminstrel) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you give the output of

$ libinput-list-devices

and also add the 'journalctl -b 0' log from the machine having the issue?

Changed in xorg (Ubuntu):
status: New → Incomplete
summary: - Touch inputs not detected
+ [WinBook TW102] Touch inputs not detected
affects: xorg (Ubuntu) → linux (Ubuntu)
Changed in libinput (Ubuntu):
status: New → Incomplete
You-Sheng Yang (vicamo)
tags: added: hwe-touchpad
Revision history for this message
You-Sheng Yang (vicamo) wrote :

[ 7.359634] silead_ts i2c-MSSL1680:00: Direct firmware load for silead/mssl1680.fw failed with error -2
[ 7.359647] silead_ts i2c-MSSL1680:00: Firmware request error -2

https://github.com/edward-p/mssl1680-firmware/blob/master/mssl1680.fw
Please try to save the firmware blob as /lib/firmware/KERNEL_VERIZON/silead/mssl1680.fw and reboot.

Revision history for this message
Will Ethridge (gamerminstrel) wrote :

I have attached a text file containing output from the libinput command. Journalctl coming next.

Also @vicamo, I have downloaded the firmware file you provided and placed it as you requested. After rebooting, there was no visible change in performance.

Revision history for this message
Will Ethridge (gamerminstrel) wrote :
Changed in libinput (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
You-Sheng Yang (vicamo) wrote :

kernel: silead_ts i2c-MSSL1680:00: Direct firmware load for silead/mssl1680.fw failed with error -2
kernel: silead_ts i2c-MSSL1680:00: Firmware request error -2

Log in comment #5 says fw blob is not in position. What is the output of following command?

  $ ls- al /lib/firmware/$(uname -r)/silead/mssl1680.fw

Revision history for this message
You-Sheng Yang (vicamo) wrote :

Sorry, it's "ls -al".

no longer affects: libinput (Ubuntu)
Revision history for this message
Will Ethridge (gamerminstrel) wrote :

I apologize for the slow reply, a lot of stuff has been going on, and I hit a snag. The device in question no longer boots reliably. I have not been able to confirm, but I believe that the internal wifi chip is failing, and when the device loads the wifi driver in the boot process it crashes. If I cannot aid in troubleshooting, should we close this bug report or leave it open in the hopes someone else with this tablet will come along?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.