XENARC 700IDT and Xorg 1.6/1.7

So, I got this device last year(from mp3car), and it worked fine with the evtouch(only driver that worked) drivers with Xorg 1.4 and 1.5. Something in 1.6 broke the drivers and the screen only responds to click events, no pointer movement. I've tried hacking around with the drivers, many combination of xorg.conf to no avail. udev rules are correct, the device node is being created and the X config does reference the proper node. I have found noone else using this combination so alas I turn here for help with hopes someone is using this! If anyone is using this screen with 1.6 or newer can you please tell me:
-your xorg.conf
-your kernel version
-any drivers not bundled with xorg that made it work

I'm running Gentoo for those who are wondering.
Thanks! :)

i'm using the egalaxTouch drivers from eeti. I've successfully gotten it to work on xserver 1.5-7.

just be sure to remove evtouch when you install.

cheers,

Quote:

---

Originally Posted by tripzero

i'm using the egalaxTouch drivers from eeti. I've successfully gotten it to work on xserver 1.5-7.

just be sure to remove evtouch when you install.

cheers,

---

Why does evtouch have to be removed? Is there some contention issue?

Quote:

---

Originally Posted by themainer

Why does evtouch have to be removed? Is there some contention issue?

---

Not loading it in xorg.conf should suffice. Since I opened this thread, Xorg 1.8 is out and evdev automagically works with no config needed to use the screen. I had to use the xinput_calibrator script to fix calibration, though.

I appreciate you opening the thread back up. I also apologize for submitting the same post 3 times! Missed the "your post must be moderated first" text that showed up. :)

Unfortunately the computer I am working with uses Xorg 1.6 and I do not have the liberty to update it. Currently I am using evtouch with success. The only thing I have defined in xorg.conf is the screen for the resolution, the rest is auto-detected. I installed the eGalax drivers and tried to update xorg.conf, and that is when things go down hill. Claims no screen can be found, yet I didn't change it at all in the conf file.

Sounds like 1.8 may be the answer. I will have to talk to the powers that be and see if upgrading is out of the question. :)

Quote:

---

Originally Posted by themainer

I appreciate you opening the thread back up. I also apologize for submitting the same post 3 times! Missed the "your post must be moderated first" text that showed up. :)

Unfortunately the computer I am working with uses Xorg 1.6 and I do not have the liberty to update it. Currently I am using evtouch with success. The only thing I have defined in xorg.conf is the screen for the resolution, the rest is auto-detected. I installed the eGalax drivers and tried to update xorg.conf, and that is when things go down hill. Claims no screen can be found, yet I didn't change it at all in the conf file.

Sounds like 1.8 may be the answer. I will have to talk to the powers that be and see if upgrading is out of the question. :)

---

I've had issues with xserver 1.8 and 1.9 with kernels above 2.6.31 and egalax based touchscreens with evdev. Calibration using xinput_calibrator never gets past the first touch point and the cursor just hides in the upper-left.

xcoldfyrex, what kernel are you using?

tripzero - I am having the exact same problem right now.

Kernel - 2.6.32-21
Xserver - 1.9

I try to run xinput_calibrator, hit the first red cross in the upper left and then go to hit the second and it doesn't register. It knows I hit the screen because the timer resets.

Quote:

---

Originally Posted by themainer

tripzero - I am having the exact same problem right now.

Kernel - 2.6.32-21
Xserver - 1.9

I try to run xinput_calibrator, hit the first red cross in the upper left and then go to hit the second and it doesn't register. It knows I hit the screen because the timer resets.

---

Yep. sounds like the same issue. I found a bug for it with a bunch of comments and some workarounds here: https://bugs.launchpad.net/ubuntu/+s...ev/+bug/549447

I haven't gotten any of the workarounds to work myself though. If you get anywhere, let me know.