Cant get eGalax touchscreen up and running
Home › Forums › GeeXboX for PC › Cant get eGalax touchscreen up and running
Tagged: eGalax touch not working
This topic contains 18 replies, has 3 voices, and was last updated by
sebastian 2 years ago.
-
AuthorPosts
-
Hi there,
I installed Geexbox 3.0 and tried to get an eGalax touch screen (Faytec) up and running. lsusb shows “D-WAV Scientific Co., Ltd eGalax TouchScreen”. I have no idea where to start to look for a reason…
Any help would be appreciated…
tia
Sebastian
search on the forum about egalax, there is a custom xorg.conf uploaded
Hi,
thank you for the answer but I have to admit that I dont understand.
I found http://www.geexbox.org/wp-content/uploads/2011/11/55-touchscreen1.txt and compared it to mine. The only difference I can see is the calibration. I also checked with lsusb (which shows the touchscreen) and evtest (which does not show the touchscreen). Still no reaction to any touch on the screen…
Do you have any further advices?
tia
Sebastian
Hi there again,
it would be great if ANYBODY can give me information. The Geexbox should be a christmas present so I am a bit stressed about this.
I have
searched for the mentioned xorg.conf (-> could not find anything that seems to match the description in the previous post)
checked Xorg.0.log (-> no eGalax mentioned)
checked dmesg (-> eGalax is found and assigned to /devices)
checked lspci -k (-> eGalax device from dmesg found, driver “ehci” assigned)
checked lsusb (-> shows eGalax Touchscreen)
checked evtest (-> does not show eGalax)
installed xinput_calibrator (-> no calibratable device found)
tried to install the eGalax driver and reboot (-> no error message, no touch)
uninstalled eGalax driver and reboot (-> no error message)
found https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/442645Â which mentions a package input-mouse (-> not found, did the rest, no touch)
found http://wiki.linuxmce.org/index.php/Egalax-Touchscreen which mentions a package xserver-xorg-input-evtouch (-> not found), tried the egalax driver howto (-> cant find the mentioned driver)No matter what I do I get no response from the touchscreen.
Any help would be greatly appreciated
Sebastian
will send a mail to the original owner, I can’t help you here for the next days, I’m away …
… but thanks for the effort…
merry christmas to you
Sebastian
Hi Sebastian,
I had some good experiment with tom for the egalax on geexbox v2.
I want to try it on the v3. I didn’t have the time to do it but I will be interested on that.
But currently I’m on holiday, far from the pc with the egalax display.
If you have so patience, We could do it after the 9th January together.
I’m curious if it works on this display.
I which you both a merry Christmas, and good start in new year.
Cemoi
Hi Cemoi,
in the mean time I found that
– eGTouchD is not running after startup (even if set in rc.local). Where should I put it?
– eGTouch—.log showing
[13:09:10:782]-:
   Sun Dec 23 13:09:10 2012
  Â
