From: ArmedAviator <ArmedAviator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: nvidia: update to 470.57.02.
Date: Thu, 22 Jul 2021 19:00:11 +0200 [thread overview]
Message-ID: <20210722170011.hGlCdgp4XuujSNfkJAeD5NjCcKjfPQobahSQzO0tI3s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32100@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
New comment by ArmedAviator on void-packages repository
https://github.com/void-linux/void-packages/pull/32100#issuecomment-885068044
Comment:
That was my thought, too. I double checked and do have the 32-bit libraries installed.
`rich@area51 ~ $ xbps-query -s nvidia*
[*] nvidia-470.57.02_1 NVIDIA drivers for linux - Libraries and Utilities
[*] nvidia-dkms-470.57.02_1 NVIDIA drivers for linux - DKMS kernel module
[*] nvidia-gtklibs-470.57.02_1 NVIDIA drivers for linux - GTK+ libraries
[*] nvidia-libs-470.57.02_1 NVIDIA drivers for linux - common libraries
[*] nvidia-libs-32bit-470.57.02_1 NVIDIA drivers for linux - common libraries (32bit)
rich@area51 ~ $ ls -lh /usr/lib32/libnvidia-glvkspirv.so.*
-rwxr-xr-x 1 root root 15M Jul 22 04:29 /usr/lib32/libnvidia-glvkspirv.so.470.57.02`
This has happened before during the 460 series of nvidia driver updates and it just "fixed" itself after an update one week. I do recall that the drivers were not updated when things began working again - maybe something built against nvidia libs in steam/proton? I don't know.
With that said, it seems this package is good to go and that my problem is coming from Steam/Proton itself.
next prev parent reply other threads:[~2021-07-22 17:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 13:45 [PR PATCH] " ardadem
2021-07-22 14:16 ` ArmedAviator
2021-07-22 14:16 ` ArmedAviator
2021-07-22 16:50 ` ardadem
2021-07-22 17:00 ` ArmedAviator [this message]
2021-07-22 17:00 ` ArmedAviator
2021-07-22 19:41 ` [PR PATCH] [Updated] " ardadem
2021-07-22 19:47 ` ardadem
2021-07-22 19:59 ` ardadem
2021-07-22 20:08 ` abenson
2021-07-22 21:09 ` ArmedAviator
2021-07-22 23:14 ` abenson
2021-07-23 20:01 ` [PR PATCH] [Merged]: " abenson
2021-07-26 11:27 ` kernle32dll
2021-07-21 22:21 [PR PATCH] " abenson
2021-07-22 0:18 ` abenson
2021-07-22 1:27 ` ericonr
2021-07-22 6:57 ` ardadem
2021-07-22 19:23 ` 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=20210722170011.hGlCdgp4XuujSNfkJAeD5NjCcKjfPQobahSQzO0tI3s@z \
--to=armedaviator@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).