Hi there!!

Im trying to put VMware-workstation-4.5.1 to work but im facing a little problem...
I've installed it (installed fine) and the vmmon module (the source of trouble) sucefully installed also by the instalation script

.....
Trying to find a suitable vmmon module for your running kernel.
The module up-2.4.21-013mdk-9.1 loads perfectly in the running kernel.
.....

Then i start the program; it allows me to create the desired virtual machine (in my case win98 )but when im going to power it up it gives me the following message

Could not open /dev/vmmon: No such file or directory.
Please make sure the kernel module 'vmmon' is loaded.

and after that anohter error

Failed to initialize monitor device.


After that i checked the modules loaded :
cat /proc/modules
giving the following result:
vmnet 24840 4
vmmon 41260 0 (unused)

I've also checked for the device /dev/vmmon but it doesnt exist althoug this two related to vmware exist
vmnet0 vmnet8


In my ignorance i've thinked that the module could be bad compilled (is it possible? )
and so i went to
/usr/lib/vmware/modules/source
untared the existing vmmon.tar compiled it and then moved the resulting
vmmon-xxx-2.4.21-0.13mdk to /lib/modules/2.4.21-0.13mdk/misc
and renamed it to vmmon .

I started again vmware but it keeps giving the same error.


From what i've seen in others post the problem is related to compilling the vmmon module wich doesn't seem to be my problem...

How can i solve this prob ??
Thanks in advance for the time spent.

Hey sandman etc ive got a problem with rox session ive installed all the programs it wanted but now im stuck it asks for dbus(python2.3-dbus) but i installed dbus so im stuck once again like all good linux problems they can be solved but i need your helps please someone help!

This may not fix your problem, but I came here looking for answers to the same problem you had. My circumstance was a little different, in that this system *was* working at one point, but nobody could get it started--same error as what you describe.

I reran the vmware-config.pl script, and tried again--it worked!

Dumb fix, and probably not guaranteed to work, but it did the trick for me!

Cheers!

sudo modprobe vmmon

This solved my problem. Thanks so much for posting.

I also had this problem.

My problem was based in the fact I had updated the kernel and therefore it didn't have the modules installed in it (something like that?!).

commands:
cd /etc/vmware
cat config

I then read where the vmware program was stored.

commands:
cd /usr/bin
./vmware

When I ran it from the command line, it scanned the kernel (?) and realised the kernel needed the modules ( or hooks?).
It asked for the admin password, then downloaded and installed the modules for the vm and the kernel.
Done.

I had another vm window (not working) open before I did this. It asked to take ownership, I clicked Cancel (no).
I then opened up the vm again, and it worked.

Note: Was on Ubuntu.

THAT was the issue. in fact, after vmmon, it gave me an error on module vmci and finally ran. Thanks again