0408:3003 Quanta Computer, Inc. Touchscreen Controller Detected But Doesn't Work

[jimlovell777]

I purchased a touchscreen computer that uses a 0408:3003 Quanta Computer, Inc. optical multi-touch touchscreen controller but the touch feature does not work. I've updated the BIOS to the latest version. I've tried multiple kernels, drivers, distros and none fixed the issue or worked. The touchscreen works under Windows version 7 and up with without manually installing a driver.

The touchscreen is detected and shows up when checking lsusb, xinput_calibrator, xinput --list, and dmesg -- all with no errors that I can see.

In another bug for this controller user elmarikon suggested the following and it did eventually allow single touches to work but the fix is not persistent across reboots.
xinput set-mode 13 RELATIVE
xinput set-mode 13 ABSOLUTE
sudo rmmod hid-multitouch
sudo modprobe hid-multitouch

Ubuntu Version (lsb_release -rd)
    Description: Ubuntu 15.10
    Release: 15.10
    Wily

Kernel Version (cat /proc/version_signature)
    Ubuntu 4.2.0-17.21-generic 4.2.3

xinput --list
    ↳ Quanta Computer OpticalTouchScreen id=12 [slave pointer (2)]

lsusb
    Bus 001 Device 005: ID 0408:3003 Quanta Computer, Inc.

lsmod
    hid 118784 7 hid_multitouch,usbhid,hid_logitech_dj,hid_logitech_hidpp

dmesg (most recent output after many attempts following elmarikon's "fix")
    input: Quanta Computer OpticalTouchScreen as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:0408:3003.0007/input/input16
    hid-multitouch 0003:0408:3003.0007: input,hiddev0,hidraw4: USB HID v1.10 Mouse [Quanta Computer OpticalTouchScreen] on usb-0000:00:1a.0-1.6/input0
    hid-multitouch 0003:0408:3003.0007: usb_submit_urb(ctrl) failed: -1
    hid-multitouch 0003:0408:3003.0007: usb_submit_urb(ctrl) failed: -1

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-17-generic 4.2.0-17.21
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: portal 1106 F.... pulseaudio
 /dev/snd/controlC0: portal 1106 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Nov 8 23:34:40 2015
HibernationDevice: RESUME=UUID=72107d2b-667e-4e55-9eab-dfc18a940de3
InstallationDate: Installed on 2015-11-09 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Gateway ZX6961
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic.efi.signed root=UUID=fc9edda2-408b-4a6d-8733-525acc239e95 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-17-generic N/A
 linux-backports-modules-4.2.0-17-generic N/A
 linux-firmware 1.149.2
RfKill:

SourcePackage: linux
StagingDrivers: r8712u
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P01-B3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: ZX6961
dmi.board.vendor: Gateway
dmi.chassis.type: 13
dmi.chassis.vendor: Gateway
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B3:bd07/22/2011:svnGateway:pnZX6961:pvr:rvnGateway:rnZX6961:rvr:cvnGateway:ct13:cvr:
dmi.product.name: ZX6961
dmi.sys.vendor: Gateway

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

jimlovell777, thank you for reporting this and helping make Ubuntu better.

Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[jimlovell777 (jimlovell777)]

I downloaded and installed the files from the link you provided then booted using the new kernel. It did not fix the issue.

:~$ uname -r
4.3.0-040300-generic

Actual packages used
linux-image-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb
linux-headers-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb
linux-headers-4.3.0-040300_4.3.0-040300.201511020949_all.deb

[penalvch (penalvch)]

jimlovell777, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue (Dmitry Torokhov CC linux-input)?

Please provide a direct URL to your newly made report when it becomes available so that it may be tracked.

Thank you for your understanding.

[jimlovell777 (jimlovell777)]

The upstream bug report has been created.
http://www.spinics.net/lists/linux-input/msg41975.html

[jimlovell777 (jimlovell777)]

Should I have heard something regarding the upstream bug report? In other words, how can I tell if I did everything properly and it's in someone else's hands for now?