I've just had a go at this.
With the attached replacement tarballs (pop them both in /usr/lib/vmware/modules/source after backing up the old files), I resume a suspended machine and access the net from a workstation 6.0.4 installation with a 2.6.26-rc7 kernel. I have not made the #ifdefs right for backwards compatability but apart from that... (Your mileage may vary).
Thanks a lot. It works for me in 2.6.26-rc8.
this works not for me.
If i compile this, this works fine, and will use, i get error that this is the wrong version of modules.
I now use the final 2.6.26 and need to build vmware-modules-184.108.40.206.
Is there a way to use?
Preparing vmmon module
Using 2.6.x kernel build system.
make -C /lib/modules/2.6.26/build M=$PWD SRCROOT=$PWD/. modules
make: Entering directory `/usr/src/linux-2.6.26'
make: warning: jobserver unavailable: using -j1. Add `+' to parent make rule.
/var/tmp/portage/app-emulation/vmware-modules-220.127.116.11/work/vmmon-only/linux/driver.c:197: error: unknown field 'nopage' specified in initializer
/var/tmp/portage/app-emulation/vmware-modules-18.104.22.168/work/vmmon-only/linux/driver.c:198: warning: initialization from incompatible pointer type
thanks, works fine with 2.6.26
Thank you very much! It worked for me with latest 2.6.26
VMWare workstation 6.04 is broken for me since 2.6.22. I use the newest ubuntu with custom kernel 2.6.26 atm.
Building modules, stage 2.
MODPOST 1 modules
WARNING: modpost: missing MODULE_LICENSE() in /tmp/vmware-config0/vmmon-only/vmmon.o
see include/linux/module.h for more information
WARNING: "init_mm" /tmp/vmware-config0/vmmon-only/vmmon.ko undefined!
make: Leaving directory `/usr/src/linux-2.6.26'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
Unable to make a vmmon module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/vmmon.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
Works for me too. Kernel 2.6.26 final.
i have the beta . + linux 2.6.26 + tuxonice patch
i replaced the source vmmon and vmnet tar.
now my question is : how do you compile the module i was unable to launh any instaler from the /usr/lib/vmware/* dir. i have not found any script helper!
Same for me, Linux 22.214.171.124 built from the stock sources.
Let me clarify that.. I thought the thread would show. I get "init_mm undefined" in vmmon.ko, linux 126.96.36.199.
I get "init_mm undefined" in vmmon.ko, linux 188.8.131.52.
It looks like you made a mistake of not including deprecated system calls when building your custom kernel. Please, recompile with CONFIG_UNUSED_SYMBOLS enabled. This option is located in the "Kernel hacking" section.
I've made a patch that seems to get the kernel module to compile and work with 2.6.26.
Now I'd really like VMware to merge it, to save everybody the trouble of applying the patch after every VMware or kernel upgrade.
This is great - works a treat ... except I couldn't figure out how to use this "automagically", so I had to extract all the .tars from /usr/lib/vmware/modules/source, patch by hand and re-tar the 3 archives. Then vmware-config.pl works and builds a working system. I'm sure there must be an easier way, but patch couldn't find files and then just didn't do the changes.
This was on Fedora 8, vmware server 1.0.7 installed by rpm.
Exactly. Applying patches manually is a pain. Does anyone know where to submit patches so that they get included in the next release of VMware?