How to select the right device on Asus EeeTop

[frodeseverin]

I have troubble using xinput_calibrator on Ubuntu Maverick on an Asus EeeTop ET202T A1.

The tool reports misclicks all the time, and when I use '--misclick 0' i am told to create a file containing some special characters in the MatchProduct string. This does not work.

If I try to use MatchDevicePath I am unsure what to use as match string. The pointer behaves erratically if I use the wron ones. Can you please help?

Please find details in the following:

xinput_calibrator --misclick 0
Warning: multiple calibratable devices found, calibrating last one (IDEACO�  IDC 6681)
    use --device to select another one.
Calibrating EVDEV driver for "IDEACO�  IDC 6681" id=9
    current calibration values (from XInput): min_x=0, max_x=65535 and min_y=0, max_y=65535

Doing dynamic recalibration:
    Setting new calibration data: 1472, 66213, 6, 63744


--> Making the calibration permanent <--
  copy the snippet below into '/etc/X11/xorg.conf.d/99-calibration.conf'
Section "InputClass"
    Identifier  "calibration"
    MatchProduct    "IDEACO�  IDC 6681"
    Option  "Calibration"   "1472 66213 6 63744"
EndSection

Note that the tool wanrns me that there are two devices available. Detals for the first device, although neither of them works:

$ xinput_calibrator --device 8 --misclick 0
Calibrating EVDEV driver for "IDEACO�  IDC 6681" id=8
    current calibration values (from XInput): min_x=0, max_x=8191 and min_y=0, max_y=8191

Doing dynamic recalibration:
    Setting new calibration data: 713, 4754, -8, 8098


--> Making the calibration permanent <--
  copy the snippet below into '/etc/X11/xorg.conf.d/99-calibration.conf'
Section "InputClass"
    Identifier  "calibration"
    MatchProduct    "IDEACO�  IDC 6681"
    Option  "Calibration"   "713 4754 -8 8098"
EndSection

Snippet fom /var/log/Xorg.0.log. note that there is no mention of calibration. If I use a simpler MatchProduct string, all the IDC devices are calibrated, and this does not work. Using MatchDevicePath could solve the problem, but which device do I use? And then I would need to set up a udev rule, I guess, to make the path consistent.

