With the 2.6.22 gentoo-sources kernel, there seems to be a problem with USB trackballs. When I upgraded the first time (to -r2), I lost the use of my trackball (which is running via USB and event interface), and went back to 2.6.21 until the next .22 release. With -r5, the problem still persist, but while with -r2 I had only 2 event interfaces, I now have 4. I've run lsusb a few times, tried diffrent USB ports in my system, and while my normal mouse (pluged into my PS/2 plug so my keyboard will act as expected) works, my trackball doesn't. I've tried catting out the event? interfaces, and the by-path interfaces as well. Reproducible: Always Steps to Reproduce: 1.Upgrade to 2.6.22-r? 2.Try to use a USB-based trackball 3.Watch nothing happen Actual Results: Wasn't recognized Expected Results: Have given me a useable trackball like in 2.6.21 Logitech trackball.
This has nothing to do with any Gentoo release.
Can you please attach the following: .config for last working kernel .config for .22-r5 dmesg lspci -v lsusb -v cat /proc/bus/input/devices
Also, can you please test with the latest vanilla kernel which is version 2.6.23_rc3 as of this writing.
This is likely to be fixed upstream; from the 2.6.22.6 changelog: commit 233b8a1ed2ef8e17c12a6f328470cf11d64a756a Author: Kay Sievers <kay.sievers@vrfy.org> Date: Wed Aug 22 15:15:51 2007 -0700 usb: add PRODUCT, TYPE to usb-interface events This fixes a regression for userspace programs that were relying on these events. Signed-off-by: Kay Sievers <kay.sievers@vrfy.org> Cc: Andreas Jellinghaus <aj@ciphirelabs.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Thanks for pointing that out Jouni. gentoo-sources-2.6.22-r6 includes this, hopefully it fixes the problem.
Sorry for the lack of response to this bug. I'm going to try -r6 and see if it helps. If not, when I get some more free time, I'll start into the rest.
I've upgraded the kernel to -r6, and it seems to work. Might as well resolve this bug.
Since switching to gentoo-sources-2.6.22-r6 fixed the issue for you, I'm closing this bug.