Github messages for voidlinux
 help / color / mirror / Atom feed
From: TeddyDD <TeddyDD@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Rocm
Date: Sun, 12 Jan 2025 03:44:41 +0100	[thread overview]
Message-ID: <20250112024441.7AA352212E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53819@inbox.vuxu.org>

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

New comment by TeddyDD on void-packages repository

https://github.com/void-linux/void-packages/pull/53819#issuecomment-2585549288

Comment:
Okay so I've been testing this, since so far the only way I managed to get ROCm on Void is to copy /opt/rocm from distro.

- ollama compiled with ROCm support works
- darktable is not working, **[opencl](https://github.com/ROCm/clr/tree/develop/opencl) runtime is missing
- You won't be able to compile ollama since [hipblas](https://github.com/ROCm/hipBLAS) is not packaged.
- Blender works

<details><summary>clinfo output</summary>
<p>

<pre>
darktable 5.0.0
Copyright (C) 2012-2024 Johannes Hanika and other contributors.

Compile options:
  Bit depth              -> 64 bit
  Debug                  -> DISABLED
  SSE2 optimizations     -> ENABLED
  OpenMP                 -> ENABLED
  OpenCL                 -> ENABLED
  Lua                    -> ENABLED  - API version 9.4.0
  Colord                 -> ENABLED
  gPhoto2                -> ENABLED
  GMIC                   -> ENABLED  - Compressed LUTs are supported
  GraphicsMagick         -> ENABLED
  ImageMagick            -> DISABLED
  libavif                -> ENABLED
  libheif                -> ENABLED
  libjxl                 -> ENABLED
  LibRaw                 -> ENABLED  - Version 0.22.0-Devel202403
  OpenJPEG               -> ENABLED
  OpenEXR                -> ENABLED
  WebP                   -> ENABLED

See https://www.darktable.org/resources/ for detailed documentation.
See https://github.com/darktable-org/darktable/issues/new/choose to report bugs.

     0.2977 [dt_get_sysresource_level] switched to 2 as `large'
     0.2978   total mem:       64203MB
     0.2978   mipmap cache:    8025MB
     0.2978   available mem:   43889MB
     0.2978   singlebuff:      1003MB
     0.2982 [opencl_init] opencl disabled via darktable preferences
     0.2983 [opencl_init] opencl library 'libOpenCL' found on your system and loaded, preference 'default path'
     0.3456 [opencl_init] found 2 platforms
     0.3456 [check platform] platform 'Clover' with key 'clplatform_clover' is NOT active
     0.3456 [check platform] platform 'rusticl' with key 'clplatform_rusticl' is NOT active
[opencl_init] found 0 device
     0.3456 [opencl_init] FINALLY: opencl PREFERENCE=OFF is NOT AVAILABLE and NOT ENABLED.
</pre>

</p>
</details> 

  parent reply	other threads:[~2025-01-12  2:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 23:56 [PR PATCH] Rocm llvm19 Calandracas606
2025-01-03  0:02 ` [PR PATCH] [Updated] Rocm Calandracas606
2025-01-03  0:26 ` Calandracas606
2025-01-09  9:29 ` Rocm hervyqa
2025-01-12  2:27 ` Rocm TeddyDD
2025-01-12  2:44 ` TeddyDD [this message]
2025-01-12  2:54 ` Rocm TeddyDD
2025-01-14 13:13 ` Rocm Calandracas606
2025-01-14 13:14 ` Rocm Calandracas606
2025-01-14 21:48 ` Rocm TeddyDD

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=20250112024441.7AA352212E@inbox.vuxu.org \
    --to=teddydd@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).