Sorry to add to this issue more than one year after the last comment, but it looks like the same problem surface again.
It seems like the release process which produces a new vmware-player- kernel-modules-2.6.15.XX package each time a new linux- image-2.6.15-XX-686|k7 is released is broken. It worked fine with Breezy: For every kernel security update, a new vmware kernel module was also released -- as far as I could see. My current situation is that o vmplayer-2.6.15-28 works with linux-image-2.6.15-28 (player version is 2.6.15.10-11). o vmplayer-2.6.15-29 fails with linux-image-2.6.15-29 with "Version mismatch with vmmon module: expecting 137.0, got 138.0." (player version is 2.6.15.11-13). o vmplayer fails "Could not open /dev/vmmon" with linux-image-2.6.15-51 which is current at the time of my writing, without surprise, since there's no vmware-player-module-2.6.15-51. So I need to keep my 2.6.15-28 image installed *and* boot that each time I want to use vmware-player. -- no prebuilt modules for 2.6.15-25 and can't build with module-assistant https://bugs.launchpad.net/bugs/49924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
