From: Ullrich Jans <ujans@ullisys.pond.sub.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test3 XF86Config-4 mouse resolution doesn't work
Date: Sun, 07 Sep 2003 12:19:35 +0200 [thread overview]
Message-ID: <87r82syk7c.fsf@ullisys.pond.sub.org> (raw)
Corey Hickey (bugfood-ml@fatooh.org) wrote:
> In my XF86Config-4 file, I have my mouse set to use the "Resolution"
> option, in order to have faster pointer motion without using
> acceleration. This worked fine in 2.4.21, but now that I'm trying
> out 2.6.0-test3 it doesn't seem to work. That is, changing the value
> of "Resolution" has no effect whatsoever. The mouse is slow, like it
> used to be in 2.4 before I added the Resolution option.
For me, loading psmouse with the parameter psmouse_resolution=200
helped, like this:
modprobe psmouse psmouse_resolution=200
Hope this helps...
Regards, Ulli
--
Ullrich Jans Eichenstrasse 4
Tel: +49 89 74427834 82024 Taufkirchen
Usenet: ujans@ullisys.pond.sub.org RealUlli@IRC
next reply other threads:[~2003-09-07 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-07 10:19 Ullrich Jans [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-12 6:24 2.6.0-test3 XF86Config-4 mouse resolution doesn't work Corey Hickey
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=87r82syk7c.fsf@ullisys.pond.sub.org \
--to=ujans@ullisys.pond.sub.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox