Hi, i was able to compile the vmmon and vmnet modules from vmware server 1.0.4 on vanilla 2.6.24.

Attached two patches, apply them as usual:

$ cp /path/to/patches/vm{mon,net}-2.6.24.patch /tmp

$ cd /tmp

$ for dir in vm{mon,net}; do

tar xf /usr/local/lib/vmware/modules/source/$.tar cd $-only

patch -p1 < $-2.6.24.patch cd .. tar cf $.tar $-only sudo cp $.tar /usr/local/lib/vmware/modules/source

done

$ sudo vmware-config.pl

Enjoy!

-vjt

does not exactly do the trick

> for dir in vm{mon,net}; do

> tar xf /usr/lib/vmware/modules/source/$.tar > cd $-only

> patch -p1 < ../$-2.6.24.patch > cd .. > tar cf $.tar $-only > cp $.tar /usr/lib/vmware/modules/source

> done

patching file Makefile.kernel

Hunk #1 FAILED at 6.

1 out of 1 hunk FAILED -- saving rejects to file Makefile.kernel.rej

patching file include/vm_basic_types.h

Hunk #1 succeeded at 163 (offset 9 lines).

Hunk #2 succeeded at 177 (offset 9 lines).

Hunk #3 succeeded at 273 with fuzz 1 (offset 11 lines).

patching file linux/driver.c

Hunk #1 FAILED at 1655.

1 out of 1 hunk FAILED -- saving rejects to file linux/driver.c.rej

patching file Makefile.kernel

Hunk #1 FAILED at 7.

1 out of 1 hunk FAILED -- saving rejects to file Makefile.kernel.rej

patching file compat_wait.h

patching file driver.c

Hunk #1 FAILED at 516.

1 out of 1 hunk FAILED -- saving rejects to file driver.c.rej

patching file netif.c

Hunk #1 FAILED at 295.

1 out of 1 hunk FAILED -- saving rejects to file netif.c.rej

patching file sk_alloc.c

Hunk #1 succeeded at 12 with fuzz 2 (offset 8 lines).

Hunk #2 succeeded at 21 with fuzz 2 (offset 8 lines).

patching file vm_basic_types.h

Hunk #1 succeeded at 163 (offset 9 lines).

Hunk #2 succeeded at 177 (offset 9 lines).

Hunk #3 succeeded at 273 with fuzz 1 (offset 11 lines).

patching file vmnetInt.h

Hunk #1 FAILED at 35.

1 out of 1 hunk FAILED -- saving rejects to file vmnetInt.h.rej

patching file vnetInt.h

Hunk #1 FAILED at 29.

1 out of 1 hunk FAILED -- saving rejects to file vnetInt.h.rej

Hey.

Indeed, thanks, it it better. I was using 1.0.0.

On 1.0.4 it is patching correctly, however:

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config11/vmmon-only'

make -C /lib/modules/2.6.24/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-2.6.24'

  CC Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config11/vmmon-only/linux/driver.o

  CC Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config11/vmmon-only/linux/hostif.o

  CC Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config11/vmmon-only/common/cpuid.o

In file included from include/asm/bitops.h:2,

                 from /tmp/vmware-config11/vmmon-only/./include/vcpuset.h:74,

                 from /tmp/vmware-config11/vmmon-only/./include/modulecall.h:22,

                 from /tmp/vmware-config11/vmmon-only/common/vmx86.h:18,

                 from /tmp/vmware-config11/vmmon-only/common/hostif.h:18,

                 from /tmp/vmware-config11/vmmon-only/common/cpuid.c:14:

include/asm/bitops_32.h:9:2: error: #error only  can be included directly

make[2]: *** /tmp/vmware-config11/vmmon-only/common/cpuid.o Error 1

make[1]: *** Re: vmware server kernel 2.6.24 support? Error 2

make[1]: Leaving directory `/usr/src/linux-2.6.24'

make: *** http://vmmon.ko Error 2

make: Leaving directory `/tmp/vmware-config11/vmmon-only'

Unable to build the vmmon module.

I'm glad that the patches are working for you all, and thanks indeed for the #include fix!

-vjt

Hi,

Did the networking part also compile for you? 

Here is what I am getting. Any advice will be very welcome! Thank you!

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config1/vmnet-only'

make -C /lib/modules/2.6.24-4-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-headers-2.6.24-4-generic'

  CC Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config1/vmnet-only/driver.o

  CC Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config1/vmnet-only/hub.o

  CC Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config1/vmnet-only/userif.o

  CC Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config1/vmnet-only/netif.o

  CC Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config1/vmnet-only/bridge.o

  CC Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config1/vmnet-only/procfs.o

  CC Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config1/vmnet-only/smac_compat.o

  SHIPPED /tmp/vmware-config1/vmnet-only/smac_linux.x386.o

  LD Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config1/vmnet-only/vmnet.o

  Building modules, stage 2.

  MODPOST 1 modules

WARNING: could not find /tmp/vmware-config1/vmnet-only/.smac_linux.x386.o.cmd for /tmp/vmware-config1/vmnet-only/smac_linux.x386.o

  CC      /tmp/vmware-config1/vmnet-only/vmnet.mod.o

  LD Re: vmware server kernel 2.6.24 support?  /tmp/vmware-config1/vmnet-only/vmnet.ko

make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-4-generic'

cp -f vmnet.ko ./../vmnet.o

make: Leaving directory `/tmp/vmware-config1/vmnet-only'

Unable to make a vmnet module that can be loaded in the running kernel:

insmod: error inserting '/tmp/vmware-config1/vmnet.o': -1 Unknown symbol in module

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.

Thanks for the solution, this also works well for vmware-server 1.0.5 on hardy heron too.  

notam42, thank you for posting the libgcc_s.so.1 fix! I was using vmware server for a while, but one day it just stopped loading. libgcc_s.so.1 fix solved the problem!