Some time ago vmware-config.pl stop (re)compiling kernel modules. Option --compile won't help too. I've found lines 8495 "configure_mon();" and 8498 "build_vmnet();" must be uncommented to return to previous behaviour. Why these lines was commented? How to force module recompilation without patching vmware-config.pl?
Would be nice if you actually told us about which of the tons of vmware ebuilds and which version are you talking about here...
At least that's true for two latest stable x86 versions: app-emulation/vmware-workstation-5.5.1.19175-r4 app-emulation/vmware-workstation-5.5.1.19175-r7 I notive this issue some time ago, but decide to wait for next version because it looks like 100% 'typo' bug, and such bugs usually quickly found and fixed. Today I've updated to -r7 and found nothing was changed, so I decide to post bugreport.
Eh, vmware-modules is a separate ebuild and vmware-* depends on it. We don't use the interactive vmware-config.pl script for this.
INVALID, re-emerge app-emulation/vmware-modules.
(In reply to comment #4) > INVALID, re-emerge app-emulation/vmware-modules. > I've done that, but no joy. Is there a version skew or something? See: http://forums.gentoo.org/viewtopic-p-3682891.html#3682891 I can't find a correct sequence of operations that allow VmWare to be started now. vmware-config can't start vmware and never seems to think the config gets done. Something is wrong with these ebuilds.
(In reply to comment #5) > Something is wrong with these ebuilds. Nope, my bad! Had a kernel mixup! Oops! The latest ebuilds seem to work fine.