Results 1 to 3 of 3

Thread: VMWare Player won't configure.

  1. #1
    Join Date
    Aug 2008
    Location
    The Netherlands
    Posts
    8

    Default VMWare Player won't configure.

    This must be thread no. 500 about this subject but it seems there is no real definite solution to this really annoying problem.

    I can't seem to configure VMWare Player using config.pl. I've read over 3 solutions that were bound to work and none of them did.

    I've tried the VMBlock patch witch resulted in the same as using the any-any patch:
    Code:
    /usr/src/linux-2.6.25.11-0.1/include/asm-generic/bitops/fls64.h:6: error: static declaration of ‘fls64’ follows non-static declaration
    /usr/src/linux-2.6.25.11-0.1/include/linux/bitops.h:112: error: previous implicit declaration of ‘fls64’ was here
    make[4]: *** [/tmp/vmware-config3/vmmon-only/common/cpuid.o] Error 1
    make[3]: *** [_module_/tmp/vmware-config3/vmmon-only] Error 2
    make[2]: *** [sub-make] Error 2
    make[1]: *** [all] Error 2
    make[1]: Leaving directory `/usr/src/linux-2.6.25.11-0.1-obj/i386/default'
    make: *** [vmmon.ko] Error 2
    make: Leaving directory `/tmp/vmware-config3/vmmon-only'
    Unable to build the vmmon module.
    Now why the hell isn't Suse coming up with a normal patch to fix this, why does this have to be such a pain? This is the only distro where I've had such pain installing this. And YES I have got it to work on older Ubuntu version.

    Does anyone have a solution to this and can anyone tell me why this has to be such a pain?

    Using suse 11.0 and VMWare player 2.04-93057

  2. #2
    oguzhaslak NNTP User

    Default Re: VMWare Player won't configure.

    hi

    i'm having the same problem then apply the this patch
    you can get it from here
    http://download.rsbac.org/tmp/vmware...date117.tar.gz

    make sure
    + kernel-source
    + make
    + gcc
    + gcc++
    are installed

  3. #3

    Default Re: VMWare Player won't configure.

    You stated this :Using suse 11.0 and VMWare player 2.04-93057

    There's an upgrade for VMPlayer: 2.05 and the bug might be swatted.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •