24
AMD GPU driver with opencl support?
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 May 2024
24 points (90.0% liked)
Linux
48376 readers
1195 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
I tried both suggestions, as well as running it without the variables changed. On all three of them, hashcat said "Device #3: Unstable OpenCL driver detected!" when I ran hashcat -I (device info if your not familiar with hashcat). I tried running the benchmark, and it crashed saying "Device #1: Kernel /usr/lib64/hashcat/OpenCL/shared.cl build failed."
Edit: I looked, and I don't see a package called rocm-ocl, nor can I install one. Edit2: Wait nvm, I see rocm-opencl, and I assume that's it.
Ah man, are you able to verify OCL working with other applications such as OpenShot or Blender?
As for your edit, sorry you're correct, the package name is
rocm-opencl, otherwise referred to asrocm-opencl-runtimeWell I tried an opencl benchmark I found, and my computer has fuckied a major wucky...
Edit: reboot fixed it but it seems opencl is super unstable on here. I ran hashcat again, this time with --force, and found that it did nothing, then there were weird colors, then plasmashell crashed. Luckily plasmashell has good crash handling and it was able to go back up so I could see that hashcat reported something about gpu hang being the reason for the crash.
Oh damn, can you send me a link to that? I'll also try Hashcat + its benchmark when I get the chance.
Reaching out to a friend who has some familiarity with HC in the mean time.
Https://github.com/projectphysx/opencl-benchmark
cheers, will give that a look
The OpenCL benchmark for me worked without any issues.
The Hashcat benchmark threw the same errors as you'd seen until I manually specified my device (my friend was able to point me in the right direction here).
You can enumerate your OpenCL device (i.e. your GPU) with something like clinfo, rocm-clinfo.
I had to run Hashcat's benchmark like so:
hashcat -b -d 2where 2 is my RX 6800XTHope this helps
I did notice it was the wrong device, however when I specify it crashes the whole os with some artifacting. I may look into other values for that environment variable tomorrow. I also might try rusticl.