Talk:NVIDIA: Difference between revisions

imported>SomeoneSerge
cudnn question
Pluieuwu (talk | contribs)
m Pluieuwu moved page Talk:Nvidia to Talk:NVIDIA: NVIDIA is a proper trademark that is stylized usually in all upper case. ArchWiki also spells it all upper case: https://wiki.archlinux.org/title/NVIDIA
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:


== Some recommendations for the NixOS NVIDIA usage ==
For a Gnome user it is useful to add the svicheroo-control application in the package section of the configuration.nix and enable  svicheroo-control service.
If there are a kernel-panic, hanging or freezing of the system on poweroff or rebooting with the NVIDIA 550 version driver, as it known https://forums.developer.nvidia.com/t/series-550-freezes-laptop/284772 , it is necessary to use the beta version of the NVIDIA driver package.


== Non-NixOS section ==
== Non-NixOS section ==


The section currently suggests using NixGL.
The section cutrrently suggests using NixGL.
In my limited experience, a more "convenient" option has been to symlink (e.g. via systemd-tmpfiles) the host's driver libraries to `/run/opengl-driver/lib` which is already in all executable's RPATHs, but I don't know how robust that is when it comes to libc. At least a mention of `/run/opengl-driver/lib` and RPATHs existing would be quite appropriate on this page.
In my limited experience, a more "convenient" option has been to symlink (e.g. via systemd-tmpfiles) the host's driver libraries to `/run/opengl-driver/lib` which is already in all executable's RPATHs, but I don't know how robust that is when it comes to libc. At least a mention of `/run/opengl-driver/lib` and RPATHs existing would be quite appropriate on this page.


Line 16: Line 21:


Another aspect of the problem is in overriding downstream derivations, that take as inputs both cudnn and cudatoolkit.
Another aspect of the problem is in overriding downstream derivations, that take as inputs both cudnn and cudatoolkit.
For example, (speaking of nixpkgs-21.11) when a user overrides pytorch to use cudatoolkit_11, the build fails because pytorch gets two conflicting versions of cuda: cudatoolkit_11 from the user, and cudatoolkit_10 through the dependency on cudnn. Until we've fixed these issues on nixpkgs, we should at least make them and the workarounds visible to the users to reduce frustration
For example, (speaking of nixpkgs-21.11) when a user overrides pytorch to use cudatoolkit_11, the build fails because pytorch gets two conflicting versions of cuda: cudatoolkit_11 from the user, and cudatoolkit_10 through the dependency on cudnn. Until we've fixed these issues on nixpkgs, we should at least make them and the workarounds visible to the users to reduce frustration. See e.g. https://discourse.nixos.org/t/cant-get-pytorch-to-recognise-override/12082


--[[User:SomeoneSerge|SomeoneSerge]] ([[User talk:SomeoneSerge|talk]]) 21:58, 17 March 2022 (UTC)
--[[User:SomeoneSerge|SomeoneSerge]] ([[User talk:SomeoneSerge|talk]]) 21:58, 17 March 2022 (UTC)
Return to "NVIDIA" page.