David Krider wrote:
I installed the VMware package that comes with 8.2. (I have an existing key to use.) In order to run vmware-config.pl, I need kernel sources. So I used YaST to install them. However, it would appear that the kernel sources that I can install are the ones for the standard kernel, and I'm running the "2.4.20-64GB-SMP" kernel.
VMware doesn't like the "PAE" enabled kernels. Since it's a performance hit (albeit slight), I don't understand why they make it the default. How many copies of SuSE are being used on machines with more than 4 GB? My bet is that anyone doing that ought to be able to install a PAE enabled kernel if they want it. Anyway. I had to remove k_smp in favor of k_psmp. I also installed the kernel sources (the ONLY kernel sources). I had been thinking that the "-XX" in 2.4.20-XX was the source of the confusion, as the k_smp package is 2.4.20-39 and the kernel-source is 2.4.20SuSE-30. Apparently, the only thing that matters is the part down to the point rev, i.e. 2.4.20. What `vmware-config.pl' needed to see was whatever is produced by the following. cd /usr/src/linux make cloneconfig make dep I never knew about the "cloneconfig" make option. It apparently builds a .config file based off the running kernel. After this sequence, I was able to get vmware-config.pl to run, even though it complained about A LOT of things. VMware has booted my old VM, and everything seems to be working. Note that this VM was built using VMware 3.2, not 3.1.1, which is what ships in SuSE 8.2. It's nice to see forward compatibility for a change. I still don't know about getting an Athlon-optimized SMP kernel. If it's true that SuSE doesn't have one in the distro, then this is a HUGE advantage for Red Hat... I *HATE* compiling my own kernels. This answer brought to you by a combination of about 10 web pages. What a mess. Why do I do this to myself? Regards, dk