On Fri August 1 2003 1:33 am, Jim Hamilton wrote:

hi

I have come across this problem on my SuSE 8.1 system.l. I have not got it fixed yet but can tell you its related to the latest SuSE kernel or kernel source. I have the following kernel installed:

k_deflt-2.4.19-329

matching kernel source should be

kernel-source-2.4.19.SuSE-308

with vmware 4.0.1 build 5289

With glibc-2.2.5-184 installed for tests on both kernels.

and this combination fails during the build of vmon (see below) but the module reports that it loads pefectly. The end result is that the VMware GUi starts but if you attempt to start a guest OS it will hang.

If I install the older kernel k_deflt-2.4.19-274 VMware 4.0 will work ok but I then break NFS between multilple SuSE 8.1 systems which affects other application systems I need.

any further suggestions would be most helpful.

------------------------------

Building the vmmon module.

make: Entering directory `/tmp/vmware-config0/vmmon-only' make[1]: Entering directory `/tmp/vmware-config0/vmmon-only' make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' ../linux/hostif.c: In function `HostIF_SemaphoreWait': ../linux/hostif.c:1818: warning: passing arg 1 of `poll_initwait' from incompatible pointer type ../linux/hostif.c:1835: warning: passing arg 1 of `poll_freewait' from incompatible pointer type make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' make[1]: Leaving directory `/tmp/vmware-config0/vmmon-only' make: Leaving directory `/tmp/vmware-config0/vmmon-only' The module loads perfectly in the running kernel.

Extracting the sources of the vmnet module.

Building the vmnet module.

make: Entering directory `/tmp/vmware-config0/vmnet-only' make: Leaving directory `/tmp/vmware-config0/vmnet-only' The module loads perfectly in the running kernel.

-- Jim Hamilton Perth, Australia

Jim, I pass on this quote from a response I received to a similar question maybe a week and a half ago, maybe it will assist you. It handled stuff for me trying to get VMWare to recognize my athlon kernel: <quote> cp /boot/vmlinuz.version.h /usr/src/linux/include/linux/version.h cp /boot/vmlinuz.autoconf.h /usr/src/linux/include/linux/autoconf.h Then run the vmware config.pl to compile. All you are doing is getting the header names to match whats running... _____________________________________ John Andersen <endquote> Richard