I'm positive that my touchpad is elantech. I never said that my solution was a permanent one but it works. Either way, I don't really care because my touchpad works fine. I can scroll up and down, double click with the touchpad, and everything. It works the way a touchpad should. Why not test it? What's the worse that could happen from loading and unloading a module with different arguments?
Edit:
Code:root@satori:/etc/modprobe.d# grep -i elantech /var/log/messages Sep 12 06:45:26 satori kernel: [ 7.065055] elantech.c: assuming hardware version 1, firmware version 20.0 Sep 12 06:45:26 satori kernel: [ 7.144405] elantech.c: Synaptics capabilities query result 0x68, 0x18, 0x0c. Sep 12 06:45:26 satori kernel: [ 7.610458] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input8 Sep 12 08:01:10 satori kernel: [ 9.420876] elantech.c: assuming hardware version 1, firmware version 20.0 Sep 12 08:01:10 satori kernel: [ 9.480618] elantech.c: Synaptics capabilities query result 0x68, 0x18, 0x0c. Sep 12 08:01:10 satori kernel: [ 9.926175] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input8
Last edited by absolutezero1287; September 14th, 2010 at 09:00 PM. Reason: I hope this proves that I know what I'm doing!
LOL I didn't mean to get you all flustered, I see you have an elantech touchpad, I didn't know lenovo was using them. Anyway, there are patches for this, so the issue has been resolved for some time, the thread really should be [SOLVED].
I'll post the link again, since it tends to get lost in all these replies: http://ubuntuforums.org/showpost.php...1&postcount=44
Hm, try tailing messages when you insmod.. in one window:
In another, cd to your linux source directory and:Code:tail -f /var/log/messages
If it gives an error, you'll have a clue, or if it says ImPS/2 there's a problem somewhere, double check your patched file (or start from scratch).Code:sudo modprobe -r psmouse sudo insmod drivers/input/mouse/psmouse.ko
Bender2k14 posted a patch here that you could use after the other patches. But it's the same thing as editing it manually.
If your mouse stops working:
Code:sudo modprobe -r psmouse;sudo modprobe psmouse
Did this:
sudo modprobe -r psmouse
sudo insmod drivers/input/mouse/psmouse.ko
and the only output in 'messages' is as follows:
I'll try the whole thing again.[36014.316381] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input10
Redone, yet the result is as described earlier.
Ah, patchwork.kernel.org is down. That's probably why -- your patch files are probably empty, yeah?
I uploaded a copy of the patched file, from your kernel source directory:
This replaces step 5. You'll still need to edit it to force version 2 as in step 5.5.Code:wget -O drivers/input/mouse/elantech.c http://pastebin.com/download.php?i=i6uPx1vb
To be absolutely sure that step 6 works, you should first delete the old object files from the previous build:
Code:rm drivers/input/mouse/*.o
Hm..., no, the patch files are not empty. All four have stuff in them.
Thanks so much! Worked great on my dell mini 10. Much appreciated.
Bookmarks