Re: Why does libinput randomly calls my touchpad "SynPS/2 Synaptics" or "Synaptics TM2722-001"?
Just so folks know: I happen to have experience with this part of the linux kernel (it's not a libinput bug) so I handled this offlist and redirected Ottavio to the right place to ask for support ♥ On Tue, 2024-04-23 at 15:12 +0100, Ottavio Caruso wrote: > Hi, > > $ sudo X -version > > X.Org X Server 1.21.1.7 > X Protocol Version 11, Revision 0 > Current Operating System: Linux t440 6.1.0-20-amd64 #1 SMP > PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 > Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-20-amd64 > root=UUID=42a17f43-89bb-4523-952f-b8d97bcb4a30 ro quiet > xorg-server 2:21.1.7-3+deb12u7 (https://www.debian.org/support) > Current version of pixman: 0.42.2 > > $ xinput --version > xinput version 1.6.3 > XI version on server: 2.4 > > > > On my old-ish Thinkpad T440, libinput alternatively calls my touchpad > "SynPS/2 Synaptics" or "Synaptics TM2722-001". > > $ grep Synaptics /var/log/messages > Nov 26 09:12:38 t440 kernel: [18070.908478] psmouse serio1: > synaptics: > serio: Synaptics pass-through port at isa0060/serio1/input0 > Nov 26 09:12:38 t440 kernel: [18070.947812] input: SynPS/2 Synaptics > TouchPad as /devices/platform/i8042/serio1/input/input35 > Nov 26 20:33:19 t440 kernel: [27221.274488] rmi4_f01 rmi4-00.fn01: > found > RMI device, manufacturer: Synaptics, product: TM2722-001, fw id: 0 > Nov 26 20:33:19 t440 kernel: [27221.314747] input: Synaptics TM2722- > 001 > as /devices/pci:00/:00:1f.3/i2c-0/0-002c/rmi4- > 00/input/input39 > Nov 27 19:28:05 t440 kernel: [ 6.327297] psmouse serio1: > synaptics: > serio: Synaptics pass-through port at isa0060/serio1/input0 > Nov 27 19:28:05 t440 kernel: [ 6.366655] input: SynPS/2 Synaptics > TouchPad as /devices/platform/i8042/serio1/input/input2 > > This without even rebooting or suspending the laptop. > > I have some scripts that disable or enable the touchpad (especially > when > I use the mouse) and I have to use tricks to accommodate this. > > Why does this happen in the first place? How can I troubleshoot it? > > Thanks. > -- Cheers, Lyude Paul (she/her) Software Engineer at Red Hat
Modifier or Meta Keys and Disabling Touchpad
Hi - I have been trying to find a way to disable my touchpad (for pre-set amount of time) while pressing keys like Alt, Ctrl, or Shift. When I type typical alphanumeric keys on the keyboard my touchpad is disabled properly. Is there a way by using any of the x-cmds or other method(s) to have my touchpad disabled this way (for a pre-set amount of time)? Thank you for any help with an X-newb. C
Re: Keyboard/Touchpad not recognized by X software
On Thu, Dec 17, 2020 at 06:40:52PM -0700, Ivan wrote:
> They work just find in FreeBSD, but fail to get recognized by X11. I got
> Xfce4 to run and all, but I have to use the power button to shutdown and
> go back the FreeBSD command prompt.
>
> These are the relevant lines in /var/log/Xorg.0.log:
>
> 9102.753 config/udev: Adding input device AT keyboard (/dev/input/event5)
> 9102.753 AT Keyboard: Applying InputClass “Evdev Keyboard”
> 9102.753 AT Keyboard: Applying InputClass “KeyboardDefaults”
> 9102.754 No input driver specified, ignoring this device.
> 9102.754 This device may have been added with another device file.
> 9102.754 config/udev: Adding input device Syn PS/2 Synaptics Touchpad
> (/dev/input/event6)
> 9102.754 No input driver specified, ignoring this device.
> 9102.754 This device may have been added with another device file.
>
> How should I proceed from here to get the X server to recognize my keyboard
> and touchpad?
basically: your xorg.conf snippets are missing a Driver "foo" line, where
"foo" is the driver name. On Linux this would be "libinput" or previously
"evdev" ("synaptics" for touchpads). FreeBSD supports the evdev kernel
interface these days, so the same config should work there too but I haven't
tested it.
The default snippets shipped by the various xorg drivers assign themselves
to the right devices, so I suspect there's something bsd-specific or some
leftover config that's tripping you up.
Cheers,
Peter
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
Keyboard/Touchpad not recognized by X software
They work just find in FreeBSD, but fail to get recognized by X11. I got Xfce4 to run and all, but I have to use the power button to shutdown and go back the FreeBSD command prompt. These are the relevant lines in /var/log/Xorg.0.log: 9102.753config/udev: Adding input device AT keyboard (/dev/input/event5) 9102.753AT Keyboard: Applying InputClass “Evdev Keyboard” 9102.753AT Keyboard: Applying InputClass “KeyboardDefaults” 9102.754No input driver specified, ignoring this device. 9102.754This device may have been added with another device file. 9102.754config/udev: Adding input device Syn PS/2 Synaptics Touchpad (/dev/input/event6) 9102.754No input driver specified, ignoring this device. 9102.754This device may have been added with another device file. How should I proceed from here to get the X server to recognize my keyboard and touchpad? Thank you very much in advance! Sent from Mail for Windows 10 ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: losing touchpad events in some windows
> > I'm on > > libinput 1.14.3 > > xf86-input-libinput 0.29.0 > > libevdev 1.8.0 > > > > do you know if these are affected? > > Not by that specific bug above, no. Time to file a bug against libinput, I > guess. > > Note that the libinput debug-events output may be a false positive, you'd > have to keep it running across the suspend/resume cycle to have it trigger > the same issues. If you start it once the bug occured, you'll have missed > the trigger. > I'm still not sure if this is libinput and if it is connected to suspend/resume. I just got it again and it acts weird: windows sometimes stop receiving finger scroll and tap events, but alt-tab back and forth fixes it for a while. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: losing touchpad events in some windows
On Fri, Mar 06, 2020 at 01:25:48PM -0800, Konstantin Sobolev wrote: > Hi > > > I'm running xorg-server 1.20.6 with xorg-drivers 1.20 on Dell Precision > > 9540 > > > libinput is used for input, with touchpad using i2c_hid driver, this is > > on > > > 5.5.7 kernel > > > > > > Sometimes (after suspend/resume?) touchpad taps and two finger scroll > > stops > > > working in some windows, which spreads to all windows after a while. > > > "libinput debug-events" still shows all the events correctly when this > > > happens, but "xev" does not. > > > > There's a regression in libinput 1.15.1 and to a lesser extent 1.15.2. If > > you're on either of those upgrading to 1.15.3 (released today) should fix > > it. Assuming this is the problem anyway. > > > > Also, libevdev 1.9.0 because it's all somewhat interconnected. > > > > I'm on > libinput 1.14.3 > xf86-input-libinput 0.29.0 > libevdev 1.8.0 > > do you know if these are affected? Not by that specific bug above, no. Time to file a bug against libinput, I guess. Note that the libinput debug-events output may be a false positive, you'd have to keep it running across the suspend/resume cycle to have it trigger the same issues. If you start it once the bug occured, you'll have missed the trigger. Cheers, Peter ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: losing touchpad events in some windows
Hi > I'm running xorg-server 1.20.6 with xorg-drivers 1.20 on Dell Precision > 9540 > > libinput is used for input, with touchpad using i2c_hid driver, this is > on > > 5.5.7 kernel > > > > Sometimes (after suspend/resume?) touchpad taps and two finger scroll > stops > > working in some windows, which spreads to all windows after a while. > > "libinput debug-events" still shows all the events correctly when this > > happens, but "xev" does not. > > There's a regression in libinput 1.15.1 and to a lesser extent 1.15.2. If > you're on either of those upgrading to 1.15.3 (released today) should fix > it. Assuming this is the problem anyway. > > Also, libevdev 1.9.0 because it's all somewhat interconnected. > I'm on libinput 1.14.3 xf86-input-libinput 0.29.0 libevdev 1.8.0 do you know if these are affected? thanks! ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: losing touchpad events in some windows
On Thu, Mar 05, 2020 at 08:35:20AM -0800, Konstantin Sobolev wrote: > Hi > I'm running xorg-server 1.20.6 with xorg-drivers 1.20 on Dell Precision 9540 > libinput is used for input, with touchpad using i2c_hid driver, this is on > 5.5.7 kernel > > Sometimes (after suspend/resume?) touchpad taps and two finger scroll stops > working in some windows, which spreads to all windows after a while. > "libinput debug-events" still shows all the events correctly when this > happens, but "xev" does not. There's a regression in libinput 1.15.1 and to a lesser extent 1.15.2. If you're on either of those upgrading to 1.15.3 (released today) should fix it. Assuming this is the problem anyway. Also, libevdev 1.9.0 because it's all somewhat interconnected. Cheers, Peter > Reloading i2c modules helps to some extent, but only for a while. A real > fix is to restart X11. > > ~ » xinput list > ⎡ Virtual core pointer id=2[master pointer > (3)] > ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer > (2)] > ⎜ ↳ DELL0926:00 044E:1220 Mouse id=13 [slave pointer > (2)] > ⎜ ↳ DELL0926:00 044E:1220 Touchpadid=15 [slave pointer > (2)] <<-- this one > ⎣ Virtual core keyboard id=3[master keyboard > (2)] > ↳ Virtual core XTEST keyboard id=5[slave keyboard > (3)] > [skip] > > How can I debug it further? > Thanks > ___ > xorg@lists.x.org: X.Org support > Archives: http://lists.freedesktop.org/archives/xorg > Info: https://lists.x.org/mailman/listinfo/xorg > Your subscription address: %(user_address)s ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
losing touchpad events in some windows
Hi I'm running xorg-server 1.20.6 with xorg-drivers 1.20 on Dell Precision 9540 libinput is used for input, with touchpad using i2c_hid driver, this is on 5.5.7 kernel Sometimes (after suspend/resume?) touchpad taps and two finger scroll stops working in some windows, which spreads to all windows after a while. "libinput debug-events" still shows all the events correctly when this happens, but "xev" does not. Reloading i2c modules helps to some extent, but only for a while. A real fix is to restart X11. ~ » xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ DELL0926:00 044E:1220 Mouse id=13 [slave pointer (2)] ⎜ ↳ DELL0926:00 044E:1220 Touchpadid=15 [slave pointer (2)] <<-- this one ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] [skip] How can I debug it further? Thanks ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Touchpad gesture events via XInput2?
Hello Peter, On Wed, Sep 11, 2019 at 01:42:05PM +1000, Peter Hutterer wrote: > There's going to be a lot more detail to it than it may seem on the surface > too, usually any attempts to add new input events come to a halt when it > comes to figuring out how grabs will work with those new events in a > backwards compatible manner. > But yeah, adding gestures to XI2 (or a new extension, but I'm not sure that > would make things easier) is the likely best option. Note that "best" > doesn't mean "easy" :) Thanks for taking the time to explain this to me. To not leave this thread dangling I just want to respond that an undertaking of this magnitude is currently beyond what I can invest time-wise. But I'll be happy to be the first to try out and review anything anyone comes up with. :) -- Thanks, Micha ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Touchpad gesture events via XInput2?
On Tue, Sep 10, 2019 at 09:51:47PM +0200, Michael Weiser wrote: > Hello, > > I've been looking into the current state of affairs regarding touchpad > gestures such as swipe and pinch on Linux as an end user. Everybody > wanting to support them seems to be talking to libinput directly, either > necessitating the user having access to the input device nodes directly > (e.g. libinput-gestures) or talking to systemd's logind, becoming its > exclusive session controller and have it hand over open fds to those > (e.g. mutter [and only on wayland?]). > > The former raises security concerns and the latter seems like a lot of > initial (logind) and followup (passing on events/access) work, quite > constraining (only one session controller) and DE(desktop > envionment)-specific to me (e.g. How does a KDE program see gestures > when running in a Gnome session where mutter is (maybe) passing them as > GTK signals?). > > So I'm wondering: Are there any plans to deliver them as X events e.g. > via XInput2 or any reasons why that would be a bad idea[tm]? > > I've done a bit of hacking of xf86-input-libinput, xorgproto, libxi and > xserver on a rainy afternoon and can now receive newly created swipe > XInput2 events - admittedly without any coordinates because I've yet to > understand the X server's valuator magic. Though it can obviously be > done I'm just wondering if it'd be worthwile spending any more thought > on. The basic thing with touchpad gestures in XI2 is: you'll need to write XI 2.4 for it, i.e. all the bits that you mention. i.e. writing the specs, figuring out the corner cases, updating everything, etc. No-one has so far found the motivation to do this and that's the simple reason it doesn't exist. It's generally code that no-one wants to touch unless they have to. There's going to be a lot more detail to it than it may seem on the surface too, usually any attempts to add new input events come to a halt when it comes to figuring out how grabs will work with those new events in a backwards compatible manner. But yeah, adding gestures to XI2 (or a new extension, but I'm not sure that would make things easier) is the likely best option. Note that "best" doesn't mean "easy" :) Cheers, Peter ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Touchpad gesture events via XInput2?
Hello, I've been looking into the current state of affairs regarding touchpad gestures such as swipe and pinch on Linux as an end user. Everybody wanting to support them seems to be talking to libinput directly, either necessitating the user having access to the input device nodes directly (e.g. libinput-gestures) or talking to systemd's logind, becoming its exclusive session controller and have it hand over open fds to those (e.g. mutter [and only on wayland?]). The former raises security concerns and the latter seems like a lot of initial (logind) and followup (passing on events/access) work, quite constraining (only one session controller) and DE(desktop envionment)-specific to me (e.g. How does a KDE program see gestures when running in a Gnome session where mutter is (maybe) passing them as GTK signals?). So I'm wondering: Are there any plans to deliver them as X events e.g. via XInput2 or any reasons why that would be a bad idea[tm]? I've done a bit of hacking of xf86-input-libinput, xorgproto, libxi and xserver on a rainy afternoon and can now receive newly created swipe XInput2 events - admittedly without any coordinates because I've yet to understand the X server's valuator magic. Though it can obviously be done I'm just wondering if it'd be worthwile spending any more thought on. -- Thanks, Michael ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: touchpad
Hi Lucas, Didn't you get errors in ./configure output ? You might also check config.log in the same directory ; it will show you more details about eventual errors. Le 11/11/2017 à 00:35, Lucas Barros a écrit : Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: touchpad
Am 11.11.2017 00:35, schrieb Lucas Barros: > I, i was installing synaptics and while following the instructions, i > opened the terminal and made cd to the right directory and made > ./configure, but after whem i made make it didn t do anything it just > printed > > make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. > > it's in portuguese... and i don t know what to do after > > thank you! > > > Hi Lucas, just a hint: Since the language of choise in this list is english (i am not native either) it is helpful to have the errors in that language also. Next time try env LANG=C make to have a error message that more people on this list can decode. re, wh ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: touchpad
On Fri, Nov 10, 2017 at 11:35:28PM +, Lucas Barros wrote: > I, i was installing synaptics and while following the instructions, i > opened the terminal and made cd to the right directory and made > ./configure, but after whem i made make it didn t do anything it just > printed > > make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. > > it's in portuguese... and i don t know what to do after > > thank you! Google translate suggests it means "No target indicated and no make file found. Stop it." (I suppose probably the 'it' is not really wanted.) So, your configure didn't work - I assume you got some error message(s) from that, so you need to fix the problem(s). If in doubt, ./configure ... 2>&1 | tee a-logfile will create an output logfile so that you can go back and look at messages which might have scrolled off your screen. ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
touchpad
I, i was installing synaptics and while following the instructions, i opened the terminal and made cd to the right directory and made ./configure, but after whem i made make it didn t do anything it just printed make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. it's in portuguese... and i don t know what to do after thank you! ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Configure touchpad for touchscreen driver
Am 2017-05-08 um 02:40 schrieb Peter Hutterer: > On Mon, May 08, 2017 at 10:39:32AM +1000, Peter Hutterer wrote: >> On Fri, May 05, 2017 at 05:30:51PM +0200, Martin Kepplinger wrote: >>> Hi, >>> >>> I'm doing a touchscreen xorg input driver. >> >> First question: why? :) >> we generally discourage people from doing that, instead it's better to write >> a kernel driver and use the existing evdev/libinput drivers. I'm reviving / rewriting xf86-input-tslib, the main sources now living at https://github.com/merge/xf86-input-tslib With tslib, I *am* somewhat pushing towards having evdev kernel drivers. (Sadly, there are *real* userspace drivers in tslib because there's no proper driver, but I don't have the hardware to write them; even more sadly, there are companies that still ship tslib drivers in their BSPs instead of kernel drivers) but that's a different thing. tslib itself lives at http://tslib.org So the real reason I need tslib is the filter stack and easy to use graphical calibration (and the little dependencies and portability are a bonus too). All these "drivers" :) To me, xf86-input-tslib is no driver. tslib (or the libts library) isn't either. It's either a userspace driver as tslib module or a proper kernel driver. But, oh well :) I'm getting off track here, but libinput is really interesting in that it does gesture recognition too. Do you somehow sync that work with gtk+ or others who do that too? >> >>> For testing purposes, I'd like to configure my laptop's touchpad for the >>> driver to use. It's totally comparable and I've done it for other stuff >>> for rough testing. I append the evtest output below. Should be fine. >>> >>> I'm unsure how to override all other touchpad configs in my system. >>> >>> * is it enough to say "MatchIsTouchpad" instead of touchscreen? There's >>> obviously only one touchpad. Ideally I think I should omit >>> "MatchIsTouchpad" and say only "Device=/dev/input/event1" or whatever >>> number it is? Would that be possible? >> >> MatchIsTouchpad maps to the udev property ID_INPUT_TOUCHPAD, your homework >> is to figure out what MatchIsTouchscreen maps to ;) >> so doing that would be enough, but you could also add a >> MatchProduct "ETPS/2 Elantech Touchpad" to only match on that touchpad. >> >> Don't match on device nodes as they can change during reboots. >> >>> * My driver config installs to /usr/local/share/X11/... Will this >>> *ever* override /usr/share/X11 configs? Even if I call it >>> "00-mydriver.conf" in /usr/local/ >> >> the server is usually configured to look into /usr/share/X11/ and /etc/X11, >> but not elsewhere. So anything you put in /usr/local is ignored. The start >> of the xorg.log should list where the server is looking for configs. >> >> for local configurations, you're supposed to put them into /etc/ anyway, >> distribution-provided config snippets go into /usr/local. > > make that: > distribution-provided config snippets go into /usr/share. Sure. thanks Peter for getting back at me. I actually had figured it out and have a pretty nice dev setup. > > Cheers, >Peter > ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Configure touchpad for touchscreen driver
On Mon, May 08, 2017 at 03:33:33AM +0200, Martin Kepplinger wrote: > Am 2017-05-08 um 02:40 schrieb Peter Hutterer: > > On Mon, May 08, 2017 at 10:39:32AM +1000, Peter Hutterer wrote: > >> On Fri, May 05, 2017 at 05:30:51PM +0200, Martin Kepplinger wrote: > >>> Hi, > >>> > >>> I'm doing a touchscreen xorg input driver. > >> > >> First question: why? :) > >> we generally discourage people from doing that, instead it's better to > >> write > >> a kernel driver and use the existing evdev/libinput drivers. > > I'm reviving / rewriting xf86-input-tslib, the main sources now living > at https://github.com/merge/xf86-input-tslib > > With tslib, I *am* somewhat pushing towards having evdev kernel drivers. > (Sadly, there are *real* userspace drivers in tslib because there's no > proper driver, but I don't have the hardware to write them; even more > sadly, there are companies that still ship tslib drivers in their BSPs > instead of kernel drivers) but that's a different thing. tslib itself > lives at http://tslib.org > > So the real reason I need tslib is the filter stack and easy to use > graphical calibration (and the little dependencies and portability are a > bonus too). > > All these "drivers" :) To me, xf86-input-tslib is no driver. tslib (or > the libts library) isn't either. It's either a userspace driver as tslib > module or a proper kernel driver. But, oh well :) > > > I'm getting off track here, but libinput is really interesting in that > it does gesture recognition too. Do you somehow sync that work with gtk+ > or others who do that too? libinput only does gesture recognition on touchpads where toolkits can't meaningfully provide gestures. it doesn't do it on touchscreens where the toolkits have the better context, so for touchscreens we merely forward the events as-is. Cheers, Peter > > > >> > >>> For testing purposes, I'd like to configure my laptop's touchpad for the > >>> driver to use. It's totally comparable and I've done it for other stuff > >>> for rough testing. I append the evtest output below. Should be fine. > >>> > >>> I'm unsure how to override all other touchpad configs in my system. > >>> > >>> * is it enough to say "MatchIsTouchpad" instead of touchscreen? There's > >>> obviously only one touchpad. Ideally I think I should omit > >>> "MatchIsTouchpad" and say only "Device=/dev/input/event1" or whatever > >>> number it is? Would that be possible? > >> > >> MatchIsTouchpad maps to the udev property ID_INPUT_TOUCHPAD, your homework > >> is to figure out what MatchIsTouchscreen maps to ;) > >> so doing that would be enough, but you could also add a > >> MatchProduct "ETPS/2 Elantech Touchpad" to only match on that touchpad. > >> > >> Don't match on device nodes as they can change during reboots. > >> > >>> * My driver config installs to /usr/local/share/X11/... Will this > >>> *ever* override /usr/share/X11 configs? Even if I call it > >>> "00-mydriver.conf" in /usr/local/ > >> > >> the server is usually configured to look into /usr/share/X11/ and /etc/X11, > >> but not elsewhere. So anything you put in /usr/local is ignored. The start > >> of the xorg.log should list where the server is looking for configs. > >> > >> for local configurations, you're supposed to put them into /etc/ anyway, > >> distribution-provided config snippets go into /usr/local. > > > > make that: > > distribution-provided config snippets go into /usr/share. > > Sure. thanks Peter for getting back at me. I actually had figured it out > and have a pretty nice dev setup. > > > > > Cheers, > >Peter > > > ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Configure touchpad for touchscreen driver
On Mon, May 08, 2017 at 10:39:32AM +1000, Peter Hutterer wrote: > On Fri, May 05, 2017 at 05:30:51PM +0200, Martin Kepplinger wrote: > > Hi, > > > > I'm doing a touchscreen xorg input driver. > > First question: why? :) > we generally discourage people from doing that, instead it's better to write > a kernel driver and use the existing evdev/libinput drivers. > > > For testing purposes, I'd like to configure my laptop's touchpad for the > > driver to use. It's totally comparable and I've done it for other stuff > > for rough testing. I append the evtest output below. Should be fine. > > > > I'm unsure how to override all other touchpad configs in my system. > > > > * is it enough to say "MatchIsTouchpad" instead of touchscreen? There's > > obviously only one touchpad. Ideally I think I should omit > > "MatchIsTouchpad" and say only "Device=/dev/input/event1" or whatever > > number it is? Would that be possible? > > MatchIsTouchpad maps to the udev property ID_INPUT_TOUCHPAD, your homework > is to figure out what MatchIsTouchscreen maps to ;) > so doing that would be enough, but you could also add a > MatchProduct "ETPS/2 Elantech Touchpad" to only match on that touchpad. > > Don't match on device nodes as they can change during reboots. > > > * My driver config installs to /usr/local/share/X11/... Will this > > *ever* override /usr/share/X11 configs? Even if I call it > > "00-mydriver.conf" in /usr/local/ > > the server is usually configured to look into /usr/share/X11/ and /etc/X11, > but not elsewhere. So anything you put in /usr/local is ignored. The start > of the xorg.log should list where the server is looking for configs. > > for local configurations, you're supposed to put them into /etc/ anyway, > distribution-provided config snippets go into /usr/local. make that: distribution-provided config snippets go into /usr/share. Cheers, Peter ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Configure touchpad for touchscreen driver
On Fri, May 05, 2017 at 05:30:51PM +0200, Martin Kepplinger wrote: > Hi, > > I'm doing a touchscreen xorg input driver. First question: why? :) we generally discourage people from doing that, instead it's better to write a kernel driver and use the existing evdev/libinput drivers. > For testing purposes, I'd like to configure my laptop's touchpad for the > driver to use. It's totally comparable and I've done it for other stuff > for rough testing. I append the evtest output below. Should be fine. > > I'm unsure how to override all other touchpad configs in my system. > > * is it enough to say "MatchIsTouchpad" instead of touchscreen? There's > obviously only one touchpad. Ideally I think I should omit > "MatchIsTouchpad" and say only "Device=/dev/input/event1" or whatever > number it is? Would that be possible? MatchIsTouchpad maps to the udev property ID_INPUT_TOUCHPAD, your homework is to figure out what MatchIsTouchscreen maps to ;) so doing that would be enough, but you could also add a MatchProduct "ETPS/2 Elantech Touchpad" to only match on that touchpad. Don't match on device nodes as they can change during reboots. > * My driver config installs to /usr/local/share/X11/... Will this > *ever* override /usr/share/X11 configs? Even if I call it > "00-mydriver.conf" in /usr/local/ the server is usually configured to look into /usr/share/X11/ and /etc/X11, but not elsewhere. So anything you put in /usr/local is ignored. The start of the xorg.log should list where the server is looking for configs. for local configurations, you're supposed to put them into /etc/ anyway, distribution-provided config snippets go into /usr/local. Cheers, Peter ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Configure touchpad for touchscreen driver
Hi, I'm doing a touchscreen xorg input driver. For testing purposes, I'd like to configure my laptop's touchpad for the driver to use. It's totally comparable and I've done it for other stuff for rough testing. I append the evtest output below. Should be fine. I'm unsure how to override all other touchpad configs in my system. * is it enough to say "MatchIsTouchpad" instead of touchscreen? There's obviously only one touchpad. Ideally I think I should omit "MatchIsTouchpad" and say only "Device=/dev/input/event1" or whatever number it is? Would that be possible? * My driver config installs to /usr/local/share/X11/... Will this *ever* override /usr/share/X11 configs? Even if I call it "00-mydriver.conf" in /usr/local/ thanks martin Input driver version is 1.0.1 Input device ID: bus 0x11 vendor 0x2 product 0xe version 0x0 Input device name: "ETPS/2 Elantech Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event code 335 (BTN_TOOL_QUADTAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 1166 Min0 Max 2772 Resolution 32 Event code 1 (ABS_Y) Value412 Min0 Max 1452 Resolution 32 Event code 24 (ABS_PRESSURE) Value 0 Min0 Max 255 Event code 28 (ABS_TOOL_WIDTH) Value 2 Min0 Max 15 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max4 Event code 48 (ABS_MT_TOUCH_MAJOR) Value 0 Min0 Max 1980 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 2772 Resolution 32 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 1452 Resolution 32 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event code 58 (ABS_MT_PRESSURE) Value 0 Min0 Max 255 Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: libinput and AlpsPS/2 ALPS DualPoint TouchPad
On Sex, 2016-10-28 at 09:48 +1000, Peter Hutterer wrote: > On Thu, Oct 27, 2016 at 05:12:25PM +0100, Sérgio Basto wrote: > > > > Hi, > > After read synaptics will be deprecated, I tried change my touchpad > > to > > libinput but vertical scroll doesn't work [1]. The story of detect > > this ALPS is back from 2009 [2], have we any place more specific to > > track download libinput problems ?. I'm using Fedora 23, xorg-x11- > > drv- > > libinput-0.16.0 and xorg-x11-drv-synaptics-1.8.3. > file a bug against libinput please and assign it to me, we'll take it > from > there. > https://bugs.freedesktop.org/enter_bug.cgi?product=wayland&component= > libinput > > > > > Another question how I disable libinput and enable synaptics, in > > xorg.conf, because I just can have synaptics working when I remove > > libinput package , which for tests is very annoying . > the driver selection is done via xorg.conf.d snippets. what I > recommend for > testing is copy this into /etc/X11/xorg.conf.d/99-force- > synaptics.conf.disabled > > Section "InputClass" > Identifier "Force synaptics" > MatchIsTouchpad "on" > Driver "synaptics" > EndSection > > > then symlink the file > ln /etc/X11/xorg.conf.d/99-force-synaptics.conf.disabled \ > /etc/X11/xorg.conf.d/99-force-synaptics.conf > > every time you want to use synaptics, add the symlink. every time you > want > to use libinput, delete the symlink. That's what I'm doing here and > it works > just fine. > > Cheers, > Peter OK , thanks for the explanation, first I will upgrade my laptop and test with xorg-x11-drv-libinput-0.19.0 . It can take some days until report the bug . Cheers, > > > > > Thanks, > > > > [1] > > https://blog.laimbock.com/2014/11/23/howto-fix-a-too-sensitive-touc > > hpad-on-linux/ > > https://blog.laimbock.com/2014/11/23/howto-fix-a-too-sensitive-touc > > hpad-on-linux/#comment-75509 > > > > [2] > > https://bugzilla.kernel.org/show_bug.cgi?id=14660 > > -- Sérgio M. B. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: libinput and AlpsPS/2 ALPS DualPoint TouchPad
On Thu, Oct 27, 2016 at 05:12:25PM +0100, Sérgio Basto wrote: > Hi, > After read synaptics will be deprecated, I tried change my touchpad to > libinput but vertical scroll doesn't work [1]. The story of detect > this ALPS is back from 2009 [2], have we any place more specific to > track download libinput problems ?. I'm using Fedora 23, xorg-x11-drv- > libinput-0.16.0 and xorg-x11-drv-synaptics-1.8.3. file a bug against libinput please and assign it to me, we'll take it from there. https://bugs.freedesktop.org/enter_bug.cgi?product=wayland&component=libinput > Another question how I disable libinput and enable synaptics, in > xorg.conf, because I just can have synaptics working when I remove > libinput package , which for tests is very annoying . the driver selection is done via xorg.conf.d snippets. what I recommend for testing is copy this into /etc/X11/xorg.conf.d/99-force-synaptics.conf.disabled Section "InputClass" Identifier "Force synaptics" MatchIsTouchpad "on" Driver "synaptics" EndSection then symlink the file ln /etc/X11/xorg.conf.d/99-force-synaptics.conf.disabled \ /etc/X11/xorg.conf.d/99-force-synaptics.conf every time you want to use synaptics, add the symlink. every time you want to use libinput, delete the symlink. That's what I'm doing here and it works just fine. Cheers, Peter > Thanks, > > [1] > https://blog.laimbock.com/2014/11/23/howto-fix-a-too-sensitive-touchpad-on-linux/ > https://blog.laimbock.com/2014/11/23/howto-fix-a-too-sensitive-touchpad-on-linux/#comment-75509 > > [2] > https://bugzilla.kernel.org/show_bug.cgi?id=14660 > > -- > Sérgio M. B. > > > ___ > xorg@lists.x.org: X.Org support > Archives: http://lists.freedesktop.org/archives/xorg > Info: https://lists.x.org/mailman/listinfo/xorg > Your subscription address: %(user_address)s > ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
libinput and AlpsPS/2 ALPS DualPoint TouchPad
Hi, After read synaptics will be deprecated, I tried change my touchpad to libinput but vertical scroll doesn't work [1]. The story of detect this ALPS is back from 2009 [2], have we any place more specific to track download libinput problems ?. I'm using Fedora 23, xorg-x11-drv- libinput-0.16.0 and xorg-x11-drv-synaptics-1.8.3. Another question how I disable libinput and enable synaptics, in xorg.conf, because I just can have synaptics working when I remove libinput package , which for tests is very annoying . Thanks, [1] https://blog.laimbock.com/2014/11/23/howto-fix-a-too-sensitive-touchpad-on-linux/ https://blog.laimbock.com/2014/11/23/howto-fix-a-too-sensitive-touchpad-on-linux/#comment-75509 [2] https://bugzilla.kernel.org/show_bug.cgi?id=14660 -- Sérgio M. B. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Touchpad scrolls to the top of the page upon touching
Hi, just as an update, I've noticed that on this machine I was actually using the synaptics driver. I've switched to libinput now and the issue has disappeared. Ingo On 06/08/2016 10:01 AM, Ingo Bürk wrote: > Hello everybody, > > I use libinput on my T460s and have been experiencing, for a while now, > that when I first start a two-finger scroll on my touchpad after having > done other things, it automatically scrolls all the way to the top. This > is quite annoying and reproducible in different applications. I've ran > evtest and it doesn't seem to be an issue coming from the kernel, so > it's probably a userspace issue. > > Does anybody have the same experience? Does anybody know of an existing > bug report? I haven't been able to find anything. > > > Thanks > > Ingo > > ___ > xorg@lists.x.org: X.Org support > Archives: http://lists.freedesktop.org/archives/xorg > Info: https://lists.x.org/mailman/listinfo/xorg > Your subscription address: %(user_address)s ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Touchpad scrolls to the top of the page upon touching
On Wed, Jun 08, 2016 at 10:01:34AM +0200, Ingo Bürk wrote: is quite annoying and reproducible in different applications. I've ran All gtk3 based? Does it work correctly when activating the window first? https://bugzilla.gnome.org/show_bug.cgi?id=750994 Cheers, Thomas ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Touchpad scrolls to the top of the page upon touching
Hi Thomas, thank you for your reply. Indeed I can't reproduce it, e.g., in my terminal emulator. However, it doesn't sound like the correct bug because the bug report is about a scroll event being ignored. In my case it somehow scrolls all the way to the top. Regards Ingo On 06/08/2016 12:49 PM, Thomas Lübking wrote: > On Wed, Jun 08, 2016 at 10:01:34AM +0200, Ingo Bürk wrote: >> is quite annoying and reproducible in different applications. I've ran > > All gtk3 based? > Does it work correctly when activating the window first? > > https://bugzilla.gnome.org/show_bug.cgi?id=750994 > > Cheers, > Thomas ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Touchpad scrolls to the top of the page upon touching
Hello everybody, I use libinput on my T460s and have been experiencing, for a while now, that when I first start a two-finger scroll on my touchpad after having done other things, it automatically scrolls all the way to the top. This is quite annoying and reproducible in different applications. I've ran evtest and it doesn't seem to be an issue coming from the kernel, so it's probably a userspace issue. Does anybody have the same experience? Does anybody know of an existing bug report? I haven't been able to find anything. Thanks Ingo ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Report a bug touchscreen & having touchpad click disabled
Now posted this in irc ANd now emailing - its a minor problem but its persistant every now and then... so when using the touchscreen there is sometimes a firstclick on the touchpad that will register and then the .conf in /etc/X11/xorg.conf.d/ that disable the click on the touchpad will then work again 10-synaptics.conf : http://sprunge.us/LSSK So the goal is to have the 10-synaptics.conf effective all the time. thanks! Rod ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Touchscreen recognized as touchpad with hid-multitouch driver
On Thu, May 01, 2014 at 11:51:15AM +0200, tomw wrote: > > why are you trying to use the multitouch driver? IIRC it's a touchpad-only > > driver and will treat anything as touchpad. And evdev handles multitouch > > out-of-the-box now anyway. > > Thanks for pointing me at this, I was not fully aware of it. > > However the question still remains why the pointer is still visible. Of > course I could remove it or do the usual tricks like setting it to an > invisible pixel. My understanding however was that the pointer is not > shown if only a touchscreen is detected. > > Perhaps this assumption is wrong or there are some conditions for this I > did not get. that's actually GNOME doing it, it detects the device type and hides the pointer when an event comes from that device. Not sure what other desktop environments do, maybe the same thing? Either way, it's not something that X controls, so if the device is labelled as TOUCHSCREEN that should be enough from our side. Cheers, Peter ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Touchscreen recognized as touchpad with hid-multitouch driver
> why are you trying to use the multitouch driver? IIRC it's a touchpad-only > driver and will treat anything as touchpad. And evdev handles multitouch > out-of-the-box now anyway. Thanks for pointing me at this, I was not fully aware of it. However the question still remains why the pointer is still visible. Of course I could remove it or do the usual tricks like setting it to an invisible pixel. My understanding however was that the pointer is not shown if only a touchscreen is detected. Perhaps this assumption is wrong or there are some conditions for this I did not get. --tomw ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Touchscreen recognized as touchpad with hid-multitiouch driver
On Wed, Apr 30, 2014 at 05:11:39PM +0200, tomw wrote: > Hi, > > I'm currently trying to integrate an ELO optical touchscreen (ET4201L) > on top of just the X server infrastructure. As I was still getting the > mouse pointer which I should not see if the touchscreen is correctly > recognized I was digging a bit deeper to find out why. Basically I ran > into two scenarios - depending whether I'm using either evdev or > multitouch for the device: why are you trying to use the multitouch driver? IIRC it's a touchpad-only driver and will treat anything as touchpad. And evdev handles multitouch out-of-the-box now anyway. Cheers, Peter > > === evdev case === > > /usr/share/X11/xorg.conf.d/10-evdev.conf > > Section "InputClass" > Identifier "evdev keyboard catchall" > MatchIsKeyboard "on" > MatchDevicePath "/dev/input/event*" > Driver "evdev" > EndSection > > Section "InputClass" > Identifier "Touchscreen" > MatchProduct "Elo TouchSystems" > MatchIsTouchscreen "on" > MatchDevicePath "/dev/input/event*" > Driver "evdev" > EndSection > > > > which makes the screen recognized as TOUCHSCREEN with device id 10: > > [23.446] (II) Using input driver 'evdev' for 'Elo TouchSystems > Optical Touchscreen 02.04.22.02.' > [23.446] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: > always reports core events > [23.446] (**) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: Device: "/dev/input/event3" > [23.446] (II) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: Using mtdev for this device > [23.446] (--) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: Vendor 0x4e7 Product 0x80 > [23.446] (--) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: Found absolute axes > [23.446] (--) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: Found absolute multitouch axes > [23.446] (II) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: No buttons found, faking one. > [23.446] (--) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: Found x and y absolute axes > [23.446] (--) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: Found absolute touchscreen > [23.446] (**) Option "SwapAxes" "0" > [23.446] (II) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: Configuring as touchscreen > [23.446] (**) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: YAxisMapping: buttons 4 and 5 > [23.447] (**) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: EmulateWheelButton: 4, EmulateWheelInertia: 10, > EmulateWheelTimeout: 200 > [23.447] (**) Option "config_info" > "udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.2/2-1.1.2:1.3/input/input4/event3" > [23.447] (II) XINPUT: Adding extended input device "Elo TouchSystems > Optical Touchscreen 02.04.22.02." (type: TOUCHSCREEN, id 10) > [23.447] (II) evdev: Elo TouchSystems Optical Touchscreen > 02.04.22.02.: initialized for absolute axes. > [23.447] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: > (accel) keeping acceleration scheme 1 > [23.447] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: > (accel) acceleration profile 0 > [23.447] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: > (accel) acceleration factor: 2.000 > [23.447] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: > (accel) acceleration threshold: 4 > > === multitouch case, jsut changing the driver to multitouch === > > Section "InputClass" > Identifier "evdev keyboard catchall" > MatchIsKeyboard "on" > MatchDevicePath "/dev/input/event*" > Driver "evdev" > EndSection > > Section "InputClass" > Identifier "Touchscreen" > MatchProduct "Elo TouchSystems" > MatchIsTouchscreen "on" > MatchDevicePath "/dev/input/event*" > Driver "multitouch" > EndSection > > > which makes the screen recognized as TOUCHPAD with device id 10: > > [22.925] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: > Applying InputClass "Touchscreen" > [22.925] (II) LoadModule: "multitouch" > [22.925] (II) Loading /usr/lib/xorg/modules/input/multitouch_drv.so > [22.946] (II) Module multitouch: vendor="X.Org Foundation&
Touchscreen recognized as touchpad with hid-multitiouch driver
Hi, I'm currently trying to integrate an ELO optical touchscreen (ET4201L) on top of just the X server infrastructure. As I was still getting the mouse pointer which I should not see if the touchscreen is correctly recognized I was digging a bit deeper to find out why. Basically I ran into two scenarios - depending whether I'm using either evdev or multitouch for the device: === evdev case === /usr/share/X11/xorg.conf.d/10-evdev.conf Section "InputClass" Identifier "evdev keyboard catchall" MatchIsKeyboard "on" MatchDevicePath "/dev/input/event*" Driver "evdev" EndSection Section "InputClass" Identifier "Touchscreen" MatchProduct "Elo TouchSystems" MatchIsTouchscreen "on" MatchDevicePath "/dev/input/event*" Driver "evdev" EndSection which makes the screen recognized as TOUCHSCREEN with device id 10: [23.446] (II) Using input driver 'evdev' for 'Elo TouchSystems Optical Touchscreen 02.04.22.02.' [23.446] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: always reports core events [23.446] (**) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: Device: "/dev/input/event3" [23.446] (II) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: Using mtdev for this device [23.446] (--) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: Vendor 0x4e7 Product 0x80 [23.446] (--) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: Found absolute axes [23.446] (--) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: Found absolute multitouch axes [23.446] (II) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: No buttons found, faking one. [23.446] (--) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: Found x and y absolute axes [23.446] (--) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: Found absolute touchscreen [23.446] (**) Option "SwapAxes" "0" [23.446] (II) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: Configuring as touchscreen [23.446] (**) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: YAxisMapping: buttons 4 and 5 [23.447] (**) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [23.447] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.2/2-1.1.2:1.3/input/input4/event3" [23.447] (II) XINPUT: Adding extended input device "Elo TouchSystems Optical Touchscreen 02.04.22.02." (type: TOUCHSCREEN, id 10) [23.447] (II) evdev: Elo TouchSystems Optical Touchscreen 02.04.22.02.: initialized for absolute axes. [23.447] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: (accel) keeping acceleration scheme 1 [23.447] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: (accel) acceleration profile 0 [23.447] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: (accel) acceleration factor: 2.000 [23.447] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: (accel) acceleration threshold: 4 === multitouch case, jsut changing the driver to multitouch === Section "InputClass" Identifier "evdev keyboard catchall" MatchIsKeyboard "on" MatchDevicePath "/dev/input/event*" Driver "evdev" EndSection Section "InputClass" Identifier "Touchscreen" MatchProduct "Elo TouchSystems" MatchIsTouchscreen "on" MatchDevicePath "/dev/input/event*" Driver "multitouch" EndSection which makes the screen recognized as TOUCHPAD with device id 10: [22.925] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: Applying InputClass "Touchscreen" [22.925] (II) LoadModule: "multitouch" [22.925] (II) Loading /usr/lib/xorg/modules/input/multitouch_drv.so [22.946] (II) Module multitouch: vendor="X.Org Foundation" [22.946]compiled for 1.15.0, module version = 0.1.0 [22.946]Module class: X.Org XInput Driver [22.946]ABI class: X.Org XInput driver, version 20.0 [22.946] (II) Using input driver 'multitouch' for 'Elo TouchSystems Optical Touchscreen 02.04.22.02.' [22.946] (**) Elo TouchSystems Optical Touchscreen 02.04.22.02.: always reports core events [22.946] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.2/2-1.1.2:1.3/input/input16/event11" [22.946] (II) XINPUT: Adding extended input device "Elo TouchSystems Optical Touchscreen 02.04.22.02." (type: TOUCHPAD, id 10) [22.946] (II) device control: init [22.946] (
Set touchpad to only scroll
Hi, I have a thinkpad x230 and use the touchpoint to move the cursor. I normally disable the the touchpad completely using "synclient TouchPadOff=1", but I would quite like to be able to still use the touchpad for scrolling. However if I try synclient TouchPadOff=1 synclient HorizTwoFingerScroll=1 synclient VertTwoFingerScroll=1 I do not get scrolling. I can't see any option to just disable cursor movement. If I set the MinSpeed and MaxSpeed to zero the cursor still moves. Is there anything else I can try? Sam ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: synaptics and ALPS DualPoint TouchPad
On Dom, 2013-09-08 at 18:27 +, Jethro Tull wrote: > The ALPS DualPoint TouchPad synaptics in linux is way too sensitive. > To check it one only needs to put on finger on it and near another > one, he'll notice that even ~1 cm far the second finger will make the > pointer on the screen vibrating. It seems to be really an issue with > the driver rather than settings. Hi, you seems that already set yours touchpad using synclient, if is an driver problem, you should look and report on bugzilla.kernel.org Product: Drivers Component: Input Devices should be something like https://bugzilla.kernel.org/show_bug.cgi?id=14660 the story to have drive for my ALPS. My ALPS is not two finger capable... > If a high value is given to FingerHigh parameter it will make the > activation of the pointer harder for the finger but as soon as the > pointer is under finger control, the second finger proximity influence > is exactly the same. Another annoying effect of this too high > sensitivity is that when scrolling with two fingers, the fingers need > to to be separated with nearly 7 mm minimum, otherwise it seems to see > only one finger. > > Though ALPS touchpad seems not well designed, this issue comes from > the linux synaptics driver since this touchpad works much better in > windows. In windows, even when the two finger are tightly in contact > scrolling works. -- Sérgio M. B. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
synaptics and ALPS DualPoint TouchPad
The ALPS DualPoint TouchPad synaptics in linux is way too sensitive. To check it one only needs to put on finger on it and near another one, he'll notice that even ~1 cm far the second finger will make the pointer on the screen vibrating. It seems to be really an issue with the driver rather than settings. If a high value is given to FingerHigh parameter it will make the activation of the pointer harder for the finger but as soon as the pointer is under finger control, the second finger proximity influence is exactly the same. Another annoying effect of this too high sensitivity is that when scrolling with two fingers, the fingers need to to be separated with nearly 7 mm minimum, otherwise it seems to see only one finger. Though ALPS touchpad seems not well designed, this issue comes from the linux synaptics driver since this touchpad works much better in windows. In windows, even when the two finger are tightly in contact scrolling works. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: cirque smartcat touchpad
On Fri, Dec 28, 2012 at 01:22:44AM -0800, Sebastian Glita wrote: > > Hi, > > The Smart Cat device is recognized with the evdev driver correctly, but it > does not respond, although it is enabled. it's not quite detected correctly, looking at the axis labels this device looks like a standard USB mouse (two relative axes, one wheel, three buttons). for evdev/synaptics to treat this properly, the device needs ABS_X/Y and BTN_TOOL_FINGER. so really, you need to add support for this device to the kernel drivers. Cheers, Peter > > >> Is it recognized with the latest sources from cgit.freedesktop.org > >> (mouse, > > evdev, synaptics)? > > > > the main question is whether it is supported by the kernel. X hardly deals > > with touchpads directly these days, it's handled by the (linux) kernel and > > we see the evdev interface. So you need to first check if the kernel > > supports it. > > > >> Do the 4-buttons work? The scroll? > > > > yes, likely, if the kernel supports the touchpad. > > You're right. > > > > >> Do the "advanced gestures" work? > > > > no, only scrolling. gestures are implemented on the client-side, so these > > must be implemented by your client-stack (which may already do so, e.g. > > newer GTK and Unity) > > You are here right too: with the `synaptics-test' program, there are 3 > buttons, but total of seven combined, motion and only vertical scrolling > works. > > It seems the touchpad is quite simple. > > Smart Cat stream is very direct (thanks Jan for synaptics-test): > byte 0: 0x01-left, 0x02-right|toprightcorner, 0x04-side, > 0x03-left+right|toprightcorner, 0x05-left+side, > 0x06-side+right|toprightcorner, > 0x07-left+side+right|toprightcorner, > byte 1: relative signed horizontal motion, > byte 2: relative signed vertical motion, > byte 3: relative signed vertical scroll, > byte 4 ... 12: 0x00. > > The driver that binds it is usbhid. But how do I make it active? > Thanks, > Sebastian > > user@localhost ~ $ xinput list-props 10 > > Device 'Cirque Corporation 9925 AG Touchpad': > Device Enabled (132): 1 > Coordinate Transformation Matrix (134): 1.00, 0.00, 0.00, > 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 > Device Accel Profile (265): 0 > Device Accel Constant Deceleration (266): 1.00 > Device Accel Adaptive Deceleration (267): 1.00 > Device Accel Velocity Scaling (268): 10.00 > Device Product ID (250): 1160, 641 > Device Node (251): "/dev/input/event19" > Evdev Axis Inversion (269): 0, 0 > Evdev Axes Swap (271): 0 > Axis Labels (272): "Rel X" (142), "Rel Y" (143), "Rel Vert Wheel" (264) > Button Labels (273): "Button Left" (135), "Button Middle" (136), > "Button Right" (137), "Button Wheel Up" (138), "Button Wheel Down" (139), > "Button Horiz Wheel Left" (140), "Button Horiz Wheel Right" (141) > Evdev Middle Button Emulation (274): 0 > Evdev Middle Button Timeout (275): 50 > Evdev Third Button Emulation (276): 0 > Evdev Third Button Emulation Timeout (277): 1000 > Evdev Third Button Emulation Button (278): 3 > Evdev Third Button Emulation Threshold (279): 20 > Evdev Wheel Emulation (280): 0 > Evdev Wheel Emulation Axes (281): 0, 0, 4, 5 > Evdev Wheel Emulation Inertia (282): 10 > Evdev Wheel Emulation Timeout (283): 200 > Evdev Wheel Emulation Button (284): 4 > Evdev Drag Lock Buttons (285): 0 > > > > > Cheers, > > Peter > > > > ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: cirque smartcat touchpad
Hi, The Smart Cat device is recognized with the evdev driver correctly, but it does not respond, although it is enabled. >> Is it recognized with the latest sources from cgit.freedesktop.org (mouse, > evdev, synaptics)? > > the main question is whether it is supported by the kernel. X hardly deals > with touchpads directly these days, it's handled by the (linux) kernel and > we see the evdev interface. So you need to first check if the kernel > supports it. > >> Do the 4-buttons work? The scroll? > > yes, likely, if the kernel supports the touchpad. You're right. > >> Do the "advanced gestures" work? > > no, only scrolling. gestures are implemented on the client-side, so these > must be implemented by your client-stack (which may already do so, e.g. > newer GTK and Unity) You are here right too: with the `synaptics-test' program, there are 3 buttons, but total of seven combined, motion and only vertical scrolling works. It seems the touchpad is quite simple. Smart Cat stream is very direct (thanks Jan for synaptics-test): byte 0: 0x01-left, 0x02-right|toprightcorner, 0x04-side, 0x03-left+right|toprightcorner, 0x05-left+side, 0x06-side+right|toprightcorner, 0x07-left+side+right|toprightcorner, byte 1: relative signed horizontal motion, byte 2: relative signed vertical motion, byte 3: relative signed vertical scroll, byte 4 ... 12: 0x00. The driver that binds it is usbhid. But how do I make it active? Thanks, Sebastian user@localhost ~ $ xinput list-props 10 Device 'Cirque Corporation 9925 AG Touchpad': Device Enabled (132): 1 Coordinate Transformation Matrix (134): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (265): 0 Device Accel Constant Deceleration (266): 1.00 Device Accel Adaptive Deceleration (267): 1.00 Device Accel Velocity Scaling (268): 10.00 Device Product ID (250): 1160, 641 Device Node (251): "/dev/input/event19" Evdev Axis Inversion (269): 0, 0 Evdev Axes Swap (271): 0 Axis Labels (272): "Rel X" (142), "Rel Y" (143), "Rel Vert Wheel" (264) Button Labels (273): "Button Left" (135), "Button Middle" (136), "Button Right" (137), "Button Wheel Up" (138), "Button Wheel Down" (139), "Button Horiz Wheel Left" (140), "Button Horiz Wheel Right" (141) Evdev Middle Button Emulation (274): 0 Evdev Middle Button Timeout (275): 50 Evdev Third Button Emulation (276): 0 Evdev Third Button Emulation Timeout (277): 1000 Evdev Third Button Emulation Button (278): 3 Evdev Third Button Emulation Threshold (279): 20 Evdev Wheel Emulation (280): 0 Evdev Wheel Emulation Axes (281): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (282): 10 Evdev Wheel Emulation Timeout (283): 200 Evdev Wheel Emulation Button (284): 4 Evdev Drag Lock Buttons (285): 0 > > Cheers, > Peter > ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: cirque smartcat touchpad
On Thu, Nov 22, 2012 at 08:50:35AM -0800, Sebastian Glita wrote: > > the main question is whether it is supported by the kernel. X hardly deals > > with touchpads directly these days, it's handled by the (linux) kernel and > > > we see the evdev interface. So you need to first check if the kernel > > supports it. > > Hmm... There seems to be no indication in synaptics USB kernel driver about > "easycat/smartcat" (drivers/input/mouse). > > Next "roundabout" question would be, given the FAQ page says an "alike" OS > works: > > "... and the USB Cirque Smart Cat® (GP410U-) ... are recommended Cirque > trackpad for > the Macintosh OS. > * Mac OS 8.5 or later is required for both of these trackpads. > * Mac OS X or later is required for the vertical scrolling feature." > > how far can I assume linux kernel would recognize it too? I know that whereas > usually linux isn't specified, but mac is, there is a good chance a device > would work with both mac and linux... the two are unrelated. it may work, it may not, sorry. Generally the older a device, the higher the chance of it working but I really don't know in this case. Cheers, Peter > >> Do the 4-buttons work? The scroll? > > > > yes, likely, if the kernel supports the touchpad. > > > Actually, clicking, tapping and scrolling are enough for me. > > Thank s. > > > > >> Do the "advanced gestures" work? > > > > no, only scrolling. gestures are implemented on the client-side, so these > > must be implemented by your client-stack (which may already do so, e.g. > > newer GTK and Unity) > > > > Cheers, > > Peter > > > > ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: cirque smartcat touchpad
> the main question is whether it is supported by the kernel. X hardly deals > with touchpads directly these days, it's handled by the (linux) kernel and > we see the evdev interface. So you need to first check if the kernel > supports it. Hmm... There seems to be no indication in synaptics USB kernel driver about "easycat/smartcat" (drivers/input/mouse). Next "roundabout" question would be, given the FAQ page says an "alike" OS works: "... and the USB Cirque Smart Cat® (GP410U-) ... are recommended Cirque trackpad for the Macintosh OS. * Mac OS 8.5 or later is required for both of these trackpads. * Mac OS X or later is required for the vertical scrolling feature." how far can I assume linux kernel would recognize it too? I know that whereas usually linux isn't specified, but mac is, there is a good chance a device would work with both mac and linux... > >> Do the 4-buttons work? The scroll? > > yes, likely, if the kernel supports the touchpad. Actually, clicking, tapping and scrolling are enough for me. Thank s. > >> Do the "advanced gestures" work? > > no, only scrolling. gestures are implemented on the client-side, so these > must be implemented by your client-stack (which may already do so, e.g. > newer GTK and Unity) > > Cheers, > Peter > ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: cirque smartcat touchpad
On Sat, Nov 17, 2012 at 04:37:49AM -0800, Sebastian Glita wrote: > While trying a simple search whether Xorg supports this device: > > > http://www.cirque.com/desktoptouchpad/productsandorders/smartcat.aspx > > the 4-button USB touchpad, probably with "synaptics" driver, I couldn't find > any RECENT (2011-2012) discussion. > > > Is it recognized with the latest sources from cgit.freedesktop.org (mouse, > evdev, synaptics)? the main question is whether it is supported by the kernel. X hardly deals with touchpads directly these days, it's handled by the (linux) kernel and we see the evdev interface. So you need to first check if the kernel supports it. > Do the 4-buttons work? The scroll? yes, likely, if the kernel supports the touchpad. > Do the "advanced gestures" work? no, only scrolling. gestures are implemented on the client-side, so these must be implemented by your client-stack (which may already do so, e.g. newer GTK and Unity) Cheers, Peter > Thank s. > > > P.S.: The description from manufacturer: > > Functionality > * Multi-finger Advanced Gestures available: scroll, zoom, rotate and more > * Execute, browse at the touch of a finger > * Zoom reduces or enlarges Office documents > * Scroll moves horizontally & vertically > * Right tap mimics a mouse right-click > * GlideExtend® virtually eliminates the edge of the pad when dragging > * Adjustable sounds, speed, sensitivity and orientation > Product Highlights > * Extra-large touch surface > * Easy-to-find textured "right" click area > * One-touch scroll, zoom and surf > * Three (3) mechanical buttons supported > * Withstands spills and abuse > * Easy PS/2 or USB connectivity > > P.S.: A description from a seller website: > > Product Features > > * Intuitive design, simply glide finger on surface. > * One-Touch Scroll and Zoom > * Ability to go from fast screen movement to pixelpoint control > * Activate vertical / horizontal scrolling at a touch of a finger > > > Technical Details > USB Keyboard > ___ > xorg@lists.x.org: X.Org support > Archives: http://lists.freedesktop.org/archives/xorg > Info: http://lists.x.org/mailman/listinfo/xorg > Your subscription address: peter.hutte...@who-t.net > ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
cirque smartcat touchpad
Hi, While trying a simple search whether Xorg supports this device: http://www.cirque.com/desktoptouchpad/productsandorders/smartcat.aspx the 4-button USB touchpad, probably with "synaptics" driver, I couldn't find any RECENT (2011-2012) discussion. Is it recognized with the latest sources from cgit.freedesktop.org (mouse, evdev, synaptics)? Do the 4-buttons work? The scroll? Do the "advanced gestures" work? Thank s. P.S.: The description from manufacturer: Functionality * Multi-finger Advanced Gestures available: scroll, zoom, rotate and more * Execute, browse at the touch of a finger * Zoom reduces or enlarges Office documents * Scroll moves horizontally & vertically * Right tap mimics a mouse right-click * GlideExtend® virtually eliminates the edge of the pad when dragging * Adjustable sounds, speed, sensitivity and orientation Product Highlights * Extra-large touch surface * Easy-to-find textured "right" click area * One-touch scroll, zoom and surf * Three (3) mechanical buttons supported * Withstands spills and abuse * Easy PS/2 or USB connectivity P.S.: A description from a seller website: Product Features * Intuitive design, simply glide finger on surface. * One-Touch Scroll and Zoom * Ability to go from fast screen movement to pixelpoint control * Activate vertical / horizontal scrolling at a touch of a finger Technical Details USB Keyboard ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Elantech touchpad issue
Hello. I have a notebook, Samsung RC530, with Elantech touchpad: [18392.637632] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x450f00) [18392.672694] psmouse serio1: elantech: Synaptics capabilities query result 0x08, 0x15, 0x0c. The touchpad is identified correctly by the kernel, sends the correct finger touch events (verified by a printk probe) and is correctly bound to synaptics driver within xorg (Xorg.log: http://pastie.org/3481273). There is one "minor" issue, however: the driver thinks that 3-finger touch is 1-finger touch, and disregards 1-finger touches whatsoever. That is, I can move cursor with 3 fingers, but not 1. I can still scroll with 2 fingers. I use Debian wheezy. Ideas? Fixes? Thanks for your time. -- WBR, Peter Zotov. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: turn off touchpad scrolling?
> But still sometimes my xterm content will scroll still when I bump or > drag hand on the pad. I can't reproduce it. Sometimes content gets > pasted in. Can anyone share some hints on some other things to look at? I think I figured out the last scrolling problem: synclient VertEdgeScroll=0 (Maybe I already fixed the pasting problem with other settings.) ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
turn off touchpad scrolling?
I moved to a new laptop with different Xorg and xterm install. (My window manager stayed the same.) Periodically my xterms would start (I thought) randomly scrolling or -- even worse -- pasting from my buffer. I didn't see anything in xterm manual about this. After a day of use, I noticed that two fingers on the track pad caused the scrolling. (As you can see, I have no experience with this multitouch.) I turned it off with: synclient VertTwoFingerScroll=0 But then later noticed pasting was still happening. I could reproduce finally by tapping with two fingers. So I turned it off: synclient TapButton2=0 And sometimes my mouse will jump across the screen and then focus a new window. I don't like focus follows mouse, so I will turn off the accidental tap that brought focus: synclient TapButton1=0 I also did: synclient TapButton3=0 But still sometimes my xterm content will scroll still when I bump or drag hand on the pad. I can't reproduce it. Sometimes content gets pasted in. Can anyone share some hints on some other things to look at? I did read some through the synaptics(4) manual. This lubuntu system has X.Org X Server 1.10.4 Release Date: 2011-08-19. xserver-xorg-input-synaptics 1.4.1-1ubuntu2 xserver-xorg 1:7.6+7ubuntu7.1 xserver-xorg-core 2:1.10.4-1ubuntu4.2 xserver-xorg-input-all1:7.6+7ubuntu7.1 xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 xserver-xorg-input-mouse 1:1.7.1-1 xterm 271-1ubuntu2 (and a lot more) I first thought this was a xterm feature so I tried to change some scrolling settings, but then saw it was in firefox too. (Over time, I may learn to accept and enjoy these new features, but until then I'd like to understand what causes them.) Thanks! ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
