From: Bob Tracy <rct@gherkin.frus.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 3.0.0-rc2 usb mouse not working
Date: Wed, 15 Jun 2011 23:56:21 -0500 [thread overview]
Message-ID: <20110616045620.GA5651@gherkin.frus.com> (raw)
In-Reply-To: <20110615131544.GA3074@gherkin.frus.com>
On Wed, Jun 15, 2011 at 08:15:44AM -0500, Bob Tracy wrote:
> On Tue, Jun 14, 2011 at 10:23:18PM -0500, Bob Tracy wrote:
> > Note: 3.0.0-rc1 hung during boot (right after parport initialization),
> > so the best I can do at the moment is say the bug first showed up after
> > 2.6.39. Processor is an AMD K6-III/450.
> >
> > Symptoms: Microsoft Intellimouse (corded USB optical) non-functional.
> > Red LED comes on when mouse is plugged in, but movement and
> > clicks are not seen.
To make a long story short, the required "usbhid" module is not being
loaded automatically in 3.0-rcX as it was in 2.6.39 and earlier kernels.
A simple "modprobe usbhid" got the mouse working again.
--Bob
prev parent reply other threads:[~2011-06-16 4:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 3:23 [BUG] 3.0.0-rc2 usb mouse not working Bob Tracy
2011-06-15 13:15 ` Bob Tracy
2011-06-16 4:56 ` Bob Tracy [this message]
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=20110616045620.GA5651@gherkin.frus.com \
--to=rct@gherkin.frus.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