Ubuntu
linux package

Mosart MA-957 not recognized

Bug #630264 reported by axoin on 2010-09-04

This bug report is a duplicate of: Bug #620609: add touch support for ACER 1820PTZ [MosArt RMTP-MA957]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	In Progress	Undecided	Unassigned
	xserver-xorg-input-evdev (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

told to report bug here by ubuntu multitouch qa
on ACER ASPIRE 1820PTZ there is touchscreen Mosart MA-957

dmesg says
usbcore: registered new interface driver hiddev
[ 2.731168] input: MosArt, Inc. RMTP-MA957 as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input5
[ 2.731371] generic-usb 0003:062A:7100.0001: input,hiddev96,hidraw0: USB HID v1.00 Mouse [MosArt, Inc. RMTP-MA957] on usb-0000:00:1a.1-1/input0

lsusb:
Bus 004 Device 002: ID 062a:7100

xinput list
$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ MosArt, Inc. RMTP-MA957 id=10 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]

$ sudo lsinput
/dev/input/event0
protocol version mismatch (expected 65536, got 65537)

Cursor is always stuck in upper left corner of screen, cannot move.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-19-generic 2.6.35-19.28
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: max 1441 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd4500000 irq 46'
   Mixer name : 'Intel Cantiga HDMI'
   Components : 'HDA:10ec0269,10250300,00100004 HDA:80862802,80860101,00100000'
   Controls : 21
   Simple ctrls : 10
Date: Sat Sep 4 17:07:56 2010
HibernationDevice: RESUME=UUID=7f954572-4ef4-4a5a-b9d7-a0c27d76c24a
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
MachineType: Acer Aspire 1820PTZ
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=93748b05-ad88-43e5-aa9f-882aba834b30 ro quiet splash
ProcEnviron:
LANG=de_DE.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 11/02/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: v1.3108
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JM12-MS
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:bvrv1.3108:bd11/02/2009:svnAcer:pnAspire1820PTZ:pvrv1.3108:rvnAcer:rnJM12-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire 1820PTZ
dmi.product.version: v1.3108
dmi.sys.vendor: Acer

Tags:

Revision history for this message

axoin (axoin) wrote on 2010-09-04:

AcpiTables.txt Edit (156.0 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (585 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (385 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (50.8 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (9.4 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.1.txt Edit (1.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (537 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (11.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (551 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (605 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (103.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (236.0 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (417.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Jeremy Foshee (jeremyfoshee) wrote on 2010-09-08:

Hi axoin,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags:	added: kj-triage
Changed in linux (Ubuntu):
status:	New → Incomplete

Revision history for this message

axoin (axoin) wrote on 2010-09-08:

Hi,
$ uname -a
Linux laptop 2.6.36-999-generic #201009080908 SMP Wed Sep 8 09:10:27 UTC 2010 x86_64 GNU/Linux

bug still exists. Cursor is stuck in upper left corner and won't move, just click.

dmesg
[ 3.080097] input: MosArt, Inc. RMTP-MA957 as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input5
[ 3.080323] generic-usb 0003:062A:7100.0001: input,hiddev0,hidraw0: USB HID v1.00 Mouse [MosArt, Inc. RMTP-MA957] on usb-0000:00:1a.1-1/input0

but should be hid-mosart?

tags:

removed: needs-upstream-testing

Revision history for this message

axoin (axoin) wrote on 2010-09-08:

just have seen that sudo lsinput now offers something, no error like 'protocol mismatch'
/dev/input/event5
   bustype : BUS_USB
   vendor : 0x62a
   product : 0x7100
   version : 256
   name : "MosArt, Inc. RMTP-MA957"
   phys : "usb-0000:00:1a.1-1/input0"
   uniq : ""
   bits ev : EV_SYN EV_KEY EV_ABS EV_MSC

Revision history for this message

axoin (axoin) wrote on 2010-09-10:

patch for hid-mosart to be loaded Edit (1.5 KiB, text/plain)

hello,

I was able to patch the kernel in order to load the correct driver.
I then had to execute xinput set-mode "MosArt, Inc. RMTP-MA957" ABSOLUTE to be able to use the touchpad.
Now it works accurately, but is not clicking. From evtest, I would expect keycode 272 to be send, but it is only send a 330, so currently I am not able to click with the touchpad. Also can I make the xinput above as udev rule so I don't have to type this in everytime I restart?

regards

Changed in linux (Ubuntu):
status:	Incomplete → In Progress

Brian Murray (brian-murray) on 2010-09-10

tags:

added: patch

Revision history for this message

axoin (axoin) wrote on 2010-09-12:

Xorg.0.log.joined Edit (1.9 KiB, text/plain)

I am still investigating why the click function does not work.

I have compared Xorgs logs with the usbhid driver and the hid-mosart driver. This points out that,

with generic, the touchscreen is recognized a 'tablet' (absolute axes, etc.)
with mosart, the touchscreen is recognized as 'touchpad'. ( See Applying InputClass "evdev tablet catchall" and Applying InputClass "evdev pointer catchall" in the logs.)

I have looked in the Xorg rule for matching as tablet and it required MatchIsTouchscreen On.
Now I would like to now how to bring the hid-mosart driver to fulfill the MatchIsTouchscreen. Or any other ideas how to tell Xorg that this is a touchscreen?

I'm quite near to the solution but this requires some more ideas that i currently don't have, I hope you may help.

kind regards

Revision history for this message

Alexandru Romanescu (alexromanescu) wrote on 2010-09-18:

While the mosart driver doesn't seem to work jet, shouldn't someone apply your solution from
https://bugs.launchpad.net/ubuntu/+bug/620609/comments/5
(equivalent from what I see now with mine from https://bugs.launchpad.net/ubuntu/+source/xf86-input-evtouch/+bug/511747)
so that we have our devices work out-of-the-box with Maverick?

Revision history for this message

Bryce Harrington (bryce) wrote on 2011-01-06:

From the patch and the comments, it sounds like this is strictly a linux kernel issue, so closing out the -evdev task at this time. If there are actually -evdev changes required please file a new bug (or reopen this task and explain further).