I can also confirm this bug on the Samsung RF710, which is one of the same new range as the RF510 and so probably has the same Elantech touchpad. I'm running Ubuntu 10.10, with the current kernel "2.6.35-22-generic #35-Ubuntu SMP". The touchpad is detected as "PS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input7" (from dmesg).
modinfo gives me this:
$ modinfo psmouse
filename: /lib/modules/2.6.35-22-generic/kernel/drivers/input/mouse/psmouse.ko
license: GPL
description: PS/2 mouse driver
author: Vojtech Pavlik <vojtech@r suse.cz>
srcversion: 5480D3D50AA2ED3ED4DBC60
alias: serio:ty05pr*id*ex*
alias: serio:ty01pr*id*ex*
depends:
vermagic: 2.6.35-22-generic SMP mod_unload modversions
parm: force_elantech:Force the Elantech PS/2 protocol extension to be used, 1 = enabled, 0 = disabled (default). (bool)
parm: proto:Highest protocol extension to probe (bare, imps, exps, any). Useful for KVM switches. (proto_abbrev)
parm: resolution:Resolution, in dpi. (uint)
parm: rate:Report rate, in reports per second. (uint)
parm: smartscroll:Logitech Smartscroll autorepeat, 1 = enabled (default), 0 = disabled. (bool)
parm: resetafter:Reset device after so many bad packets (0 = never). (uint)
parm: resync_time:How long can mouse stay idle before forcing resync (in seconds, 0 = never). (uint)
So it would seem that the "force_elantech" option is supported. However adding "options psmouse force_elantech=1" to /etc/modprobe.d/psmouse.conf seems to have no effect.After a reboot, "dmesg | grep elantech" matches nothing.
Is there another way to find out the firmware version, or any other information that may help to nail this one? I'm happy to offer whatever limited help I can!
I can also confirm this bug on the Samsung RF710, which is one of the same new range as the RF510 and so probably has the same Elantech touchpad. I'm running Ubuntu 10.10, with the current kernel "2.6.35-22-generic #35-Ubuntu SMP". The touchpad is detected as "PS/2 Logitech Wheel Mouse as /devices/ platform/ i8042/serio1/ input/input7" (from dmesg).
modinfo gives me this:
$ modinfo psmouse 2.6.35- 22-generic/ kernel/ drivers/ input/mouse/ psmouse. ko ED4DBC60 Force the Elantech PS/2 protocol extension to be used, 1 = enabled, 0 = disabled (default). (bool) Resolution, in dpi. (uint) Logitech Smartscroll autorepeat, 1 = enabled (default), 0 = disabled. (bool)
filename: /lib/modules/
license: GPL
description: PS/2 mouse driver
author: Vojtech Pavlik <vojtech@r suse.cz>
srcversion: 5480D3D50AA2ED3
alias: serio:ty05pr*id*ex*
alias: serio:ty01pr*id*ex*
depends:
vermagic: 2.6.35-22-generic SMP mod_unload modversions
parm: force_elantech:
parm: proto:Highest protocol extension to probe (bare, imps, exps, any). Useful for KVM switches. (proto_abbrev)
parm: resolution:
parm: rate:Report rate, in reports per second. (uint)
parm: smartscroll:
parm: resetafter:Reset device after so many bad packets (0 = never). (uint)
parm: resync_time:How long can mouse stay idle before forcing resync (in seconds, 0 = never). (uint)
So it would seem that the "force_elantech" option is supported. However adding "options psmouse force_elantech=1" to /etc/modprobe. d/psmouse. conf seems to have no effect.After a reboot, "dmesg | grep elantech" matches nothing.
Is there another way to find out the firmware version, or any other information that may help to nail this one? I'm happy to offer whatever limited help I can!