On Friday 20 September 2002 23.12, Richard Bos wrote:
What a nice product, but what it's very picky about the kernel versions.
Can someone explain why vmware-3.2 works with kernel 2.4.18-53, but not with kernel 2.4.18-253 (SuSE-8.0). In the later case vmware complains that the vmnet.o is not right and it wants to create by building it. So I decided to download the latest available kernel-source rpm... This is release 2.4.18-135... and as vmware is very picky about the right sources, it did not accept that the sources (...-135) differ from the binaries (..-235).
Any glues, how to deal with this?
1. When you compile kernel modules it is important that you have the same sources installed that was used to build the kernel. This is regardless of where you get the kernel. If you build a module against different sources it could be that it uses features that was added or removed, and that could potentially cause the kernel to crash 2. I doubt that vmware complains that SuSE's build numbers for the rpms differ. They are *never* identical between kernel-source.rpm and k_*.rpm, so if vmware was sensitive to that it couldn't build on any installation. I think you could get by with cd /usr/src/linux make mrproper make cloneconfig make dep Assuming nothing drastic has been patched between the kernel you use and the kernel-source.rpm you downloaded, that should give you a source tree configured to match your running kernel. //Anders