Just did an update of the kernel and everything went smoothly, as always. Have the nvidia driver directly from nvidia. Very reliable. But then I noticed that KNemo was showing my vmnet1 and vmnet8 icons greyed out. No problem, had forgotten to run the vmware-config.pl script. Ran it, was told the new kernel was compiled with gcc 3.4.3 and I have 3.4.2. Sure enough, after doing an update of the system, the new gcc-3.4.3 arrived. Well, tried to reconfigure vmware using the proper gcc, and I get this error: Extracting the sources of the vmmon module. Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config4/vmmon-only' make -C /lib/modules/2.6.11-1.14_FC3/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/lib/modules/2.6.11-1.14_FC3/build' CC [M] /tmp/vmware-config4/vmmon-only/linux/driver.o CC [M] /tmp/vmware-config4/vmmon-only/linux/hostif.o In file included from /tmp/vmware-config4/vmmon-only/linux/hostif.c:68: /tmp/vmware-config4/vmmon-only/./include/pgtbl.h: In function `PgtblVa2PTELocked': /tmp/vmware-config4/vmmon-only/./include/pgtbl.h:81: warning: passing arg 1 of `pmd_offset' from incompatible pointer type CC [M] /tmp/vmware-config4/vmmon-only/common/cpuid.o CC [M] /tmp/vmware-config4/vmmon-only/common/memtrack.o CC [M] /tmp/vmware-config4/vmmon-only/common/phystrack.o CC [M] /tmp/vmware-config4/vmmon-only/common/task.o CC [M] /tmp/vmware-config4/vmmon-only/common/vmx86.o LD [M] /tmp/vmware-config4/vmmon-only/vmmon.o Building modules, stage 2. MODPOST CC /tmp/vmware-config4/vmmon-only/vmmon.mod.o LD [M] /tmp/vmware-config4/vmmon-only/vmmon.ko make[1]: Leaving directory `/lib/modules/2.6.11-1.14_FC3/build' cp -f vmmon.ko ./../vmmon.o make: Leaving directory `/tmp/vmware-config4/vmmon-only' The module loads perfectly in the running kernel. This program previously created the file /dev/vmmon, and was about to remove it. Somebody else apparently did it already. Extracting the sources of the vmnet module. Building the vmnet module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config4/vmnet-only' make -C /lib/modules/2.6.11-1.14_FC3/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/lib/modules/2.6.11-1.14_FC3/build' CC [M] /tmp/vmware-config4/vmnet-only/driver.o CC [M] /tmp/vmware-config4/vmnet-only/hub.o CC [M] /tmp/vmware-config4/vmnet-only/userif.o In file included from /tmp/vmware-config4/vmnet-only/userif.c:45: /tmp/vmware-config4/vmnet-only/pgtbl.h: In function `PgtblVa2PTELocked': /tmp/vmware-config4/vmnet-only/pgtbl.h:81: warning: passing arg 1 of `pmd_offset' from incompatible pointer type /tmp/vmware-config4/vmnet-only/userif.c: In function `VNetCopyDatagramToUser': /tmp/vmware-config4/vmnet-only/userif.c:563: warning: implicit declaration of function `skb_copy_datagram' CC [M] /tmp/vmware-config4/vmnet-only/netif.o CC [M] /tmp/vmware-config4/vmnet-only/bridge.o CC [M] /tmp/vmware-config4/vmnet-only/procfs.o LD [M] /tmp/vmware-config4/vmnet-only/vmnet.o Building modules, stage 2. MODPOST Warning: could not open /tmp/vmware-config4/vmnet-only/includeCheck.h: Success *** Warning: "skb_copy_datagram" [/tmp/vmware-config4/vmnet-only/vmnet.ko] undefined! CC /tmp/vmware-config4/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-config4/vmnet-only/vmnet.ko make[1]: Leaving directory `/lib/modules/2.6.11-1.14_FC3/build' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-config4/vmnet-only' Unable to make a vmnet module that can be loaded in the running kernel: insmod: error inserting '/tmp/vmware-config4/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. Any ideas? The new kernel was compiled with a gcc that is not the one that has been released? So, where do I get the right gcc?
