kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: DKMS module and recipe for target '.../virtualbox/5.2.34/build/vboxdrv' failed
Date: Fri, 19 Jun 2020 00:45:37 -0400	[thread overview]
Message-ID: <CAH8yC8npuv3S+VDtjOtqtX+n7efH-kbZnhxjH4pQGesXZEQgcQ@mail.gmail.com> (raw)
In-Reply-To: <451909.1592540836@turing-police>

On Fri, Jun 19, 2020 at 12:27 AM Valdis Klētnieks
<valdis.kletnieks@vt.edu> wrote:
>
> On Thu, 18 Jun 2020 08:13:00 +0200, Greg KH said:
> > On Thu, Jun 18, 2020 at 01:41:23AM -0400, Jeffrey Walton wrote:
> > > Hi Everyone,
> > >
> > > I recently upgraded Ubuntu 18.04 x86_64 to the 5.4.0-37 kernel.
> > > VirtualBox died, and I am trying to reinstall virtualbox-dkms. The
> > > reinstall fails because the build fails. The log is below.
> > >
> > > Is there anything I can do to solve the problem?
> >
> > Ask the out-of-tree virtualbox developers to fix their code to work with
> > the newer kernel source.  Nothing we can do about that, sorry.
>
> Won't do any good, because...
>
> > cat /var/lib/dkms/virtualbox/5.2.34/build/make.log
>
> 5.2.34 is a few releases back. 6.1.10 is out, and supports the 5.7 kernel (and
> most of the fixes to support 5.8-rc1 have already landed for 6.1.12).
> They fixed that problem probably close to a year ago.

Thanks Valdis .

A quick question... Why is a 5.4 kernel using 5.2 dkms source code? It
seems to me if Ubuntu used the proper source code, then the problem
would not exist.

Jeff

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2020-06-19  4:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  5:41 DKMS module and recipe for target '.../virtualbox/5.2.34/build/vboxdrv' failed Jeffrey Walton
2020-06-18  6:13 ` Greg KH
2020-06-19  4:27   ` Valdis Klētnieks
2020-06-19  4:45     ` Jeffrey Walton [this message]

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=CAH8yC8npuv3S+VDtjOtqtX+n7efH-kbZnhxjH4pQGesXZEQgcQ@mail.gmail.com \
    --to=noloader@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /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).