All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parag Warudkar <kernel-stuff@comcast.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] 2.6.12 - USB Mouse not detected
Date: Sun, 10 Jul 2005 17:11:59 -0400	[thread overview]
Message-ID: <200507101712.00181.kernel-stuff@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0507101638470.24579-100000@netrider.rowland.org>

On Sunday 10 July 2005 16:42, Alan Stern wrote:
> > Beginning 2.6.12 my Wireless USB Mouse is not detected in the first
> > attempt - Meaning if I boot the machine with the mouse connected, it's
> > not detected until I disconnect the mouse and then reconnect it.
>
> That's not quite right.  Your log clearly shows the mouse was detected and
> assigned address 2.
Yeah, I shoud have worded it properly - kernel detects the device but it's 
unusable since the driver for it - USBHID wasn't loaded.
>
> >  It works fine after the disconnect-reconnect cycle. Looking at the
> > dmesg, it seems that at first time it forgets to register the hiddev
> > driver - mysteriously, it remembers the second time.
>
> Exactly.  The hiddev driver wasn't loaded the first time, which makes this
> sound like some sort of hotplug failure.  Are your hotplug and udev
> packages up to date?
I hadn't changed anything (except for the system board which failed recently) 
and it used to work fine - So I didnt suspect hotplug to be the culprit - 
another reason for not considering hotplug was it worked the second time with 
identical setup.

What's funny - I rebuilt hotplug - same version - and it works now! Probably 
it was failing for some reason the first time.

Thanks!

Parag

  reply	other threads:[~2005-07-10 21:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-10 13:36 2.6.12 - USB Mouse not detected Parag Warudkar
2005-07-10 20:42 ` [linux-usb-devel] " Alan Stern
2005-07-10 21:11   ` Parag Warudkar [this message]
2005-07-11 17:14     ` Ian Abbott

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=200507101712.00181.kernel-stuff@comcast.net \
    --to=kernel-stuff@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.