Hi Georg,
>Does this mean, if running jessie and a backported kernel, each time the
>kernel receives an update, virtualbox has to be updated as well?
well, each virtualbox release is guaranteed to build (except for bugs of course)
to kernels up to a particular version (e.g. 5.0.4 build fine u
On Saturday, September 19, 2015, ge...@riseup.net wrote:
> Hi,
>
> Just a quick follow-up question:
>
> On Mon, 14 Sep 2015 05:11:58 + (UTC) Gianfranco Costamagna <
> costamagnagianfra...@yahoo.it > wrote:
> > Unfortunately we can't know *in advance* the kernel that will be
> > backported to
Hi,
Just a quick follow-up question:
On Mon, 14 Sep 2015 05:11:58 + (UTC) Gianfranco Costamagna
wrote:
> Unfortunately we can't know *in advance* the kernel that will be
> backported to jessie, so we can't make it build with a newer kernel
> that the one in jessie when it was released.
Doe
I'm encountering what's probably the same issue.
omer@triton:~$ aptitude show linux-headers-`uname -r`
Package: linux-headers-4.1.0-0.bpo.2-amd64
State: installed
Automatically installed: yes
Version: 4.1.6-1~bpo8+1
Priority: optional
Section: kernel
Maintainer: Debian Kernel Team
Architecture: a
Control: tag -1 +moreinfo
What is the output of:
ls /lib/modules/`uname -r`/ -l
On Sunday 22 March 2015 01:13 PM, dE wrote:
> Package: virtualbox-dkms
> Version: 4.3.18-dfsg-2~bpo70+1
> Severity: important
>
> virtualbox-dkms does not work for backported kernels.
>
> # dpkg-reconfigure virtualb
Package: virtualbox-dkms
Version: 4.3.18-dfsg-2~bpo70+1
Severity: important
virtualbox-dkms does not work for backported kernels.
# dpkg-reconfigure virtualbox-dkms
--
Deleting module version: 4.3.18
completely from the DKMS tree.
--
Done.
6 matches
Mail list logo
