vmware kernel modules for 2.6.22-15 missing

Bug #242505 reported by Onno Benschop
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: vmware-server-kernel-modules

Can this please be updated whenever the kernel is updated, before you release the kernel?

Revision history for this message
Onno Benschop (onno-itmaze) wrote :

Hmm, there should also be a dependency that stops this kind of behaviour, that is, if there is no vmware module, the updated kernel modules should also not be able to be installed.

Revision history for this message
Onno Benschop (onno-itmaze) wrote :

The VMware packages were installed from the Canonical partner repository:
deb http://archive.canonical.com/ubuntu gutsy partner

Revision history for this message
Nick Barcet (nijaba) wrote :

There is indeed a dependency, but it is still met as the old kernel is still installed (but unfortunately not running).
I agree that this could be improved, though.

Revision history for this message
erny (erevilla) wrote :

I just created a symbolic link to kernel modules of 2.6.22-14 and it works, although that not be very safe:

sudo ln -sf /lib/modules/2.6.22-14-generic/updates/ /lib/modules/2.6.22-15-generic/

Revision history for this message
Onno Benschop (onno-itmaze) wrote :

Erny, a better process I just bumped into is outlined here:

https://answers.launchpad.net/ubuntu/+question/36849

In essence, you install the vmware-server-kernel-source package and build it for the new kernel, then install the resulting package. I cannot say if this will work for all future versions of the kernel -- I suspect not -- but it would be pretty safe to say that it will work for 2.6.22-* versions at least.

I should point out it now appears that fixing this bug should be trivial, given that a package such as vmware-server-kernel-source exists -- something which I didn't know until about 10 minutes ago -- and that it does not appear to be dependent on VMware to actually do anything.

Perhaps there is a dependency in the vmware-server package that hasn't been configured correctly to force the kernel modules to be built -- but that is outside my area of expertise.

Of course, the kicker might be that this is known *not* to work for other kernel versions and that this bug is serving as a place-holder to fix that issue. (For kernels in Hardy and Intrepid.) I'll investigate that...

Revision history for this message
Onno Benschop (onno-itmaze) wrote :

In case my comment wasn't clear enough, this is only for Gutsy -- since Hardy and Intrepid don't yet have vmware-server at all.

Revision history for this message
Scott Moser (smoser) wrote :

> In essence, you install the vmware-server-kernel-source package and build it
> for the new kernel, then install the resulting package.

Just to point out, that consits of:
  apt-get install vmware-server-kernel-source
  m-a a-i vmware-server-kernel-source

I did this yesterday on hardy 2.6.22-15-generic and it seems to have worked perfectly (working vmware-server now)

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue. Thanks.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi onno-itmaze,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 242505

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers