Can't remove VMware modules

[OralDeckard]

I tried modprobe and was told that modprobe was a command not found :O

[root@Debbie debbie]# modprobe -v -r -i vmxnet
bash: modprobe: command not found
[root@Debbie debbie]#

I got the syntax from the manpage. What is the correct way to do it ?

[scottro]

Until F10, /usr/sbin and /sbin weren't in any user's path but root. I believe they're now in root's path as well though in F10.

When you get command not found, you can always try

whereis <command>

In this case, it's in /sbin, so if you try /sbin/modprobe you should be good.

http://home.roadrunner.com/~computer...su/rhpath.html

[OralDeckard]

Thank you Scott. Here is what I have now:

[root@Debbie debbie]# cd /sbin
[root@Debbie sbin]# modprobe -v -r -i vmxnet
bash: modprobe: command not found
[root@Debbie sbin]# whereis modprobe
modprobe: /sbin/modprobe /etc/modprobe.conf~ /etc/modprobe.d /etc/modprobe.conf /usr/share/man/man8/modprobe.8.gz
[root@Debbie sbin]# modprobe -v -r -i vmxnet
bash: modprobe: command not found
[root@Debbie sbin]#

And its my wife's F8.

[OralDeckard]

Uh, let me try /usr/sbin

[OralDeckard]

Here is what I got from /usr/sbin:

[root@Debbie sbin]# cd /usr/sbin
[root@Debbie sbin]# modprobe -v -r -i vmxnet
bash: modprobe: command not found
[root@Debbie sbin]#

[OralDeckard]

Whereis said it was in /sbin, so I went back there and listed:

[root@Debbie sbin]# cd /sbin
[root@Debbie sbin]# ls modprobe
modprobe
[root@Debbie sbin]#

[OralDeckard]

Whoah, I found it.

It's not enough to cd to /sbin, I have to run /sbin/modprobe even if I'm already in that folder :O

[OralDeckard]

Now it no longer says command not found, but it is not having any success at removing them.
Here is my problem:

[root@Debbie bin]# vmware-config.pl
The following VMware kernel modules have been found on your system that were
not installed by the VMware Installer.  Please remove them then run this
installer again.

vmxnet
vmci
vmmemctl
vmhgfs
vmblock

Execution aborted.

And here are the results:

[root@Debbie sbin]# /sbin/modprobe -v -r -i vmxnet
[root@Debbie sbin]# /sbin/modprobe -v -r -i cmci
FATAL: Module cmci not found.
[root@Debbie sbin]# /sbin/modprobe -v -r -i vmmemctl
rmmod /lib/modules/2.6.26.6-49.fc8/extra/open-vm-tools/vmmemctl.ko
[root@Debbie sbin]# /sbin/modprobe -v -r -i v,jgfs
FATAL: Module v,jgfs not found.
[root@Debbie sbin]# /sbin/modprobe -v -r -i vmjgfs
FATAL: Module vmjgfs not found.
[root@Debbie sbin]# /sbin/modprobe -v -r -i vmblock
FATAL: Module vmblock is in use.
[root@Debbie sbin]#

[scottro]

Ok, well you figured out the /sbin/modprobe part. Actually, it might work if you're in /sbin and do ./modprobe, but the canonical way is to /sbin/modprobe, or do su - to root, as explained in the link earlier.
Now, the other problem.

This is one where I'm reluctant to give advice long distance, because I could easily be wrong.
I'm taking the liberty of renaming the thread so that perhaps someone more familiar with the situation can help.
You could try finding the modules and manually removing them. It sounds like you installed VMware from various sources, for example, once from source and once from rpm.

You could do something like
updatedb

This will update your search database.

Then you can do locate vmnet and the others, and try to manually remove them. However, that seems a bit dangerous, which is why I'm renaming your thread.

[OralDeckard]

Thank you Scott. Renaming the thread is the correct thing to do since it has turned out to be not a generic removal of modules but something particular to VMware.

Actually what happened is I decided to upgrade my wife's VMware Player to the latest version, 2.5, and it didn't work. I first tried with the RPM, and found that there was no longer any /usr/bin/vmware-config.pl. It seems it was supposed to do its configuration when I ran it. But it couldn't. So I uninstalled it and tried again with something called "The Bundle," which is simply the RPM in an executable .bin wrapper. That wouldn't work either, so in desperation to go back to what worked I decided to uninstall and reinstall version 2.0.5.

Well, 2.0.5 installed, but during the running of /usr/binvmware-config.pl it complained about the modules installed by the future version of the player.

So I'm in the dawg haus now. My wife's Windows is gone, and when Momma ain't happy, ain't nobody happy.