[Pkg-virtualbox-devel] Bug#703358: virtualbox-guest-dkms: vboxvideo_drm.c fails to compile after upgrade of linux-headers-3.2.0-4 from 3.2.35-2 to 3.2.39-2

[Felix Geyer]

On 20.03.2013 23:15, Roger Leigh wrote:
> severity 703358 serious
> thanks
>
> On Mon, Mar 18, 2013 at 08:06:29PM +0100, Tomasz Wierzbicki wrote:
>> Making dpkg-reconfigure on virtualbox-guest-dkms gives the following error:
>>
>> Loading new virtualbox-guest-4.1.18 DKMS files...
>> Building only for 3.2.0-4-amd64
>> Building initial module for 3.2.0-4-amd64
>> Error! Bad return status for module build on kernel: 3.2.0-4-amd64 (x86_64)
>> Consult /var/lib/dkms/virtualbox-guest/4.1.18/build/make.log for more
>> information.
> Having virtualbox kernel modules broken out of the box for wheezy
> isn't ideal.  Looks like this broke relatively recently; increasing
> the severity.

This is caused by
   * Backport drm and agp subsystems from Linux 3.4.29 (closes: #687442)
from linux 3.2.39-1 (2013-02-25).

> VirtualBox maintainers: would backporting the necessary bits be
> possible to make it buildable with the wheezy kernel?

The kernel module already supports kernel 3.4. The problem is detecting
that the 3.2 kernel contains a backported drm subsystem.

VirtualBox has this code to detect the backported drm subsystem in RHEL:

> #   if RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(6,3)
> #    define DRM_RHEL63
> #   endif

Ideally we could use a similar check for Debian.
As a last resort I could forcefully define DRM_RHEL63 but that would break
pre-3.4 custom kernels.

Regards,
Felix