kernel-headers-5.17.5-200-fc35 package missing

[Adam Mercer]

Hi

I had an update to the 5.17.5 kernel ,on my Fedora 35 system, this
morning but there was no corresponding update to the kernel-headers
package. As such I'm unable to rebuild the VMWare modules for VMWare
Workstation. Do I just need to wait until the next mirror sync or is
this not available for some other reason?

Cheers

Adam

[Doug Herr]

On Thu, May 5, 2022, at 9:41 AM, Adam Mercer wrote:
> Hi
>
> I had an update to the 5.17.5 kernel ,on my Fedora 35 system, this
> morning but there was no corresponding update to the kernel-headers
> package. As such I'm unable to rebuild the VMWare modules for VMWare
> Workstation. Do I just need to wait until the next mirror sync or is
> this not available for some other reason?

I don't have VMWare, using VirtualBox. But I think it did actually *build* my new driver.

I can confirm that I am still running on the .4 version of the headers:

9:58-doug@wombat-~>rpm -qa | grep headers-5
kernel-headers-5.17.4-200.fc35.x86_64

9:59-doug@wombat-~>rpm -qa |grep 5.17.5
kernel-core-5.17.5-200.fc35.x86_64
kernel-modules-5.17.5-200.fc35.x86_64
kernel-5.17.5-200.fc35.x86_64
kernel-modules-extra-5.17.5-200.fc35.x86_64
kernel-devel-5.17.5-200.fc35.x86_64
kmod-VirtualBox-5.17.5-200.fc35.x86_64-6.1.34-2.fc35.x86_64

Maybe the VMWare build is being a bit too picky about the required header?

[ja]

On Thu, 2022-05-05 at 09:41 -0700, Adam Mercer wrote:
> Hi
>
> I had an update to the 5.17.5 kernel ,on my Fedora 35 system, this
> morning but there was no corresponding update to the kernel-headers
> package. As such I'm unable to rebuild the VMWare modules for VMWare
> Workstation. Do I just need to wait until the next mirror sync or is
> this not available for some other reason?
>
> Cheers
>
> Adam

I have been using this repository for building VMWare modules

https://github.com/mkubecek/vmware-host-modules

Fully updated F35

The following kernel/modules work OK

ja@harting ~ 15$ uname -a
Linux harting.jaa.org.uk 5.17.5-200.fc35.x86_64

ja@harting ~ 23$ vmware -v
VMware Workstation 16.2.3 build-19376536

ja@harting ~ 18$ rpm -qa|grep headers
vulkan-headers-1.3.204.0-1.fc35.noarch
kernel-headers-5.17.4-200.fc35.x86_64
glibc-headers-x86-2.34-32.fc35.noarch

ja@harting ~ 21$ rpm -qa|grep kernel-devel
kernel-devel-5.16.20-200.fc35.x86_64
kernel-devel-5.17.4-200.fc35.x86_64
kernel-devel-5.17.5-200.fc35.x86_64

Appears to work with the older header file,
but I seem to remember (not certain) that valid "kernel-devel" required.

John

[Adam Mercer]

On Fri, May 6, 2022 at 1:55 AM ja  wrote:
> I have been using this repository for building VMWare modules
>
> https://github.com/mkubecek/vmware-host-modules

I tried that as well, but that fails in a slightly different way:

ram@zathras [08:34:09] [~/git/vmware-host-modules] [workstation-16.2.3]
-> % make
make -C vmmon-only
make[1]: Entering directory '/home/ram/git/vmware-host-modules/vmmon-only'
Using kernel build system.
make -C /lib/modules/5.17.5-200.fc35.x86_64/build/include/.. M=$PWD
SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[2]: Entering directory '/usr/src/kernels/5.17.5-200.fc35.x86_64'
make[2]: *** No rule to make target 'modules'.  Stop.
make[2]: Leaving directory '/usr/src/kernels/5.17.5-200.fc35.x86_64'
make[1]: *** [Makefile:117: vmmon.ko] Error 2
make[1]: Leaving directory '/home/ram/git/vmware-host-modules/vmmon-only'
make: *** [Makefile:21: vmmon-only] Error 2
ram@zathras [08:34:10] [~/git/vmware-host-modules] [workstation-16.2.3]
-> %

and the Makefile in /usr/src/kernels/5.17.5-200.fc35.x86_64 is an
empty file, unlike in other kernel directories. I've reinstalled the
kerel-devel-5.17.5-200.fc35 package and that installed a Makefile with
actual contents which allowed me to rebuild the module.

Thanks for the help!

Cheers

Adam

[stan]

On Thu, 5 May 2022 09:41:31 -0700
Adam Mercer  wrote:
> Hi
>
> I had an update to the 5.17.5 kernel ,on my Fedora 35 system, this
> morning but there was no corresponding update to the kernel-headers
> package. As such I'm unable to rebuild the VMWare modules for VMWare
> Workstation. Do I just need to wait until the next mirror sync or is
> this not available for some other reason?

If there was no update to the kernel-headers package, it means that the
kernel api did not change, so you can use the older headers package so
compile with the newer kernel.  As Doug said, even though a compile
would succeed, it might be that the vmware modules are being too
particular and requiring complete synchronization.