support for Acer 1420P

[Michael]

The touchscreen in the Acer 1420P tablet uses ABS_RY and ABS_RZ for position reporting. To support it, these must be considered as input data sources.

Info:
The devices is labeled as MosArt, Inc., RMTP-MA957 in the USB device tree.
---
Architecture: i386
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
MachineType: Acer ASPIRE1420P_MSFT
Package: xf86-input-evtouch (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=/dev/sda3 loop=/hostname/disks/root.disk ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/usr/bin/fish
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: ubuntu-une lucid lucid ubuntu-une lucid lucid
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/19/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: v0.3106
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvrv0.3106:bd10/19/2009:svnAcer:pnASPIRE1420P_MSFT:pvrv0.3106:rvnAcer:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: ASPIRE1420P_MSFT
dmi.product.version: v0.3106
dmi.sys.vendor: Acer
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

[Jose Miguel Parrella (bureado)]

I confirm that this patch to evtouch makes the tablet on the Acer Aspire 1420P work after calibration.

[Felix Homann (fexpop)]

Hi,

could someone please explain how to calibrate the touchscreen.
I've tried the calibrate.sh script in /usr/lib/xf86-input-evtouch without success:

1. "No evtouch capable device found..."
2. After putting this:

<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
  <device>

    <match key="input.product" contains="RMTP-MA957">
       <merge key="input.x11_driver" type="string">evtouch</merge>
    </match>

  </device>
</deviceinfo>

in /usr/share/hal/fdi/policy/20thirdparty/30-Acer1420p-touchscreen.fdi

the script runs (with sudo), but I won't see any red crosshair, nor will I see any effect after restarting my session.

At the moment, whenever I touch the screen, the mouse pointer will move straight to the upper left corner of the screen.

Kind regards,

Felix

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi mig000,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 511747

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 511747 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/511747

[Constantin Berhard (cberhard)]

Hey I've just tested it with a fresh Lucid (AMD 64 version) and the bug is still there.

[Bryce Harrington (bryce)]

[Resetting to incomplete since we need a response from the original reporter on this].

[Michael (mig000)]

Tested with Lucid on x64, bug is still there.

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[Michael (mig000)]

apport information

[madbiologist (me-again)]

Support for the MosArt multitouch panel was introduced upstream in kernel 2.6.34, but it looks like it might be for ASUS only.

[Alexandru Romanescu (alexromanescu)]

The problem might also be in the kernel, not the evtouch driver:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/549447/comments/11
I have it on a Packard Bell Butterfly Touch (similar hardware as the 1420p).

[Michael (mig000)]

The 2.6.34 hid-mosart driver seems to fit better because it's a real multitouch driver. This evtouch driver just uses the absolute HID position information and doesn't provide multitouch therefore.

I don't see a relation between this bug and 549447, though. If I apply the patch everything works.

[ng (ng-ngcorp)]

tested it with lucid x64, got the same result...

applied the patch. i had some problems with the cailbration. font *freemono* was not there, i solved it by replacing it only with a *, afterwards i was able to calibrate, but no changes. the pointer is always jumping into the left corner.

i have one question for my better understanding, if i do the same on karmic the touchscreen works?

[ng (ng-ngcorp)]

i have to ask the question again, is it posible to make the touchscreen work in singletouch mode or not? i really really want to know.

on my search for a solution i found a script that allows me to move the pointer all over the screen, but its slow and interferes with the left corner phenomen. on the otherside maybe it is helpful to someone: http://blog.vinay-srini.com/2010/02/my-simplistic-python-driver-for-my.html

[Alexandru Romanescu (alexromanescu)]

Shouldn't this kind of bugs be solved with quirks for hid? (in the kernel - so evdev could also work - evtouch is not installed by default and this device is handled by default with evdev).

See:
http://www.pubbs.net/200912/xorg/1650-patchevdev-add-touchscreen-absrxabsz-quirk.html
https://patchwork.kernel.org/patch/64411/
https://patchwork.kernel.org/patch/77055/
http://old.nabble.com/-PATCH--HID:-use-multi-input-quirk-for-eTurboTouch-touchscreen-td27426659.html

(the examples above are with ABS_Z and ABS_RX... we'd need ABS_RY and ABS_RZ)

[ng (ng-ngcorp)]

hey, i have a question, again, maybe someone can help me. i applied the patch into the ubuntu evtouch package, i am using lucid 64bit. the laptop is a acer 1820pt, if understand it right is has the same hardware as the 1420p.

afterwards the pointer not longer jumps to the left corner. it moves on the x-axis exactly in the middle of the y-axis. the movement on the x-axis isn't proportional, if i am at the middle the pointer goes of the screen. i guess it is a calibration problem, but i am not able to solve it myself.

the xinput_calibrator gives me the following information:
Calibrating standard Xorg driver "EVTouch TouchScreen"
 current calibration values: min_x=0, max_x=1366 and min_y=0, max_y=768
 If these values are estimated wrong, either supply it manually with the --precalib option, or run the 'get_precalib.sh' script to automatically get it (through HAL).

== Applying the calibration ==
There are multiple ways to do this: the tranditional way (xorg.conf), the new way (udev rule) and the soon deprecated way (HAL policy):

xorg.conf: edit /etc/X11/xorg.conf and add in the 'Section "InputDevice"' of your device:
 Option "MinX" "328"
 Option "MaxX" "1513"
 Option "MinY" "384"
 Option "MaxY" "384"

udev rule: create the file '/etc/udev/rules.d/99_touchscreen.rules' with: (replace %Name_Of_TouchScreen% appropriately)
 ACTION!="add|change", GOTO="xorg_touchscreen_end"
 KERNEL!="event*", GOTO="xorg_touchscreen_end"
 ATTRS{product}!="%Name_Of_TouchScreen%", GOTO="xorg_touchscreen_end"
 ENV{x11_options.minx}="328"
 ENV{x11_options.maxx}="1513"
 ENV{x11_options.miny}="384"
 ENV{x11_options.maxy}="384"
 LABEL="xorg_touchscreen_end"

HAL policy: create the file '/etc/hal/fdi/policy/touchscreen.fdi' with: (replace %Name_Of_TouchScreen% appropriately)
 <match key="info.product" contains="%Name_Of_TouchScreen%">
   <merge key="input.x11_options.minx" type="string">328</merge>
   <merge key="input.x11_options.maxx" type="string">1513</merge>
   <merge key="input.x11_options.miny" type="string">384</merge>
   <merge key="input.x11_options.maxy" type="string">384</merge>
 </match>

the calibration script of the package does not seem to help. i tried to manually change the values in the different files, but it doesn't change anything.

i guess i am a little bit out of my league here, in matters of my knowledge. i am going to attach some files. if someone could help me i would be very thankful!!!

[Steve Drew (steverdrew)]

I have a 1820PTZ which seems to be exactly the same as the 1420P, and I have the same issue with 10.04 64bit. The pointer jumps to the very top left of the screen.

[Manuel (manuel-schoelling)]

I can confirm this bug on Lucid i386

[neutrix (james-sharam)]

I can also confirm this bug.

[Constantin Berhard (cberhard)]

There seems to be a solution: https://bbs.archlinux.org/viewtopic.php?id=96530
Could someone please try to apply this to ubuntu? I won't have enough time in the next days...

[Alexandru Romanescu (alexromanescu)]

I made some patches for Maverick in order to make the PB Butterfly Touch / Acer 1420 mosart touchscreen work.
This kind of problem appears in many touchscreens, and can be solved in hid. The following 2 simple patches do this:
- /drivers/hid/hid-ids.h -> registers an ID for our particular device
- /drivers/hid/usbhid/hid-quirks.c -> applies the MULTI INPUT quirk for our device
Hopefully this will get upstream (they only add this device in lists along other touchscreens) so that our touchscreens work out of the box :D
(Tested with the 2.6.35.4 kernel - Maverick beta x64 + updates)

(For those who are just looking for a quick sollution in Lucid, I did a evdev workaround (similar to #1 ) and the file can be found here: http://romanescu.net/content/mosart-touchscreen-linux
(=just replace your evdev_drv.so driver with the one I compiled there and it should work ;) )

[Alexandru Romanescu (alexromanescu)]

And also people are working in order to make it work with the mosart driver:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/630264
https://bugs.launchpad.net/ubuntu/+bug/620609

[Alexandru Romanescu (alexromanescu)]

Does anyone follow this bugs? There are only 2 lines (in 2 files - one per file!) to change in order to put this device on that lists and have it work!
(and close like... 3 or more related bug reports... and make the users of ACER 1420p, ACER 1820ptz, PackardBell Butterfly Touch etc. happy)

[Alexandru Romanescu (alexromanescu)]

patch applied upstrem apparently :)
https://patchwork.kernel.org/patch/245581/

[Oliver Grawert (ogra)]

it seems these patches are small enough to justify for an SRU, i'm assigning it to the linux package (as the patches are against kernel code and already applied upstream), lets see if teh kernel team accepts them into maverick (and probably lucid)

[Oliver Grawert (ogra)]

@drem, please send the patches to the kernel team mailing list for inclusion, see:
https://wiki.ubuntu.com/Kernel/Dev/KernelGitGuide?action=show&redirect=KernelTeam/KernelGitGuide#Pushing changes to the main repo

[Oliver Grawert (ogra)]

teh kernel team pointed me to https://wiki.ubuntu.com/Kernel/Dev/KernelPatches too

[Andy Whitcroft (apw)]

Looks to be this commit below, this was officially included in v2.6.36 so should be in all recent Natty kernels:

  commit e1f092102f65e424be40c318a0fab7bb6e34194f
  Author: Pierre BAILLY <email address hidden>
  Date: Tue Oct 12 11:39:26 2010 +0200

    HID: Add MULTI_INPUT quirk for turbox/mosart touchscreen

Could someone with this H/W confirm that a Natty kernel works for them.

[ng (ng-ngcorp-de)]

I just installed the mainline kernel 2.6.36 for maverick amd64
and the mainline kernel 2.6.37rc2 also for maverick amd64.

The touchscreen works like it should, or as described above,
meaning its singletouch.

after all, i can confirm that those kernels work.

now i'm only waiting for the multitouch support. does anyone
know something about this?

[Micah Gersten (micahg)]

Unsubscribing ubuntu-sponsors since it seems this has to go through the Kernel team. Please resubscribe if there's an action to be taken outside of the kernel team.