can't start VMware-Workstation-7.1.2 on fc14

[TheBigRed]

hi,

after updating from fc13 to fc14 vmware workstation couldn't start any longer.
The VMWare Kernel Modul Updater couldn't compile the module vmmon.

installed components:
kernel-devel-2.6.35.6-48.fc14.x86_64
kernel-2.6.35.6-48.fc14.x86_64
kernel-headers-2.6.35.6-48.fc14.x86_64
VMware-Workstation-7.1.2-301548.x86_64.bundle
Linux fc14 2.6.35.6-48.fc14.x86_64
gcc-4.5.1-4.fc14.x86_64

this is was the log file says:

Okt 31 09:22:22.959: app-139690174371616| Log for VMware Workstation pid=11889 version=7.1.2 build=build-301548 option=Release
Okt 31 09:22:22.959: app-139690174371616| The process is 64-bit.
Okt 31 09:22:22.959: app-139690174371616| Host codepage=UTF-8 encoding=UTF-8
Okt 31 09:22:22.959: app-139690174371616| Logging to /tmp/vmware-root/setup-11889.log
Okt 31 09:22:23.122: app-139690174371616| modconf query interface initialized
Okt 31 09:22:23.122: app-139690174371616| modconf library initialized
Okt 31 09:22:23.158: app-139690174371616| Your GCC version: 4.5
Okt 31 09:22:23.165: app-139690174371616| Your GCC version: 4.5
Okt 31 09:22:23.177: app-139690174371616| Your GCC version: 4.5
Okt 31 09:22:23.192: app-139690174371616| Your GCC version: 4.5
Okt 31 09:22:23.203: app-139690174371616| Your GCC version: 4.5
Okt 31 09:22:23.238: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.240: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.243: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.245: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.247: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.268: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.271: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.273: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.275: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.278: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.284: app-139690174371616| Your GCC version: 4.5
Okt 31 09:22:23.296: app-139690174371616| Your GCC version: 4.5
Okt 31 09:22:23.333: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.335: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.338: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.340: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.342: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.349: app-139690174371616| Your GCC version: 4.5
Okt 31 09:22:23.362: app-139690174371616| Your GCC version: 4.5
Okt 31 09:22:23.415: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.417: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.419: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.422: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.424: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.662: app-139690174371616| Trying to find a suitable PBM set for kernel 2.6.35.6-48.fc14.x86_64.
Okt 31 09:22:23.663: app-139690174371616| Building module vmmon.
Okt 31 09:22:23.663: app-139690174371616| Extracting the sources of the vmmon module.
Okt 31 09:22:23.678: app-139690174371616| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.35.6-48.fc14.x86_64/build/include CC=/usr/lib64/ccache/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.5.1
Okt 31 09:22:24.864: app-139690174371616| Failed to compile module vmmon!

[leigh123linux]

You need to patch it. (the patch originally came from the vmware forum but needed modifying to work)
Download both files to the same directory and run the script.

[TheBigRed]

thanks for your quick respone leigh123linux.

i have to run the following bash script, and this do the trick.
http://www.sputnick-area.net/scripts/vmware7.1.1-patch-kernel-2.6.35.bash
vmware-modconfig --console --install-all

[poncho68]

i have to run the following bash script, and this do the trick.
http://www.sputnick-area.net/scripts/vmware7.1.1-patch-kernel-2.6.35.bash

I think your script breaks the lsmod command on fedora because it links (with the -f option) /bin/lsmod to /sbin/lsmod but /bin/lsmod doesn't exist.

ln 2>/dev/null -sf /bin/lsmod /sbin/lsmod

[TheBigRed]

I think your script breaks the lsmod command on fedora because it links (with the -f option) /bin/lsmod to /sbin/lsmod but /bin/lsmod doesn't exist.

ln 2>/dev/null -sf /bin/lsmod /sbin/lsmod

it's not my script, but indeed the command is wrong.

this is better:
ln 2>/dev/null -sf /sbin/lsmod /bin/lsmod

[wangmaster]

It seems like getting rid of that line would be better. I wonder if that was written for some specific linux distro where lsmod was placed in /bin causing problems with some other scripts.

Looking at ubuntu, it looks like lsmod resides in /bin and /sbin/lsmod is a symlink to it.

Wouldn't surprise me if some other linux distro doesn't have /sbin/lsmod as a symlink and whoever wrote this script was using that distro.