On Wed, 2008-10-22 at 09:59 +0200, Dominique Leuenberger wrote:
> So a little bit better... just yet: /etc/init.d/vmware start fails on
> loading all of the modules. It seems not to be happy with this setup
> yet.

Just a follow up on this:
I had to modify the script /etc/init.d/vmware;

the change was like this:
vmwareLoadModule() {
   /sbin/insmod -s -f "/lib/modules/`uname
-r`/kernel/drivers/misc/$1.ko" || exit 1
   return 0
}

The line with insmod did not contain kernel/drivers/misc, but only misc.
Thus it failed. With this change now applied, vmware seems to start up
finally and machines seem to boot including network access.

Why not simply use "/sbin/modprobe $1" There? This would take care of it
all in my opinion.

Wohoo ;)

Dominique


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
open-vm-tools-devel mailing list
open-vm-tools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel

Reply via email to