vmware troubles (4.5.2-8848)

pobudz · 2005-05-08 18:54:35

For some reason or another the installation goes smoothly until it tries building the vmnet module (vmmon works flawlessly...but vmnet?!) its using the same build path... same kernel (I only have the one 2.6.11-7.

If anyone has any suggestions or knows what I need to do let me know, I'm stumped.

Trying to find a suitable vmmon module for your running kernel.
None of the pre-built vmmon modules for VMware Workstation is suitable for your
running kernel. Do you want this program to try to build the vmmon 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.11.7-ARCH/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/2.6.11.7-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.11.7-ARCH'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config1/vmmon-only/linux/hostif.o
In file included from /tmp/vmware-config1/vmmon-only/linux/hostif.c:68:
/tmp/vmware-config1/vmmon-only/./include/pgtbl.h: In function `PgtblVa2PTELocked':
/tmp/vmware-config1/vmmon-only/./include/pgtbl.h:81: warning: passing arg 1 of `pmd_offset' from incompatible pointer type
CC [M] /tmp/vmware-config1/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config1/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/task.o
CC [M] /tmp/vmware-config1/vmmon-only/common/vmx86.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config1/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.11.7-ARCH'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
The file /lib/modules/2.6.11.7-ARCH/misc/vmmon.o that this program was about to
install already exists. Overwrite? [yes]
The module loads perfectly in the running kernel.
Extracting the sources of the vmnet module.
Building the vmnet module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmnet-only'
make -C /lib/modules/2.6.11.7-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.11.7-ARCH'
CC [M] /tmp/vmware-config1/vmnet-only/driver.o
CC [M] /tmp/vmware-config1/vmnet-only/hub.o
CC [M] /tmp/vmware-config1/vmnet-only/userif.o
In file included from /tmp/vmware-config1/vmnet-only/userif.c:45:
/tmp/vmware-config1/vmnet-only/pgtbl.h: In function `PgtblVa2PTELocked':
/tmp/vmware-config1/vmnet-only/pgtbl.h:81: warning: passing arg 1 of `pmd_offset' from incompatible pointer type
/tmp/vmware-config1/vmnet-only/userif.c: In function `VNetCopyDatagramToUser':
/tmp/vmware-config1/vmnet-only/userif.c:563: warning: implicit declaration of function `skb_copy_datagram'
CC [M] /tmp/vmware-config1/vmnet-only/netif.o
CC [M] /tmp/vmware-config1/vmnet-only/bridge.o
CC [M] /tmp/vmware-config1/vmnet-only/procfs.o
LD [M] /tmp/vmware-config1/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST
Warning: could not open /tmp/vmware-config1/vmnet-only/includeCheck.h: No such file or directory
CC /tmp/vmware-config1/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config1/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.11.7-ARCH'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config1/vmnet-only'
Unable to make a vmnet module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config1/vmnet.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
"http://www.vmware.com/support/reference … linux.html".
Execution aborted.

FUBAR · 2005-05-08 18:58:55

I bet you can fix this with the so-called "any-any" patch. Do a Google on "vmware any any patch", you should find a Czech FTP-site. Grab the latest version of the patch and patch your VMware. Then rerun the setup-script, it should work fine.

pobudz · 2005-05-08 19:23:05

heh.. thanks man

dunno what i'd do without forums...

FUBAR · 2005-05-08 19:34:22

I'm pretty sure you'll run into similar problems after a kernel upgrade so be sure to bookmark this page (or remember what you did ). It's possible you have to wait a while for the new any-any patch if you like to install the latest kernel as soon as possible.

Arch Linux

#1 2005-05-08 18:54:35

vmware troubles (4.5.2-8848)

#2 2005-05-08 18:58:55

Re: vmware troubles (4.5.2-8848)

#3 2005-05-08 19:23:05

Re: vmware troubles (4.5.2-8848)

#4 2005-05-08 19:34:22

Re: vmware troubles (4.5.2-8848)

Board footer