Dell ST2220T multi-touch monitor

[cccc]

Hi

I have Ubuntu 10.04 and bought Dell ST2220T multi-touch monitor with USB interface:

# cat /proc/bus/input/devices
I: Bus=0003 Vendor=1fd2 Product=0064 Version=0100
N: Name="LG Display LGD-MultiTouch"
P: Phys=usb-0000:00:1d.7-2.1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2.1/1-2.1:1.0/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: EV=1b
B: KEY=403 0 30000 0 0 0 0 0 0 0 0
B: ABS=700 3f
B: MSC=10

Touch screen works under Vista without problems, but howto get it working under Ubuntu?

[cccc]

Has someone any idea howto get touch screen working?

[Copper Bezel]

I think the usual solution has to do with recognizing the touchscreen as a Wacom device. I don't have any hands-on experience with touchscreen support, however. Unless someone more knowledgeable comes along, I'd suggest Google searching for wacom device support in Ubuntu. There's also the experimental work in ginn/uTouch.

[cccc]

Thx, but still doesn't work.

[Copper Bezel]

As I said, I can't offer much help on this subject, but could you post exactly what you tried so that someone can help to diagnose the problem?

[Favux]

They have it partially working in Natty. See this launchpad bug report: https://bugs.launchpad.net/utouch/+bug/736752
The Ubuntu Multi-touch wiki also tells you what hardware is supported and other useful stuff.

For Lucid it depends on if it is supported in the 2.6.32 kernel. It seems like it might be at least partially supported since you're getting some output mentioning it. You should also run in a terminal:

lsusb
and
xinput list

And see what the outputs show for the device's name so you have something to google with. Right now it looks like "LGD-MultiTouch"? Or is the "LG Display" part of the name too?

Then you need an X driver. Evdev is probably picking it up by default but apparently isn't working. You could try evtouch and/or google around to see if anything works. My guess is in Lucid you'll only be able to get single finger touch, if you get it working. But you'll need to do some more research.

[cccc]

Thx, I get these outputs, but cannot find a solution:

# lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
Bus 003 Device 003: ID 413c:2002 Dell Computer Corp. SK-8125 Keyboard
Bus 003 Device 002: ID 413c:1002 Dell Computer Corp. Keyboard Hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 1fd2:0064  
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

# xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech USB Optical Mouse              	id=10	[slave  pointer  (2)]
⎜   ↳ LG Display LGD-MultiTouch               	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ Dell Dell USB Keyboard Hub              	id=8	[slave  keyboard (3)]
    ↳ Dell Dell USB Keyboard Hub              	id=9	[slave  keyboard (3)]
    ↳ ACPI Virtual Keyboard Device            	id=12	[slave  keyboard (3)]

[Favux]

In lsusb is it?:

Bus 001 Device 004: ID 1fd2:0064

If it is that gives us the Vendor and Product ID's. Oh sure it is, that's the same ones as from cat /proc/bus/input/devices.

The system knows it's there given the xinput output so evdev should be picking it up. Let's find out with the output of:

xinput list-props "LG Display LGD-MultiTouch"

[mrsellout]

I am in the same boat.

$ xinput list
⎡ Virtual core pointer                        id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
⎜   ↳ LG Display LGD-MultiTouch                   id=8    [slave  pointer  (2)]
⎜   ↳ ImPS/2 Logitech Wheel Mouse                 id=10    [slave  pointer  (2)]
⎣ Virtual core keyboard                       id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard                 id=5    [slave  keyboard (3)]
    ↳ Power Button                                id=6    [slave  keyboard (3)]
    ↳ Sleep Button                                id=7    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard                id=9    [slave  keyboard (3)]

Here's the output from xinput list-props "LG Display LGD-MultiTouch"

$ xinput list-props "LG Display LGD-MultiTouch"
Device 'LG Display LGD-MultiTouch':
    Device Enabled (116):    1
    Coordinate Transformation Matrix (118):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (243):    0
    Device Accel Constant Deceleration (244):    1.000000
    Device Accel Adaptive Deceleration (245):    1.000000
    Device Accel Velocity Scaling (246):    10.000000
    Evdev Axis Inversion (247):    0, 0
    Evdev Axis Calibration (248):    <no items>
    Evdev Axes Swap (249):    0
    Axis Labels (250):    "Abs X" (236), "Abs Y" (237), "Abs Z" (238), "Abs Rotary X" (239), "Abs Rotary Y" (240), "Abs Rotary Z" (241), "Abs Misc" (242), "Abs Misc" (242), "Abs Misc" (242)
    Button Labels (251):    "Button Left" (119), "Button Unknown" (235), "Button Right" (121), "Button Wheel Up" (122), "Button Wheel Down" (123)
    Evdev Middle Button Emulation (252):    0
    Evdev Middle Button Timeout (253):    50
    Evdev Wheel Emulation (254):    0
    Evdev Wheel Emulation Axes (255):    0, 0, 4, 5
    Evdev Wheel Emulation Inertia (256):    10
    Evdev Wheel Emulation Timeout (257):    200
    Evdev Wheel Emulation Button (258):    4
    Evdev Drag Lock Buttons (259):    0

