Github messages for voidlinux
 help / color / mirror / Atom feed
From: namgo <namgo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Package request] Nvidia CUDA Kit
Date: Tue, 05 Dec 2023 16:07:58 +0100	[thread overview]
Message-ID: <20231205150758.CaBxMf8837cWRAzYdwVD6H4MhbeNnFZieCmcA-n5arg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20077@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

New comment by namgo on void-packages repository

https://github.com/void-linux/void-packages/issues/20077#issuecomment-1840789318

Comment:
This comment is less important than the former, but:

https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html#id5 is an important reference for driver versions to cuda versions if we're bundling them separately. Nvidia driver is 535.129(.03?) as of Dec 5, 2023 which corresponds to CUDA 12.2 - I had downloaded 12.3 and was encountering:

`cuLinkAddData(): the provided PTX was compiled with an unsupported toolchain.` running hashcat as a generally available quick test.

I think this is important for matching CUDA versions to drivers if we package (https://developer.nvidia.com/cuda-toolkit-archive).

We can also always package a nvidia-cuda-download-helper script if the cuda licensing becomes an issue.

Here's an example of how nvidia-cuda-download-helper might look: https://gist.github.com/namgo/9aeeee2025b341779be85e596822893f - I've tested the result with hashcat briefly but haven't tried building pytorch with it yet. If CUDA licensing is really an issue, a restricted package might be necessary then? Still waiting to hear back, but the above script seems to be a start.

  parent reply	other threads:[~2023-12-05 15:07 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 20:40 [ISSUE] Question: Is there a package for the Nvidia CUDA Kid Frick-David
2020-03-13 22:44 ` daniel-eys
2020-12-03  7:31 ` Question: Is there a package for the Nvidia CUDA Kit Frick-David
2021-03-12  4:50 ` WormChickenWizard
2022-04-16  2:02 ` github-actions
2022-04-19 13:20 ` WormChickenWizard
2022-04-19 17:16 ` Duncaen
2022-05-25 14:02 ` [Package request] " soanvig
2022-06-03  7:02 ` jjc224
2022-06-03  7:03 ` jjc224
2023-04-30 20:16 ` DirtyVoid
2023-10-03 20:47 ` namgo
2023-11-05  3:49 ` mcneb10
2023-11-05  3:56 ` mcneb10
2023-11-05  4:07 ` mcneb10
2023-11-05  9:17 ` mcneb10
2023-12-04 18:57 ` namgo
2023-12-04 18:59 ` namgo
2023-12-04 19:46 ` namgo
2023-12-04 23:58 ` mcneb10
2023-12-05 12:26 ` namgo
2023-12-05 13:06 ` namgo
2023-12-05 13:09 ` namgo
2023-12-05 13:17 ` namgo
2023-12-05 13:25 ` namgo
2023-12-05 13:29 ` namgo
2023-12-05 14:52 ` namgo
2023-12-05 15:07 ` namgo [this message]
2024-01-28 16:08 ` atisharma
2024-02-23 19:37 ` namgo
2024-03-31  2:24 ` jlhamilton777

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=20231205150758.CaBxMf8837cWRAzYdwVD6H4MhbeNnFZieCmcA-n5arg@z \
    --to=namgo@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).