eGalax touch screen

[Tuftec]

So this is want the /proc/bus/......  file looks like.

[Juanito]

If that's all of it, it doesn't look like your touch screen is detected.

If you load the usb-utils extension, what does "lsusb" show?

[Tuftec]

Yep.
It looks like the touch screen is not showing up correctly.
How do I use usbutils?

[Juanito]

How do I use usbutils?

Install the usb-utils extension and use the command "lsusb"

[Tuftec]

This is what lsusb gives.

[Tuftec]

I get these messages for the USB port with the touch screen controller connected.

usb 3-1: new low speed USB device using ohci_hcd and address 5
generic-usb: probe of 0003:0EEF:0001.0004 failed with error -32
usbcore: registered new interface driver usbtouchscreen

What does this mean?

[Tuftec]

The messages are from dmesg.

[Juanito]

This is what lsusb gives.

Code: [Select]

Bus 003 Device 002: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
It seems the touch screen is at least recognised, you can get more details (though I don't know if that will add anything) using "lsusb -vv"

[Juanito]

I wonder if you need a "waitusb=10" or similar on boot to allow the touchscreen time to start correctly?

[Tuftec]

I have waitusb=15 set.
I am not sure that is the problem.
I can try waitusb=30 or so to see what happens.

The problem (error messages) show up when you plug the touchscreen in with the system running. Not just on boot up. Does waitusb influence this as well as at boot?

[Juanito]

I have waitusb=15 set.
I am not sure that is the problem.
I can try waitusb=30 or so to see what happens.

I'd say 15 seconds is already more than enough

The problem (error messages) show up when you plug the touchscreen in with the system running. Not just on boot up. Does waitusb influence this as well as at boot?

No, waitusb is only for the initial boot.

I wonder if the usb interface of your touchscreen is buggy or defective - is there a firmware update or similar available?

[tinypoodle]

As the device seems to be recognized despite error output, you could still proceed with configuring and running gpm and just see what will happen   

[Tuftec]

I tried that, but GPM (as from the TC repository) does not seem to respond to all the necessary command line options (like -R) it throughs up an error.
Maybe I am doing something wrong?

[smultita]

try: sudo evtest /dev/input/eventX
and check the events, if they report under type 3 (absolute) you could use
http://forum.tinycorelinux.net/index.php?topic=9146.msg51729#msg51729

[Tuftec]

I tried evtest, but the touchscreen does not appear to show up in the list.