modprobe: Module hid_generic not found.

I found some info regarding this error which occurs during mkinitrd, as well as at each boot, which is why I’m posting. Is there a way to maybe hide errors like this at boot time, say if I wanted to use openSuse in a more ‘mainstream’ setting?

This is amd64, 12.2. The entire ‘error’ is:

modprobe: Module hid_generic not found.
WARNING: no dependencies for kernel module ‘hid-generic’ found.

and a post about it I found here, I’m liking the translated version from google: Google Translate

To directly quote Sebastian:

Sebastian Siebert | September 26 13:47

The warning is due to the dependence on the mkinitrd mkinitrd script
/ Lib / mkinitrd / scripts / boot usb.sh the missing kernel module hid-generic
output. If by the initrd for the kernel 3.4.6 openSUSE
generated, one can not ignore the issue, but because the correct
HID module is included.

The kernel developers from Kernel 3.5.x kernel module usbhid in 2
Modules (usbhid and hid-generic) split. Here was no warning
come more from mkinitrd.

Does this mean perhaps that unless a 3.5 kernel for 12.2 is released there is nothing that can be done, or is a patch possible?

So where is the problem? Something does not work?

To quote myself:

There is no “problem” really, it’s just the unwanted notice that is an issue, things like this do slow down boot time as they add up, and are just plain ugly to look at it when they interupt the polished grub to plymouth boot. With grub2 things are even worse at boot, so focusing on the smoothness and quietness of the boot operation is the point of this post.

If you insist on not seeing it, edit /lib/mkinitrd/scripts/boot-usb.sh and remove hid-generic from list of modules. But do not complaint if it breaks with next kernel update :slight_smile:

Thanks, I’ll try that. I guess I can run mkinitrd just to be safe? With the next kernel release it shouldnt matter if I read correctly.

To my best knowledge this message comes only when mkinitrd runs when it probes for list of modules to include in initrd. But you say you also see it on boot, so I am curious whether it goes away if you recreate initrd.