Fedora 8 (kernel 2.6.24.3-34.fc8) vs WMware Workstation 5.5.6 build-80404 ?

[CassiusVinicius]

Hello,

I'm trying to install WMware Tools on Fedora with no success.

How to get it work on Fedora 8, please?

1. uname -srvmpio

Linux 2.6.24.3-34.fc8 #1 SMP Wed Mar 12 18:17:20 EDT 2008 i686 i686 i386 GNU/Linux

# vmware-config-tools.pl

Stopping VMware Tools services in the virtual machine:
   Guest operating system daemon:                          [  OK  ]
Trying to find a suitable vmhgfs module for your running kernel.

None of the pre-built vmhgfs modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmhgfs module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.24.3-34.fc8/build/include]

Extracting the sources of the vmhgfs module.

Building the vmhgfs module.

Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-config8/vmhgfs-only'
make -C /lib/modules/2.6.24.3-34.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entrando no diretório `/usr/src/kernels/2.6.24.3-34.fc8-i686'
  CC [M]  /tmp/vmware-config8/vmhgfs-only/cpName.o
In file included from include/linux/string.h:11,
                 from /tmp/vmware-config8/vmhgfs-only/cpName.h:18,
                 from /tmp/vmware-config8/vmhgfs-only/cpName.c:18:
include/linux/types.h:40: error: conflicting types for 'uintptr_t'
/tmp/vmware-config8/vmhgfs-only/vm_basic_types.h:160: error: previous declaration of 'uintptr_t' was here
make[2]: ** [/tmp/vmware-config8/vmhgfs-only/cpName.o] Erro 1
make[1]: ** [_module_/tmp/vmware-config8/vmhgfs-only] Erro 2
make[1]: Saindo do diretório `/usr/src/kernels/2.6.24.3-34.fc8-i686'
make: ** [http://vmhgfs.ko|http://vmhgfs.ko] Erro 2
make: Saindo do diretório `/tmp/vmware-config8/vmhgfs-only'
Unable to build the vmhgfs module.

The filesystem driver (vmhgfs module) is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
independently of this feature.
If you wish to have the shared folders feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.
These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]

pcnet32                31941  0
Unloading pcnet32 module

Trying to find a suitable vmxnet module for your running kernel.

None of the pre-built vmxnet modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmxnet module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmxnet module.

Building the vmxnet module.

Using 2.6.x kernel build system.
make: Entrando no diretório `/tmp/vmware-config9/vmxnet-only'
make -C /lib/modules/2.6.24.3-34.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entrando no diretório `/usr/src/kernels/2.6.24.3-34.fc8-i686'
  CC [M]  /tmp/vmware-config9/vmxnet-only/vmxnet.o
In file included from /tmp/vmware-config9/vmxnet-only/vmxnet.c:35:
/tmp/vmware-config9/vmxnet-only/vm_basic_types.h:160: error: conflicting types for 'uintptr_t'
include/linux/types.h:40: error: previous declaration of 'uintptr_t' was here
/tmp/vmware-config9/vmxnet-only/vmxnet.c: In function 'vmxnet_probe_device':
/tmp/vmware-config9/vmxnet-only/vmxnet.c:476: error: implicit declaration of function 'SET_MODULE_OWNER'
/tmp/vmware-config9/vmxnet-only/vmxnet.c: In function 'vmxnet_open':
/tmp/vmware-config9/vmxnet-only/vmxnet.c:674: error: 'SA_SHIRQ' undeclared (first use in this function)
/tmp/vmware-config9/vmxnet-only/vmxnet.c:674: error: (Each undeclared identifier is reported only once
/tmp/vmware-config9/vmxnet-only/vmxnet.c:674: error: for each function it appears in.)
/tmp/vmware-config9/vmxnet-only/vmxnet.c: In function 'vmxnet_netpoll':
/tmp/vmware-config9/vmxnet-only/vmxnet.c:1058: error: too many arguments to function 'vmxnet_interrupt'
make[2]: ** [/tmp/vmware-config9/vmxnet-only/vmxnet.o] Erro 1
make[1]: ** [_module_/tmp/vmware-config9/vmxnet-only] Erro 2
make[1]: Saindo do diretório `/usr/src/kernels/2.6.24.3-34.fc8-i686'
make: ** [http://vmxnet.ko|http://vmxnet.ko] Erro 2
make: Saindo do diretório `/tmp/vmware-config9/vmxnet-only'
Unable to build the vmxnet module.

The fast network device driver (vmxnet module) is used only for our fast
networking interface. The rest of the software provided by VMware Tools is
designed to work independently of this feature.
If you wish to have the fast network driver enabled, you can install the driver
by running vmware-config-tools.pl again after making sure that gcc, binutils,
make and the kernel sources for your running kernel are installed on your
machine. These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]



Detected X.org version 1.3.



No drivers for X.org version: 1.3.



Do you want to change your guest X resolution? (yes/no) [no]

Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                       [  OK  ]
   DMA setup:                                              [  OK  ]
   Guest operating system daemon:                          [  OK  ]

The configuration of VMware Tools 5.5.6 build-80404 for Linux for this running
kernel completed successfully.

You must restart your X session before any mouse or graphics changes take
effect.

You can now run VMware Tools by invoking the following command:
"/usr/bin/vmware-toolbox" during an XFree86 session.

Enjoy,

--the VMware teamrnel completed successfully.

Thanks,cviniciusm.

[PabloCardoso]

CassiusVinicius,

Actually there's a problem between VMware Tools configuration script and the latest kernel available at this moment (2.6.24-16). I was having the exact same problem on my Ubuntu 8.04 running Kernel 2.6.24-16 and I was able to solve it by following Peter Cooper's post at

Maybe this could help you... Give it a try!