Asus ep121 (eee slate) touchscreen not working

[Chinook Piroh]

The Asus ep121 touchscreen is a two-finger (at the time) eGalax multitouch screen 0xeef:0xa001. It should function as such but does not. The pointers movement and position are relative and not absolute, like a giant laptop touchpad. The hardware logs say it is a touchpad and load the Synaptics module for it.
Touching the screen causes a constant "mouse wheel up" issue as well as removing the ability to click even with a real mouse. The computer is unusable in this state until rebooted.
There are a number of workarounds for other eGalax touchscreens such as http://samiux.blogspot.com/2011/04/howto-ubuntu-1104-on-gigabyte-touchnote.html but nothing works.

These issues occur on 10.10, 11.04, and the 11.10 beta released sept. 1. In the 11.10 beta, blacklisting the synaptics module allows the touchscreen to work with absolute coordinates but bad calibration. It also registers a constant "left mouse button pressed" event after being touched.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Chinook Piroh (chinookpiroh)]

As of August, eGalax has updated their Linux drivers but due to lack of time (and belief that they would update anytime soon) I haven't been able to try them out. It should be noted that the download includes the sources and guides to compile and package or install them in different distros.

[tuxiano (tuxiano2)]

You have to ask the EETI-Support (touch_fae at eeti.com) for a special driver (Asus EP121; ubuntu 11.10 64bit). They will send you a archive called "eGTouch_v1.00.0812.L-x64.tar.gz" (Note: the driver provided on the driver page of EETI is not working properly ).

You just have to run the setup.sh as sudo and add to the "52-egalax-virtual.conf" file the option InvertY, that it looks like this:

[QUOTE]Section "InputClass"
 Identifier "eGalax virtual class"
 MatchProduct "eGalaxTouch Virtual Device"
 MatchDevicePath "/dev/input/event*"
 Driver "evdev"
 [B][COLOR="Red"]Option "InvertY" "true"[/COLOR][/B]
EndSection[/QUOTE]

And finally reboot you system.

Observations:
1.) I asked the EETI Support if I could share their drive in the ubuntu forum, they said "NO" it is a project (I do not understand what this means, but anyway, please do not upload the driver)
2.) Multi-touch does not work, they told me "If you want to have multi-touch function, the user-space (application) must be able to receive our multi report data from our controller." Well, I also do not understand what this means ...

[tuxiano (tuxiano2)]

There is an ongoing discucion on the linuxwacom-devel mailing list. Which could help to solve this problem upstream.

http://sourceforge.net/mailarchive/forum.php?thread_name=CAGzDe_ag7KWkF4uDa7rd3rrtq75B4bwkn7vA26YAsS2EEJebag%40mail.gmail.com&forum_name=linuxwacom-devel

[Chris Bagwell (chris-cnpbagwell)]

The discussion then moved over to linux-input mailing list were it got fully resolved by hid-multitouch developer. A fix will be in Linux 3.3 (its in a hid next branch). The fix is slightly larger than adding new product ID's to hid-multitouch. The touchscreen uses a "MT serial" protocol that happened to be added to hid-multitouch for another touchscreen in November timeframe as well. This version of eGalax touchscreen makes use of that new feature in hid-multitouch.

This issue is pure kernel side issue and nothing to change in xf86-input-evdev if you want to reassign bug report. If your interested in more why xf86-input-evdev was acting strange with HW you can look at thread in comment #4.

[penalvch (penalvch)]

Chinook Piroh, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xserver-xorg-input-evdev REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Chinook Piroh (chinookpiroh)]

Hey there, I will do this when I get the chance. If I remember correctly I
had to make a small change to the xorg configuration before the touchscreen
worked properly.

On Thu, Jan 9, 2014 at 12:26 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> Chinook Piroh, this bug was reported a while ago and there hasn't been
> any activity in it recently. We were wondering if this is still an
> issue? If so, could you please test for this with the latest development
> release of Ubuntu? ISO images are available from
> http://cdimage.ubuntu.com/daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p xserver-xorg-input-evdev REPLACE-WITH-BUG-NUMBER
>
> Please note, given that the information from the prior release is
> already available, doing this on a release prior to the development one
> would not be helpful.
>
> Thank you for your understanding.
>
> Helpful bug reporting tips:
> https://wiki.ubuntu.com/ReportingBugs
>
> ** Changed in: xserver-xorg-input-evdev (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xserver-xorg-input-evdev (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/854445
>
> Title:
> Asus ep121 (eee slate) touchscreen not working
>
> Status in “xserver-xorg-input-evdev” package in Ubuntu:
> Incomplete
>
> Bug description:
> The Asus ep121 touchscreen is a two-finger (at the time) eGalax
> multitouch screen 0xeef:0xa001. It should function as such but does not.
> The pointers movement and position are relative and not absolute, like a
> giant laptop touchpad. The hardware logs say it is a touchpad and load the
> Synaptics module for it.
> Touching the screen causes a constant "mouse wheel up" issue as well as
> removing the ability to click even with a real mouse. The computer is
> unusable in this state until rebooted.
> There are a number of workarounds for other eGalax touchscreens such as
> http://samiux.blogspot.com/2011/04/howto-ubuntu-1104-on-gigabyte-touchnote.htmlbut nothing works.
>
> These issues occur on 10.10, 11.04, and the 11.10 beta released sept.
> 1. In the 11.10 beta, blacklisting the synaptics module allows the
> touchscreen to work with absolute coordinates but bad calibration. It
> also registers a constant "left mouse button pressed" event after
> being touched.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/854445/+subscriptions
>

[Launchpad Janitor (janitor)]

[Expired for xserver-xorg-input-evdev (Ubuntu) because there has been no activity for 60 days.]