unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: Lars-Dominik Braun <lars@6xq.net>
To: Zacchaeus Scheffer <zaccysc@gmail.com>
Cc: guix-science@gnu.org
Subject: Re: Freeing Machine Learning with ROCm
Date: Mon, 25 Apr 2022 08:31:09 +0200	[thread overview]
Message-ID: <YmZALT6hxKX5MWxI@noor.fritz.box> (raw)
In-Reply-To: <CAJejy7m-PS3BQZtoEiBSE5uMXHsdjjOPhsayJ3a-2U50jMkZCg@mail.gmail.com>

Hi Zacchaeus,

I packaged ROCm for Guix.

> Based on the fact that many ROCm packages exist in guix, and
> that I don't see people complain, it seems it must have worked in the
> past.
Indeed, I am using Guix’ darktable and rocm-opencl-runtime packages
for OpenCL-accelerated photo editing. But I’m also doing this on a
foreign distribution with a custom kernel (5.15) – not Guix System.

> > ROCk module is loaded
> > Unable to open /dev/kfd read-write: No such file or directory
> > <my username here> is member of video group
Which GPU are you using? Can you see it with `lspci` and does it have the
`amdgpu` driver attached? Is the firmware loaded (`dmesg | grep amdgpu`,
I’m guessing no, since you use linux-libre)?

> In retrospect, could it maybe be that I can use the card without probing it
> with rocminfo?  It would certainly be nice to be able to check the
> temperature (especially so I don't have to leave the fan on full blast)
> among other things, but maybe that isn't strictly necessary for doing
> machine learning on it?
rocminfo does not show the card’s temperature. You need this[1]
(unpackaged) tool.

Cheers,
Lars

[1] https://github.com/RadeonOpenCompute/rocm_smi_lib/tree/master/python_smi_tools



  reply	other threads:[~2022-04-25 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23  5:14 Freeing Machine Learning with ROCm Zacchaeus Scheffer
2022-04-25  6:31 ` Lars-Dominik Braun [this message]
2022-04-26  4:45   ` Zacchaeus Scheffer
2022-04-26  6:24     ` Lars-Dominik Braun

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YmZALT6hxKX5MWxI@noor.fritz.box \
    --to=lars@6xq.net \
    --cc=guix-science@gnu.org \
    --cc=zaccysc@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).