I'm trying to install vmware tools on a slackware 13 guest.

Instalation goes without problems but when running the configuration script there is a problem. After compiling the required modules (no problems) the configuration freezes after testing X.

The last message is "X is running fine with the new config file.".

However, no config file (xorg.conf?) is created and it simply freezes.

I waited over an hour and nothing. I tryed to see what is happening with "ps" and it showed "mkinitrd" is running.

What does it mean? Anyone had a similar problem? What should I try?

I run Vmware version 1.0.7 build-108231 and have never installed Vmwaretools. I have just tried it on a Slackware 13 guest and it all worked OK (I had to create a directory /etc/pam.d to keep the scipt happy). I can now run the VM with a proper screen display rather than a miniature one. To be honest I mostly run VirtualBox for VM's and so wasn't even aware of Vmwaretools till I read this post ! Sorry I can't offer any wise advice as I am no expert with Vmware but just to let you know - it works for me.

In a different VT killall mkinitrd will allow the process to complete. I haven't bothered to look at exactly what the script is doing, but it is calling mkinitrd -h and just hangs. The next time I need to do a fresh Slackware install in VMware I'll take a look.

If you are using the generic kernel or any kernel which requires an initrd, be sure to rebuild it yourself. Vmware's install script nukes the currently installed one.

About the xorg.conf, it's optional with newer versions of Xorg. Without an xorg.conf, the mouse switching and graphics appear to work well. Or at least I can get a 1650x1080 FB console and same resolution in Xorg, unity works, clipboard sharing works ....
If you want to create and edit your own xorg.conf, run Xorg -configure to create an auto-probed one, edit, then copy over to /etc/X11/xorg.conf.

2 members found this post helpful.

Thanks for your help disturbed1.

I killed mkinitrd and the script seems to end up with no complaints. However, mouse capture/release had some problems in fullscreen. I gave up and tried Slackware on VirtualBox. It was love at first sight. After half an hour I decided to switch to VirtualBox. Everything works fine and integration with Windows has no problem at all. The hell with Vmware Workstation! VirtualBox is better and for free!

I'm using the Free VMware player 3.0. The Player has changed in this version, allowing you to create VMs and gives you the VMware tools as well. Much unlike the previous overly crippled versions.

Hopefully VirtualBox treats you better on Windows than it has myself in Linux. I have a love/hate relationship with VirtualBox.

Install vmware tools as usual but don't run vmware-config-tools.pl

change line 5613
from:
if (not open(FILE, $binary. " -h 2>&1 |")) {
to:
if (not open(FILE, $binary. " --help 2>&1 |")) {


change line 5614 (not that it gets here, another vmware bug)
from:
error("Unable to run 'mkinitrd -h.'\n");
to:
error("Unable to run 'mkinitrd --help.'\n");


mark