Erwin Lam wrote:
On Wednesday 22 August 2007, Richard Creighton wrote:
Erwin Lam wrote:
On Wednesday 22 August 2007, Andrei Verovski (aka MacGuru) wrote:
Hi !
I have SuSE 10.2 and:
kernel-default-2.6.22.2-ccj52 VMware-player-2.0.0-45731.i386
+ kernel sources and kernel syms 2.6.22.2-ccj52 installed.
For unknown reason compilation of vmware kernel modules fails:
<snip>
Unable to build the vmnet module.
Compilation of the VMware module failed because of changes in the
Linux
kernel, i.e. your kernel is to new and you should fallback to the latest 2.6.18 kernel.
Please, check the VMware forum for a discussion of these compilation problems. IIRC, the forum also contains some links to patches.
Regressing to 2.6.18 is not a viable option as 2.6.22 solves some
issues
with new motherboard hardware.
The OP did not say he needed a bleeding edge kernel because of new hardware. He also did not say that a fallback of the kernel was not an option.
The right solution is for VMware to update their product or lose the ability to have SUSE customers in the future. In the past, they have been responsive and I suspect they will be so in this case also.
I agree, however, don't hold your breath:-)
Let me clarify my previous post...I didn't say the poster I quoted had to have a bleeding edge kernel, I'm saying *I* need to have a bleeding edge kernel and right now the only way I can run 10.3 and VMWare is under 10.2 in a virtual machine running 10.3....it should be the other way around :( I have a new ASUS motherboard with 2.45 TB of raid5 hardware disk drives and running an AMD 5000+ Dual cpu and the new kernel solves several problems so I don't really want to go backward. I want VMWare to move forward. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org