Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: Tuftec on May 01, 2011, 01:17:38 AM
-
I am trying to get a small 7" LCD with eGalax touch screen working on TC.
Has anyone developed a package to instal the eGalax drivers and tools easily?
I really do not know about how to recompile things into the kernel.
Peter.
-
the forum search shows up this:
http://forum.tinycorelinux.net/index.php?topic=8654.msg46864#msg46864
http://forum.tinycorelinux.net/index.php?topic=8528.msg47016#msg47016
Looks like somebody already compiled the driver(s)?
-
Beyond me!!
Where do i get the package to install?
Peter.
-
You could send a pm to user "vinnie"
-
Alternatively you might want to look into using gpm in repeater mode:
http://www.nico.schottelius.org/software/gpm/browse_source/gpm-1.99.6/doc/README.evabs
-
Thanks
-
Where do i get the package to install?
http://home.eeti.com.tw/web20/drivers/touch_driver/Linux/20110406/eGalaxTouch-3.05.5025-32b-k26.tar.gz
untar this somewhere, cd to the directory created and "sudo ./setup.sh"
-
I think it's best that you follow the steps listed in the second post linked by juanito, I can give you the package if you need but I don't think it will work, I even tried on a variant of my model and doesn't work.
If you need some help, ask, if I can I will
-
I think I am out of my depth now.
I have downloaded and extracted the EGalax files to a location on my HDD.
When I run the setup.sh file it tells me it can not find an X directory?????
Where should this be?
Does TC not use X?
The TC GUI is all working correctly.
Where is the xorg.conf file that I have to create and how do I create this?
A bit lost!
Peter.
-
Sounds like you need to be loading Xorg-7.5.
-
I speak bad english, I do not know if egalax also work with TinyX, does anyone know if is possible have a working xorg.configure in tinycorevanilla?
however, if you install xorg (and reboot), please follow this step http://forum.tinycorelinux.net/index.php?topic=8528.msg46841#msg46841
-
xorg.conf is irrelevant to Xvesa, however, gpm in repeater mode should work with any X server.
-
Ok.
So now I have set xorg 7.5 to come up on boot.
I run the EGalax setup script and it reports a problem with my USB interface.
Something about USB driver not being right.
-
Ok.
If I want to stay with XVesa how do I get GPM going?
It appears that the version of GPM in the TC repository does not support all the required options. Or am I doing something wrong?
I can not identify my touchscreen in /proc/bus/......
When I look at dmesg after plugging in the touchscreen is indicates that it has detected it on the USB port (although with errors. Error -32).
It indicates that a new driver usbtouchscreen was registered. What does this mean? How do I access the driver so that I can then use GPM?
Peter.
-
cat /proc/bus/input/devices
-
So this is want the /proc/bus/...... file looks like.
-
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?
-
Yep.
It looks like the touch screen is not showing up correctly.
How do I use usbutils?
-
How do I use usbutils?
Install the usb-utils extension and use the command "lsusb"
-
This is what lsusb gives.
-
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?
-
The messages are from dmesg.
-
This is what lsusb gives.
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"
-
I wonder if you need a "waitusb=10" or similar on boot to allow the touchscreen time to start correctly?
-
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?
-
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?
-
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 ;)
-
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?
-
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 (http://forum.tinycorelinux.net/index.php?topic=9146.msg51729#msg51729)
-
I tried evtest, but the touchscreen does not appear to show up in the list.
-
Hi All,
I have resurected this post as I am still struggling to get my eGalax screen going with TC.
I have done a lot of reading and testing and I now feel that the problem I have is because my touch screen does not work correctly with the USBHID driver.
After boot, I get a message in DMSEG indicating that the touch screen can not be set up correctly ( it reports an error of -32 in response to a generic-usb: probe). I think this is the driver trying to tell me that my touch screen is not HID aware.
I have read that others have run into similar problems.
If I install the input-tablet-touchscreen-2.6.33.3 drivers then it appears that the usbtouchscreen driver loads but it does not create the necessary /dev/input/eventX entry and hence touch does not work.
I think that this is due to an issue in the input- ..... code. From what I have read, it appears that the codse believes that the touch screen is HID aware (from info thet it reads from the device) and decides that the device should be handled by the usbhid driver.
This results in a stalemate and the touchscreen does not get serviced.
I do not have the skills to solve this little issue. Is there anyone out there that can help with a bit of code or instructions that I can use to get arround this problem.. I do not want to move away from the touch screen that I have.
Here is a link to some further information on the topic that I believe is relevant https://patchwork.kernel.org/patch/6107/
There are many touch screens out there that use this cheap eGalax technology. Solving this should provide options for many other TC users.
Cheers
Peter.
-
That patch is present in our kernel, so the issue is somewhere else.
-
I think the patch is the problem. I think it results in the driver looking for a mode of operation that is not supported by my touch screen. You have to read the post in the link that I posted carefully. There is some double negative logic in the narative.
Maybe the unpatched driver is what I need. Can I get hold of the unpatched driver to try? I do not know where to look for this or how I should load it.
Is there somehere that I can look to find out exactly what the error -32 being report actually means? I suspect there must be an error number listing somewhere.
Peter.
-
As mentioned, a couple of users (http://forum.tinycorelinux.net/index.php?topic=8528.0) got it to work, so we know it can be done. What we don't have is an extension so it will work for everyone. Does anyone in the US have one I can borrow for creating an extension? I don't mind donating some time since it seems to be a popular device.
-
Thanks Daniel.
HoPefully someone will pipe up with a loaner.
I am in Melbourne Aus. If anyone here has the skills to get it going, they can borrow my 7" touchscreen.
Peter.