Control: affects -1 gpm On Sat, 2014-08-23 at 01:27 +0300, أحمد المحمودي wrote: > Package: src:linux > Version: 3.14.15-2 > Severity: normal > > Dear Maintainer, > > I am using a Dell Latitude E5540 laptop, the touchpad is working fine > on X. Yet on the console UI, I wasn't able to use gpm with the mouse, > after some searching I found a bug on Launchpad [1] that suggested setting > the 'proto' option for psmouse module [2].
This parameter sets the protocol that psmouse expects as input from the
hardware.
> So when I set proto=exps, I was able to use the touchpad with gpm. The
> gpm command line was:
>
> gpm -m /dev/input/mice -t exps2
The protocol of /dev/input/mice is *always* PS/2 with Intellimouse
Explorer extensions (what gpm calls 'exps2') The 'mousedev' driver
translates input from any mouse-like input device into this protocol.
So the options you've given gpm here are a good default, and indeed they
*are* the default configuration in Debian.
> I think that what I've done is a workaround rather than a
> configuration, especially that according to 'modinfo psmouse', this
> option is useful for KVM switches (which is not my case here)
[...]
It's possible that the mousedev driver does not recognise your touchpad
as sufficiently similar to a mouse, if psmouse detects its full
capabilities. If you tell the psmouse to use a specific protocol,
perhaps it looks more like a mouse.
Please can you send the output of this command, firstly when psmouse is
loaded with the 'proto=exps' parameter, and secondly when it is loaded
without the parameter:
cat /sys/class/input/mouse?/device/uevent
Ben.
--
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
- Albert Einstein
signature.asc
Description: This is a digitally signed message part
