From: Zoltan Boszormenyi <zboszor@freemail.hu>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Mousedev or hiddev problem, was: Re: USB mice do not work on 2.6.12-rc5-git9, -rc5-mm1, -rc5-mm2
Date: Wed, 08 Jun 2005 06:55:07 +0200 [thread overview]
Message-ID: <42A67A2B.50600@freemail.hu> (raw)
In-Reply-To: <20050607053943.GA1778@ucw.cz>
Vojtech Pavlik írta:
> On Tue, Jun 07, 2005 at 12:04:15AM +0200, Zoltan Boszormenyi wrote:
>
>>Hi,
>>
>>Zoltan Boszormenyi írta:
>>
>>>All the -bk7+ kernels I tried produced the same strange bug
>>>on my system: after gpm started I was able to move the
>>>pointer on the screen but when X started up, it's pointer froze.
>>
>>it turned out that there is nothing wrong with USB on my system.
>>
>>But someone broke the /dev/input/mouseX <-> USB mouse interaction
>>in 2.6.11-bk7 and my two-headed system with two X servers were
>>manually set up to use the distinct mouse devices so the two heads
>>do not interfere.
>>
>>No wonder gpm works, it reads /dev/input/mice. Starting only
>>one X and using /dev/input/mice I found no problems. Setting it
>>back to /dev/input/mouse0, the mouse pointer is dead again.
>>
>>Someone deserves a mousebite...
>
>
> Most likely it's because the keyboards are now identified as having
> mouse capabilities, too, and changing the numbers. Check
> /proc/bus/input/devices.
Thanks for the enlightenment, now I have to use /dev/input/mouse2 and
mouse3 for the two X servers.
BTW, where is it documented? Was it this changeset?
<vojtech@suse.cz>
input: Fix keyboard scrollwheel support, add horizontal
wheel support, and enable both by default.
Signed-off-by: Vojtech Pavlik <vojtech@suse.cz>
Best regards,
Zoltán Böszörményi
next prev parent reply other threads:[~2005-06-08 4:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 6:50 USB mice do not work on 2.6.12-rc5-git9, -rc5-mm1, -rc5-mm2 Zoltan Boszormenyi
2005-06-05 7:14 ` Zoltan Boszormenyi
2005-06-05 7:10 ` Andrew Morton
2005-06-05 7:27 ` Dmitry Torokhov
2005-06-05 14:18 ` Sid Boyce
2005-06-05 14:33 ` Sid Boyce
2005-06-05 8:48 ` Zoltan Boszormenyi
2005-06-05 10:08 ` Zoltan Boszormenyi
2005-06-05 10:29 ` Zoltan Boszormenyi
2005-06-05 15:17 ` Zoltan Boszormenyi
2005-06-06 20:33 ` Zoltan Boszormenyi
2005-06-06 22:04 ` Mousedev or hiddev problem, was: " Zoltan Boszormenyi
2005-06-07 5:39 ` Vojtech Pavlik
2005-06-08 4:55 ` Zoltan Boszormenyi [this message]
2005-06-08 5:17 ` Vojtech Pavlik
2005-06-05 9:09 ` Gene Heskett
2005-06-05 9:10 ` Gene Heskett
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=42A67A2B.50600@freemail.hu \
--to=zboszor@freemail.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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