On 3/22/2009 at 19:43, Randall R Schulz
wrote: Hi, I'm sure I should know this, but I can't recall or find the answer...
After updating a kernel, what must be done to restore VMware functionality?
Randall, In a perfect world: nothing. In a VMware world: the kernel modules need to be recompiled. now the trick: - VMware actually should detect if the modules are there, and if not ask for the root password and compile them. most likely though, when you start VMware, it just tells you which modules are not loaded and at segfaults. In this case, you will need this script: --- START SCRIPT --- #/bin/sh cd /usr/lib/vmware/modules/source for a in *.tar ; do tar xf $a; done pushd vmblock-only; make; popd pushd vmci-only; make; popd pushd vmmon-only; make; popd pushd vmnet-only; make; popd cp vmci-only/Module.symvers vsock-only/ pushd vsock-only; make; popd find -name *.ko -exec cp \ {} /lib/modules/$(uname -r)/kernel/drivers/misc/ \; depmod -aq --- END SCRIPT --- Sometimes I ended up also with the need to modify /etc/init.d/vmware. You would find a function vmwareLoadModule() I suggest to change it to: vmwareLoadModule() { /sbin/modprobe "$1" || exit 1 return 0 } then issue "/etc/init.d/vmware start" and you should be back in business. (that is, if you're using a kernel < 2.6.28! Otherwise it's getting really nasty with an additional patch to be applied to the modules.) Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org