cancel
Showing results for 
Search instead for 
Did you mean: 

AI Discussions

Akuma_Na_Tata
Journeyman III

can't install rocm 6.2.3 on my radeon gpu

Hello, i have an rx 7900xtx and my main goal in to install onnxruntime. But It doesn't seem to be available with rocm 6.2.2 so i installed ubuntu 22.04.5LTS and tryed to install rocm 6.2.3. It is not working. when i type the command: "amdgpu-install -y --usecase=graphics,rocm", i have this error message: "E: Failed to fetch https://repo.radeon.com/amdgpu/6.2.3/ubuntu/dists/jammy/main/binary-amd64/Packages.gz File has unexpected size (14796 != 14502). Mirror sync in progress? [IP: 2.23.13.7 443]"

I'm a bit lost, amd is making a driver for radeon gpus that can't even be installed. So how will i install onnxruntime and use comfyui DW poses properly?

1 Solution

Hello, I issued this error in the github rocm web page and it is now fixed (it wasn't related to sudo apt update and was more complicated than that). Anyway. I'm now happy that it works. Have a great day.

View solution in original post

2 Replies
fawodiran
Journeyman III

According to the Linux support matrices by ROCm version documentation:  

ONNX Version 1.18 is compatible with ROCm Version 6.2.3

 

The error I saw in your comment isn't related to ROCm or ONNX:

"E: Failed to fetch https://repo.radeon.com/amdgpu/6.2.3/ubuntu/dists/jammy/main/binary-amd64/Packages.gz File has unexpected size (14796 != 14502). Mirror sync in progress? [IP: 2.23.13.7 443]"

 

That's a APT package manager error, meaning you try to run this command "amdgpu-install -y --usecase=graphics,rocm" without run a "sudo apt update" first, because the metadata for this file: "Packages.gz" changed you OS is expecting a size of 14796 from local repo cache information but online repo indicate a size of 14502. This could be solved with a "sudo apt update". try 


Reference:
https://rocm.docs.amd.com/projects/radeon/en/latest/docs/compatibility/native_linux/native_linux_com... 

0 Likes

Hello, I issued this error in the github rocm web page and it is now fixed (it wasn't related to sudo apt update and was more complicated than that). Anyway. I'm now happy that it works. Have a great day.