If you load psmouse with proto=imps (which is the default on Slackware for example) the synaptics touchpad is not recognized by xf86-input-synaptics and the standard mouse driver is used instead. If psmouse is loaded with proto=imps the synaptics touchpad is identified as PS/2 Synaptics TouchPad instead of SynPS/2 Synaptics TouchPad when loaded with standard settings Xorg.0.log shows the following error messages: (II) Synaptics touchpad driver version 0.15.0 Mouse0 no synaptics event device found (checked 17 nodes) [...] (EE) Mouse0 no synaptics touchpad detected and no repeater device (EE) Mouse0 Unable to query/initialize Synaptics hardware. I've used xf86-input-synaptics when looking for the errors, but the problem is still there with 0.15.2. (System is Slackware-12.1, gcc-4.2.3, glibc-2.7, kernel-2.6.26.2)
On Wed, Sep 17, 2008 at 03:44:59AM -0700, bugzilla-daemon@freedesktop.org wrote: > If you load psmouse with proto=imps (which is the default on Slackware for > example) the synaptics touchpad is not recognized by xf86-input-synaptics and > the standard mouse driver is used instead. Erm, so don't do that. Slackware should leave the kernel default as-is.
> Erm, so don't do that. Slackware should leave the kernel default as-is. Avoiding the bug does not solve it. According to various resources on the web proto=imps should restore kernel-2.4 behaviour. If I remember correctly synaptics did work with kernel-2.4.x too. Second thing, If the driver reports it as "Synaptics TouchPad" I would feel the synaptics touchpad driver responsible for it. I'll leave this closed after someone has been able to give me a valid reason, why this should in no way be handled by synaptics. Telling me to just not use it that way does not fit in that category.
On Sat, Oct 04, 2008 at 07:24:00AM -0700, bugzilla-daemon@freedesktop.org wrote: > --- Comment #2 from Heinz Wiesinger <HMWiesinger@gmx.at> 2008-10-04 07:23:58 PST --- > > Erm, so don't do that. Slackware should leave the kernel default as-is. > > Avoiding the bug does not solve it. No, it doesn't. proto=imps avoids the bug, at the cost of other functionality. > According to various resources on the web proto=imps should restore kernel-2.4 > behaviour. If I remember correctly synaptics did work with kernel-2.4.x too. > Second thing, If the driver reports it as "Synaptics TouchPad" I would feel the > synaptics touchpad driver responsible for it. You're mixing up the kernel and userspace. xf86-input-synaptics (which lives in userspace) relies on psmouse (which lives in the kernel) doing its job correctly. proto=imps means that xf86-input-synaptics cannot work properly, by limiting PS/2 support to the IntelliMouse subset of the 'protocol'. If you want full Synaptics support, do not pass proto=imps. If there's some kernel bug which apparently compels you to pass proto=imps, fix it. > I'll leave this closed after someone has been able to give me a valid reason, > why this should in no way be handled by synaptics. Telling me to just not use > it that way does not fit in that category. -> INVALID, xf86-input-synaptics doesn't work with proto=imps, so either stop using proto=imps, or get the kernel fixed
Now it's alright :) Thanks for the explanation.
Daniel, I sent an email to you about this (CC'd Volkerding), which he also later replied (and CC'd you). Did you get those? We never got a response from you, but you might be filtering that account so that only bugzilla mail reaches you... To make a long story short, we got lots of bug reports that the kernel's default psmouse options breaks KVM switches - after switching consoles, the mouse goes crazy. Basically, we were faced with a situation where either solution had bad effects, and since we didn't at that time ship the synaptics driver, the choice was relatively easy. I'll see about testing that with later kernels to see if the mouse still goes crazy, and if so, we'll looking into a bug against the kernel. Thanks! :-)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.