Github messages for voidlinux
 help / color / mirror / Atom feed
From: bobertlo <bobertlo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: cuda
Date: Wed, 29 Dec 2021 15:27:46 +0100	[thread overview]
Message-ID: <20211229142746.lsZZmdPzNL2qvp4xgMwTaFCmvjKiGd_rTfvw8PxIheg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31984@inbox.vuxu.org>

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

New comment by bobertlo on void-packages repository

https://github.com/void-linux/void-packages/issues/31984#issuecomment-1002598948

Comment:
To my surprise, CUDA is included with the proprietary NVIDIA packages.

```
nvidia-libs-470.94_1	/usr/lib/libcuda.so -> /usr/lib/libcuda.so.470.94
nvidia-libs-470.94_1	/usr/lib/libcuda.so.1 -> /usr/lib/libcuda.so.470.94
nvidia-libs-470.94_1	/usr/lib/libcuda.so.470.94
```

I was able to install pytorch, `torch.cuda.is_available()` returns true, and the mnist example trains a model.

This issue could be closed (edit maybe not?) but I view this as a documentation issue since there is absolutely no mention of cuda in any package descriptions or documentation. If you google cuda void linux you find multiple open package requests and reports that cuda is not available or supported.

EDIT: I am unclear about what else is generally provided with CUDA. I think conda is actually pulling in a lot of the runtime. I will try to look into what is missing and may be required for other native packages wanting cuda. What is included already is enough for me, and I think enough to get nvidia-docker running. I wanted to share this because I was about to just multiboot (while looking at possibly packaging cuda) based on the information I found about cuda on void.

  parent reply	other threads:[~2021-12-29 14:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 17:55 [ISSUE] " lastrodamo
2021-07-25 15:46 ` xslendix
2021-12-29 13:38 ` bobertlo
2021-12-29 14:27 ` bobertlo [this message]
2022-12-18  6:49 ` cl3m3c7
2022-12-18  8:19 ` bobertlo
2022-12-18  8:21 ` bobertlo
2022-12-18 14:34 ` cl3m3c7
2024-04-04 15:54 ` [ISSUE] [CLOSED] " classabbyamp
2024-04-04 15:54 ` classabbyamp
2024-04-04 15:54 ` [ISSUE] [CLOSED] " classabbyamp

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=20211229142746.lsZZmdPzNL2qvp4xgMwTaFCmvjKiGd_rTfvw8PxIheg@z \
    --to=bobertlo@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).