While upgrading a server from kernel 3.2.9 to kernel 3.5 I had a problem with the network (ifconfig eth0 up won't work) so I updated the system to get a newer userspace, but in the process something seemed to go wrong with modprobe, so the HID kernel module didn't come up, although I know it is compiled and ready to be used.
Since I can't log in through SSH and only USB keyboards can be used I got stuck, but I suspect I should be able to load the HID kernel module from the kernel command line, but I don't know the right arguments for that.
EDIT:
Since I use LILO as bootloader, I know it is possible to supply kernel command-line arguments on the boot: prompt following the kernel image label. If my image label is Linux-3.5, what do I need to include after it so USB HID driver is loaded? Should it just read boot: Linux-3.5 usbhid? (The module name was hinted by @Renan on his answer, but it was removed before I could finish commenting it)
lilo.confbefore testing the new one? If not, just boot the old one. If you did... ouch, don't do that – Alan Curry Jul 31 '12 at 2:24