LinuxQuestions.org - eGalax Touchscreen and xorg: Driver problems (No core pointer)

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - eGalax Touchscreen and xorg: Driver problems (No core pointer) (https://www.linuxquestions.org/questions/linux-hardware-18/egalax-touchscreen-and-xorg-driver-problems-no-core-pointer-200928/)

eGalax Touchscreen and xorg: Driver problems (No core pointer)

Hi.

I first want to thank you all. This forum has become one of the greatest resources for linux problems just using the Search feature. Thanks for your great work and keep it up.

Now to my problem. I've got a eGalax Touchscreen [touchkitusb kernel driver] connected to my epia me 6000 and it worked all fine before (had to reinstall because of a head crash). I don't know which version of xorg I had before the head crash and I don't know if I had an extra driver for my touchscreen, but the driver I use now makes problems.

The interesting part of my xorg output (verbose level 5) is:

Code:

(**) Option "CorePointer"

(**) TKPANEL: Core Pointer

(**) touchkit X device name: TKPANEL

(**) touchkit associated screen: 0

(WW) TKPANEL: does not have core pointer capabilities

(II) Keyboard "Keyboard0" handled by legacy driver

(II) XINPUT: Adding extended input device "TKPANEL" (type: touchkit Panel)

(**) Option "Device" "/dev/input/event1"

No core pointer



Fatal server error:

failed to initialize core devices



Please consult the The X.Org Foundation support

        at (http)wiki.X.Org

 for help.

Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Reading that I think, the driver does not implement one function that is needed to be a core pointer.

I need a driver that can act on the event-Interface, supports absolute coordinates and touchscreen clicks (which in fact was a problem with the old driver, too) and can work as a core pointer. Has anyone any experiences or ideas on how to solve the problem?

xorg.log (verbose 9) -> (http)firefist.ch/files/files/xorg.log
xorg.conf -> (http)firefist.ch/files/files/xorg.conf

Sorry, but I had to remove the protocol from any links I postet because of this 5 posts rule. So please copy the links to your browsers location bar.

[edit]
Forgot some usefull system information:
Linux carpc 2.6.7 #16 Sun Jul 4 10:38:50 CEST 2004 i686 VIA Samuel 2 CentaurHauls GNU/Linux
[/edit]
[edit2]
I just found the driver I used with my old installation. For archive purposes:
(http)ariescomputing.com/lifebook/
This driver works on event devices with absolute pointer data, but has no "click" support. I'll have a look into this topic, but tpaneld (easely found using google) seems to handle this topic...
Thanks to anyone who read this thread, even if noone could help. Keep up the good work.
[/edit2]

I'm in a similar boat. I'd like to get the toucscreen working on a Lilliput 7" display with ts. and was running a 2.6.6 kernel. eGalax's touchkit driver does not compile under 2.6.6 (not that thier makefile noticies such, oops) due to kdev_t (whcih seems to have been depricated?). Anayway one still will need the touchcfg utility and the XFree86 changes and for those to be updated. But I see no linux updates of touchkit on eGalax's site since Feb (at least this year! :-) and thier doc seems to assume a 2.4 kenrel (whcih which is consistent with what I observe). I'm not sure how to proceed at this point.

Would movoing to XFree86 4.4.0 help? (I tried that recently and had some problems so I'm not wild about doing so but...)

RH 9, upgraded to kernel 2.6.7 (new glibc, rpm)
XFree86 4.3.0
VIA EPIA MII-10000 mini-itx
Lilliput 619GL-70NP LCD

update: My problems are solved. A blind email to egalax.com (i.e. to the one email listed on their site that wasn't obviously wrong, sales, hr, etc) and about 3 hrs later I got a response suggesting that the Fedora core 2 touchkit would likely work better (duh! why didn't I think of that) and indeed with just a quick hack for the X config file name it all wored great and I'm touching like crazy!

Hi,

I found this problem too. I have a different screen, but it uses the same chips, so I did a quick google search for 'fedora core 2 touchkit' which lead me to the egalax site. They have recently posted a driver for fc2 (6th July). Looks like it works funky-dory.

HTH

Dave

Further to getting the new driver off egalax, I'm having a couple of small, but annoying issues.

1. I can't get the drawing/desktop tool up
2. I can only get the device to respond as 'ok' once (the first time it's checked) after this, all eeproms return errors.
3. The calibation app doesn't work correctly - the first time i touch the screen, cirlce animation stops. Once it's registered, the next cross is removed. This means I can't see the next cross to touch. If i guess where it is, it comes back in yellow, and the next cross dissapears.

It's the last one that's a pain!

Has anybody already fixed this, or do I need to do this myself? Or is it just me? The RH8 version worked fine, so at least i have a place to start.

MTIA

Dave

The targets disappearing on the calibrate app sounds like an X server problem not necessarly related to the touch screen. The desktop / drawing mode app works fine for me too (I just leave it in desktop mode though). I'm only using it to interact with a web page, but its working fine doing that. that's with a fc2 touchkit (slightly hacked for the X config file name), RH9 with new glibc and pcmcia-cs to go with a 2.6.7 kernel.

I found an extra space in the source of the driver code that shouldn't have been there. That seems to have solved lots of the little issues, but I still don't have the mode selection tool. As I now have a trackball too, I'm not too worried by this, as I still have a right mouse button.