VMWare install - vmmon.ko will not build on FC5

[Irvine Short]

Hey All

I was just playing with the new VMWare server but could not build
vmmon.ko:

  LD [M]  /tmp/vmware-config1/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.17-1.2157_FC5-i586'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
Unable to make a vmmon module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config1/vmmon.o': -1 Invalid module
format
There is probably a slight difference in the kernel configuration
between the
set of C header files you specified and your running kernel.  You may
want to
rebuild a kernel based on that directory, or specify another directory.

For more information on how to troubleshoot module-related problems,
please
visit our Web site at
"http://www.vmware.com/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

However, checking the running kernel and installed sources I get:

[root at arthur ~]# uname -r
2.6.17-1.2157_FC5
[root at arthur ~]# rpm -qa | grep kernel
kernel-devel-2.6.17-1.2157_FC5
kernel-2.6.16-1.2096_FC5
kernel-2.6.17-1.2157_FC5
kernel-doc-2.6.17-1.2157_FC5


Has anyone else run into a similar problem?

Cheers,

--Irvine
--------------------------------------------------------

This e-mail and any attachments are confidential and may also be legally
privileged and/or copyright material of Intec Telecom Systems PLC (or its
affiliated companies). If you are not an intended or authorised recipient
of this e-mail or have received it in error, please delete it immediately
and notify the sender by e-mail. In such a case, reading, reproducing,
printing or further dissemination of this e-mail or its contents is strictly
prohibited and may be unlawful.
Intec Telecom Systems PLC does not represent or warrant that an attachment
hereto is free from computer viruses or other defects. The opinions
expressed in this e-mail and any attachments may be those of the author and
are not necessarily those of Intec Telecom Systems PLC.