mkubecek
Workstation 17.6.3 problem with building modules on kernel 6.15.rcX
Is there a solution to the problem with building modules under kernel 6.15 rc?
make -C vmmon-only
make[1]: Wejście do katalogu '/opt/vmware-host-modules/vmmon-only'
Using kernel build system.
make -C /lib/modules/6.15.0-0.rc4.20250430gtb6ea1680.336.vanilla.fc42.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[2]: Wejście do katalogu '/usr/src/kernels/6.15.0-0.rc4.20250430gtb6ea1680.336.vanilla.fc42.x86_64'
make[3]: Wejście do katalogu '/opt/vmware-host-modules/vmmon-only'
CC [M] linux/driver.o
linux/driver.c:21:10: fatal error: driver-config.h: Nie ma takiego pliku ani katalogu
21 | #include "driver-config.h"
| ^~~~~~~~~~~~~~~~~
compilation terminated.
make[5]: *** [/usr/src/kernels/6.15.0-0.rc4.20250430gtb6ea1680.336.vanilla.fc42.x86_64/scripts/Makefile.build:203: linux/driver.o] Błąd 1
make[4]: *** [/usr/src/kernels/6.15.0-0.rc4.20250430gtb6ea1680.336.vanilla.fc42.x86_64/Makefile:2019: .] Błąd 2
make[3]: *** [/usr/src/kernels/6.15.0-0.rc4.20250430gtb6ea1680.336.vanilla.fc42.x86_64/Makefile:256: __sub-make] Błąd 2
make[3]: Opuszczenie katalogu '/opt/vmware-host-modules/vmmon-only'
make[2]: *** [Makefile:256: __sub-make] Błąd 2
make[2]: Opuszczenie katalogu '/usr/src/kernels/6.15.0-0.rc4.20250430gtb6ea1680.336.vanilla.fc42.x86_64'
make[1]: *** [Makefile:117: vmmon.ko] Błąd 2
make[1]: Opuszczenie katalogu '/opt/vmware-host-modules/vmmon-only'
make: *** [Makefile:21: vmmon-only] Błąd 2
I'm struggling to get this working on CachyOS 6.15.0-rc7-4-cachyos-rc
how did you actually install those patched files?
The make fails....
I'm using Fedora 43 and Ubuntu-25.10,under both systems the patch works.
The question was how to actually use these patch files and doing a make will fail... (or arch 6.15 latest RC anyway)
just extract the file and see README file,there has step to step commands.
just extract the file and see README file,there has step to step commands.
The README file is useless. It does not provide any kind of instruction towards what is required for compiling properly.
I will provide a fix in AUR. Here you go. https://aur.archlinux.org/packages/vmware-host-modules-dkms-fix-git TESTED WORKING Archlinux with 6.15.0-2-cachyos kernel @jpeaglesandkatz @marplusz 🎉
Here is a simple fix for kernel-6.16.rc0 vmware-host-modules-workstation-17.6.0-kernel-6.16.rc0.tar.gz
Here is a simple fix for kernel-6.16.rc0 vmware-host-modules-workstation-17.6.0-kernel-6.16.rc0.tar.gz
Again with the previous tar that was shared.. No indication on how to actually use it as doing a make will not work... The adjusted AUR from zDEFz worked on 6.15 though so all good
Here is a simple fix for kernel-6.16.rc0 vmware-host-modules-workstation-17.6.0-kernel-6.16.rc0.tar.gz
Again with the previous tar that was shared.. No indication on how to actually use it as doing a make will not work... The adjusted AUR from zDEFz worked on 6.15 though so all good
Yea. With what I've learned is that the knowledge is meant to be inferred. But that's not how you teach others. I would had hoped there were at least some instructions. What I did, was to take the existing AUR entry and modify it.
Also the suspense - almost 30 days of wait for somebody else... not ideal.
That is just for kernel-6.16 rc0 that is not released。file INSTALL in this package explain how to build。
That is just for kernel-6.16 rc0 that is not released。file INSTALL in this package explain how to build。
Except THAT doesn't work What is the point of posting tar's that MAY work on that users system/distro etc but fail to do on any other... I'd say.. be more specific with posting stuff.. Simply linking a tar is just silly in the world of linux
That is just for kernel-6.16 rc0 that is not released。file INSTALL in this package explain how to build。
Except THAT doesn't work What is the point of posting tar's that MAY work on that users system/distro etc but fail to do on any other... I'd say.. be more specific with posting stuff.. Simply linking a tar is just silly in the world of linux
What you say isn't the fact.at least it is effect for two major Linux relase:fedora and ubuntu.you build fail may caused by unsufficient depends,this isn't my fault。
yup... that adjusted AUR did work as I commented with a 👍 That was actually just about the only useful post
The way I patched this module was simple and direct, and perhaps primitive: compile it in the original folder (before patched), then find reasons which result the compliation failed from the error message of the compilation process, then fix it (modify the source file that leads the compilation abort), finally repackage it into a usable file.
just extract the file and see README file,there has step to step commands.
The README file is useless. It does not provide any kind of instruction towards what is required for compiling properly.
I will provide a fix in AUR. Here you go. https://aur.archlinux.org/packages/vmware-host-modules-dkms-fix-git TESTED WORKING Archlinux with 6.15.0-2-cachyos kernel @jpeaglesandkatz @marplusz 🎉 My post above is indeed wrong, but the patch I provided is valid. In fact, you can simply unzip the compressed package to a folder, then enter the folder, execute make first, then execute sudo make install. The method in the INSTALL file allows you to automatically compile the two kernel modules required by the virtual machine when running VMWARE every time you boot from a new kernel (of course, it is still the 6.15 version of the kernel) to the desktop.
I never thought that one day, I, a non-professional Linux enthusiast, would argue with programmers on GitHub over an issue related to a program patch.
@jeamieofqidan
I never thought that one day, I, a non-professional Linux enthusiast, would argue with programmers on GitHub over an issue related to a program patch.
marplusz etc did already had their fix @jpeaglesandkatz came with a new request: How to compile it for archlinux/cachyos But now you write that it works on Fedora and Ubuntu, unrelated to the request.
The question was - how to compile it for archlinux. You should have simply said that you do not know, or that you need to spin up a virtual machine to check on it. I checked it out myself and it wasn't as straightforward as one might think.
When you write helpful content for others, it should always be in the context of what was asked. Not whether if it works for you, unrelated to the problem at hand.
I never thought that one day, I, a non-professional Linux enthusiast, would argue with programmers on GitHub over an issue related to a program patch.
marplusz etc did already had their fix @jpeaglesandkatz came with a new request: How to compile it for archlinux/cachyos But now you write that it works on Fedora and Ubuntu, unrelated to the request.
The question was - how to compile it for archlinux. You should have simply said that you do not know, or that you need to spin up a virtual machine to check on it. I checked it out myself and it wasn't as straightforward as one might think.
When you write helpful content for others, it should always be in the context of what was asked. Not whether if it works for you, unrelated to the problem at hand.
You seem to be ignoring others in order to prove that you are right. It was the owner of this issue who first said that the solution I provided is effective, and two other people later proved that it is effective.
other people have proven that the solution I provided is effective. But you are here, ignoring the facts and saying nonsense that I don't know how to do it. You must prove that your solution is the only one, right?
再次看了一下＠marplusz提交的issue,他本人提交的问题就是在Fedora下编译相关的。我解决了楼主本人的问题，楼主也证实了，而你却要反复的否认这一点。我不想再和你争论。请楼主把这个问题标记为已解决吧。
other people have proven that the solution I provided is effective. But you are here, ignoring the facts and saying nonsense that I don't know how to do it. You must prove that your solution is the only one, right?
No. I already said, the original question has been answered. The issue is, that a new question had been started to which the answer that was given by you was not helpful. For that part, I had provided a solution. There's nothing to discuss.
Here are patched files.
Why not provide a PR here? So we would see what the changes actually are.
Spent 2 days trying to figure this out, finally fixed it with ChatGPT and lost my message with it trying to figure out the issue and actually solve it. For anyone trying to get this to work without much knowledge on how to do it:
Step 1: Download this
Step 2: Extract somewhere onto your computer
Step 3: In terminal, cd into the folder you just extracted
Step 4: Run make
Step 5: Run sudo make install
Step 6: VMware should run flawlessly now, happy VMing!
Here are patched files.
Actually I don't know you, do you expect me to analyze your tarball to see what you actually changed and that you didn't add a backdoor. It would be actually more helpful if you posted the patches.
