FC5 problems, VMware Tools, No mouse

davidmcconnell · #1 26th March 2006, 05:12 AM

Having a couple FC5 problems as follows:

FC5 installed without any problems on VMware server. I am not able to get VMware tools to install. I've installed 'kernel-devel' and 'gcc' and applied the 'vmware-tools-any...' patch. Of course vmware-config-tools.pl is unable to find a suitable vmhgfs module for my kernel, so allowing the script to try to build one give the following output:

Code:

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? [/usr/src/kernels/2.6.15-1.2054_FC5-i586/include]

Extracting the sources of the vmhgfs module.

Building the vmhgfs module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config4/vmhgfs-only'
make -C /usr/src/kernels/2.6.15-1.2054_FC5-i586/include/.. SUBDIRS=$PWD SRCROOT=
$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.15-1.2054_FC5-i586'
  CC [M]  /tmp/vmware-config4/vmhgfs-only/cpName.o
In file included from /tmp/vmware-config4/vmhgfs-only/vm_assert.h:29,
                 from /tmp/vmware-config4/vmhgfs-only/cpName.c:17:
/tmp/vmware-config4/vmhgfs-only/vm_basic_defs.h:208:5: warning: "_MSC_VER" is no
t defined
  CC [M]  /tmp/vmware-config4/vmhgfs-only/cpNameLinux.o
In file included from /tmp/vmware-config4/vmhgfs-only/vm_assert.h:29,
                 from /tmp/vmware-config4/vmhgfs-only/cpNameLinux.c:13:
/tmp/vmware-config4/vmhgfs-only/vm_basic_defs.h:208:5: warning: "_MSC_VER" is no
t defined
  CC [M]  /tmp/vmware-config4/vmhgfs-only/dev.o
In file included from /tmp/vmware-config4/vmhgfs-only/vm_assert.h:29,
                 from /tmp/vmware-config4/vmhgfs-only/main.h:27,
                 from /tmp/vmware-config4/vmhgfs-only/dev.c:19:
/tmp/vmware-config4/vmhgfs-only/vm_basic_defs.h:208:5: warning: "_MSC_VER" is no
t defined
  CC [M]  /tmp/vmware-config4/vmhgfs-only/driver.o
In file included from /tmp/vmware-config4/vmhgfs-only/vm_assert.h:29,
                 from /tmp/vmware-config4/vmhgfs-only/main.h:27,
                 from /tmp/vmware-config4/vmhgfs-only/driver.c:15:
/tmp/vmware-config4/vmhgfs-only/vm_basic_defs.h:208:5: warning: "_MSC_VER" is no
t defined
/tmp/vmware-config4/vmhgfs-only/driver.c:3962: warning: initialization from inco
mpatible pointer type
  CC [M]  /tmp/vmware-config4/vmhgfs-only/hgfsUtil.o
In file included from /tmp/vmware-config4/vmhgfs-only/vmware.h:24,
                 from /tmp/vmware-config4/vmhgfs-only/hgfsUtil.c:11:
/tmp/vmware-config4/vmhgfs-only/vm_basic_defs.h:208:5: warning: "_MSC_VER" is no
t defined
In file included from /tmp/vmware-config4/vmhgfs-only/hgfsUtil.c:12:
/tmp/vmware-config4/vmhgfs-only/vm_basic_asm.h:48:5: warning: "_MSC_VER" is not
defined
  CC [M]  /tmp/vmware-config4/vmhgfs-only/main.o
In file included from /tmp/vmware-config4/vmhgfs-only/vm_assert.h:29,
                 from /tmp/vmware-config4/vmhgfs-only/main.h:27,
                 from /tmp/vmware-config4/vmhgfs-only/main.c:26:
/tmp/vmware-config4/vmhgfs-only/vm_basic_defs.h:208:5: warning: "_MSC_VER" is no
t defined
  CC [M]  /tmp/vmware-config4/vmhgfs-only/staticEscape.o
In file included from /tmp/vmware-config4/vmhgfs-only/vm_assert.h:29,
                 from /tmp/vmware-config4/vmhgfs-only/staticEscape.c:15:
/tmp/vmware-config4/vmhgfs-only/vm_basic_defs.h:208:5: warning: "_MSC_VER" is no
t defined
  LD [M]  /tmp/vmware-config4/vmhgfs-only/vmhgfs.o
  Building modules, stage 2.
  MODPOST
  CC      /tmp/vmware-config4/vmhgfs-only/vmhgfs.mod.o
  LD [M]  /tmp/vmware-config4/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.15-1.2054_FC5-i586'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-config4/vmhgfs-only'
Unable to make a vmhgfs module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config4/vmhgfs.o': -1 Invalid module format
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.

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 ]

Anyone have any suggestions for getting vmtools running?

Thanks,
David McConnell

davidmcconnell · #2 26th March 2006, 09:29 PM

Ok, I fixed the module compile and insert problem. It seems that my kernel is using i686 architecture and when I did 'yum install kernel-devel', I got the i585 architecture development files. Anyway, I fixed that and now it compiles and inserts into the kernel without a problem.

I'm still having issues with the mouse displaying either directly on the vmware server, or using vmware server console from a remote workation. Does anyone have any ideas on this problem?

Thanks,
David