From: Andrew Morton <akpm@linux-foundation.org>
To: "Parag Warudkar" <parag.lkml@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: 2.6.28-rc9: USB Mouse unhappy
Date: Sat, 20 Dec 2008 22:12:53 -0800 [thread overview]
Message-ID: <20081220221253.e09b1b1f.akpm@linux-foundation.org> (raw)
In-Reply-To: <f7848160812201911k7988221asd095ce873fd8105f@mail.gmail.com>
(cc's added)
On Sat, 20 Dec 2008 22:11:17 -0500 "Parag Warudkar" <parag.lkml@gmail.com> wrote:
> Just installed today's git on my workstation and my Logitech USB Mouse
> only wants to move vertically around the centre of the monitor.
>
> I have no clue where to look - all I know is that it works with the
> 2.6.27 and various 2.6.28-rcs prior to this one.
>
> Parag
>
> [parag@xw6600 ~]$ diff Xorg.0.log.not.working /var/log/Xorg.0.log |grep Logi
> < (**) Logitech USB Receiver: Device: "/dev/input/event5"
> > (**) Logitech USB Receiver: Device: "/dev/input/event6"
> < (II) config/hal: Adding input device Logitech USB Receiver
> < (**) Logitech USB Receiver: always reports core events
> < (**) Logitech USB Receiver: Device: "/dev/input/event3"
> < (II) Logitech USB Receiver: Found x and y relative axes
> < (II) Logitech USB Receiver: Found mouse buttons
> < (II) Logitech USB Receiver: Configuring as mouse
> < (II) XINPUT: Adding extended input device "Logitech USB Receiver"
> (type: MOUSE)
> > (II) config/hal: Adding input device Logitech USB Receiver
> > (**) Logitech USB Receiver: always reports core events
> > (**) Logitech USB Receiver: Device: "/dev/input/event5"
> > (II) Logitech USB Receiver: Found x and y relative axes
> > (II) Logitech USB Receiver: Found mouse buttons
> > (II) Logitech USB Receiver: Configuring as mouse
> > (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE)
Could be input, could be HID, could even be USB.
You're sure that 2.6.28-rc8 was OK?
2.6.28-rc9 had only a small number of changes. Nothing I can see in
input or HID. A few USB changes, but pretty specific ones -
unusual_devs entries and such.
Maybe your mouse has died? Did you retest with an older kernel?
next prev parent reply other threads:[~2008-12-21 6:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 3:11 2.6.28-rc9: USB Mouse unhappy Parag Warudkar
2008-12-21 6:12 ` Andrew Morton [this message]
2008-12-21 6:26 ` Parag Warudkar
2008-12-21 10:56 ` Anssi Hannula
2008-12-21 15:17 ` Parag Warudkar
2008-12-21 17:30 ` Jiri Kosina
2008-12-21 18:39 ` Jiri Kosina
2009-01-09 23:11 ` Rafael J. Wysocki
2009-01-09 23:18 ` Parag Warudkar
2009-01-09 23:19 ` Jiri Kosina
2009-01-10 0:19 ` Rafael J. Wysocki
2008-12-21 19:49 ` [PATCH] USBHID: Make Boot Protocol drivers depend on EMBEDDED Parag Warudkar
2008-12-21 21:48 ` Jiri Kosina
2008-12-21 22:02 ` Andrew Morton
2008-12-21 22:03 ` Jiri Kosina
2008-12-21 22:12 ` Parag Warudkar
2008-12-21 22:17 ` Anssi Hannula
2008-12-21 22:23 ` Parag Warudkar
2008-12-21 22:44 ` Jiri Kosina
2008-12-21 23:55 ` Parag Warudkar
2008-12-22 21:52 ` Jiri Kosina
2008-12-21 17:24 ` 2.6.28-rc9: USB Mouse unhappy Jiri Kosina
2008-12-21 18:22 ` Parag Warudkar
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=20081220221253.e09b1b1f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=parag.lkml@gmail.com \
/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