aims team mailing list archive

[Lekensteyn <1081307@xxxxxxxxxxxxxxxxxx>]

I propose to use the patch from #3, but refresh it against the current
sources. Then use dkms.conf to apply it to 3.5 only. This will not cause
regressions with the 3.2 Precise kernel for sure, but it allows the
currently broken quantal lts kernel to build.

As a quick hack, I downloaded the patch to /etc/dkms/ and post-processed
it to allow DKMS to accept the patch:

    sed 's,/src/VBox/Runtime,,' 38-fix-for-3.5-kernel.patch -i

Next, I created /etc/dkms/virtualbox.conf containing:

    PATCH[0]=../../../../../../../../../../../../../../etc/dkms/38-fix-for-3.5-kernel.patch
    PATCH_MATCH[0]=^3.5
(the definitive fix for ubuntu should put the patch in /usr/src/virtualbox-*/patches which allows the ../...../etc/dkms/ part to be stripped)

Result:
# dkms -m virtualbox -v 4.1.12 install

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
Kernel preparation unnecessary for this kernel.  Skipping...
applying patch ../../../../../../../../../../../../../../etc/dkms/38-fix-for-3.5-kernel.patch...patching file r0drv/linux/memobj-r0drv-linux.c
Hunk #3 succeeded at 524 (offset -1 lines).
Hunk #4 succeeded at 592 (offset -1 lines).
Hunk #5 succeeded at 613 (offset -1 lines).
Hunk #6 succeeded at 1204 (offset -9 lines).
Hunk #7 succeeded at 1221 (offset -9 lines).
Hunk #8 succeeded at 1415 (offset -9 lines).
Hunk #9 succeeded at 1427 (offset -9 lines).
Hunk #10 succeeded at 1511 (offset -9 lines).
Hunk #11 succeeded at 1528 (offset -9 lines).
patching file r0drv/linux/the-linux-kernel.h
[...]
DKMS: build completed.

vboxdrv.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.5.0-25-generic/updates/dkms/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.5.0-25-generic/updates/dkms/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.5.0-25-generic/updates/dkms/

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.5.0-25-generic/updates/dkms/

depmod....

DKMS: install completed.

-- 
You received this bug notification because you are a member of AIMS,
which is subscribed to a duplicate bug report (1126315).
https://bugs.launchpad.net/bugs/1081307

Title:
  virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module
  failed to build [merge request]

Status in “virtualbox” package in Ubuntu:
  Fix Released
Status in “virtualbox” source package in Precise:
  Confirmed
Status in “virtualbox” source package in Quantal:
  Confirmed
Status in “virtualbox” source package in Raring:
  Fix Released

Bug description:
  I'm using aptitude as a packet manager.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  DKMSKernelVersion: 3.5.0-18-generic
  Date: Tue Nov 20 23:13:23 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  MarkForUpload: True
  PackageArchitecture: all
  PackageVersion: 4.1.12-dfsg-2ubuntu0.2
  SourcePackage: virtualbox
  Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]
  Users are not able to use virtualbox from the repository on 12.04. It is totally broken.
  The patch proposed backports only the relevant parts from upstream to fix the bug.
  The patch is from: https://www.virtualbox.org/changeset/41660/vbox

  [Test Case]
  Upgrade to 3.5 kernel on 12.04 and install virtualbox.

  [Regression Potential]
  It is best to use the latest upstream version. But since that will cause major disruption, we have to track this package and corresponding bugs for regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307/+subscriptions