dell latitude e6510 touchpad driver windows 10

The trackpad is mis-detected and treated as 'ImPS/2 Generic Wheel Mouse' according to /proc/bus/input/devices. I have a similar and possibly related problem with my HP 311c (model 311c-1101SA). From what I gathered, it also applied a different driver to the trackpad. Related, Ubuntu applied an entry for '0x73, 0x02, 0圆4' with different masks and flags, but had to revert. I see no difference in how the trackpad actually works. Likewise synclient -m 100 will show a single line of all zeros, but does not show action. If I 'cat /dev/input/mouse1' it shows all events but nothing for mouse2. The former is mouse1 and the latter is mouse2. The trackpad and trackstick is handled by 'DualPoint Stick' and not 'AlpsPS/2 ALPS DualPoint TouchPad'. Synclient -l now sees the trackpad and I can set options. I've included a patch for alps.c with this change. I know it needs ALPS_PASS and ALPS_DUALPOINT, don't know about the last (nor how to test it). I'm guessing regarding the masks and flags. I turned on debug in alps.c and it spit out the following:Īdding an entry for this (using the same flags as for the E6400) it gave the following status: The track pad should allow setting of functionality via synclient. The trackpad and track stick have basic mouse functionalities and are not visible via synclient. Examine /var/log/Xorg.0.log for mention of the ALPS trackpad.

I tried it in Fedora 12 and in Ubuntu, too.Ģ. This is a kernel problem in drivers/input/mouse/alps.c and is applicable to this and other distributions. Version-Release number of selected component (if applicable): It is an alps trackpad with stick.įrom what I can gather the E6510 also uses the same trackpad.

The trackpad on the Dell E6410 is not recognized.

Dell latitude e6510 touchpad driver windows 10