Portage just upgraded me to modutiles 2.4.22, and when I rebooted, my USB mouse doesn't work anymore. At boot, I see that the hid module did not load. Modprobe hid gives me the error "Can't locate module keybdev which is needed for hid." I'm quite sure keybdev was NOT needed before, because it was not installed. (/lib/modules/2.4.19-gentoo-r10/modules.dep does not list it as a dependency either.) I tried depmod, and rebuilding the kernel modules, with no improvement. Finally, if I try isnmod hid, it loads fine. Mailing list online (http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg09043.html) hints that it's a problem with modutils, which was fixed in 2.4.21, but seems to have sprung up for me again.
Hmm, I'll look into this when I get a chance, until then, if modutils 2.4.20 works for you, just use that... I'll let ya know when or if I figure this out or when a new modutils version fixes it.
i get the same problem.. it doesn't see any of my usb mice: hub.c: 2 ports detected hub.c: USB new device connect on bus1/2, assigned device number 2 usb.c: USB device 2 (vend/prod 0x45e/0x24) is not claimed by any active driver. (all have varying vend/prod codes)..
I have suffered the same problem. The problem, is that "modprobe hid" keeps asking for keybdev.o or mousedev.o modules, even if they were built statically into the kernel. The solution is to go back to modutils-2.4.20
As I sort of mentioned, if you don't want to downgrade modutils, you could try adding "insmod hid" to /etc/conf.d/local.start as a workaround until a fix comes out. The hid module is quite loadable and really works, but modprobe seems broken.
This is the same bug as Bug #11931 started on 2002-12-10. Glad to see someone is working on it. I guess since you are working on this later bug, you can close 11931 as a duplicate and clear your plate a little bit.
Shouldn't they be a dup of each other? And the same problem exists with module-init-tools which uses modutils. Except the problem is compounded by the fact that insmod hid doesn't work. I had to manually edit the ebuild to use modutils-2.4.20
*** Bug 11931 has been marked as a duplicate of this bug. ***
OK, I figured this out. depmod adds some unholy defaults to the module configuration. I'll get this fixed today.
fixed in modutils-2.4.24 (due to our patch, not yet fixed upstream)
