|Date Added:||8 December 2004|
|File Size:||28.33 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
My theory is that the mouse1 input is what creates clicks, and that is not being registered. Partners Support Community Ubuntu. This is pro, dude. Adding extended input device “eGalax Inc.
May 16th, 3. Sometimes it goes silent but when I touch the screen it always pulls back to there. Nope, a ferrite core is just for EM noise reduction.
Hey Black God, thanks for the tutorial this looks like a really fun project! I’d love to uninstall the original eGalax driver When I click the top left of the screen, the mouse moves to somewhere in the middle of the screen.
Post as a guest Name.
How to get eGalax TouchScreen film (0eef) working in Linux for Raspberry Pi – Black God
The same device 0eef: Now it is time to edit xorg. Inappropriate ioctl for device. Configuring as touchscreen [ Sign up using Facebook. The device has an integrated serial touchscreen, and the manufacturer is notorious for hiding any and all documentation on legacy devices such as this one. With a normal host-device cable, something like this can’t happen. Thank you for answer!
Flipping the USB was a confounding factor, but the problem is that the monitor is a budget monitor and the actual screen moves around inside of the monitor’s housing. Looks like it’s time for a return.
Unable to query fd: Vendor 0xeef Product 0x1 [ I placed calibration values for my XR-1 in both GDM and as a gnome startup script, since it uses automatic login: While reversing the cable I must have moved the monitor around into a position in which it worked.
If your touchscreen has an USB interface, and it isn’t working, then you may need to blacklist the usbtouchscreen driver for it to work: Your email address will not be published.
eGalax Touchscreens in 14.04LTS
Yeah that’s why I didn’t try this for so long – thought the cable was identical both ways. Join Date Nov Beans I’m just curious, that’s the first time I’ve ever heard of such a behaviour caused by reversing a cable.
The methods documented here should work with other distros as well.