From: Tom Aspenwall <tom@linuxtom.com>
To: linux-input@vger.kernel.org
Subject: Issue with psmouse Kernel Module and Trackpoint Drift Correction
Date: Wed, 24 Apr 2024 14:50:30 -0600 [thread overview]
Message-ID: <84dd7dc2-32f7-42f4-b10b-fd3d93f1a759@linuxtom.com> (raw)
Hello,
I'm experiencing an annoying issue with the psmouse kernel module on my
Gen3 T14 ThinkPad, which uses an Elan Trackpoint. When I hold the
trackpoint in one direction for about 5 seconds, it seems to recalibrate
to a new center spot. Consequently, when I release the trackpoint, the
mouse cursor moves in the opposite direction for about 5 seconds.
I've tried to disable this feature by adjusting the module parameters
(resync_time, resetafter) through various methods including udev,
modprobe, and sysfs, and even by modifying the source code. However,
none of these adjustments have changed the behavior, though sensitivity
adjustments seem to work as expected.
I've dipped into the psmouse source code, which is a over my head, and
changed default values for the parameters, recompiled the module, and
reloaded it, to no avail. I'm beginning to suspect these parameters do
not control the recalibration "feature". modinfo does state that setting
both parameters to 0 should disable them, but this has not resolved the
issue.
I've confirmed it's likely a psmouse issue, having replicated the
problem on a minimal system setup without a desktop environment or
libinput, using only evtest. I even tried modifying TP_DEF_DRIFT_TIME in
trackpoint.h out of pure desperation.
Is there any way to fix this issue, or could someone provide more
insight into what exactly these parameters (resync_time, resetafter)
control? Also where can I change the length of time that the
recalibration occurs. If the recalibatron where a longer period I doubt
I would hold it for the length of time it takes to trigger the
recalibration, but 5 seconds gets in the way of fine control of the
trackpoint.
My setup is debian sid, gnome on wayland, debian kernel 6.7.9 and 6.8.7
built from source.
Thank you for your assistance,
Tom
tom@linuxtom.com
reply other threads:[~2024-04-24 20:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84dd7dc2-32f7-42f4-b10b-fd3d93f1a759@linuxtom.com \
--to=tom@linuxtom.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.