I also ran evtest, touching the screen produces no change (when running evtest on the mouse changes do occur).

$ sudo evtest /dev/input/event3
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x1fd2 product 0x64 version 0x100
Input device name: "LG Display LGD-MultiTouch"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 320 (ToolPen)
    Event code 321 (ToolRubber)
    Event code 330 (Touch)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value      0
      Min        0
      Max     1920
    Event code 1 (Y)
      Value      0
      Min        0
      Max     1080
    Event code 2 (Z)
      Value      0
      Min        0
      Max     1920
    Event code 3 (Rx)
      Value      0
      Min        0
      Max     1080
    Event code 4 (Ry)
      Value      0
      Min        0
      Max    32767
    Event code 5 (Rz)
      Value      0
      Min        0
      Max    32767
    Event code 40 (Misc)
      Value      0
      Min        0
      Max        1
    Event code 41 (?)
      Value      0
      Min        0
      Max        1
    Event code 42 (?)
      Value      0
      Min        0
      Max     1080
  Event type 4 (Misc)
    Event code 4 (ScanCode)
Testing ... (interrupt to exit)

I am running Natty xubutntu, updated from Maverick and beyond that in the past.

However I do have an issue with the graphics card. Something broke a while back (when I upgraded to Maverick) and I haven't yet got the proprietory Nvidia ones working again. I am running a pretty old GeForce2 MX/MX 400 card, and I've had nightmares trying to get the legacy drivers running on Fedora, I'm going to have another bash this weekend with a clean install of Natty. (I've tried installing a fresh version of Natty, but didn't try fixing the drivers, and I had no joy with the touchscreen).

The reason I brought that up is the monitor was unknown in the GNOME Display Settings configuration app and I can't get a resolution higher than 1024x768. Is this important? The event codes seem to go to the max resolution.

In the mouse configuration program there are 2 mice displayed: the actual mouse and the 'LG Display LGD-MultiTouch'. There are no extra settings under the MultiTouch mouse.

What I will try to do this weekend is get a clean install of Natty up, try fixing the Nvidia driver issue and then seeing how it goes from there.

[Favux]

Alright, we may have something here:

Evdev Axis Calibration (248 ): <no items>

It looks like the kernel isn't feeding evdev the min and max x & y. We should be able to put that in manually.

Option "Calibration" "min-x max-x min-y max-y"
Calibrates the X and Y axes for devices that need to scale to a different coordinate system than reported to the X server. This feature is required for devices that need to scale to a different coordinate system than originally reported by the kernel (e.g. touchscreens). The scaling to the custom coordinate system is done in-driver and the X server is unaware of the transformation. Property: "Evdev Axis Calibration".

I'm thinking the following might only work for Natty. Get the touch working on evdev if possible. Then rely on Canonical's implementing multitouch stuff in Natty. I'm hoping with multitouch working on evdev (we can install mtview to check) then ginn and its wishes.xml may give us multitouch gestures. A pre-Natty release like Lucid might only support single finger touch with the default kernel and evdev driver, once we figure out the correct coordinates to use.

Unfortunately I don't know how to figure out the touchscreen coordinates. Some combination of the active area and resolution?

The kernel reports in points/micrometer. So it should be the active area (screen size?) in cm.s or mm.s converted to micrometers.

The Xserver uses points/meter. So you convert the resolution to that.

But that's the extent of my knowledge so we'll likely be guessing. But we should be able to test coordinates with xinput before we construct a LGD-MultiTouch.conf to apply them permanently. Presumably if we can find the scaling for one axis it should apply to the other.

So I suppose use:
xinput --set-prop "LG Display LGD-MultiTouch" "Evdev Axis Calibration" ? ? ? ?
and guess. Starting with 0 0 1000 1000? Scaling the max x and y to the screen ratios. So need at least the screen size from someone.