Github messages for voidlinux
 help / color / mirror / Atom feed
From: p2501mk <p2501mk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] nvidia 390 fails to build for kernel 5.8
Date: Tue, 15 Sep 2020 11:13:15 +0200	[thread overview]
Message-ID: <20200915091315.o4Y8aRmb44xC-NMjb_TWWYAL3uiFrbqh2OyNUfWosBA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24705@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 585 bytes --]

Closed issue by p2501mk on void-packages repository

https://github.com/void-linux/void-packages/issues/24705

Description:
Both DKMS fail to build for every 5.8 series kernel.

### System

* xuname:  
  Void 5.7.19_1 x86_64 GenuineIntel uptodate rrFFFF
* package:  
  basically every 5.8 series kernel release
* affected package(s) including the version:
  virtualbox-ose-6.1.10_2
  nvidia-390.138

### Expected behavior
 DKMS builds

### Actual behavior
 `Building DKMS module: nvidia-390.138... FAILED!
Building DKMS module: virtualbox-ose-6.1.10... FAILED!`




      parent reply	other threads:[~2020-09-15  9:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06  5:45 [ISSUE] nvidia 390 and virtualbox-ose DKMS fail " p2501mk
2020-09-06  5:58 ` flexibeast
2020-09-06  7:04 ` p2501mk
2020-09-08 19:16 ` pullmoll
2020-09-09  7:01 ` nvidia 390 (and virtualbox-ose DKMS: new version, builds now) " p2501mk
2020-09-10 19:30 ` nvidia 390 fails " pullmoll
2020-09-10 20:30 ` pullmoll
2020-09-10 20:31 ` pullmoll
2020-09-12  7:44 ` pullmoll
2020-09-14 17:41 ` p2501mk
2020-09-14 17:55 ` ericonr
2020-09-14 18:11 ` pullmoll
2020-09-14 18:24 ` pullmoll
2020-09-14 18:28 ` pullmoll
2020-09-14 22:06 ` pullmoll
2020-09-15  4:38 ` p2501mk
2020-09-15  9:13 ` p2501mk [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=20200915091315.o4Y8aRmb44xC-NMjb_TWWYAL3uiFrbqh2OyNUfWosBA@z \
    --to=p2501mk@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).