From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: nvidia: update to 515.76.
Date: Sat, 05 Nov 2022 08:07:42 +0100 [thread overview]
Message-ID: <20221105070742.xzpeFEIlN22_7vdbWXgjuyA7bpqZGi6vBfDx9SZSJw8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40327@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
New comment by abenson on void-packages repository
https://github.com/void-linux/void-packages/pull/40327#issuecomment-1304427874
Comment:
I've held off of this update because of [issues](https://forums.developer.nvidia.com/t/bug-report-black-x11-screen-and-partial-lockup-when-upgraded-to-515-76-and-dual-rtx3060/228912).
Unfortunately, it seems to only affect certain recent versions I can't test for multiple reasons.
I'm willing to merge if someone can verify the issue is fixed now.
next prev parent reply other threads:[~2022-11-05 7:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 6:34 [PR PATCH] " dataCobra
2022-11-05 7:07 ` abenson [this message]
2022-11-05 9:30 ` dataCobra
2022-11-05 12:49 ` [PR PATCH] [Updated] " dataCobra
2022-11-05 12:50 ` [PR PATCH] [Updated] nvidia: update to 520.56.06 dataCobra
2022-11-05 12:52 ` dataCobra
2022-11-09 15:06 ` dataCobra
2022-11-16 13:47 ` dataCobra
2022-11-22 15:21 ` abenson
2022-11-23 0:44 ` abenson
2022-11-23 6:24 ` dataCobra
2022-11-24 16:06 ` [PR PATCH] [Updated] " dataCobra
2022-11-29 0:24 ` abenson
2022-12-08 18:26 ` [PR PATCH] [Closed]: " dataCobra
-- strict thread matches above, loose matches on Subject: below --
2022-10-02 23:36 [PR PATCH] nvidia: update to 515.76 migue07juegos
2022-10-02 23:46 ` abenson
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=20221105070742.xzpeFEIlN22_7vdbWXgjuyA7bpqZGi6vBfDx9SZSJw8@z \
--to=abenson@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).