From: Duncaen <over...@googlemail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: Virtualbox can't reconfigure ose-dkms against latest linux-headers
Date: Mon, 24 Aug 2015 05:30:47 -0700 (PDT) [thread overview]
Message-ID: <47ffb50b-99f2-4fad-a610-e633ed9abae1@googlegroups.com> (raw)
In-Reply-To: <94653e90-8eb8-46ec-ad36-d2ae09712ee8@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1280 bytes --]
Could you provide the output or an error message?
For me its working with all installed kernel versions:
Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.0.9_1... done.
Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.0.9_1... done.
Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.3_1... done.
Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.3_1... done.
Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.4_1... done.
Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.4_1... done.
Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.5_1... done.
Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.5_1... done.
Building DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.6_1... done.
Installing DKMS module 'virtualbox-ose-5.0.2' for kernel-4.1.6_1... done.
Am Montag, 24. August 2015 14:26:57 UTC+2 schrieb Frankie Wild:
>
> Virtualbox ain't working for quite some time now. Last time it worked was
> when I booted with 3.19.8.1.
>
> Currently on up to date 4.1.6.1 force reconfigure fails against all
> kernels.
>
> xbps-query -l | grep header shows I have 3.19.8.1, 4.0.9.1 and 4.1.6.1
> installed. Is this a conflict and shall I just leave the latest version in
> order to sort it out ?
>
[-- Attachment #1.2: Type: text/html, Size: 1603 bytes --]
next prev parent reply other threads:[~2015-08-24 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 12:26 Frankie Wild
2015-08-24 12:30 ` Duncaen [this message]
2015-08-24 12:54 ` Frankie Wild
2015-08-25 13:34 ` Stefan Mühlinghaus
2015-08-26 5:23 ` Frankie Wild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47ffb50b-99f2-4fad-a610-e633ed9abae1@googlegroups.com \
--to="over..."@googlemail.com \
--cc="void..."@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).