[13:09:10:782]-:File: read – /etc/eGTouchL.ini
[13:09:10:798]-:Device[0] PID [null] was set to add to module.
[13:09:10:798]-:Device[1] PID [null] was set to add to module.
[13:09:10:798]-:Daemon Version: [2.5.2107]
[13:09:10:798]-: DebugMode[FFFF], ShowDebugPosition[0]
[13:09:10:798]-: MaxDeviceNums[1], ScanInterface[0], DeviceBaudRate[0]
[13:09:10:798]-: UinputPath = /dev/input/uinput
[13:09:10:798]-:Run process as a background daemon
[13:09:10:798]-:===============  Entering GetEnvironment  ===============
[13:09:10:798]-:Entering GetXVersion
[13:09:10:800]-:Command X -version doestn’t support
[13:09:10:800]-:Entering GetKernelVersion
[13:09:10:804]-:Kernel_Version = 3.4.4
[13:09:10:804]-:Entering GetCPUinfo
[13:09:10:808]-:CPU = i686
[13:09:10:808]-:Entering ListEETIUsbDevice
[13:09:11:040]-:All avaialbe connected USB Device #1. PID: 0001
[13:09:11:040]-:————— Done with GetEnvironment  —————
[13:09:11:040]-:File /tmp/TouchPID doesn’t existed
[13:09:11:040]-:New CManager is called.
[13:09:11:040]-:Daemon process ID = [682]
[13:09:11:040]-:Loop in endless scan
[13:09:11:040]-:Entering EndlessScanLoop
[13:09:11:040]-:Entering CheckVIDinlsusb()
[13:09:11:239]-:In lsusb: Get device [0eef]:[0001].
[13:09:11:239]-:Entering AddPIDintoModuleRoutine() with [0eef]:[0001]
[13:09:11:239]-:Entering CheckPIDinInputDevice()
[13:09:11:244]-:Dismatch device [0001]. Didn’t list under cat /proc/bus/input/devices
[13:09:11:255]-:Do modprobe hid-multitouch success
[13:09:11:258]-:Command ls /sys/module/hid_multitouch/drivers/hid:hid-multitouch/ doestn’t support
[13:09:11:258]-:Entering AddPidToModule with VID[0eef] PID[0001]
[13:09:11:259]-:Add deviceID [0eef:0001] into hid-multitouch success
[13:09:11:259]-:Entering CheckIniDevPID
[13:09:14:259]-:Entering CheckVIDinlsusb()
[13:09:14:522]-:In lsusb: Get device [0eef]:[0001].
[13:09:14:522]-:Entering AddPIDintoModuleRoutine() with [0eef]:[0001]
[13:09:14:522]-:Entering CheckPIDinInputDevice()
[13:09:14:527]-:Dismatch device [0001]. Didn’t list under cat /proc/bus/input/devices
[13:09:14:541]-:Do modprobe hid-multitouch success
[13:09:14:545]-:Command ls /sys/module/hid_multitouch/drivers/hid:hid-multitouch/ doestn’t support
[13:09:14:545]-:Entering AddPidToModule with VID[0eef] PID[0001]
[13:09:14:547]-:Add deviceID [0eef:0001] into hid-multitouch success
[13:09:14:547]-:Entering CheckIniDevPID
[13:09:17:547]-:Entering CheckVIDinlsusb()
[13:09:17:816]-:In lsusb: Get device [0eef]:[0001].
[13:09:17:816]-:Entering AddPIDintoModuleRoutine() with [0eef]:[0001]
[13:09:17:816]-:Entering CheckPIDinInputDevice()
[13:09:17:823]-:Dismatch device [0001]. Didn’t list under cat /proc/bus/input/devices
[13:09:17:837]-:Do modprobe hid-multitouch success
[13:09:17:839]-:Command ls /sys/module/hid_multitouch/drivers/hid:hid-multitouch/ doestn’t support
[13:09:17:839]-:Entering AddPidToModule with VID[0eef] PID[0001]
[13:09:17:840]-:Add deviceID [0eef:0001] into hid-multitouch success
[13:09:17:840]-:Entering CheckIniDevPID
[13:09:20:840]-:Entering CheckVIDinlsusb()
[13:09:21:113]-:In lsusb: Get device [0eef]:[0001].
[13:09:21:113]-:Entering AddPIDintoModuleRoutine() with [0eef]:[0001]
[13:09:21:113]-:Entering CheckPIDinInputDevice()
[13:09:21:117]-:Dismatch device [0001]. Didn’t list under cat /proc/bus/input/devices
[13:09:21:131]-:Do modprobe hid-multitouch success
[13:09:21:136]-:Command ls /sys/module/hid_multitouch/drivers/hid:hid-multitouch/ doestn’t support
[13:09:21:136]-:Entering AddPidToModule with VID[0eef] PID[0001]
[13:09:21:137]-:Add deviceID [0eef:0001] into hid-multitouch success
[13:09:21:137]-:Entering CheckIniDevPID
[13:09:24:137]-:Entering CheckVIDinlsusb()
[13:09:24:351]-:In lsusb: Get device [0eef]:[0001].
[13:09:24:351]-:Entering AddPIDintoModuleRoutine() with [0eef]:[0001]
[13:09:24:351]-:Entering CheckPIDinInputDevice()
[13:09:24:356]-:Dismatch device [0001]. Didn’t list under cat /proc/bus/input/devices
[13:09:24:370]-:Do modprobe hid-multitouch success
[13:09:24:372]-:Command ls /sys/module/hid_multitouch/drivers/hid:hid-multitouch/ doestn’t support
[13:09:24:372]-:Entering AddPidToModule with VID[0eef] PID[0001]
[13:09:24:373]-:Add deviceID [0eef:0001] into hid-multitouch success The log file is growing rapidly.
I also send an email with the information to [email protected].
Any help would be great…
tia
Sebastian
Hi Cemoi,
because of christmas I had to find a solution so I stepped back to Geexbox 2.0.1 where the screen works like a charme.
I had to install it to the hdd because my Geforce FX5200 was not supported by the installed package and for replacing it I found no other way than to install it (and therefore replacing my 3.0 installation)
I would prefer GeeXBox 3 over 2 because the computer is in the room of my daughter and version 3 switches of nearly everything if idle so there is a difference in noise (and the possibility of profiles would be really great).
I hope you have time to take a look at it…
… and also merry christmas
Sebastian
Hi to all,
I had a chat with a support guy from eeti.com who told me that the kernel misses the hid-multitouch kernel patch.
I have learnt quite a lot about linux in the last days but recompiling the kernel is way beyond my knowledge. Anyone out there who can help me (and maybe others)?
tia
Sebastian
which patch are you talking about ?
Hi,
the documentation says:
2.1Â Â Â Patch kernel module
To install driver, please check module configuration as below:
Necessary:
1. EVDEV
2. UINPUT
3. HIDRAW ( USB Interface )
4. HID_MULTITOUCH ( USB Interface & Kernel 3.0 upwards )
Remove:
CONFIG_TOUCHSCREEN_USB_COMPOSITE
(USB Interface & PID 0001 controller)tia
Sebastian
ok, where can I find the patch ?
Hi,
I can only point you to the documentation (can be found here). It seems that there is also a newer version available but the documenation is the same…
tia
Sebastian
Hi Tom,
do you have any news about this?
tia
Sebastian
-
AuthorPosts
You must be logged in to reply to this topic.