Nvidia 516.94 Driver Download

0 views

Skip to first unread message

Kathrine Selvage

unread,

Aug 3, 2024, 11:13:34 AM8/3/24

to tipafise

"Standard" refers to driver packages that predate the DCH driver design paradigm. Standard drivers are for those who have not yet transitioned to contemporary DCH drivers, or require these drivers to support older products.

Please run nvidia-bug-report.sh as root and attach the resulting .gz file to your post. Hovering the mouse over an existing post of yours will reveal a paperclip icon.
[url] -files-to-forum-topics-posts/[/url]

I am experiencing a similar problem trying to get the NVIDIA driver running on my SurfaceBook-2 running Ubuntu 18.04.3 LTS in a dual-boot dual-monitor (via Surface Dock) with Windows and secure boot disabled.

Thanks for spotting that. Not sure how that happened, but I think it is corrected now. I still cannot get the NVIDIA GPU working though. (I would like to run the GPU enabled TensorFlow and GPU enabled OpenCV.) I have rolled back the driver to 390 and back to 430 (rebooting in the process). I cycled between Intel and Nvidia using prime-select with no success. New bug-report attached.

Whether you are playing the hottest new games or working with the latest creative applications, NVIDIA drivers are custom tailored to provide the best possible experience. If you are a gamer who prioritizes day of launch support for the latest games, patches, and DLCs, choose Game Ready Drivers. If you are a content creator who prioritizes reliability for creative workflows including video editing, animation, photography, graphic design, and livestreaming, choose Studio Drivers. Do a little bit of both? No worries, either can support running the best games and creative apps.

"Beta Release" Beta drivers are provided by NVIDIA as preview releases for quick bug fixes and access to new features. Beta drivers are under qualification testing, and may include significant issues. It is the end user's responsibility to protect system and data when using Beta drivers with NVIDIA products. It is strongly recommended that end users back up all the data prior to using Beta drivers from this site. Please ensure that newer Recommended/Certified drivers are not already posted on NVIDIA.com prior to installation and usage of Beta drivers. Beta drivers posted do not carry any warranties nor support services.

I think it may be due to some change with the systemd services added in version 550 because that is when it happens the most. It has already happened to me twice when I am updating the system and it breaks it because the update cannot be completed. In the video it happens when the specific hooks are being processed (reloading system manager configuration).

I use endeavourOS(with kde) too on a lenovo legion 5(15h6h w/amd5600h+rtx3060) and can confirm random freezing on desktop use (currently ever since updating from 545 from nvidia-lts package i cannot also get nvidia to deep sleep which could affect stability?), REISUB works at least, when using nvidia-550 so i decided to wait for it and revert to 545, hope it gets fixed or else could be just distro specific.
If needed i can revert to back to nvidia-550 and fill bug report, for now i leave mine from 545:
nvidia-bug-report.log.gz (3.4 MB)

Other cases:
I found it to happen randomly, or just when chaining platform profiles.
Sometimes just when rebooting/powering off the machine, or randomly while booting/on the login screen.
It even happens when the GPU is not in use, powered off, on battery.

But this issue happens randomly, i just now did again and it did not happen, but in contrast e.g: the other day when i had vscode open, the app froze, then only mouse was working and then froze the system, REISUB worked still.

The trigger to cause the freeze is not consistent. The most reliable way to trigger it seems to be inserting / removing a USB-C cable which connects a single external monitor to the laptop. When the freeze starts to happen, I can move the mouse around sometimes but the UI does not respond and eventually the mouse cursor does not move anymore. There does not seem to be any correlation between the freeze and the applications which are running when it happens.

After this 2nd hang occurred, I booted the system one more time (2 minutes after the 2nd hard shutdown). 12 minutes later I performed a normal shutdown in the KDE start menu and this is where things got interesting. The system hung with a black screen pretty much immediately and would not respond to any user input.

I left it running overnight and did a hard shutdown in the morning to see what it would log overnight, but when checking the journal log today there was nothing logged past 1 second after the shutdown was initiated. Below is the complete journal log from this instance of hanging and the subsequent boot entry this evening

