Re: evdev fails with Couldn't open mtdev device
On Mon, 2011-07-11 at 16:07 -0700, walt wrote: Have you read about the new InputClass Section? It has some advantages over the older InputDevice, including the important ability to identify devices by their plug-n-play names instead the event number. As an example, here's my input section for a non-standard mouse: #cat /etc/X11/xorg.conf.d/10-trackball.conf Section InputClass --- note the new name Identifier trackball - I made this name up MatchProduct ImExPS- important: I did not make this up Option AutoServerLayout on Option Emulate3Buttons on Option EmulateWheel on Option EmulateWheelButton 8 EndSection Thanks for the hint - I've also stumbled across that in the manpage and it actually does provide sort of a solution for my problem: Section InputDevice Identifier nullpointer Driver void Option CorePointer true EndSection Section InputClass Identifier mimoTouch MatchIsTouchscreen true Option InvertY true Option Calibration 1252 31534 1598 31680 EndSection Section InputClass Identifier nokeyboard MatchIsKeyboard true Option Ignore true EndSection Section InputClass Identifier nomouse MatchIsPointer true Option Ignore true EndSection Section ServerFlags Option AllowEmptyInput true Option AutoAddDevices true Option AutoEnableDevices false EndSection So I have 3 InputClasses - 2 to disable standard devices, 1 to configure the touchscreen and one void InputDevice to disable the default core pointer (which would otherwise use /dev/input/mice). Looks a bit like a hack to me, but works. Florian signature.asc Description: This is a digitally signed message part ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: evdev fails with Couldn't open mtdev device
On Tue, Jul 12, 2011 at 01:48:53PM +0200, Florian Echtler wrote: On Mon, 2011-07-11 at 16:07 -0700, walt wrote: Have you read about the new InputClass Section? It has some advantages over the older InputDevice, including the important ability to identify devices by their plug-n-play names instead the event number. As an example, here's my input section for a non-standard mouse: #cat /etc/X11/xorg.conf.d/10-trackball.conf Section InputClass --- note the new name Identifier trackball - I made this name up MatchProduct ImExPS- important: I did not make this up Option AutoServerLayout on Option Emulate3Buttons on Option EmulateWheel on Option EmulateWheelButton 8 EndSection Thanks for the hint - I've also stumbled across that in the manpage and it actually does provide sort of a solution for my problem: Section InputDevice Identifier nullpointer Driver void Option CorePointer true EndSection Section InputClass Identifier mimoTouch MatchIsTouchscreen true Option InvertY true Option Calibration 1252 31534 1598 31680 EndSection Section InputClass Identifier nokeyboard MatchIsKeyboard true Option Ignore true EndSection Section InputClass Identifier nomouse MatchIsPointer true Option Ignore true EndSection Section ServerFlags Option AllowEmptyInput true Option AutoAddDevices true Option AutoEnableDevices false EndSection So I have 3 InputClasses - 2 to disable standard devices, 1 to configure the touchscreen and one void InputDevice to disable the default core pointer (which would otherwise use /dev/input/mice). Looks a bit like a hack to me, but works. input classes accumulate in lexical sort order (for the filenames). So you could have a class that ignores _all_ input devices and then set Option Ignore false for the ones you want to enable. Cheers, Peter ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: evdev fails with Couldn't open mtdev device
On Mon, Jul 11, 2011 at 11:24:28AM +0200, Florian Echtler wrote: Hi everyone, I'm trying to configure a secondary X server for an auxiliary touchscreen, but I'm having some problems with the input configuration. To keep input for my main screen and the auxiliary screen separate, I'm using the following config for the secondary one: Section InputDevice Identifier mimoTouch Driver evdev Option CorePointer trueB CorePointer is a default anyway, so yuou don't need it (besides, deprecated upstream, see Option Floating) Option Device /dev/input/event2 EndSection Section ServerFlags Option AllowEmptyInput true don't ever use this option. We've even removed it upstream now so people can't use it anymore but I don't know if your server version carries the patch. Option AutoAddDevices false Option AutoEnableDevices false EndSection The idea is that the secondary server doesn't touch any devices from the primary, just the statically configured touchscreen device. However, I'm getting the following error (the touchscreen is single-touch): (II) Using input driver 'evdev' for 'mimoTouch' (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so (**) Option CorePointer (**) mimoTouch: always reports core events (**) mimoTouch: Device: /dev/input/event2 (EE) mimoTouch: Couldn't open mtdev device (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device (EE) PreInit returned 8 for mimoTouch (II) Unloading evdev for the mtdev stuff, not sure. We don't carry that upstream yet and I'm not sure what Ubuntu ships here. However, I do notice that your config says event2 and your log snippet says event8. This may be the source for the issue. Cheers, Peter On the other hand, when I set AutoAddDevices to true, then evdev handles the touchscreen just fine: (II) config/udev: Adding input device e2i Technology, Inc. USB Touchpanel (/dev/input/event8) (**) e2i Technology, Inc. USB Touchpanel: Applying InputClass evdev touchscreen catchall (II) Using input driver 'evdev' for 'e2i Technology, Inc. USB Touchpanel' (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so (**) e2i Technology, Inc. USB Touchpanel: always reports core events (**) e2i Technology, Inc. USB Touchpanel: Device: /dev/input/event8 (--) e2i Technology, Inc. USB Touchpanel: Found absolute axes (II) evdev-grail: failed to open grail, no gesture support (--) e2i Technology, Inc. USB Touchpanel: Found x and y absolute axes (--) e2i Technology, Inc. USB Touchpanel: Found absolute touchscreen (II) e2i Technology, Inc. USB Touchpanel: Configuring as touchscreen (**) e2i Technology, Inc. USB Touchpanel: YAxisMapping: buttons 4 and 5 (**) e2i Technology, Inc. USB Touchpanel: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (**) Option config_info udev:/sys/devices/pci:00/:00:1d.7/usb2/2-2/2-2.3/2-2.3:1.0/input/input31/event8 (II) XINPUT: Adding extended input device e2i Technology, Inc. USB Touchpanel (type: TOUCHSCREEN) (II) e2i Technology, Inc. USB Touchpanel: initialized for absolute axes. (**) e2i Technology, Inc. USB Touchpanel: (accel) keeping acceleration scheme 1 (**) e2i Technology, Inc. USB Touchpanel: (accel) acceleration profile 0 (**) e2i Technology, Inc. USB Touchpanel: (accel) acceleration factor: 2.000 (**) e2i Technology, Inc. USB Touchpanel: (accel) acceleration threshold: 4 So my question is: what do I have to do to get the static config to work just like the auto-added config? OS is stock Ubuntu 11.04. Thanks, Florian ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: evdev fails with Couldn't open mtdev device
On 07/11/2011 02:24 AM, Florian Echtler wrote: Hi everyone, I'm trying to configure a secondary X server for an auxiliary touchscreen, but I'm having some problems with the input configuration. To keep input for my main screen and the auxiliary screen separate, I'm using the following config for the secondary one: Section InputDevice Identifier mimoTouch Driver evdev Option CorePointer trueB Option Device /dev/input/event2 EndSection Have you read about the new InputClass Section? It has some advantages over the older InputDevice, including the important ability to identify devices by their plug-n-play names instead the event number. As an example, here's my input section for a non-standard mouse: #cat /etc/X11/xorg.conf.d/10-trackball.conf Section InputClass --- note the new name Identifier trackball - I made this name up MatchProduct ImExPS- important: I did not make this up Option AutoServerLayout on Option Emulate3Buttons on Option EmulateWheel on Option EmulateWheelButton 8 EndSection Note the MatchProduct keyword. Unless you have two identical input devices this product name will be unique and invariant over reboots, unlike event2. There are two places I could get the string for MatchProduct -- dmesg and #udevadm info --export-db: #dmesg|grep Logitech input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input4 And the corresponding (very small) section from udevadm info --export-db: P: /devices/platform/i8042/serio1/input/input4 E: UDEV_LOG=3 E: DEVPATH=/devices/platform/i8042/serio1/input/input4 E: PRODUCT=11/2/6/6d E: NAME=ImExPS/2 Logitech Explorer Mouse E: PHYS=isa0060/serio1/input0 E: PROP=0 E: EV=7 E: KEY=1f 0 0 0 0 0 0 0 0 E: REL=143 E: MODALIAS=input:b0011v0002p0006e006D-e0,1,2,k110,111,112,113,114,r0,1,6,8,amlsfw E: SUBSYSTEM=input I don't know if any of this will help solve your problem, but I'd be interested to know if any of the experts here will include it in their advice. ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
