Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UUF] Imprecise link #43972

Closed
gewarren opened this issue Dec 14, 2024 · 1 comment
Closed

[UUF] Imprecise link #43972

gewarren opened this issue Dec 14, 2024 · 1 comment
Assignees
Labels
dotnet-ml/svc 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer

Comments

@gewarren
Copy link
Contributor

gewarren commented Dec 14, 2024

Describe the issue or suggestion

Link for cuDNN v7.6.4 for CUDA 10.1 is not precise. Please update it.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.


Associated WorkItem - 364555

@dotnetrepoman dotnetrepoman bot added the ⌚ Not Triaged Not triaged label Dec 14, 2024
@gewarren gewarren changed the title Imprecise link [UUF] Imprecise link Dec 14, 2024
@gewarren gewarren self-assigned this Dec 14, 2024
@gewarren gewarren added the 🗺️ reQUEST Triggers an issue to be imported into Quest. label Jan 19, 2025
@dotnet-policy-service dotnet-policy-service bot removed the ⌚ Not Triaged Not triaged label Jan 19, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Jan 19, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Jan 19, 2025
@gewarren gewarren moved this from 🔖 Ready to 👀 In review in dotnet/docs January 2025 sprint project Jan 19, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Jan 19, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Jan 19, 2025
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Jan 20, 2025
@BillWagner BillWagner removed the Pri2 label Jan 22, 2025
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in dotnet/docs January 2025 sprint project Jan 30, 2025
@thomasclaudiushuber
Copy link
Contributor

@gewarren @BillWagner

I'm sorry, but I think now the documentation is broken.

Is installing cuDNN 7.6.4 for CUDA 10.1 no requirement anymore?

Visual Studio still says so, and even your issue here says that exactly 7.6.4 is required. But now the docs say "cuDNN for CUDA 10.1" without any specific cuDNN version.

The link goes to the latest cuDNN version, which is 9.7.0 right now, that is not the one for 10.1. Instead, the link should go to the 8.x-1.x archive, where developers find the cuDNN 7.6.4 release for CUDA 10.1, which is this link: https://developer.nvidia.com/rdp/cudnn-archive

And what about copying the cuDNN.exe into the CUDA 10.1 installation? Why did you remove that, is it not necessary anymore?

thomasclaudiushuber added a commit to thomasclaudiushuber/docs-1 that referenced this issue Feb 1, 2025
Point to cuDNN archive that contains cuDNN 7.6.4 for CUDA 10.1 and include necessary cuDNN installation instructions.

Fixes issue dotnet#43972 and non-precise doc introduced by PR dotnet#44444
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dotnet-ml/svc 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer
Projects
No open projects
Development

No branches or pull requests

3 participants