No kernel modules for the 2.6.22 kernel

[Robbert]

Binary package hint: vmware-player-kernel-modules

There are currently no vmware kernel modules for the 2.6.22 kernel. Therefore, vmware player isn't usable on Gutsy.

[Robbert (robbertkrebbers)]

I'm wondering or someone is working on this?

Or could someone tell me a way to work around this problem?

[hangy (hangy)]

Any news on this?

[exactt (giesbert)]

just take the .tar.gz from the vmware site. the installer compiles the modules for the running kernel normally without any problems...

just a work around but in case you need it...

[Robbert (robbertkrebbers)]

I've found a way to work around this issue which is more the Debian way:
* Download make-vmpkg from the Debian unstable repositories. (http://packages.debian.org/unstable/misc/vmware-package)
* Download vmware-any-any (http://knihovny.cvut.cz/ftp/pub/vmware/)
* Create a kernel source package from the any-any tar.gz with make-vmpkg (make-vmpkg [name of the tar.gz file you've downloaded].tar.gz)
* Install the source package (sudo dpkg -i [name of generated deb file].deb)
* Create a kernel binary package with module-assistant (sudo m-a auto-install vmware-any-any-kernel /usr/src/modules)

[Philipp Hack (philipp-hack)]

robbert, thanks for the workaround. No problem building and installing the module package. However, the resulting module seems to be incompatible with the vmware-player package. On startup I get the following error:

Version mismatch with vmmon module: expecting 138.0, got 161.0.
You have an incorrect version of the `vmmon' kernel module.
Try reinstalling VMware Player.

[Robbert (robbertkrebbers)]

I've also used make-vmpkg to make a package of the newest version of vmware player (version 2.0), but forgot to mention that in my previous comment.

That works like:
* Download version 2 of vmware player from http://www.vmware.com/download/player/
* Create a package with make-vmpkg (make-vmpkg [name of the file you've downloaded])
* Install the packages with sudo dpkg -i

[Pelládi Gábor (pelladigabor)]

If somebody packages vmware kernel modules for the Gutsy kernel, please do it for the 2.0 version. 1.0.2 is old.

[berg (berg-foss)]

I confirme this bug , and there is not kernel-modules yet

http://packages.ubuntu.com/cgi-bin//search_packages.pl?version=all&subword=1&exact=&arch=any&releases=all&case=insensitive&keywords=vmware&searchon=names

root@instavel-laptop:/home/myloginz# apt-get install vmware-player
Lendo lista de pacotes... Pronto
Construindo árvore de dependências
Reading state information... Pronto
Alguns pacotes não puderam ser instalados. Isso pode significar que
você solicitou uma situação impossível ou se você está usando a
distribuição instável, que alguns pacotes requeridos não foram
criados ainda ou foram tirados do Incoming.

Já que você solicitou uma única operação é bem provável que o pacote
esteja simplesmente não instalável e um relato de erro sobre esse
pacotes deve ser enviado.
A informação a seguir pode ajudar a resolver a situação:

Os pacotes a seguir têm dependências desencontradas:
  vmware-player: Depende: vmware-player-kernel-modules mas não vai ser instalado
E: Pacotes quebrados
root@instavel-laptop:/home/myloginz# apt-get install vmware-player vmware-player-kernel-modules
Lendo lista de pacotes... Pronto
Construindo árvore de dependências
Reading state information... Pronto
Alguns pacotes não puderam ser instalados. Isso pode significar que
você solicitou uma situação impossível ou se você está usando a
distribuição instável, que alguns pacotes requeridos não foram
criados ainda ou foram tirados do Incoming.
A informação a seguir pode ajudar a resolver a situação:

Os pacotes a seguir têm dependências desencontradas:
  vmware-player-kernel-modules: Depende: vmware-player-kernel-modules-2.6.20-15 mas não está instalável
E: Pacotes quebrados
root@instavel-laptop:/home/myloginz#

[Robbert (robbertkrebbers)]

This problem still exists, it would be very bad when Gutsy doesn't have vmware working when it's released. And there is a way to get it working, use Vmware 2 with the vmware-any-any modules.

[ouellettesr (koxxv)]

I have the same problem

[Thomas Zander (zander-kde)]

Can we expect this to be fixed before October starts? :)
I really need this...

[Thomas Novin (thomasn80)]

Robbert,

I've tried installing the latest vmware-player but I immediately got stumped. Since it's a lot of output, please see http://paste.ubuntu-nl.org/38683/ for details. I will try to continue later, after all the packages were created so maybe they are OK.

[Robbert (robbertkrebbers)]

When I made the packages with make-vmpkg I used version 2.0.0 of Vmware, because 2.0.1 wasn't released at that moment. I don't know whether the 2.0.1 packages you've just created work, but i guess they will. I will try to make packages later.

[moof (dogcow+ubuntu)]

It'd be nice if this were fixed before gutsy is released.

[Robbert (robbertkrebbers)]

I still get it either why this hasn't been fixed yet, the importance is "important" and there is a way to fix it.

[Matthew Gregg (mcg)]

Is it just me or did Gutsy ship with no vmware?

[Robbert (robbertkrebbers)]

I can confirm that.

[Richard Ayotte (rich-ayotte)]

Yes, but try this package for now.

deb http://ppa.launchpad.net/cschieli/ubuntu gutsy main restricted universe
multiverse

And see https://bugs.launchpad.net/ubuntu/+source/vmware-player/+bug/135358

Rich

On 10/20/07, Matthew Gregg <email address hidden> wrote:
>
> Is it just me or did Gutsy ship with no vmware?
>
> --
> No kernel modules for the 2.6.22 kernel
> https://bugs.launchpad.net/bugs/124775
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Paul Aspinall (fozzedout)]

it has removed vmware player and is now listed as unsupported software.

On 20/10/2007, Matthew Gregg <email address hidden> wrote:
>
> Is it just me or did Gutsy ship with no vmware?
>
> --
> No kernel modules for the 2.6.22 kernel
> https://bugs.launchpad.net/bugs/124775
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Matthew Gregg (mcg)]

I realize this probably isn't the place to ask, but this probably has or will bite a few people. Should a new bug be opened for the lack of vmware or is there a place that explains why this is no longer available?

[Thomas Hotz (thotz-deactivatedaccount)]

Your Ubuntu version is EOL. Does this still occur under supported Ubuntu versions? Thank you for telling us!