Once again, hello Folks! Here is the workaround: Become root: 1. cd /lib/modules/<kernel name>/misc 2. for each module in directory, modprobe <module> 3. BINGO! Everything works. Again, I suspect a VMware QA failure. Heaven help a newbie trying to set up 6.5 under open SUSE. Over the next few days, I'll try and summarize this into a tidy usable solution. Thanks all, Daniel Daniel Feiglin wrote:
Hello Folks!
Here are the results of a VMware Workstation 6.5 install under 10.3:
1. I removed the 6.0.2 RPM using yast, but ensured that my settings in /etc/vmware were preserved. 2. The supplied 6.5 RPM package is faulty. It simply copies the bundle to /var/cache/vmware - well, sometimes. (I did several trials for reasons which will become apparent below.) 3. To actually install anything, you need to become root, cd to /var/cache/vmware and sh <the bundle name> with or without switches. Taking the simple default of nothing, it installs without (apparent) mishap. 4. On my system, I need to change the default Bridged network to always use eth1. Win XP comes up - much faster than under 6.0.2, and everything works as expected - net work assignments, internet , the works.
Here comes the rub:
1. Unlike 6.0.2, I don't see the virtual vmnetN devices under ifconfig. Is that correct? 2. The installation does not survive a reboot. After rebooting I can start the VMware Workstation, but I can't start the XP client. I get a spate of "/dev/vmmon" unavailable error messages. 3. None of the virtual vmnetN devices are loaded during reboot, as happened under 6.0.2, however vmmon and friends show up in modules.dep, so they are around somewhere.
Nowhere during the install was I asked to recompile support modules like 6.0.2, nor is it clear how you can force such recompilation, or even whether it in necessary.
uname -all output: Linux danny 2.6.22.18-0.2-bigsmp #1 SMP 2008-06-09 13:53:20 +0200 i686 i686 i386 GNU/Linux
There is evidently something very basic wrong with all this.
BTW, I have also posted a similar query to the relevant VMware discussion group, since it is not clear whether this is issue belongs to openSUSE or VMware.
Regards,
Daniel