Quanta Optical touchscreen recognized as usb but not as input device

[Maarten Wisse]

I bought a IIyama T2250MTS touchscreen with a Quanta Optical screen in it that is attached through USB. It fails to register as a hiddev at kernel level with the following message:

[21071.312190] usbhid 1-12.2:1.0: can't add hid device: -110
[21071.312219] usbhid: probe of 1-12.2:1.0 failed with error -110

Looking into kernel.log shows the same message. Device is seen, udev tries to link it to the kernel module and this fails.

I tried all sort of things:

sudo modprobe hid-multitouch (this seems the new module that supports it, since hid-quanta has been dropped from the kernel after 3.2)

The module loads, but the device is not recognized.

It does appear in lsusb:

Bus 001 Device 011: ID 0408:3000 Quanta Computer, Inc. Optical dual-touch panel

xinput --list does not see it:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PixArt USB Optical Mouse id=9 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Power Button id=7 [slave keyboard (3)]
    ↳ Sleep Button id=8 [slave keyboard (3)]
    ↳ UVC Camera (046d:0821) id=10 [slave keyboard (3)]
    ↳ DELL Dell USB Entry Keyboard id=11 [slave keyboard (3)]

There haven't been bug reports on Quanta touchscreens for years. My problem seems most similar to this one:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514310

O yes and the device properly works on Windows 10... I've exchanged the USB cable for another one. No solution.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-36-generic 4.13.0-36.40
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: maarten 1288 F.... pulseaudio
 /dev/snd/controlC1: maarten 1288 F.... pulseaudio
 /dev/snd/controlC2: maarten 1288 F.... pulseaudio
 /dev/snd/controlC0: maarten 1288 F.... pulseaudio
CurrentDesktop: KDE
Date: Mon Mar 5 14:49:49 2018
HibernationDevice: RESUME=UUID=419dcb02-2bfc-4caf-8e07-3bf2c1faf2a2
InstallationDate: Installed on 2016-12-30 (429 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
IwConfig:
 enp5s0 no wireless extensions.

 lo no wireless extensions.
MachineType: MSI MS-7971
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=6bc48507-dba2-4e26-beb8-4d999a7aa978 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-36-generic N/A
 linux-backports-modules-4.13.0-36-generic N/A
 linux-firmware 1.169.3
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-26 (130 days ago)
dmi.bios.date: 05/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C.70
dmi.board.asset.tag: Default string
dmi.board.name: B150 PC MATE (MS-7971)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.70:bd05/23/2016:svnMSI:pnMS-7971:pvr2.0:rvnMSI:rnB150PCMATE(MS-7971):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.family: Default string
dmi.product.name: MS-7971
dmi.product.version: 2.0
dmi.sys.vendor: MSI

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc4

[Maarten Wisse (pmwisse)]

The mainline kernel does not fix the bug. My problem is, I do not know how to add a tag in Launchpad. It is a long time ago since I did this... and the help I get from the internet suggests there is an 'add tag' button on top of the page, but there isn't. So maybe I do not have the rights to add tags?

I could not extensively test the mainline kernel because X did not start fully, with strange resolution and Plasma did not start. But I could go to console mode, where I could look at dmesg etc and see that the exact same message popped up during boot and in dmesg.

I mark the bug as confirmed though, but would like to know how to tag it.

[Maarten Wisse (pmwisse)]

Ok, sorry, I see that I have added the tag.

[Maarten Wisse (pmwisse)]

In the meantime, I have switched my graphics to the internal Intel. This will make it a lot easier to install custom kernels because I will no longer depend on the nouveau or nvidia drivers.

[Maarten Wisse (pmwisse)]

This turned out to be a hardware bug.