Egalax Inc. Usb Touch Controller Driver
not sure, but it might work with earlier versions. Without installing the eGalaxTouch support I got everything working great with default evdev setup in ubuntu 10.04 adding these two commands to fix the old problems with rotation / swapped axes.
Correct tap behaviour was present out-of-the-box. Xinput set-prop -type=int -format=8 'eGalax Inc. USB TouchController' 'Evdev Axes Swap' 1fixed the swap If Y is inverted: xinput set-int-prop 'eGalax Inc. USB TouchController' 'Evdev Axis Inversion' 8 0 1 and then calibration: xinput set-prop -type=int -format=32 'eGalax Inc. USB TouchController' 'Evdev Axis Calibration' 57 1938 162 1979to get Your own calibration numbers You need this: building from source: #for fresh desktop install You'll need some packages: sudo apt-get install g autoconf libtool xorg-devunpack the calibrator, cd to the folder and run./autogen.sh make cd to the src folder and run./xinputcalibratorx11 do the clicks and it will write Your config to console. Binary built on ubuntu 10.04 32bit 156303. Does not work for me on Lucid Lynx, full updated and a eGalax Touchscreen (xinput name 'eGalax Inc.
I'm facing the same problem as the person above. I have a Lilliput EBY701, using eGalax drivers, on a desktop computer. I can only calibrate to one point, and even before doing this, regardless where I touched, the pointer would remain in the upper-left position of the screen. Could you please mark this thread as unsolved?
Thanks +1 I got a Gigabyte T1028x (eGalax touch screen) and get this 'jump to top left' behaviour since upgrading to 10.04. In 9.10 UNR I got the touch screen working fine using these instructions: I attempted to use those again to no avail in 10.04. I notice that I don't get the 'Calibrate Touchscreen' option under administration anymore either even after following the instructions in the link. Im having some issues after updating too. Xinput set-prop -type=int -format=32 'eGalax Inc.
USB TouchController' 'Evdev Axis Calibration' 57 1938 162 1979 unable to find device eGalax Inc. USB TouchController I tried it through the /dev/input/by-id/usb.etc got the same result using the attatchment calibrator of Naugter recognized the points very good, but didnt seem to write. In 9.10 i ended up manually editing my numbers in the evtouch configuration file. Is that still being used in 10.04? Only way to get the touchscreen work with Lucid for me is to use the original 32Bit beta-driver - 'xinput -list' shows 2 eGalax-devices - deactivate the device managed by evdev (device 13 here)- calibrate with eGalax tool - done. How did u do that? Cause i cant use it at all now.
First of all: using the original egalax driver is suboptimal for me as the touchscreen stops working after a while, using it with easystroke somehow causes the touchscreen to quit working, too. That's the reason I'm trying to get the touchscreen to work with evdev/evtouch. Made my 'Egalax Inc. Touch' (-screen) work with module 'usbtouchscreen': Preferences: Fully updated Ubuntu Lucid Lynx, Samsung NC10, Touchscreen w Xinput-ID 'Egalax Inc. Touch' 1) Edited /etc/default/grub adding 'usbhid.quirks=0xeef:0x1:0x40' to the boot parameters line so it looks like this: GRUBCMDLINELINUXDEFAULT='quiet splash usbhid.quirks=0xeef:0x1:0x40' Then 'sudo update-grub' in (gnome-)terminal. 2) Edited /etc/modules, inserting usbtouchscreen usbhid right after the line containing 'lp'. Important: 'usbtouchscreen' MUST be loaded before 'usbhid' 3) Reboot 4) Calibration using xinputcalibratorx11 from first post in this thread That's it.
The touchscreen seems to work as intended, left-click, moving windows, using easystroke, drawing with xournal - all simple tests are looking good. Does anybody know how to get right-click functionality by touching 3sec. With module usbtouchscreen? All the used hints above were gathered in many searches about the egalax touchscreen, it seems i never tried the right/working combination. In 9.10 UNR I got the touch screen working fine using these instructions: I attempted to use those again to no avail in 10.04. I looked at that link, and it's obvious that it does not work in 10.04 since hal is not used anymore (deprecated) and since they use hal rules inthere.
But I adapted it to 10.04 (with xorg.conf.d) and it works for my touchscreen!!! I have a Samsung Q1 ultra. Hello Cka3o4nik, thanks for all the help from this thread, and the other post you sent on my thread, i've just a request for some more info please. Is there a working Graphic calibration tool specifically for the Samsung Q1 ultra under Ubuntu netwbook Edition 10.04 as you mention the use of one that you had used, or, were the settings in the '11-touchkit.conf' file worked out through personal diagnosis while testing the Q1 Ultra's touch-screen, the reason i ask is, i can't seem to follow or work out what's the Samsung Q1 Ultra's calibration tool that's being refered to in this thread, or it's instructions on how to install it. I just wanted to see if i could get the touch-screen to be a little more precise. Kind regards Livio.
Hello Is there a working Graphic calibration tool specifically for the Samsung Q1 ultra under Ubuntu netwbook Edition 10.04 as you mention the use of one that you had used Oh, there's some misunderstanding. I only referenced border's method to solve the problem.
On my Q1 I just made that config and it helped. I didn't use any calibration tools. Only tried several configs before.
But I seriously doubt someone would develop calibration tool specially for Q1 under Ubuntu. There might be some common tools., or, were the settings in the '11-touchkit.conf' file worked out through personal diagnosis while testing the Q1 Ultra's touch-screen, You should ask the author of config, I suppose:-) the reason i ask is, i can't seem to follow or work out what's the Samsung Q1 Ultra's calibration tool that's being refered to in this thread, or it's instructions on how to install it. I just wanted to see if i could get the touch-screen to be a little more precise.
I also plan to do precise calibration, but later. I need to get WiFi working stable first.
Does your's work properly? Mine looses connection in a minute it connected to network. Getting fresh MadWifi drivers didn't help. Cheers for that Cka3o4nik, i use a UK 'T-Mobile' mobile broadband dongle connection, i just followed the network manager/tools setup process and it setup without a hitch, i've had no issues using this connection, i have had the unit connected by 'Ethernet' and not had problems either, but have not tried a 'Wireless' connection through any network's routers as yet, i will give this a go, i'll try either later tonight or tommorow (Thursday) using a friends router he's on a 'Plusnet' connection, and his router's made by 'Huawei' i think. I'll post back the results. I got these calibration values from a config file which was included in hardy If my information is correct the q1 ultra was the main development platform for the ubuntu mobile edition version of hardy heron.
The calibrations options are ok, but not quite that, they seem a little bit of at the right side of the screen, which makes it difficult to scroll windows. I have had a little bit of succes adjusting the max X value a little. More details on that later on. There seems to exist a calibration tool for the evtouch driver (the driver used in the config I posted). /usr/lib/xf86-input-evtouch/calibrate.sh But that doesn't work. That could be because it uses hal, and hal is not used anymore in lucid.
And the last update the package had was in 2008. So I guess there is not much hope in it getting an update so the calibration method works. The calibration program explained in the OP of this thread does work, but it's values are not usable as far as I know.
Maybe it is time to create a new thread with all this information about the q1 ultra, since we are hijacking this thread more or less (MODS?) Maybe I'll create a new one tomorrow. Hello Cka3o4nik, I've just check my wireless connection, the ISP was Plusnet, and i know this to be a recent broadband account of a friends, i'm guessing it's was there latest 'Wireless' router that i was using, i didn't make a note of the model though. I can only describe the router, it's Apple mac glossy white finish with rounded corners, and a single ariel, all the lights are very small and green when fully syncronised, there located on the top, and to the corner of the router, diagonally oposite to the ariel. It was sited in his basement area, and i was using the Q1 Ultra in the loft of the house when i first chose the plusnet connection and put in the wireless security 'key', it connected with no problems. I did some browsing for around 2 hours, and then went to the 'Update manager' for any new updates, there were 34 and they were mainly 'OpenOffice', Chromium browser and 'Rythembox' plugins, from the distance of the router and my location the download rate did fluctuate, jumping around '5000 B/s' going upto '35 Kb/s', but i notice the signal bar's of the 'Network connection' icon kept increasing, then decreasing constantly.
As the updates were being downloaded. I decided to move the Q1 Ultra closer to the router, so i went into the basement, i notice that although the download rate had increased, going between 40 Kb/s and 198 Kb/s, the 'Network connection' signal strength idicator bars at this location were now full, and stable though, and 'Update Manager' completing all it's downloading, and installing took around 1 hour to do, i then did a little more web browsing, about an hour, and then disconnected the Plusnet connection. What i would mention is, that while i was using the Q1 Ultra via it Wireless connection, i found it was slightly slower, as if running the Wireless adapter with a connection running through it was using more memory, even though i always have the wireless adapter turned on, though i don't have a router to use on it.
I would also mention that my Q1 Ultra has been fitted with the maximum memory modules allowed in it, and that i did have BIO's updates installed via the Samsung Update Plus software when it was running Windows XP, i ran the Samsung Update check on a regular basis, i've only been running Ubuntu Netbook Edition 10.04 for around month, or just over. After checking if you have latest BIO's version, and installing it if you don't, i would then go back into the BIO's again and make sure to 'Load Default settings', and 'Save and Exit', just incase something has changed, or was never quite right with the Wireless adapter in the settings for running Ubuntu. I then delete any current network connections you have, and, any old Wireless or Mobile connections you previously had used, through the 'Network Connections' software, then restart the Q1 ultra, i wouldn't setup a Wireless connection again on the router your having these issues with, but would try someone elses router first, this may show the problems with your router. I looked at that link, and it's obvious that it does not work in 10.04 since hal is not used anymore (deprecated) and since they use hal rules inthere. But I adapted it to 10.04 (with xorg.conf.d) and it works for my touchscreen!!! I have a Samsung Q1 ultra. Has anyone managed to get the eGalax screens working properly?
I just recently put one in my Asus Eee 1005HAB. I was able to install the eGalax driver without any problem. I was even able to calibrate with their tool. It took running the eGalaxTouch tool as root for it to work correctly. When I wasn't running it as root, it would let me get through a few points and then just completely crash, leaving an error in the terminal. The calibration seems to have worked fine, but I still have one remaining issue. The whole thing where everyone says the cursor jumps to the top-left of the screen.
I got that before the calibration and, although I can touch and move the cursor where I want, it jumps at that top left with every tap, causing it to think i'm doing a drag and highlighting text, icons, etc. I'm assuming this is just left over from what was originally there on a clean install. Is there any way to remove that? I'm not a noob, but i'm no pro either.
Hopefully I can be of some use if anyone needs to know specifics on how I got this far at least. I've just been through the whole eGalax journey with a Xenarc 700TSV display. This thread (and some others) was a major part of my finally getting it working (after an entire day of trying things). I'm writing this to summarize what worked for me on an Asus EB1501, running Lucid 10.4 with the Xenarc display. My system also has a USB/Bluetooth mouse and keyboard. The mouse is extra helpful while trying to get things working, and seems to coexist well with the touchscreen. The key steps were: - downloading the beta Linux driver (3.03.4510 at this time) from the EETI website: - running the unmodified setup.sh script with sudo - rebooting - running the eGalaxTouch command after rebooting and selecting USB and disabling right click - running the TKCal command and doing a 4-point calibration - running xinput -list and note that there were two eGalax input sources - adding a startup program: xinput -set-prop 'eGalax Inc.
Touch' 'Device Enabled' 0 Disabling the second eGalax input device was the key to eliminating the upper-left pointer issue. I'm still working to determine exactly where to run this command during startup, as it sometimes seems to lose its effect, but rerunning it.always.
removes the upper-left pointer problem. I have a eeepc 901 asus and ubuntu 10.10 netbook with touchscreen i did this and then Linux driver installer for TouchKitTouch controller (I) Check user permission: root, you are the supervisor.
(I) Begin to setup the TouchKitTouch driver. (I) Found and removed previous TouchKitTouch driver.
(I) Extract TouchKitTouch driver archive to /usr/local/TouchKit32. (I) Create TouchKit utility shortcut in /usr/bin.
(I) Create TKCal tool shortcut in /usr/bin. (I) Check X window version: 6.9.0 7.2.0 (I) Copy X module: x69/egalaxdrv.so to /usr/lib/xorg/modules/input. (Q) Which interface controller do you use? (I) 1 RS232 2 PS/2 3 USB: 3 (I) Using interface: USB (I) Found a HID compliant touch controller. (I) Found inbuilt kernel module: usbtouchscreen. (I) It is highly recommended that add it into blacklist.
(Q) Do you want to add it into blacklist? (y/n) y (I) Found X configuration file: /etc/X11/xorg.conf.
(I) Removed touch configuration from /etc/X11/xorg.conf. (I) Add touch configuration into /etc/X11/xorg.conf. (I) Please reboot the system for some changes to take effect. (I) After booting, type 'TouchKit' to do calibration. Hello, with Ubuntu 10.10 (Maverick) I also was able to use my eGalax touchscreen. This is my /usr/share/X11/xorg.conf.d/40-touch.conf file: Section 'InputClass' Identifier 'eGalax touch class' MatchProduct 'eGalax' MatchDevicePath '/dev/input/event.'
Driver 'evtouch' Option 'MinX' '150' Option 'MinY' '100' Option 'MaxX' '1900' Option 'MaxY' '1950' Option 'ReportingMode' 'Raw' Option 'Emulate3Buttons' Option 'Emulate3Timeout' '50' Option 'SendCoreEvents' 'On' Option 'Rotate' 'CCW' Option 'SwapY' '1' EndSection But with 11.04 the 'evtouch' isn't available any more:( The news is: The eGalax input device gets detected automatically using the general evdev driver. With help of 'xinput' it is possible to configure it (swap, calibration, invert.). BUT there is a nasty hassle with the touchscreen 'button' emulation (see below). In 10.10 'evtouch' was kind of clever: if you ticked short onto the screen, it was detected as 'left mouse button'; if you ticked short and then a little longer immediate after that, it was detected as 'right mouse button'.
If you touched the screen for longer (and moving the finger/mouse around), no mouse event was recorded (as it should be!). In 11.04, if you touch the screen this will always trigger a mouse button event. And because of this, the new state of affairs renders the touchscreen unusable.
Anyone with a suggestion? Kind regards, aanno. I bought a little car computer type 7' LCD touch screen that uses the eGalax USB driver and I am using it with Ubuntu 10.04. I read many lists and forums regarding how to get a touchscreen to function with Ubuntu, and much of the information was wrong or misleading. So I would like to clear up what has and has not worked for me after spending 18 hours to get this screen to work properly. The eGalax drivers that came with the screen were old and obsolete.
3.02 was the latest on the little mini cd. I found a 3.06 version on the web from the company that writes the drivers and although it looked good and it had concise instructions on how to use it, it did not work with Ubuntu 10.04 on a MW525 intel mb. The software could never find the touch controller, even though it was showing up in the USB device list! After doing a lot of reading on the web about this driver, I came to the conclusion that the driver is junk and should be avoided. I lost some hair working with that driver. Do yourself a favor and don't bother trying to use these old drivers.
With no additional drivers loaded into Ubuntu 10.04, the system cannot identify the eGalax touch screen device. A driver called evtouch must be loaded. You can find it via the Synaptic package manager.
Install that and reboot. Not comes the really weird part. The newest USB driver is called the evdev driver and the evtouch driver is apparently being phased out (I have read that it does not work with version 11 or later??) After you load the evtouch driver, Ubuntu will find the touch device using the evtouch driver but then the evdev driver apparently wrestles control of the touchscreen away from the evtouch driver. So two files need to be modified to allow this screen to work: The configuration file for the evdev and evtouch driver is in /usr/lib/X11/xorg.conf.d and the files I edited were called 05-evdev.conf and 10-evtouch.conf. Do not be tempted to try and make and edit a file called xorg.conf as mentioned in older docs.
That is a no no in Ubuntu 10.04 and later. Only edit the config files in xorg.conf.d. This is how I modified the last InputClass section of the evdev config file (at the very bottom): Section 'InputClass' Identifier 'evdev touchscreen catchall' MatchIsTouchscreen 'on' MatchDevicePath '/dev/input/event.' Driver 'evdev' Option 'InvertX' 'true' Option 'InvertY' 'true' Option 'Calibration' '38 20' EndSection The calibration section is minX maxX minY maxY for settings.
This is how I modified the config file for the evtouch driver: Section 'InputClass' Identifier 'eGalax TouchScreen' MatchProduct 'eGalax TouchScreen' MatchDevicePath '/dev/input/event.' Driver 'evtouch' EndSection The descriptor (in this case 'eGalax TouchScreen' ) must match up with what the computer identifies in the description you can see via 'lsusb' at a terminal window. Other things: If you look in the boot up log for X you can see how your computer is trying to handle the touch screen. /var/log/xorg.0.log You can access it via gedit like this: sudo gedit /var/log/xorg.0.log. If you run evtest (may need to install the evtest software) via sudo evtest /dev/input/eventx” and try different x events, then you can find the touch screen and see how it is interacting with linux – live. This is a real eye opener if you haven't seen the evtest program run. Of course you can get some info from boot up via 'dmesg' at a terminal screen also.
If you get a lockout of the screen and end up not seeing Gnome desktop on the reboot, then hit Control-Alt-F2 and log in as root (make sure you have a root login setup or else you could lock yourself out of your computer on an error), go and edit the.conf file via nan. Ie nano 05-evdev.conf. Reboot and try it again. A typo in that file can cause a lockout of the Gnome desktop. There is a calibration program called xinput-calibrator, but I have found it of limited use and it also has directions on how to update an fdi hal entry which is not required when using the evdev driver. (The hal entry is stuff from version 9.10 I believe) However finding the screen calibration coordinates might be useful for some. I ended up tweaking them manually in the.conf file, reboot, try, repeat.
On my eGalax equipped screen ( I don't know the brand as it was made in China and really don't have a brand name!) if I input a MaxY value that was too large the touchscreen simply stopped responding via the evdev driver. So if in doubt start with smaller values for the maxX and maxY and work up until things look right.
I really like Linux but the development of the software moves so fast from version to version and the changes between major version are substantial that trying to stay on top of what is required is a major task. The good thing is that the software is progressing (unlike windows) and making technical jumps. Has anyone managed to get the eGalax screens working properly? Took about 2 hours of reading and then in 5 min it was working. Its realy simpel. 1) go here, and get the drivers. (2) backup you config of xorg.conf remove it.
( make sure its al back to basic, like new install ) cd /etc/X11 X -configure 3) unpack downloaded drivers, and run setup.sh. Reboot the server. 4) touch wil work now, but things are not right. ( for me x-y mouse was incorrect ) to fix this.
Egalax Touch Driver Windows 10
Login in X, In Aplications-Accessories, you find: eGalaxTouch Utiliy Start it and go to tab Tool. First do a 4 Pts Calibration, then do 25 points linearization. After this every thing was working correct for me. Hope this helps someone. I've just been through the whole eGalax journey with a Xenarc 700TSV display.
This thread (and some others) was a major part of my finally getting it working (after an entire day of trying things). I'm writing this to summarize what worked for me on an Asus EB1501, running Lucid 10.4 with the Xenarc display. My system also has a USB/Bluetooth mouse and keyboard. The mouse is extra helpful while trying to get things working, and seems to coexist well with the touchscreen.
Egalax Touch Driver Windows 7
The key steps were: - downloading the beta Linux driver (3.03.4510 at this time) from the EETI website: - running the unmodified setup.sh script with sudo - rebooting - running the eGalaxTouch command after rebooting and selecting USB and disabling right click - running the TKCal command and doing a 4-point calibration - running xinput -list and note that there were two eGalax input sources - adding a startup program: xinput -set-prop 'eGalax Inc. Touch' 'Device Enabled' 0 Disabling the second eGalax input device was the key to eliminating the upper-left pointer issue. I'm still working to determine exactly where to run this command during startup, as it sometimes seems to lose its effect, but rerunning it.always. removes the upper-left pointer problem. Thanks a lot for the tip on disabling the eGalax device using xinput, it solved my problem with the upper-left pointer. Before this I was planning to discard any mouse event with 0,0 coordinates in my software (I'm developing a custom system). In my system, xinput list shows two eGalax devices, one named 'egalax' and the second 'eGalax Inc.
TouchController', disabling the second one fixes the problem. I have placed the xinput calls in my xinitrc file, hope it helps you.