Amd released Rocm 6.4

[muziqaz]

Don't add amdgpu, actually remove amdgpu.
AMD has drivers in the kernel. I'm waiting for thread editing permissions here, I need to edit my guide. To simplify it even more, or complicate more

[arisu]

I had installed amdgpu-install_6.2.60203-1_all.deb which automatically added both of those. It doesn't pull in the driver which is as you say a kernel module already included (thank god they don't do dkms). It just pulls in some tools I think. I can remove it anyway.

Should it be as simple as this?

Code: Select all

# systemctl stop fah-client
# sed -i 's/6.2.3/6.4/g' /etc/apt/sources.list.d/*.list
# apt update
# apt -y upgrade
# systemctl start fah-client

[muziqaz]

I wouldn't be able to advise you of Linux command line magic. My knowledge goes as far as the best duck duck go search result
But, yes, swapping 6.3.4 to 6.4 should do it

[DarkFoss]

If just updating the sources fail you probably have to update the gpg key 1st. I kept amdgpu as a source even though I'm not using dkms maybe additional firmware updates pulled from there. I tend to error on the side of caution.

Tax day so I'm folding from Win and from what I'm seeing there really isn't any performance penalties incurred for folding on Linux, as always ymmv.

[arisu]

I switched to 6.4 on Debian 12. The installation went smoothly but initially FAH couldn't see my GPU anymore. It turns out that 6.4 has no rocm-opencl-icd-loader which provided the symlink libOpenCL.so -> libOpenCL.so.1. So to get it to work I had to do this:

Code: Select all

$ sudo ln -s /usr/lib/x86_64-linux-gnu/libOpenCL.so.1 /usr/lib/x86_64-linux-gnu/libOpenCL.so

And then FAH picked up the GPU. I haven't started folding on it yet though.

[muziqaz]

You are symlinking a symlink
Better symlink libOpenCL.so.1.0.0

[arisu]

It's harmless to symlink a symlink. I'm just doing it the way that other ROCm libraries are like these:

Code: Select all

$ ls -lh /opt/rocm-6.4.0/lib/librocm-core*
lrwxrwxrwx 1 root root  17 Apr  2 18:26 /opt/rocm-6.4.0/lib/librocm-core.so -> librocm-core.so.1
lrwxrwxrwx 1 root root  25 Apr  2 18:26 /opt/rocm-6.4.0/lib/librocm-core.so.1 -> librocm-core.so.1.0.60400
-rw-r--r-- 1 root root 17K Apr  2 18:26 /opt/rocm-6.4.0/lib/librocm-core.so.1.0.60400

Either way works, but the "standard" is for the less specific library names to symlink to the more precise ones, like libfoo.so -> libfoo.so.x -> libfoo.so.x.y.

The best solution is for AMD's packages to include the symlink natively like they did in 6.2.3. I don't know why they removed it. Surely they tested their own package before releasing it.

[muziqaz]

It is not harmless
I've done enough fiddling with AMD related .so files to pick few snags along the way. Symlink it to original file which is .so.1.0.0 in the same x86...GNU directory
And let's not talk about why they removed stuff compared to previous rocm versions
It is a miracle they listened to me to include rocm-opencl-sdk within 6.3.4 and now 6.4

[arisu]

Oh that's interesting. If it's not harmless then AMD is doing something odd.

What happens? It resolves fine now. Do they break the middle symlink on upgrades or something?

[muziqaz]

They break many things. While fixing other things, and not keeping to the same system of filing things. Let's leave it at that