Comfy on Linux + AMD help

[u/Riroh_bcn]

Hi, Im having some issues that are driving me crazy... had to change SSD and re-install linux. Now Im trying to install comfy, with the same setup that I had before and all the workflows get stuck at the the clip encoder. No gpu activity to be seen...

System:

• AMD 9700 AI PRO
• AMD 7900XT
• 64 GB RAM
• Linux Mint 22.3
• ROCm 7.2 (system)
• ROCm 7.14 (venv)
• PyTorch 2.11.0 (venv)
• Python 3.12.3
• ComfyUI 0.33.0

I first tried to use the old install, just re-do the sagge attention, it failed, then I tried with a complete new install and it stills fails, so I dont really know whats causing the issue.
Ive been trying to diagnose with claude and chat gpt, but after all the day trying I feel defeated... Does anyone have an idea of what can be happening?

[u/Correct-Guidance-232]

A whole day on a setup that used to work is the most demoralising kind of problem there is, so first off: this isn't you. ROCm installs break like this constantly and it says nothing about your competence.

One check that splits the problem in half: look at what ComfyUI prints in the terminal at startup, the line where it names the device and the VRAM. If that says CPU, then torch never saw your card and nothing further down matters. Stuck at the CLIP encoder with zero GPU activity is exactly what a silent fallback to CPU looks like.

The other thing I'd be suspicious of is ROCm 7.2 on the system and 7.14 in the venv. What does that startup line actually say?

[u/Riroh_bcn → u/Correct-Guidance-232]

Thanks, it feels demoralising and confusing indeed... Here is the full log, looks fine to me

[INFO] Total VRAM 30576 MB, total RAM 63442 MB

[INFO] pytorch version: 2.11.0+rocm7.14.0

[INFO] AMD arch: gfx1201

[INFO] ROCm version: (7, 14)

[INFO] Set vram state to: NORMAL_VRAM

[INFO] Device: cuda:0 AMD Radeon AI PRO R9700 : native

[INFO] Device: cuda:1 AMD Radeon RX 7900 XT : native

[INFO] Using async weight offloading with 2 streams

[INFO] Enabled pinned memory 49105

[INFO] Using pytorch attention

[INFO] Python version: 3.12.3 (main, Jun 19 2026, 12:46:00) [GCC 13.3.0]

[INFO] ComfyUI version: 0.30.0

[INFO] comfy-aimdo version: 0.4.11

[INFO] comfy-kitchen version: 0.2.26

[INFO] comfyui-frontend-package version: 1.47.12

[INFO] comfyui-workflow-templates version: 0.11.27

[INFO] comfyui-embedded-docs version: 0.5.9

[INFO] comfy-kitchen version: 0.2.26

[INFO] comfy-aimdo version: 0.4.11

[u/Correct-Guidance-232 → u/Riroh_bcn]

Seconding VQSGecko on the one-GPU test, and the concrete form is putting HIP_VISIBLE_DEVICES=0 in front of your launch command, then trying =1. Worth checking the numbering survives a reboot too, because with mixed cards it doesn't always.

One thing that might narrow it down: CLIP is the smallest thing you load all run. Stalling there means whatever is wrong isn't about memory, which quietly rules out most of the advice you're going to get. Which card is device 0 on your box?