You are not logged in.
Hi,
With the upgrade over the weekend of xorg (sorry, can't give exact version numbers at the moment - did a full system rebuild and lost a lot of info), my touch screen stopped working. It is an eGalax Dwav Scientific device vid:pid: 0eef 7302. I noticed in my dmesg output that the driver (xf86-input-egalax) was segfaulting so I downgraded my xorg.
While the downgrade stopped the driver segfaulting, touch did not return. I checked all configs and considering the only package change was xorg, it seemed odd that the downgrade did not resolve the issue.
Out of curiosity, I restored windows to the device (acer iconia tab) to confirm the screen itself has not died. Touch worked on windows (phew, not a warranty job).
On re-installing arch, I am back to the same issue, but today, with the kernel and udev upgrade, lsusb is no longer including this device in it's output, so the problem has gone from bad to worse. The device is no longer recognised by the kernel/udev on boot.
Is anyone aware if the touch input stack in the kernel has changed again, or of any other reason my touch screen device (which up until now has been recognised by all kernels from late 2.6 series until 3.3.5? 3.3.6?) is no onger being recognised? Also, has the xorg input stack changed as well, thus rendering my device useless?
Hoping someone can shed some light on this.
Cheers.
Last edited by Padfoot (2012-05-25 12:24:50)
Offline
Ok, this is very strange. I decided I would roll back my packages about 1 week and the system was certainly in a working state then. I turned on the tablet and lo and behold, touch was working, the device listed in lsusb. So I tried re-installing the device driver to get access to multitouch, restarted and no touch again. The device is not recognised again. Removed the driver, started again and, no still not recognised.
Something fishy is going on with hardware detection. The device is randomly recognised and ignored........
This is getting very annoying....have been working on fixing this since last Saturday......
All help will be gratefully received...this is beginning to drive me insane!
Cheers.
Offline
Ok, I have discovered the issue leading to the random non-discovery of the device. After a boot where the device appeared, lsusb produces the following:
Bus 005 Device 002: ID 0eef:7302 D-WAV Scientific Co., Ltdand dmesg | grep usb
[ 3.540134] usb 5-1: new full-speed USB device number 2 using ohci_hcd
[ 3.918530] usbcore: registered new interface driver usbhid
[ 3.918539] usbhid: USB HID core driver
[ 3.926863] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/input/input1
[ 3.927271] hid-multitouch 0003:0EEF:7302.0001: input,hiddev0,hidraw0: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-0000:00:13.0-1/input0Now, on the occassions where the device is not recognised I get the following:
dmesg | grep usb
[ 4.296742] usb 5-1: device descriptor read/64, error -62
[ 4.533461] usb 5-1: device descriptor read/64, error -62
[ 4.766994] usb 5-1: new full-speed USB device number 4 using ohci_hcd
[ 5.173654] usb 5-1: device not accepting address 4, error -62
[ 5.303761] usb 5-1: new full-speed USB device number 5 using ohci_hcd
[ 5.710269] usb 5-1: device not accepting address 5, error -62
[ 5.710384] hub 5-0:1.0: unable to enumerate USB device on port 1So it seems something is randomly causing the device to not work with the usb drivers.
I read somewhere that disabling ehci_hcd should solve the issue, but looking at the above, it fails with ehci_hcd and ohci_hcd, yet when it works, it uses ohci_hcd.
Hoping someone may have some ideas.
Cheers.
Offline
Marking as solved for now. The USB drivers still seem flakey at best with this device. It appears to have settled a little with kernel 3.4 from testing. As for the multitouch driver (xf86-input-egalax) it is working after downgrading xorg-server to 1.12.1-2. Hoping it is an xorg bug in the latest package that will be corrected in v 1.13.
Cheers.
Offline