[SOLVED] Slackware 14.1 on VMware Workstation guest : VMware Tools doesn't work
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
that means that you are using huge kernel, so that kernel panic thing shouldn't happen even after installing VMWare Tools, unless i missed something from your activities
I use a generic kernel, the problem can to come there ?
during installation of Slackware, did you use full installation or do you select your packages yourself?
if you use generic kernel, you must also make an initrd since the generic kernel only support ext2 file system in it. If you use other than ext2, you will have to make initrd that contains your filesystem inside it and update your lilo configuration.
during installation of Slackware, did you use full installation or do you select your packages yourself?
In package selection screen I selected packages and next step I chose full installation.
Quote:
if you use generic kernel, you must also make an initrd since the generic kernel only support ext2 file system in it. If you use other than ext2, you will have to make initrd that contains your filesystem inside it and update your lilo configuration.
@willysr : I rebuild an initrd after to install VMware Tools ?
But, if we use a huge kernel the installation of VMware Tools haven't need to make an initrd ?
In the installation of VMware Tools written modules in the kernel, this is why I have to rewrite it ?
huge kernels doesn't need initrd since all modules are built statically inside the kernel
You need to build initrd before rebooting your system.
Vmware tools doesn't really care whether you use huge/generic kernel, as long as the could find the relevant kernel source to build their modules
Your current problem is because you don't make a initrd for your generic kernel
I would suggest to do full installation again and start fresh
This time, use huge kernel first and when all is done, you can start planning to move on generic kernels
Perfect, thank you willysr for the explication, I go to try with huge kernel in a first time and second time try to rebuild initrd after the installation of VMware Tools on a fresh/full installation.
It works.
I just executed LILO after the installation of VMware Tools, reboot and generic kernel work very well.
I did not try with huge kernel yet but that should not to be a problem.
I deleted network and vmtoolsd.pid files for fixing the SSH connexions.
Works fine since host OS.
An alternative to the Red Hat targeted binary tools are the open source open-vm-tools. The userspace part of them works fine and the basic kernel support needed for VMware is already part of the vanilla kernel.
You could try the SlackBuild in the attached shell archive.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.