[  3544.826] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[  3544.853] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[  3544.853] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[  3544.853] (II) LoadModule: "evdev"
[  3544.854] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[  3544.855] (II) Module evdev: vendor="X.Org Foundation"
[  3544.855]    compiled for 1.9.0, module version = 2.3.2
[  3544.855]    Module class: X.Org XInput Driver
[  3544.855]    ABI class: X.Org XInput driver, version 11.0
[  3544.855] (**) Power Button: always reports core events
[  3544.855] (**) Power Button: Device: "/dev/input/event1"
[  3544.873] (II) Power Button: Found keys
[  3544.873] (II) Power Button: Configuring as keyboard
[  3544.873] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[  3544.873] (**) Option "xkb_rules" "evdev"
[  3544.873] (**) Option "xkb_model" "evdev"
[  3544.873] (**) Option "xkb_layout" "no"
[  3544.880] (II) XKB: reuse xkmfile /var/lib/xkb/server-98DE986667AD67BA200A7AACB598729E85757727.xkm
[  3544.886] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[  3544.886] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[  3544.886] (**) Power Button: always reports core events
[  3544.886] (**) Power Button: Device: "/dev/input/event0"
[  3544.905] (II) Power Button: Found keys
[  3544.905] (II) Power Button: Configuring as keyboard
[  3544.905] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[  3544.905] (**) Option "xkb_rules" "evdev"
[  3544.905] (**) Option "xkb_model" "evdev"
[  3544.905] (**) Option "xkb_layout" "no"
[  3544.911] (II) config/udev: Adding input device IDEACO�  IDC 6681 (/dev/input/event2)
[  3544.911] (**) IDEACO�  IDC 6681: Applying InputClass "evdev tablet catchall"
[  3544.911] (**) IDEACO�  IDC 6681: always reports core events
[  3544.911] (**) IDEACO�  IDC 6681: Device: "/dev/input/event2"
[  3544.937] (II) IDEACO�  IDC 6681: Found 3 mouse buttons
[  3544.937] (II) IDEACO�  IDC 6681: Found absolute axes
[  3544.937] (II) evdev-grail: failed to open grail, no gesture support
[  3544.937] (II) IDEACO�  IDC 6681: Found x and y absolute axes
[  3544.937] (II) IDEACO�  IDC 6681: Found absolute tablet.
[  3544.937] (II) IDEACO�  IDC 6681: Configuring as tablet
[  3544.938] (**) IDEACO�  IDC 6681: YAxisMapping: buttons 4 and 5
[  3544.938] (**) IDEACO�  IDC 6681: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[  3544.938] (II) XINPUT: Adding extended input device "IDEACO�  IDC 6681" (type: TABLET)
[  3544.938] (II) IDEACO�  IDC 6681: initialized for absolute axes.
[  3544.939] (II) config/udev: Adding input device IDEACO�  IDC 6681 (/dev/input/mouse0)
[  3544.939] (II) No input driver/identifier specified (ignoring)
[  3544.940] (II) config/udev: Adding input device IDEACO�  IDC 6681 (/dev/input/event3)
[  3544.940] (**) IDEACO�  IDC 6681: Applying InputClass "evdev pointer catchall"
[  3544.940] (**) IDEACO�  IDC 6681: always reports core events
[  3544.940] (**) IDEACO�  IDC 6681: Device: "/dev/input/event3"
[  3544.969] (II) IDEACO�  IDC 6681: Found 3 mouse buttons
[  3544.969] (II) IDEACO�  IDC 6681: Found absolute axes
[  3544.969] (II) evdev-grail: failed to open grail, no gesture support
[  3544.969] (II) IDEACO�  IDC 6681: Found x and y absolute axes
[  3544.969] (II) IDEACO�  IDC 6681: Configuring as mouse
[  3544.969] (**) IDEACO�  IDC 6681: YAxisMapping: buttons 4 and 5
[  3544.969] (**) IDEACO�  IDC 6681: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[  3544.969] (II) XINPUT: Adding extended input device "IDEACO�  IDC 6681" (type: MOUSE)
[  3544.970] (II) IDEACO�  IDC 6681: initialized for absolute axes.
[  3544.971] (II) config/udev: Adding input device IDEACO�  IDC 6681 (/dev/input/js0)
[  3544.971] (II) No input driver/identifier specified (ignoring)
[  3544.971] (II) config/udev: Adding input device IDEACO�  IDC 6681 (/dev/input/mouse1)
[  3544.971] (II) No input driver/identifier specified (ignoring)
[  3544.973] (II) config/udev: Adding input device Chicony 2.4G Multimedia Wireless Kit (/dev/input/event4)
[  3544.973] (**) Chicony 2.4G Multimedia Wireless Kit: Applying InputClass "evdev keyboard catchall"
[  3544.973] (**) Chicony 2.4G Multimedia Wireless Kit: always reports core events
[  3544.973] (**) Chicony 2.4G Multimedia Wireless Kit: Device: "/dev/input/event4"
[  3545.001] (II) Chicony 2.4G Multimedia Wireless Kit: Found keys

[frodeseverin]

I did not intend to close this issue. How do I reopen it?

[tias]

Hey frodeseverin,

Sorry for reopening without commenting, I must have overlooked it later on.

I'm interested in the special characters in the MatchProduct string. Could you send me the full output of running the calibrator with the --verbose flag? (on deviceid 8)

As to the misclick behaviour: this usually means that something is wrong in getting the coordinates. Can you verify that your screen is recognized correctly, e.g. if you drag your finger over the screen, does the pointer move in a comparable way, although mis-calibrated?

As to the xorg configuration: that's a bit beyond my knowledge. Your MatchProduct string should be "IDEACO IDC 6681". Interestingly the xorg log shows that your device is recognised as both a table and a mouse, but not as a touchscreen. I guess it should be recognised as touchscreen for the calibration to take effect...
Please file a bug against evdev at the xorg bugzilla https://bugs.freedesktop.org
to figure out what is going wrong there, and how to fix it.