Jonathan Ervine wrote: >> Could be, because after a reboot -yes you are reading right :-) - I >> could run the vmware-config.pl ok >> > > OK - good to know that the script itself is now working as expected. > > Yes nice to know. > After running the vmware-config.pl script, did it build the networking module > correctly? (vmnet.ko) The script should build vmnet.ko and then make sure it > is loaded. The VMware daemon should also be automatically started by the > script as well. Try running /etc/init.d/vmware start as root to make sure > this is running. Also does lsmod | grep vmnet show that vmnet.ko is listed? > If not, maybe modprobe vmnet might help (but this shouldn't be necessary). > > As regards the comment about using the tarball for VMware - you can do this, > but I've never had any problems with the RPM that couldn't be fixed with the > any-any patch. My own opinion is that the RPM install is the easiest way to > run VMware on RPM based distributions. > > Here's the result, and this is nothing to yell hurrah for :-)
# locate vmnet.ko /lib/modules/2.6.18.8-0.3-default/misc/vmnet.ko lajka3:~ # /etc/init.d/vmware start Starting VMware services: Virtual machine monitor failed Virtual ethernet failed Bridged networking on /dev/vmnet0 failed Host-only networking on /dev/vmnet1 (background) done Host-only networking on /dev/vmnet8 (background) done NAT service on /dev/vmnet8 failed lajka3:~ # lsmod | grep vmnet vmnet 45484 12 lajka3:~ # modprobe vmnet FATAL: Module vmnet not found. Then Jon, what's the next step now ? > Jon > -- Med venlig hilsen / Best regards Erik Jakobsen [EMAIL PROTECTED] openSuSE 10.2 (i586) -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
