kmod-usbip for 4.18.0-408.el8.x86_64 kernel?

[tedlum]

I have a development machine running CentOS Stream release 8, where 4.18.0-408.el8.x86_64 appears to be the latest kernel. I need the kmod-usbip kernel module, but, I've been unable to find a package that was built for this kernel.

Code: Select all

kmod-usbip-0.0-7.el8_4.elrepo.x86_64 is built for 4.18.0-305.el8.x86_64
kmod-usbip-0.0-8.el8_4.elrepo.x86_64 is built for 4.18.0-305.19.1.el8_4.x86_64
kmod-usbip-0.0-9.el8_5.elrepo.x86_64 is built for 4.18.0-348.el8.x86_64
kmod-usbip-0.0-9.el8_6.elrepo.x86_64 is built for 4.18.0-372.9.1.el8.x86_64
kmod-usbip-0.0-10.el8_7.elrepo.x86_64 is built for 4.18.0-425.3.1.el8.x86_64

Am I looking in the wrong repo? Is there another that I'm not aware of?
I presume I'm going to need to build this module for this kernel. Is this the way of the new world order, post CentOS? Is *-Stream too much of a moving target - and I digress - but why wouldn't something so fundamental as kmod-usbip not be built as part of Core or Extras?

-TIA

[TrevorH]

ELRepo do not build for Stream as it changes so frequently that it is too much work. You are better off using one of the RHEL 8 clones like Rocky/Alma or OEL or even RHEL itself (you can run uip to 16 instances using the free developer subscription).

[tedlum]

I do use Rocky in most cases on bare metal, but this dev instance is in an Openstack environment, so that means acquiring or building images for any flavour of any instance... it actually meant that Openstack itself got very broken about this time last year when CentOS got EOLed and the repo's vanished - I had to migrate the whole cluster to 8-stream. At least at the time there were no "cloud" images available for the various "clones". I do have CentOS 8 and 9 images but there is little point in instantiating either because their EOLed and you have to hack them just to get them to point to the archived repos.

One way or the other I'm going to have to build something unless there is an off-the-shelf cloud image with a kernel version for which there is a kmod-usbip build OR even less likely, the kernel was built WITH it. I might be wrong but building a kmod seems like less trouble than building an OS cloud image. The whole ecosystem got turned on its ear 1 year ago yesterday and I'm still learning where all the pieces landed.

[tedlum]

Okay, so that this question may be helpful to others and not leave people hanging, wondering... there is already a ticket open on this, here 0001140: request kmod-usbip support for EL8 kernel 4.18.0-315.el8.x86_64

There is a blog post explaining stream support, or lack there of, here ELRepo and CentOS Stream

And, there is a CentOS Kmods SIG, whose charter appears to be providing Kmods not available in Stream, here Kmods SIG, which has a repository here kmods8s-packages-main-release, although, they are not supporting kmod-usbip... yet.


As for Rocky lacking generic cloud image support, their generic cloud images have matured greatly in the last year. I was able to locate a compatible image that so far has not demonstrated any problems on Openstack, from here Index of /pub/rocky/8/images/x86_64/