From: walt <wa1ter@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 had good mouse-support, why is 2.6 so bad?
Date: Mon, 29 Dec 2003 05:27:01 -0800 [thread overview]
Message-ID: <3FF02BA5.2080809@myrealbox.com> (raw)
In-Reply-To: <3fefe3ed$0$9748$edfadb0f@dread14.news.tele.dk>
Peter Michael Jensen wrote:
> Yes with psmouse_noext the wheel stops to work completely and xev does
> not detect anything when I use the wheel.
There were some changes committed just a few hours ago which might fix it.
The psmouse_noext parameter has been replaced by psmouse_proto which is
what you might want to try. I'm about to try it myself on the one
machine I have problems with.
The patches are here:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/cset/
(click on Full Patch Set from v2.6.0)
next parent reply other threads:[~2003-12-29 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.l7jjj9n.1n66tjf@ifi.uio.no>
[not found] ` <fa.fmguq42.vj43qe@ifi.uio.no>
[not found] ` <3fefe3ed$0$9748$edfadb0f@dread14.news.tele.dk>
2003-12-29 13:27 ` walt [this message]
[not found] <3feefec6$0$9741$edfadb0f@dread14.news.tele.dk>
2003-12-28 23:25 ` 2.4 had good mouse-support, why is 2.6 so bad? walt
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=3FF02BA5.2080809@myrealbox.com \
--to=wa1ter@myrealbox.com \
--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