top of page
serlighsinfmonsmec

Egalax touch driver linux arm: Troubleshooting common issues and errors



Out of the box when I boot up with the device plugged in, the usbtouchscreen module handles the device and creates two inputs: /dev/input/event3 and /dev/input/mouse1. Xorg registers the event3 input and I am able to interact via touch with the system, but not in a way that I'd expect. I cannot click on anything, only move the mouse around. It also does not register the mouse1 input due to no driver found (more details in log outputs below). Touches register mostly everywhere on the screen except for the extreme corners, but the mouse moves back to near the bottom left corner after every touch. When I say near the bottom left corner, I mean about 1/8th of the screen away from the actual corner on both axes. After putting in the Xorg config to swap and invert axes into 10-evdev.conf:


I have tried following the EETI guide to install their proprietary driver, located at _Linux.html. I downloaded the eGTouch_v2.5.5814.L-ma file, tweaked the 4 kernel settings they recommended, applied the source code patches for kernel versions 2.6+, and built. When I put the kernel onto my Pi SD and booted, the event3 and mouse1 weren't created because they had me remove usbtouchscreen from the kernel. The guide said I was supposed to see my eGalax touch screen with no handlers (as opposed to mouse1 and event3 I was seeing before) when I ran cat /proc/bus/input/devices but it didn't show up at all. I additionally am not able to interact at all via touch in this setup.




egalax touch driver linux arm




If you ever tried to set up a touchscreen device in linux, you might have noticed that it is either working out of the box (besides some calibration) or is very tedious, especially when it is not supported by the kernel.


Touchegg is a multitouch gesture program, only compatible with X, that runs as a user in the background, recognizes gestures, and translates them to more conventional events such as mouse wheel movements, so that you can for example use two fingers to scroll. But it also interferes with applications or window managers which already do their own gesture recognition. If you have both a touchpad and a touchscreen, and if the touchpad driver (such as synaptics or libinput) has been configured not to recognize gestures itself, but to pass through the multi-touch events, then Touchegg will recognize gestures on both: this cannot be configured. In fact it does a better job of recognizing gestures than either the synaptics or libinput touchpad drivers; but on the touchscreen, it is generally better for applications to respond to touch in their own unique ways. Some Qt and GTK applications do that, but they will not be able to if you have Touchegg "eating" the touch events. So, Touchegg is useful when you are running mainly legacy applications which do not make their own use of touch events.


I'm trying a Egalax touchscreen to work for a TPV on Ubuntu 18.04, but everything I tried didnt work at all. I tried to make it work with "calibrate touchscreen" as Ubuntu seems to detect the screen correctly, but no input at all from calibration.I tried with the Egalax driver as this tutorial:


So that should have the effect of make a fake serial link, connect the touchscreen to one end (ttyVA00) and the driver to the other end (ttyVB00). Then I can feed nulls or something into ttyVA00 in order to keep traffic on the link, and thus stop it from being removed.


Although I got what I expected from ttyVB00, by catting it and touching the screen and seeing the traffic, the driver did not want to see it. It just stops at Entering EndlessScanLoop so I am guessing it is querying something from the touchscreen and socat is messing with that data somehow.


you can download the LibreELEC 7.0.1 image with egalax support and tslib integration for Faytech touchscreens here-> it should work out of the box, if there is a calibration problem just go to programm section and start the calibration addon and touch the five crosses (do not plug in any keybord or other USB device before Kodi is loaded, except WiFi)


Our 5 inch screen supports Raspbian,Ubuntu Mate,Kali Linux and Retropie system for Raspberry Pi.If you use it on PC or others that the touch function is unable to use.And next, we will teach you how to install the driver for your raspberry pi OS. If no system in your SD card, please refer to the Raspberry Pi office tutorial. Step1: Install the 5 inch LCD


Never mind the above comment! I managed to add the external driver, re-build my kernel and image, and the touchscreen is now working perfectly! For anyone else that is struggling to incorporate an out-of-device-tree driver in their OE build, the (very) high level steps are as follows:


* Input: Handle EV_PWR type of input caps in input_set_capability. * Input: jornada680_kbd - fix default keymap * increase PNP_MAX_PORT to 40 from 24 * sched: fix gcc warnings * leds: Fix leds_list_lock locking issues * leds: Fix locomo LED driver oops * x86: fix asm-x86/byteorder.h for userspace export * x86: fix asm-x86/msr.h for user-space export * ACPI: EC: Enable boot EC before bus_scan * ACPI: Make sysfs interface in ACPI power optional. * fix lguest rmmod "bad pgd" * slub: provide /proc/slabinfo * [POWERPC] Fix build failure on Cell when CONFIG_SPU_FS=y * slub: register slabinfo to procfs * [SCSI] scsi_sysfs: restore prep_fn when ULD is removed * Unify /proc/slabinfo configuration * scsi: revert "[SCSI] Get rid of scsi_cmnd->done" * restrict reading from /proc//maps to those who share ->mm or can ptrace pid * Fix kernel/ptrace.c compile problem (missing "may_attach()") * hwmon: (w83627ehf) Be more careful when changing VID input level * NFS: Fix a possible Oops in fs/nfs/super.c * NFSv4: Fix circular locking dependency in nfs4_kill_renewd * NFS: add newline to kernel warning message in auth_gss code * NFSv4: nfs4_open_confirm must not set the open_owner as confirmed on error * NFSv4: Fix open_to_lock_owner sequenceid allocation... * gameport: don't export functions that are static inline * Input: spitzkbd - fix suspend key handling * Input: pass EV_PWR events to event handlers * [ARM] 4735/1: Unbreak pxa25x suspend/resume * IB/srp: Fix list corruption/oops on module reload * Console is utf-8 by default * [IA64] Update Altix BTE error return status patch * [IA64] Update Altix nofault code * [X25]: Add missing x25_neigh_put * [XFRM]: Do not define km_migrate() if !CONFIG_XFRM_MIGRATE * [CASSINI]: Fix endianness bug. * [CASSINI]: Revert 'dont touch page_count'. * [CASSINI]: Program parent Inte... 2ff7e9595c


0 views0 comments

Recent Posts

See All

Comments


!
Widget Didn’t Load
Check your internet and refresh this page.
If that doesn’t work, contact us.
bottom of page