Github messages for voidlinux
 help / color / mirror / Atom feed
From: AngryPhantom <AngryPhantom@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Nvidia340 fails to compile on a new 5.7.9 lts kernel
Date: Tue, 10 Nov 2020 13:20:49 +0100	[thread overview]
Message-ID: <20201110122049.TncfV0jsm4Jc7fbN0lRXuKyD89OqoGUjIWeYw65ITaw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23602@inbox.vuxu.org>

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

New comment by AngryPhantom on void-packages repository

https://github.com/void-linux/void-packages/issues/23602#issuecomment-724667431

Comment:
That's nice that it can be still supported. Actually I switched to a more stable 5.4.x kernel branch. I've also found out that **Debian** still supports **nvidia340** driver and will support it in the future releases with **5.8.x**, **5.9.x** and higher kernels. Probably you can take the patches from them? Here is the [driver](https://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=nvidia-legacy-340xx-kernel-source) (you need to unpack it and take the _nvidia-legacy-340xx-kernel.tar.xz_ archive, there will be a '**patches**' directory inside). I think you should take the latest version (for Debian Sid).
I guess I'm not the one with old hardware here, so it would be really nice if you continue supporting legacy drivers.
Well, if it's not a problem for you, of course...

Thank you!

  parent reply	other threads:[~2020-11-10 12:20 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 18:17 [ISSUE] " AngryPhantom
2020-07-16 18:30 ` ericonr
2020-07-16 18:31 ` ericonr
2020-07-16 19:08 ` AngryPhantom
2020-07-16 19:18 ` ericonr
2020-07-16 19:22 ` AngryPhantom
2020-07-16 19:28 ` AngryPhantom
2020-07-16 19:29 ` q66
2020-07-16 19:41 ` ericonr
2020-07-16 19:51 ` AngryPhantom
2020-07-16 19:52 ` AngryPhantom
2020-07-16 19:55 ` q66
2020-07-16 19:57 ` AngryPhantom
2020-07-16 20:00 ` q66
2020-07-16 20:06 ` AngryPhantom
2020-07-16 20:08 ` q66
2020-07-16 20:13 ` AngryPhantom
2020-07-16 20:14 ` AngryPhantom
2020-07-16 20:28 ` AngryPhantom
2020-07-16 20:30 ` AngryPhantom
2020-07-16 20:31 ` AngryPhantom
2020-07-17 20:13 ` AngryPhantom
2020-07-18  0:33 ` q66
2020-07-18  2:07 ` AngryPhantom
2020-07-22  6:15 ` fosslinux
2020-07-23 20:19 ` AngryPhantom
2020-07-23 20:36 ` q66
2020-07-24  4:13 ` fosslinux
2020-11-02  3:35 ` fosslinux
2020-11-02 18:44 ` seannaswell
2020-11-03  7:56 ` AngryPhantom
2020-11-03 10:22 ` fosslinux
2020-11-03 10:22 ` fosslinux
2020-11-07 16:29 ` AngryPhantom
2020-11-07 23:39 ` fosslinux
2020-11-10 12:20 ` AngryPhantom [this message]
2020-11-10 12:21 ` AngryPhantom
2020-11-10 22:09 ` fosslinux
2020-11-11  8:49 ` AngryPhantom
2021-01-04 22:52 ` Chocimier
2021-01-04 22:52 ` [ISSUE] [CLOSED] " Chocimier
2021-01-05  0:43 ` fosslinux
2021-01-17 17:16 ` Yay-mod
2021-01-17 21:21 ` fosslinux
2021-01-18  1:00 ` Yay-mod
2021-01-18  1:03 ` Yay-mod
2021-01-18  1:09 ` Yay-mod
2021-01-18  1:09 ` Yay-mod
2021-01-18  2:19 ` ericonr
2021-01-18  2:25 ` ericonr
2021-01-18  8:14 ` AngryPhantom
2021-01-18 10:59 ` fosslinux
2021-01-18 11:45 ` AngryPhantom
2021-01-18 18:30 ` Yay-mod
2021-01-18 18:33 ` Yay-mod
2021-01-18 19:28 ` Yay-mod
2021-01-18 19:30 ` Yay-mod
2021-01-18 22:11 ` AngryPhantom
2021-01-19  0:01 ` fosslinux
2021-01-19  0:02 ` fosslinux
2021-01-19  3:17 ` Yay-mod
2021-01-19  4:38 ` fosslinux
2021-01-19 18:43 ` Chocimier
2021-01-20  2:45 ` Yay-mod
2021-01-20  2:46 ` Yay-mod
2021-01-20  2:52 ` Yay-mod
2021-01-20  6:31 ` fosslinux
2021-01-20 11:00 ` AngryPhantom
2021-01-22  2:45 ` Yay-mod
2021-01-22  2:46 ` Yay-mod

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=20201110122049.TncfV0jsm4Jc7fbN0lRXuKyD89OqoGUjIWeYw65ITaw@z \
    --to=angryphantom@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).