[SOLVED] Kernel 3.2.1 and USB Touchscreen Failure

Question

With the upgrade from linux 3.1.9 to 3.2.1, my touchscreen device is no longer recognised.
Hoping someone may be able to shed some light on the situation.
Here are my Xorg logs for both kernels:
http://home.exetel.com.au/padfoot/logs/xorg.log.3.1.9
http://home.exetel.com.au/padfoot/logs/xorg.log.3.2.1
xinput list for 3.1.9
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SONiX USB Keyboard id=12 [slave pointer (2)]
⎜ ↳ eGalaxTouch Virtual Device for Multi id=14 [slave pointer (2)]
⎜ ↳ eGalaxTouch Virtual Device for Single id=15 [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)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ 1.3M Rear id=9 [slave keyboard (3)]
↳ 1.3M Front id=10 [slave keyboard (3)]
↳ SONiX USB Keyboard id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
xinput list for 3.2.1
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SONiX USB Keyboard id=12 [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)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ 1.3M Rear id=9 [slave keyboard (3)]
↳ 1.3M Front id=10 [slave keyboard (3)]
↳ SONiX USB Keyboard id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
↳ Acer WMI hotkeys id=14 [slave keyboard (3)]
dmesg extract for 3.1.9
[ 4.920911] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/input/input10
[ 4.923565] generic-usb 0003:0EEF:7302.0001: input,hiddev0,hidraw0: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-0000:00:13.0-1/input0
[ 7.701218] input: eGalaxTouch Virtual Device for Multi as /devices/virtual/input/input13
[ 7.701692] input: eGalaxTouch Virtual Device for Single as /devices/virtual/input/input14
dmesg extract for 3.2.1
[ 3.853443] usb 5-1: new full-speed USB device number 2 using ohci_hcd
[ 3.990164] usb 5-1: device descriptor read/64, error -62
[ 4.226771] usb 5-1: device descriptor read/64, error -62
[ 4.460091] usb 5-1: new full-speed USB device number 3 using ohci_hcd
[ 4.593421] usb 5-1: device descriptor read/64, error -62
[ 4.830326] usb 5-1: device descriptor read/64, error -62
[ 5.063660] usb 5-1: new full-speed USB device number 4 using ohci_hcd
[ 5.470315] usb 5-1: device not accepting address 4, error -62
[ 5.600320] usb 5-1: new full-speed USB device number 5 using ohci_hcd
[ 6.006989] usb 5-1: device not accepting address 5, error -62
[ 6.256982] usb 5-5: new full-speed USB device number 6 using ohci_hcd
Holding off on upgrading to kernel 3.2 until this can be resolved
Appreciate your help.
Cheers.
Last edited by Padfoot (2012-01-21 01:35:03)

Answer 1

Ok, I have the solution. Multitouch is now working with kernel 3.2.1. It seems the kernel devs are separating multitouch devices from the generic input stack as they can cause issues. Here is the reply I got from the linux-input mailing list:
Well, many eGalax devices are multitouch devices, and can not be
handled by the generic input hid layer without having strange issues.
We have a patch in 3.2 that auto detect such devices and release them
from the generic input stack.
Then, it's easier for people to handle the devices through
hid-multitouch as the recompilation of the kernel is not required
anymore.
I also submitted a patch to catch multitouch devices in
hid-multitouch, but it has not been accepted as it would require
everybody to load hid-multitouch for every hid device.
To enable your device, do (as root)
# modprobe hid-multitouch
# echo 3 VID PID 104 >
/sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id
where:
- 3 is the bus, usb here
- VID: vendor ID (must be 0eef in your case)
- PID: product ID
- 104 is the number of the right class of multitouch device to use
(see MT_CLS_* definitions in hid-multitouch)
VID/PID  can be retrieved from lsusb.
If it's working, then you should also give us your PID so that we can
add it in the source of hid-multitouch.
So, I did the following to enable multitouch:
1. Before upgrading your kernel (should also work after, but may as well be prepared):
# lsusb
Bus 005 Device 002: ID 0eef:7302 D-WAV Scientific Co., Ltd
VID is 0eef
PID is 7302
2. Now we need to get the MT_CLS_* definition for our device (extracted from http://lxr.free-electrons.com/source/dr … titouch.c)
86
87 /* classes of device behavior */
88 #define MT_CLS_DEFAULT 0x0001
89
90 #define MT_CLS_SERIAL 0x0002
91 #define MT_CLS_CONFIDENCE 0x0003
92 #define MT_CLS_CONFIDENCE_MINUS_ONE 0x0004
93 #define MT_CLS_DUAL_INRANGE_CONTACTID 0x0005
94 #define MT_CLS_DUAL_INRANGE_CONTACTNUMBER 0x0006
95 #define MT_CLS_DUAL_NSMU_CONTACTID 0x0007
96
97 /* vendor specific classes */
98 #define MT_CLS_3M 0x0101
99 #define MT_CLS_CYPRESS 0x0102
100 #define MT_CLS_EGALAX 0x0103
101
I have an eGalax device, so I need MT_CLS_* = 0x0103 (259 in decimal)
3. We have all we need to set up the device. Install kernel 3.2.1
# pacman -S linux
4. Start the hid-multitouch module on boot
# nano /etc/rc.conf
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=(hid-multitouch)
Now reboot to see if your device is auto configured with the hid-multitouch module. If so, you are all good to go. If not, continue as follows:
5. Ensure your device details are passed to the hid-multitouch module
# nano /etc/rc.local
echo 3 0eef 7302 259 > /sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id
The command above contains my device details, replace with your details obtained from steps 1 & 2 above:
echo 3 VID PID MT_CLS_*
(If someone can point me in a better direction for setting up these details at boot, it would be appreciated)
Reboot again to see if the device is now working. If not, you may need binary drivers from the vendor. I know in my case, my device needs the eGalax touch daemon driver. A package for this is available in the AUR https://aur.archlinux.org/packages.php?ID=55050
Of course, as the email states, if you have a device that is not automatically configured with the hid-multitouch module, yet it does work after step 5, submit your device details to the linux-input mailing list so it may be added to the source.
Cheers.
Last edited by Padfoot (2012-01-21 01:34:42)