Same symptoms, same 550 driver, likewise the error appears in both X11 and Wayland, likewise the kernel panic stack starts with the __die function, likewise happens most often when shutting down/rebooting the laptop

If you installed the NVIDIA driver from .run files or bundled driver from CUDA Toolkit, the driver may be lost when you upgrade your Linux kernel. You should reinstall the NVIDIA driver. You can install the driver with dkms option on:

BTW, If your server has a network connection, I still suggest you install the driver from APT instead of .run file (driver run file or CUDA run file). Since it is much easier to upgrade your driver for future maintenance, you will not need to visit the driver download page to download the driver .run file again.

[ Impact ]Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME.[ Test Plan ]0. Set up a desktop with Nvidia driver 545 or 550.1. Log into Ubuntu, ensuring it's a Xorg session.2. Open a Terminal,...

Yep, I just noticed I tried the wrong version, blind me. I got confused while booting around different versions trying to make it work. So basically, my PC is useless as workstation with Nvidia card for the time being.

Is there any plans to make the driver work with the current kernels? Or does it work if re-installed locally some other way, like the scripted install? Or are they the same binaries behind all of the different install ways?

Is this somehow a case of BIOS or some chip having different idea of PCI bus memory addressing vs. what the driver sees? Anyhow, it has worked for rather long time, couple of years until it broke like this.

Nvidia claim its optimisations include Blender, so might have some merit for Cycles, but who knows? (@nathanletwory?). I elected to use it because I figured it might not be subject to so much development churn as the Game driver.

I have noticed on a couple new installs that the nvidia-drm-modeset=1 seems no longer to be added into /etc/default/grub. If an older install already has it the option is not removed, but a new clean install seems to no longer receive that option in the kernel command line.

After an upgrade I got problems making the nvidia drivers work for a Geforce RTX 3050. After a frustrating day of fielding around, I decided to install Rocky 9.3 from scratch, but with a similar outcome.

and it semi works. On a single (non 4K) monitor I get an output, which looks fine, but on a 4K monitor the resolution is set to 1024x768 and I can not change it. In any case I can only make one monitor work. Interestingly if I install

instead gives me just a black screen. When I follow the instruction to install the driver from rmpfusion, I have an output, but the resolution is stuck at 1024x768 and the output of lshw -C display also remains t

Please be sure if you have a problem to always include a screenshot from the Plugin page, a screenshot of the output of the command 'nvidia-smi' (simply open up a Unraid terminal with the button on the top right of Unraid and type in 'nvidia-smi' without quotes) and the error from the startup of the Container/App if there is any.

After starting the container and playing some movie that needs to be transcoded that your graphics card is capable of you should see that you can now successfully transcode using your Nvidia graphics card (Jellyfin doesn't display if it's actually transcoding with the graphics card at time of writing but you can also open up a Unraid terminal and type in 'watch nvidia-smi' then you will see at the bottom that Jellyfin is using your card) :

I upgraded to 6.9.0-beta35 from the 6.8.3 nvidia kernel with hardware transcoding working in all containers (Plex, Jellyfin, etc.). After successful installation of the nvidia-plugin, the graphics card is showing up in settings and nvidia-smi, but I am unable to get hardware transcoding to work. As soon as I activate hardware transcoding in Plex, I get a black screen instead of the video. Software transcoding works fine.

From what I know about this driver is that it integrates support for the RTX 3000 series (at least for the 3070), fixes a few minor bugs adds also a new Vulkan beta driver but is also still not fully compatible with Kernel 5.9

I had exactly the same problem (same behaviour : microskip and skipping few secondes every 1 minute) with Nvidia-Unraid 6.8.3 and older nvidia drivers while using latests versions of plex... Upgrading to Nvidia-Unraid 6.9.0.beta-29 with newer nvidia drivers solved the problem...

It seems tha Plex is very picky concerning Nvidia drivers...