Sorry I forgot to mention that you’ll have to change the path to the download script to your download rather than mine in the line:
patch -p0 /home/joe.blogs/Downloads/vmware2.6.39fixed.patch
This may just mean changing joe.blogs to your username or typing a completely new path.
If your not sure what this should be then you can open a new console prompt (no su this time) and type:
find -name vmware2.6.39fixed.patch
and just copy and paste the path in …
Good luck!
Yes thanks I did that 
Hi
You need to add a ’ <’ and probably easier to cp it to where the script is running, eg;
cp /home/joe.blogs/Downloads/vmware2.6.39fixed.patch .
patch -p0 < vmware2.6.39fixed.patch
Hmmmmm…
Thanks Malcolm! Maybe that’s why the patch hung and didn’t return to cli ?
I’ll try adding that and run it again after copy the original tarballs back.
Yeeeeeha 
SOLVED
Workstation is working again
The < was apparently the trick. Hadn’t done any patch stuff before so I would have never caught that!
Thanks audiocomp for your very comprehensive guidance!
Thanks Malcolm for dropping in and catching the missing <
Not sure if the patch needed to be moved into the working folder but did that just to make sure.
Now back to getting some work done!
Hi gents,
First off: I appreciate all the effort in keeping things going even on a rolling release like Tumbleweed.
Now, can someone host the latest version of the patch somewhere else than heliohost.org? I keep getting a 404. . .
Thanks!
Ah, at last the site went up again late last night, so I could get to the patch. It works perfectly, thanks.
Works great with VMware Player 3.1.4 if you modify “plreqver=3.1.3” to be “plreqver=3.1.4”. Very simple, great fix but all this patching is making Vbox look better and better even if it’s owned by Oracle now.
I thought so too until I tried to migrate a Workstation Windows 7 VM to Vbox. Gave up after three days
LOL … know you realy anything about VMWare ?
For every new version of kernel VMWare modules are AUTOMTICALY compiled. It is standard procedure. Our tip (just download… bla bla bla …) is USELES and stupid.
When modules are compiled with new kernel, all is ok.
When compiling not posible (2.6.39), then is PROBLEM - not working. Then is time for kernel roll-back. But, roll-back to PREViOUS (2.6.38) kernel is not possible. Not present in Tumbleweed repo.
Who get out working kernel 2.6.38 from Tumbleweed and left only one ( RC ! ) version of new kernel ?! When Tumbleweed came, I expected the next final versions of the kernel, not RCx !! Now i must return to 2.6.37 from official repos. Isn’t possible left 2 versions of kernel in repo ?
This is not good idea for Tumbleweed.
If you are using Software that has known problems with new kernel versions, then is Tumbleweed not the right use case for you.
Well, I have tried this :
http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.39patchv3.tar.bz2
The file contents one script (that avoid to have to do all the cp, untar, tar by hand, and the latest patch (v3) for kernel 2.6.39.
It just works.
As an answer to another post that complains about the head kernel repo only having the latest kernel build :
A kernel upgrade/update is not a neutral process, it cannot (or should not) be considered as another update, you should consider some steps before and after the update, like
verifying if anyone else has already tried and if issues have been raised and solved (like this patch for vmware), the opensource community is huge enough to provide this kind of solution a couple of days already after the release of new kernels.
Never use a production machine/installation, there are plenty solutions to do so (a second machine, Vms, second boot disk etc…).
make backups of the current kernel installed, personally added to a backup of my working install (a partition dump using dd) I always make a local copy of the repository just after having updated and tested my new kernel once I get everything working. To do so, I have create and added a simple directory repository to my repository list, I can then easily rollback to the previous version if some issues aren’t solved.
Have a nice day
The patch works for the latest Tumbleweed kernel 2.6.39.1-31. However, the user must uninstall the VMware-Workstation and delete the “vmware” directory in “usr/lib”.
Otherwise, when you try to rerun the script you will get a message that it has already been applied. In addition, you will not be able to install the tools.
To resolve this issue, follow the steps below:
**Example:**sh VMware-Workstation-Full-7.1.4-385536.x86_64.bundle
I hope you find this useful for future Tumbleweed kernel updates.
Remember to have fun!
Romanator
Or you could keep a copy of the un-patched /usr/lib/vmware/modules/source directory.
Copy the directory back to /usr/lib/vmware/modules/source.
Then run the patch
That is also another good option 
I have a correction to the steps I provided below:
The patch works for the latest Tumbleweed kernel 2.6.39.1-31. However, the user must uninstall the VMware-Workstation and delete the “vmware” directory in “usr/lib”.
Otherwise, when you try to rerun the script you will get a message that it has already been applied. In addition, you will not be able to install the tools.
To resolve this issue, follow the steps below:
**Example:**sh VMware-Workstation-Full-7.1.4-385536.x86_64.bundle