I am currently running the 64-bit version of Slackware and while this is probably VMWare's crappy installer at work, I am hoping someone here has gotten this to work. With the stock 2.6.33.4 kernel my USB 3.0 ports do not perform as well as they should so I decided to move onto a new kernel, 2.6.34 and with that performance has been fixed. I have not had much time to check out anything else because VMWare needed my attention, as it usually does when you change kernels. Letting the installer attempt to create the necessary modules for the 2.6.34 kernel fails when locating the kernel headers. Within the graphical installer I have the option to point to a location where the kernel headers are, but no matter what I choose it would not proceed. I have tried running the installer in a console and completely removing VMWare and installing it again, but both end up with the same effect of not being able to create the necessary modules. Anyone with this combination able to get this working?

I have the 2.6.34 source located in /usr/custom/src and have compiled and installed it from there if it makes any difference.

Have you seen this? I haven't tried it on 2.6.34, but it does work on the stock 2.6.33 kernel.

Thing is, this patch gets it so the VMWare modules compile properly and is for VMWare Server. I remember patches in the past would help with getting the modules to compile properly, however I cannot even get VMWare to locate the proper headers needed to compile. The stock kernel for me did not require any patching to get working properly...

At some point with the previous kernel did you ever mess with creating links to the new locations for autoconf.h and utsrelease.h? In one of the more recent releases they were moved from /usr/src/linux/include/linux to /usr/src/linux/include/generated and that caused problems for VMware. If you create links in /usr/src/linux/include/linux that point to the new location of these files, that may solve the issue. You also might have to create a link to version.h as well.

Hrmm, the previous kernel was the stock kernel and other than switching from huge to generic, I have not messed with anything as root with the occasion of installing a package here and there. For some reason your mention of the change in location of /usr/src/linux/include/linux rings a bell... like I have done it in the past, which may be the case as this particular install of Slackware64 is new and I have had used a previous version of Slackware before. Unfortunately I do not have access to my machine at the moment, but I am looking forward to getting home to try this out! I have a feeling this will be it and can mark this thread as solved... we shall see!

Ok, this was a little interesting. Yesterday when I attempted to start VMWare Workstation, a GUI would pop up telling me I needed to compile the kernel modules and then it would ask me to log in as root. After doing so it would complain about missing kernel headers for 2.6.34 and no matter what I put in it would not go any further. I remember pressing one of the buttons on the GUI, the "Refresh" button, and it would show nothing. Just now I decided to try that button again and this time it pointed to the /lib/modules/2.6.34/ and from there it proceeded to compile the necessary modules. Upon finishing I started VMWare Workstation again, but this time it gave a different message saying some kernel modules were missing and needed to be created. At this point I went to a console and issued 'vmware-modconfig --console --install-all' where it recompiled without a hitch and now I am back in business!