-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to import AMDGPU fails with (an lvm?) error #579
Comments
My guess is that HIP is built with statically linked LLVM in Fedora, when it probably should link dynamically. |
You can check if this is true by dev'ing [AMDGPU]
use_artifacts = true Then try importing it again. Artifacts don't have all the libraries and are of older ROCm version, but at least you'll be able to confirm that dynamically linked LLVM is what you need. |
Thanks. Tried creating |
Managed to force artifacts through |
Forgot to mention that you then need to launch julia with project set to the AMDGPU.jl folder:
Otherwise, you should put that file where your current project is (and modify project path accordingly). The downside of artifacts is that you can use only Julia kernels, so things like matmul (rocBLAS) are not available (and other stuff). Будь ласка :) |
Most tests pass, 263 errored, 19 broken. Back to the original issue, my system library has
To provide you the context, I am looking into porting this small CUDA PoC https://github.com/jinwen-yang/cuPDLP.jl/tree/master to run on my 6600. It does not look like there is a lot to port (uses zeros, norm, dot and sparse arrays). But maybe sparse arrays or something else are out of the question until I resolve the original q? |
Mine looks like this:
Not really sure what to suggest besides recompiling HIP without linking against LLVM, but then you'd need to change this line to point to your As an alternative approach, I prefer to get ROCm from the official install script which links dynamically, but it does not have Fedora support. |
Making some connections: Here's a thread on a Julia forum about this issue. One post there suggests the problem comes from how the ROCm .so file is opened: |
I can confirm that patching |
We can then add a set of predefined locations where we'll look for instead of relying on |
Not sure where from to approach. Platform is Fedora 39
Traced it down to this
The text was updated successfully, but these errors were encountered: