Arch Linux User Repository

When validation fails this is usually because nvidia silently updated a minor version link. The download link redirects to the new minor version. In this case I need to update the pkgver (e.g. 2021.1 -> 2021.1.1) and the checksum.

When this happens, please flag the package as out of date. Thank you.

Nsight Compute is shipped together with CUDA, but it can also be downloaded as a standalone; they also sometimes release updates to it in between CUDA releases, so one might want to go and grab the latest update directly from the website in those cases. And that standalone download has been requiring a login for at least a year or two IIRC.

Sounds like the DLAGENTS thing could be an interesting work around.

I might be able to get registered users to use the package without having to download the installer like in optix.

I do some DLAGENTS hacking in my gog-* packages and I could add a shell or python script to ask for credentials once, store them locally and use that to download. This would be a last resort. That or like what optix does.

The thing is that web requests aren't my expertise so I can figure it out but it will take me some time to find the proper requests to make to get the tokens needed. Also, it gets much more complicated with 2FA involved.

Ideally, NVIDIA could reverse their change. It could be an oversight. I emailed them to let them know. You can always respectfully let them know your thoughts on their contact page [1].

[1] https://developer.nvidia.com/contact

I think nsight compute comes with the cuda package. Interestingly, you don't need to be registered to download that.

This is unfortunate, but not surprising as some other tools (Nsight Compute maybe?) had already been requiring to login before downloading for some time.

I am guessing something similar to the optix AUR package will be needed, where the user downloads the script themselves and place it at a specific location for the package to use.

Maybe contact Nvidia to reverse that?

They probably won't (unfortunately) but they should understand that blocking direct access is stupid

Looks like nvidia started requiring users login via the NVIDIA Registered Developer Program to download their installer. I don't know if there's anything I can do about that.

The 2021_4_2 build fails with the message:

curl: (22) The requested URL returned error: 403
==> ERROR: Failure while downloading https://developer.nvidia.com/rdp/assets/nsight-graphics-2021_4_2-linux-installer
    Aborting...

When validation fails this is usually because nvidia silently updated a minor version link. The download link redirects to the new minor version. In this case I need to update the pkgver (e.g. 2021.1 -> 2021.1.1) and the checksum.

When this happens, please flag the package as out of date. Thank you.

the 2021.1 build fails the validity check

The 2020.6 build is failing for me in pamac with the message:

==> Starting prepare()...
sed: can't read /var/tmp/pamac-build-neko-san/nsight-graphics/src/nsight-graphics/pkg/host/linux-desktop-nomad-x64/VK_LAYER_NV_nomad.sh: No such file or directory
==> ERROR: A failure occurred in prepare().

Thank you for the package.

Would it be possible to change the dependency on the “nvidia” package to “NVIDIA-MODULE” so that it also works if one is using the “nvidia-dkms” package? Thank you in advance.

The desktop entry file could benefit from some additional fields like “Categories” or “Keywords”. I have been using some variant of the following for some time now; feel free to reuse (parts of) it if you would like.

[Desktop Entry]
Type=Application
Version=1.1
Name=NVIDIA Nsight Graphics
GenericName=Development Tool
Comment=Standalone application for the debugging and profiling of graphics applications
Exec=ngfx-ui
Icon=nsight-graphics
StartupNotify=true
Terminal=false
Keywords=3d;debugging;graphics;nvidia;profiling;rendering;
Categories=Development;

Good catch, should be installing both layers now.

Registering VK_LAYER_NV_GPU_Trace as Vulkan implicit layer
Registering VK_LAYER_NV_GPU_Trace_release_public_2020_2_0.json to /usr/share/vulkan/implicit_layer.d
cp: cannot create regular file '/usr/share/vulkan/implicit_layer.d/VK_LAYER_NV_GPU_Trace_release_public_2020_2_0.json': Permission denied
chmod: cannot access '/usr/share/vulkan/implicit_layer.d/VK_LAYER_NV_GPU_Trace_release_public_2020_2_0.json': No such file or directory

verification failed with the latest update did you run updpkgsums?

Actually the error happens when using buildpkg. The package builds fine with makepkg and yay. So probably not an issue with the package.

Error building 2019.5 ==> Starting prepare()... /var/tmp/pamac-build-jeancf/nsight-graphics/PKGBUILD: line 25: /var/tmp/pamac-build-jeancf/nsight-graphics/src/nsight-graphics/pkg/host/linux-desktop-nomad-x64/VK_LAYER_NV_nomad.sh: No such file or directory ==> ERROR: A failure occurred in prepare(). Aborting...