new modules for linux-image-2.6.15-26-686

[Alan Porter]

On 7/12/2006, linux-image-686 was upgraded to linux-image-2.6.15-26-686, but vmware-player-kernel-modules is still at the old version, vmware-player-kernel-modules-2.6.15-25.

So after booting into the new version of the kernel, vmmon and vmnet do not load, and you can not run vmware-player.

[Jochen Becher (jochen-becher)]

I confirm this bug.

This seems to be a general problem with upgrades of the kernel; it is not the first time that the kernel was updated but the vmware kernel modules weren't. Some dependency should be added or process improvement should be defined to ensure that vmware modules are always kept in synv with kernel version.

[VMware Build Team (vmware-builds)]

I've spoken to dholback about this, and we're trying to work something out. As a side not, people can always use the source package and use module-assistant to build modules for kernels that aren't supported yet. I agree, this is lame, but it helps in the short term.

[Mario Vukelic (kreuzsakra)]

Except that m-a fails. I might miss something, never used m-a before.

I ran "sudo m-a prepare,clean,get,build vmware-player-kernel-source". It downloads the appropriate headers for 2.6.15-26 and the module source, and tries to build. Then fails with

"cannot read debian/control: No such file or directory". Will attach logfile.

[holgi (holger-tasch)]

I can confirm this, exactly the same happens on my system, with the exception that two lines in the output are as follows: 's/@@ABIVER@@/2.6.15-23/g', which is quite strange to me, because running kernel and kernel headers are all on 2.6.15-26. I don't understand the whole thing.

[Lukas Fittl (lfittl)]

This has been fixed: http://changelogs.ubuntu.com/changelogs/pool/multiverse/v/vmware-player-kernel-2.6.15/vmware-player-kernel-2.6.15_2.6.15.10-8/changelog