From: Mark Lord <kernel@teksavvy.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Regression: ps2mouse not working in 2.6.34
Date: Mon, 28 Jun 2010 13:18:35 -0400 [thread overview]
Message-ID: <4C28D96B.6060409@teksavvy.com> (raw)
In-Reply-To: <20100628163350.GA11670@core.coreip.homeip.net>
On 28/06/10 12:33 PM, Dmitry Torokhov wrote:
> On Mon, Jun 28, 2010 at 12:04:46PM -0400, Mark Lord wrote:
>> Okay, who broke it, and how do I re-enable it?
>>
>> The PS/2 mice on my systems here don't do anything with 2.6.34.
>> One system complains that I need to boot with i8042.nopnp to enable it,
>> which I also tried, but still nogo. Same behaviour with or without
>> /dev/psaux enabled. 64-bit kernel.
>>
>> The other system, running older userspace, hangs at the X-server startup
>> because it cannot find the mouse. No i8042 warnings. 32-bit kernel.
>>
>> Both systems working fine with older kernels.
>> Google finds lots of other people discovering the same problem.
>>
>> What gives?
>>
>
> Well, lest start small: did it work ifor you with 2.6.33? Does kernel
> discover AUX serio port (dmesg)? What about the mouse itself? Is it
> absent or is it not reporting events?
..
I started by crawling into the wire nest under the table. :)
After a certain amount of experimentation, it appears that the newer
kernel is not compatible with the USB-to-PS2 dongle on the end of the mouse.
I found a different USB-to-PS2 dongle which does work, though.
Very weird. I can mail you the other dongle if are really interested
in figuring out what broke and fixing it.
Otherwise, things are now working here again after the hardware change.
Cheers
next prev parent reply other threads:[~2010-06-28 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 16:04 Regression: ps2mouse not working in 2.6.34 Mark Lord
2010-06-28 16:33 ` Dmitry Torokhov
2010-06-28 17:18 ` Mark Lord [this message]
2010-06-28 17:31 ` Dmitry Torokhov
2010-06-28 20:57 ` Mark Lord
2010-06-28 16:34 ` Mark Lord
2010-06-28 16:51 ` Dmitry Torokhov
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=4C28D96B.6060409@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=dmitry.torokhov@gmail.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