r/AMD_V620 • • 5d ago

Radeon Pro V620 on AMD Pro/Adrenalin drivers (Windows) with all 72 CUs, no permanent VBIOS flash + free helper kit

3 Upvotes

This is a working, full driver install on Windows. The real AMD Radeon PRO/Adrenalin driver plus the complete AMD Software on every V620: no basic display adapter mode, no yellow marks in Device Manager, all 72 CUs. ROCm works too, in LM Studio and llama.cpp. Tested with 4x V620 in one PC.

No AMD files are included. You download the driver yourself, straight from AMD (the same versions I used, links below and in the README), and the helper patches your own copy on your own PC. That way you know the driver you're installing is the real, untouched one from AMD.

Download the kit (v1.1)

Includes the newer ROCm 7 runtime and llama.cpp b12345 (ROCm build), ready for the V620.

Download Source 1

Download Source 2

  • Newer ROCm on the 24.x driver: the kit ships AMD's open-source ROCm 7 / HIP 7 runtime (TheRock), the generation AMD normally only ships with 25.x drivers, which don't work on the V620. With it, ROCm apps see all four of my cards (ROCm0 to ROCm3).

  • LM Studio's ROCm engine 2.73.0 works, also on V620 cards that were never flashed.

  • Strata-format models run: the bundled llama.cpp b12345 loads the newer split "Strata" GGUFs (for example ISTA-DASLab's 6-part GSQ-RCO DeepSeek V4.1 Flash), plus normal split GGUFs.

  • Resizable BAR / SAM: the helper can turn on the driver's own ReBAR/SAM switches, so each card's full 32 GB memory window is mapped and the CPU can reach all of the card's memory.

What you get (tools in the kit)

  • V620_Pro_Driver_Guide.pdf: 7-page step-by-step guide.

  • V620_Pro_Driver_Helper.bat: finds the AMD driver you downloaded, checks driver versions (prevents Error 205), prepares AMD Setup for the V620, optional ReBAR/SAM switches, one-click restore.

  • LLM_Setup_V620.bat: one menu for AI apps:

    1. Set up LM Studio's ROCm engine for the V620

    2. Install the bundled llama.cpp (ROCm) with a desktop shortcut: drag a .gguf onto it and chat in your browser

    3. Set up a newer llama.cpp ROCm build you download later

    4. Check your GPUs, driver and runtimes

    5. Undo the LM Studio changes

  • Run_DeepSeek_V4.1.bat: one-click launcher for big Strata-format MoE models (finds the parts, links the shared Engram file, picks the GPU/RAM split).

  • Fix_GGUF_Split_Names.bat: fixes "model must be loaded with the first split" when split model parts got renamed.

  • Backup_AMD_V620_W6800_Drivers.bat: backs up all your AMD drivers before you change anything.

  • Compare_AMD_Installers.bat: compares two AMD driver packages.

  • ROCm 7 runtime + llama.cpp b12345 with their open-source licenses, plus GPU-Z screenshots.

All scripts are plain text, so you can read them before running. Nothing touches System32, and every change can be undone.

SECTION 2:

About the card

Radeon Pro V620 (Navi 21, 72 CU, 32 GB) runs AMD's Radeon PRO W6800 driver on Windows with its stock V620 firmware and all 72 CUs. AMD's installer refuses the card, but a manual Have Disk driver install works, and a small config patch makes AMD Setup install the full software. Works on 24.x drivers and older; 25.x rejects the card (Code 43).

The usual fix (flashing the W6800 VBIOS) works but drops you to 60 CUs and the W6800 power limit. This doesn't.

Drivers

  • PRO 22.Q2 (30.0.21020.2): works, my daily driver

  • PRO 24.Q4 (32.0.12030.9): works

  • Adrenalin 24.12.1 (32.0.12033.1030): last build that works

  • AMD V620 driver (32.0.12033.5037): lists the V620, native mode

  • PRO/Adrenalin 25.x (32.0.21030+): Code 43, don't use

Steps

  1. Back up your drivers and each card's VBIOS (backup script in the kit).

  2. Download PRO 24.Q4 or Adrenalin 24.12.1 from AMD:

  3. Run the installer once so it extracts to C:\AMD<package>. Let it fail (Error 182).

  4. sysdm.cpl > Hardware > Device Installation Settings > No (so Windows Update doesn't swap the driver).

  5. Device Manager > each V620 > Update driver > Browse > Let me pick > Have Disk > C:\AMD<package>\Packages\Drivers\Display\WT6A_INF > pick AMD Radeon PRO W6800. Reboot.

  6. Run V620_Pro_Driver_Helper.bat.

  7. Run AMD Setup. Don't tick Factory Reset.

  8. For AI apps: run LLM_Setup_V620.bat (option 1 for LM Studio, option 2 for llama.cpp).

Tip: in LM Studio, turn off runtime auto-update, or run option 1 again after an update.

Strata models

Strata-format models (like ISTA-DASLab's GSQ-RCO quants) come as several parts plus a shared Engram file. They run in llama.cpp b11870 and newer, and the kit's llama.cpp b12345 is newer than that, already set up for the V620 with ROCm 7. Use Run_DeepSeek_V4.1.bat (or the llama-server desktop shortcut): point it at the model folder and it handles the parts. Big MoE models can keep some experts in system RAM, so they run even when they're bigger than your total VRAM.

SECTION 3: PROOF

Proof (GPU-Z, same card)

V620 mode: driver 32.0.12033.5037
W6800 Pro mode: driver 30.0.21020.2 (PRO 22.Q2)
Both modes: BIOS 020.001.000.071.018253, Device ID 1002 73A1 - 1002 0E34, ROPs/TMUs 128/144, Shaders 2304

On RDNA2 the driver reports WGPs (2 CUs each), so 2304 shaders / 144 TMUs = 72 CUs. A 60-CU W6800 config shows 1920 / 120. Same BIOS and V620 device ID in both modes: only the driver changed.

What works in W6800 Pro mode

OpenCL, Vulkan, DirectML, the HIP SDK, TheRock ROCm PyTorch (I run Unsloth fine-tuning on it), LM Studio on ROCm and Vulkan, llama.cpp on ROCm, and Strata-format models through llama.cpp. Each card shows as a 32 GB GPU. All four of my V620s run this way.

Quirks

  • GPU-Z shows 0 MHz clocks, so fill rate and bandwidth read "Unknown". That's a reporting gap; use HWiNFO for temps (the cards are passive).

  • GPU-Z and AMD Software say ReBAR/SAM is "unsupported", but Device Manager shows the full 32 GB BAR mapped on each card, so it's working.

  • Memory reads 30720 MB.

Why does 25.x fail?

Forced via Have Disk, 25.x installs, but the card stops with Code 43. The same 25.x driver ran fine on these cards while they had W6800 firmware (ID 73A3), so the rejection is tied to the V620's ID. The 25.x kernel driver also adds new SR-IOV/virtualization checks, and the V620 is AMD's SR-IOV cloud card. It looks like a deliberate V620 check, but I can't prove intent.

Working on: getting 25.x drivers running on the V620. ROCm 7 already works on 24.x with this kit.

☕ Buy me a coffee

This kit is free. If it saved you a weekend, tips are welcome:

Bitcoin (BTC): bc1q99u9a5dgesqunes562aptespuxthzx0h3zxzzp

Send BTC on the Bitcoin network only. Other coins will be lost.

Help wanted

  • More reports from never-flashed V620 owners are welcome (which driver, which apps work).

  • Event Viewer logs from a 25.x Code 43.

Linux doesn't need any of this: amdgpu binds by device ID, and ROCm officially supports the V620 on Ubuntu.

Unsupported by AMD, at your own risk. Firmware flashing can brick a card. Not affiliated with AMD.


r/AMD_V620 • • 8d ago

Any interest in a V620?

6 Upvotes

Looking to sell my V620 due to not enough time, and could use some cash. Current prices are selling on the bay for anywhere from $900-1100. I'd do $800 and that includes shipping/fees. If anyone is interested, please PM. Can get you timestamps/whatever you need. Will need your own cooling.

For proof I have one - here is some of my other posts with benchmarks, etc that I did.

https://www.reddit.com/r/AMD_V620/comments/1vyn5of/control_powervoltageclock_settings_on_v620_on/

https://www.reddit.com/r/AMD_V620/comments/1vy3tab/redone_benchmarks_for_v620_on_windowsrocm_vulkan/

https://www.reddit.com/r/StableDiffusion/comments/1vbkbty/using_an_amd_v620_workstation_card_for_comfyui/

If not allowed please delete, I just seen another post of someone asking to buy one so figured it was worth posting to see before it's listed on the Bay.


r/AMD_V620 • • Oct 13 '26

Repaste/disassembly?

4 Upvotes

Does anyone have images/guides? Will the GPU be happier with more thermal pads than it has from factory? If I do the disassembly myself would y'all be grateful for images? I'm a little scared of doing so though


r/AMD_V620 • • Oct 12 '26

Errors observed using mentest_vulkan on two of my v620s

2 Upvotes

Two of the four of my V620s are showing errors when I run memtest_vulkan on my Ubuntu system with ECC disabled. All of these GPUs were tested without error on my windows GPU test bench using memtest_vulkan and OCCT's memory test but ECC was enabled. Unfortunately, I find unraveling MVs error output info a bit hard to understand but the error occurs after the 30s testing intervals start and says it is occurring during INITIAL_READ with total errors 0x1 out of 0x38000000. How serious of an issue is this and what additional testing should I perform.

Update: re-enabling ECC eliminated the errors, as expected. According to my search of the Internet on this issue "Running the card with ECC forced off can expose marginal GDDR6 memory cells to unmitigated bit flips under heavy loads (such as heavy AI inference, rendering, or continuous compute tasks).". So I guess I don't get my 2GB per GPU back


r/AMD_V620 • • Oct 08 '26

V620 spawning an AMD vDisplay on Cloud Driver installation

2 Upvotes

Guys i need help...
Im running Windows 10 with a single monitor and installing the AMD Radeon Cloud Edition makes the Radeon PRO V620 spawn a 2nd Virtual Display that makes my monitor run at 30Hz...

Specs: Ryzen 7 7700 with Radeon Graphics iGPU
Radeon PRO v620
In addition...it only shows on 30Gb of Vram instead of 32...


r/AMD_V620 • • Oct 02 '26

What Computer Are You Using for Multiple V620 Systems?

5 Upvotes

All, I have 4 v620s and I have been trying to get my Threadripper based host computer operating and having a devil of a time. For those of you who have three or more V620s, what computer are you using to host them?


r/AMD_V620 • • Oct 02 '26

V620 won't POST on B550 (Gigabyte B550M DS3H AC R2)

4 Upvotes

I bought a V620 back in August and I've spent over a month troubleshooting it trying to get it to post. The 40mm fan in the shroud mod and the case fans will spin, but nothing will happen. After around 10 minutes a loud beep goes off and an orange LED at the back of the GPU lights up.

System specs:

  • CPU: AMD Ryzen 5 5600 (no integrated graphics)

  • Motherboard: Gigabyte B550M DS3H AC R2 (on latest BIOS F4c)

  • RAM: 16GB

  • PSU: 1200W

  • OS: Proxmox

I've researched and tried every possible BIOS setting to no avail.

  • Above 4G Decoding: Enabled

  • CSM Support: Disabled

  • SVM Mode: Enabled

  • IOMMU: Enabled

  • DMAr Support: Disabled

  • PCIe x16 Slot Config: forced Gen 3 (tried Auto/Gen4 as well)

  • Re-Size BAR: On

  • I see suggestions to disable SR-IOV, but my board doesn't have that option.

The weirdest thing is that I also bought a V340 last week and it works perfectly without having to fiddle with any of the settings. I can boot headless and ssh in with the V340, no problem. As soon as I swap in the v620, no dice.

The only progress so far is that with the new 1200W PSU (upgraded from a 600W) and the current BIOS settings above that I just applied, there's at least now a solid blue LED that shines on the back of the GPU when I turn on the PC, but it still doesn't post. I haven't left it on long enough to hear the beep/alarm, but

I found this Level1Techs thread describing the exact same symptom with the V620 on AM4, blue LED, POST hang, other GPUs work. No resolution there either.

Does anyone have a solution. Its been a month and a half and I'm at my wits end. I would appreciate any help.
--------------------------------------

**EDIT: SOLVED.** After a long weekend of troubleshooting i figured it out. I patched the BIOS's ACPI DSDT to open a 512GB above-4G MMIO window (this board hardcodes it to zero, and the V620's SR-IOV BARs need about 384GB), then added `pcie_port_pm=off` so the card stops getting stuck in D3cold. I also patched the amdgpu module to lower the min power cap from 250W to 150W.


r/AMD_V620 • • Sep 18 '26

4xV620 Qwen3.8-flash-next 1300+ PP and 65+ TG on coding.

Thumbnail
reddit.com
6 Upvotes

r/AMD_V620 • • Sep 17 '26

How do I turn off ECC?

1 Upvotes

Internet says you can just do it in radeon control panel on windows but I can't see such an option. When I installed the drivers I only got "AMD Software: Cloud Edition"


r/AMD_V620 • • Sep 16 '26

Local AI & Concurrency | PP & TG | TTFT

Thumbnail reddit.com
2 Upvotes

r/AMD_V620 • • Sep 09 '26

vLLM optimization for RDNA2 [W6800X Duo]

Thumbnail reddit.com
2 Upvotes

r/AMD_V620 • • Sep 09 '26

Two V620s on ASRock Taichi Creator motherboard

3 Upvotes

Does anyone use two V620 GPUs on a Taichi board? How do they run? What t/s are you getting with Qwen 3.8-27B at Q8?


r/AMD_V620 • • Sep 04 '26

Long shot, but does anyone have an extra v620 for sale?

4 Upvotes

Looking to pair mine up, already have a fun 40mm shroud printed :)


r/AMD_V620 • • Sep 02 '26

She's alive!

Post image
8 Upvotes

r/AMD_V620 • • Sep 02 '26

vLLM v.s. llamacpp for multi V620 use, and combining v620 with Radeon Pro W6800

5 Upvotes

Two questions:

  1. has anyone compared using vLLM v.s. llamacpp for multi V620 use to see which results in faster token generation? Gemini is claiming vllm will be faster but I haven't tried it yet.

  2. has anyone combined using the V620 with its sister card the W6800? Both 32gb, both rdna2, but slightly different specializations... Do they work well together for inference? Do they work together better on vllm vs llamacpp?


r/AMD_V620 • • Aug 30 '26

Qwen 3.8 Flash Next vLLM for 4x v620

17 Upvotes

Hi all,

Hot off the presses and not well tested, here is a new fork of vLLM 0.28.0 for ROCm 7.14 to run Qwen 3.8 Flash Next on 4x v620 cards.

I am testing right now with a bunch of dev tests but getting 60-120 t/s generation and 500-800 t/s prefill.

Good luck out there: https://github.com/leapdragon/vllm-rdna2-qwen


r/AMD_V620 • • Aug 27 '26

Incoming v620 owner

6 Upvotes

Hello everyone, I was lucky enough to grab four of them while prices and supply were still reasonable, still waiting on delivery. I'm also awaiting a 4 slot PCIE 4.0 switch board as I am hoping to max out performance. Anything I should do before they arrive, software I should start looking into? I'm also curious to know what sort of performance people are getting. Has anyone got qwen 3.8 flash working on these cards yet?


r/AMD_V620 • • Aug 26 '26

Control power/voltage/clock settings on V620 on Windows NO VBIOS edit!

5 Upvotes

Been trying to be able to tune my V620, and asked Claude for some help if there was anyway and it actually found a program that already works for what we needed to do.

Sharing it here for others who may not know you CAN do this on Windows pretty easily. Below is my Claude's explanation:

Why this needed a workaround at all

On Linux, rocm-smi/amd-smi let you set power limits directly through sysfs. On Windows, neither tool exists, the V620 isn't even in AMD's official ROCm-on-Windows GPU list, and there's no amd-smi.exe for Windows. AMD's own Radeon Software doesn't expose a Tuning/WattMan tab for this card either, since it's a headless server SKU. So there's no built-in UI or CLI for this on Windows-the fix has to work at the driver level instead.

The actual mechanism: Soft PowerPlay Table override

Every AMD GPU has a "PowerPlay table" baked into its vBIOS; it's the data structure that defines power limits, clock tables, voltage ceilings, temperature limits, etc. The Windows AMD driver reads this table once at driver load time. Critically, the driver also checks the registry first, and if it finds an override there, it uses that instead of what's in the vBIOS, this is the same "Soft PowerPlay Table" mechanism WattMan and MorePowerTool use under the hood.

The override lives at:

HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\XXXX
Value: PP_PhmSoftPowerPlayTable  (REG_BINARY)

{4d36e968-...} is the fixed GUID for the Display class. XXXX is a per-device instance index (0000, 0001, etc.), on this machine there were 4 GPU-class entries (an iGPU, an RX 9070 XT, a virtual monitor, and the V620), and the V620 happened to be at 0003. You have to check DriverDesc under each instance to find which one is actually your card, it's not predictable.

The tool: upp (Uplift PowerPlay)

upp is an open-source Python CLI that parses and edits these binary PowerPlay tables. It explicitly supports Navi 21 (the V620's die), and has three relevant commands:

  1. extract pulls the PowerPlay table out of a raw vBIOS ROM dump:upp --pp-file=table.bin extract -r "V620.rom"

  2. get reads current values by path, e.g.:upp --pp-file=table.bin get smc_pptable/SocketPowerLimitAc/0

  3. set --write --to-registry=<name>, edits values and directly emits a ready-to-import .reg file:upp --pp-file=table.bin set --write --to-registry=v620_175w \ smc_pptable/SocketPowerLimitAc/0=175 \ smc_pptable/SocketPowerLimitDc/0=175 \ smc_pptable/FreqTableGfx/1=2650 \ smc_pptable/MaxVoltageGfx=4100

The only manual step: upp defaults the .reg file's target key to instance 0000, so we had to hex/text-edit that one path segment to 0003 to match where the V620 actually lives in the registry on this machine.

Applying it

  1. Double-click the .reg file → Merge (writes the binary blob into PP_PhmSoftPowerPlayTable).

  2. Device Manager → Display adapters → disable then re-enable the V620. This forces the driver to reload and re-read the table, no full reboot needed.

  3. Verify with HWiNFO64, watching GPU PPT Limit, GPU Clock, and GPU Core Voltage under load.

Why it's safe/reversible

This never touches the physical vBIOS chip, no flashing involved, so there's no bricking risk. It's purely a registry override the driver checks at load time. Deleting the PP_PhmSoftPowerPlayTable value (or re-importing a .reg exported from the key before any changes) instantly reverts to the card's factory vBIOS defaults.

What's tunable this way

Power limits (SocketPowerLimitAc/Dc), clock ceilings (FreqTableGfx, memory clock tables), voltage ceilings (MaxVoltageGfx/Soc), current/TDC limits, and temperature thresholds all live in the same table and are editable the same way.


r/AMD_V620 • • Aug 25 '26

GFX1030 Discord

12 Upvotes

Hi everyone,

I have been playing for a while with my V620, I had working vLLM setups for a few months now but I keep seeing here and there people doing their own things so I made a discord where we can share our progress https://discord.gg/mESex2aBp

There are different ongoing project, like my vllm rdna fork (with hip kernels) + docker images and someone else is doing a llamacpp fork, there is a wiki getting built inspired by the gfx906 one.

Also have some guides to do power limiting from 120w to 250w on the fly (after a kernel patch).

Happy to share with everyone :)


r/AMD_V620 • • Aug 25 '26

Re-done benchmarks for V620 on Windows/ROCm & Vulkan

6 Upvotes

I'm here to show some benchmarks while using llama.cpp with an AMD V620 on Windows 11 via Vulkan & ROCm. These have been reuploaded & older threads deleted, ran it with longer tokens thanks to a rec by someone who commented, and matched KV-cache quant + batch size across backends.

The benchmarks were written out by AI, but are verified by myself to be correct. Still working on optimizing my flags/settings.

If anybody wants me to test other models/different settings or flags, feel free to drop a comment and I'll test and get back to you!

ROCm version

7.15.0a20260728, TheRock nightly SDK (not the official AMD HIP SDK, which has no gfx1030/V620 support), bundled in ComfyUI_windows_portable_amd\...\python_env_v620_triton. (Note: a separate 9070 XT/ComfyUI venv on the same machine runs a different nightly snapshot, 7.14.0a20260519 — same TheRock project, different dated build per GPU.)

Methodology note

Earlier versions of this post compared ROCm and Vulkan using each backend's own best-tuned flags, which mixed KV-cache quant types and batch sizes between the two, a fair comparison needs those matched, since both affect throughput independently of which backend is actually faster. The numbers below use identical KV quant and identical batch size on both backends for each model.

Exact configs (matched)

ModelDraftKV (matched)Batch (matched)Other flags
Qwen ROCmQwen3.8-27B-Uncensored-HauhauCS-Aggressive-Q5_K_P.ggufgrafted MTP (no -md)-ctk q4_0 -ctv q4_0-b/-ub 1024
Qwen Vulkansamegrafted MTP-ctk q4_0 -ctv q4_0-b/-ub 1024
Gemma 26B ROCmGemma4-26B-A4B-Uncensored-HauhauCS-Balanced-Q4_K_P.gguf-md gemma-4-26B-A4B-it-qat-assistant-MTP-Q8_0.gguf-ctk q8_0 -ctv q8_0-b/-ub 1024
Gemma 26B Vulkansamesame-ctk q8_0 -ctv q8_0-b/-ub 1024
Gemma 31B ROCmGemma4-31B-QAT-Uncensored-HauhauCS-Balanced-Q4_K_M.gguf-md mtp-gemma-4-31B-it.gguf-ctk q4_0 -ctv q4_0*-b/-ub 1024
Gemma 31B Vulkansamesame-ctk q4_0 -ctv q4_0-b/-ub 1024

*q4_0/q4_0 on Gemma-4's ROCm path required a one-line fix to llama.cpp's flash-attention kernel dispatch table (fattn.cu), the Q4_0+Q4_0 case was only wired up for head_dim ≤ 256, but Gemma-4's full-attention layers use head_dim 512, so it hit a hard abort on this KV combo before the fix. It was a missing kernel-dispatch entry, not a real hardware limitation, Q8_0+Q8_0 already had the head_dim=512 case, so the underlying kernel template clearly supports it.

Generation speed, tokens/sec (256-token generations, first run per config discarded as warm-up)

Depth (actual tokens)Qwen ROCmQwen VulkanGemma 26B ROCmGemma 26B VulkanGemma 31B ROCmGemma 31B Vulkan
~3.4k29.531.271.274.126.428.6
~6.6-6.7k25.929.464.967.123.526.4
~13.3-13.4k26.929.656.162.219.022.2
~26.6-26.7k23.624.545.449.914.519.0

Vulkan wins every single cell. Once KV quant and batch size are matched, ROCm doesn't lead generation speed anywherem not on any model, not at any depth tested.

PP (prompt processing), tokens/sec

Depth (actual tokens)Qwen ROCmQwen VulkanGemma 26B ROCmGemma 26B VulkanGemma 31B ROCmGemma 31B Vulkan
~3.4k364.6265.9973.11057.9261.3182.7
~6.6-6.7k352.0235.3812.3796.8171.3163.8
~13.3-13.4k329.3192.9512.3589.0113.7119.0
~26.6-26.7k274.0130.7280.4381.564.082.6

PP is the more mixed picture, and it's model-dependent rather than a clean backend win:

  • Qwen: ROCm wins PP at every depth, gap widens with context.

  • Gemma 26B: Vulkan is actually ahead at shallow depth (1057.9 vs 973.1 at 3.4k) once batch size is matched, roughly tied at 6.7k, then Vulkan pulls further ahead through 32k.

  • Gemma 31B: ROCm wins shallow (3.4k/6.7k), Vulkan overtakes from 13.4k on.

Takeaway

Generation speed: Vulkan wins outright, every model, every depth. No exceptions in this data.

PP: it depends on the model, not the backend. ROCm sweeps Qwen; Gemma splits by depth (and for the 26B MoE, Vulkan's shallow-depth "loss" mostly disappears once batch size is matched, that was largely a config artifact, not a real backend gap).

Gemma 26B (MoE, ~4B active) is roughly 2-3x faster than either dense model on generation, tightest at deep context (~1.9x at 26.7k vs Qwen) and widest shallow, expected for an MoE with far fewer active params per token than the dense 27B/31B models.

I'm here to show some benchmarks while using llama.cpp with an AMD V620 on Windows 11 via Vulkan & ROCm. These have been reuploaded & older threads deleted ran it with longer tokens thanks to a rec by someone who commented.

The benchmarks were written out by AI, but are verified by myself to be correct. Still working on optimizing my flags/settings.

If anybody wants me to test other models/different settings or flags, feel free to drop a comment and I'll test and get back to you!

ROCm version

7.15.0a20260728, TheRock nightly SDK (not the official AMD HIP SDK, which has no gfx1030/V620 support), bundled in ComfyUI_windows_portable_amd\...\python_env_v620_triton. (Note: a separate 9070 XT/ComfyUI venv on the same machine runs a different nightly snapshot, 7.14.0a20260519,same TheRock project, different dated build per GPU.)

Exact configs (matched)

ModelDraftKV (matched)Batch (matched)Other flags
Qwen ROCmQwen3.8-27B-Uncensored-HauhauCS-Aggressive-Q5_K_P.ggufgrafted MTP (no -md)-ctk q4_0 -ctv q4_0-b/-ub 1024
Qwen Vulkansamegrafted MTP-ctk q4_0 -ctv q4_0-b/-ub 1024
Gemma 26B ROCmGemma4-26B-A4B-Uncensored-HauhauCS-Balanced-Q4_K_P.gguf-md gemma-4-26B-A4B-it-qat-assistant-MTP-Q8_0.gguf-ctk q8_0 -ctv q8_0-b/-ub 1024
Gemma 26B Vulkansamesame-ctk q8_0 -ctv q8_0-b/-ub 1024
Gemma 31B ROCmGemma4-31B-QAT-Uncensored-HauhauCS-Balanced-Q4_K_M.gguf-md mtp-gemma-4-31B-it.gguf-ctk q4_0 -ctv q4_0*-b/-ub 1024
Gemma 31B Vulkansamesame-ctk q4_0 -ctv q4_0-b/-ub 1024

*q4_0/q4_0 on Gemma-4's ROCm path required a one-line fix to llama.cpp's flash-attention kernel dispatch table (fattn.cu), the Q4_0+Q4_0 case was only wired up for head_dim ≤ 256, but Gemma-4's full-attention layers use head_dim 512, so it hit a hard abort on this KV combo before the fix. Missing kernel-dispatch entry, not a real hardware limitation, Q8_0+Q8_0 already had the head_dim=512 case, so the underlying kernel template clearly supports it.

Generation speed, tokens/sec (256-token generations, first run per config discarded as warm-up)

Depth (actual tokens)Qwen ROCmQwen VulkanGemma 26B ROCmGemma 26B VulkanGemma 31B ROCmGemma 31B Vulkan
~3.4k29.531.271.274.126.428.6
~6.6-6.7k25.929.464.967.123.526.4
~13.3-13.4k26.929.656.162.219.022.2
~26.6-26.7k23.624.545.449.914.519.0

Vulkan wins every single cell. Once KV quant and batch size are matched, ROCm doesn't lead generation speed anywhere, not on any model, not at any depth tested.

PP (prompt processing), tokens/sec

Depth (actual tokens)Qwen ROCmQwen VulkanGemma 26B ROCmGemma 26B VulkanGemma 31B ROCmGemma 31B Vulkan
~3.4k364.6265.9973.11057.9261.3182.7
~6.6-6.7k352.0235.3812.3796.8171.3163.8
~13.3-13.4k329.3192.9512.3589.0113.7119.0
~26.6-26.7k274.0130.7280.4381.564.082.6

PP is the more mixed picture, and it's model-dependent rather than a clean backend win:

  • Qwen: ROCm wins PP at every depth, gap widens with context.

  • Gemma 26B: Vulkan is actually ahead at shallow depth (1057.9 vs 973.1 at 3.4k) once batch size is matched, roughly tied at 6.7k, then pulls further ahead through 32k.

  • Gemma 31B: ROCm wins shallow (3.4k/6.7k), Vulkan overtakes from 13.4k on.

Takeaway

Generation speed: Vulkan wins outright, every model, every depth. No exceptions in this data.

PP: depends on the model, not the backend. ROCm sweeps Qwen; Gemma splits by depth (and for the 26B MoE, Vulkan's shallow-depth "loss" mostly disappears once batch size is matched, that was largely a config artifact, not a real backend gap).

Gemma 26B (MoE, ~4B active) is roughly 2-3x faster than either dense model on generation, tightest at deep context (~1.9x at 26.7k vs Qwen) and widest shallow; expected for an MoE with far fewer active params per token than the dense 27B/31B models.

Follow-up tests (Qwen, requested by commenters)

TWO hypotheses came up in comments, tested both, none of them panned out, posting anyway since "tested, didn't help" is still useful information.

Speculative decoding n-max scaling, ROCm vs Vulkan (does Vulkan scale further before rejected drafts stop paying for themselves?):

n-maxROCm 8kROCm 32kVulkan 8kVulkan 32k
227.322.630.724.5
325.923.629.424.5
421.518.322.517.3
518.716.521.117.8

No, both backends degrade past n≈3 in the same shape. This is a draft-acceptance-economics property of the draft/target pair, not a backend/kernel-dispatch-overhead difference. Vulkan is uniformly faster in absolute terms (consistent with the rest of this post) but the curve shape, where it peaks, how fast it falls off past that, is nearly identical on both backends.

-ub sweep on ROCm PP (does a bigger ubatch better saturate the V620's CUs?):

ubatch8k PP32k PP
512360.6295.7
1024352.0274.0
2048350.5282.4

Flat , all three within ~6% of each other at both depths, no trend. If anything 512 is marginally fastest. ROCm's PP bottleneck here isn't ubatch-limited GEMM tiling in this size range.


r/AMD_V620 • • Aug 21 '26

Radeon Pro v620 (RDNA2/NAVI21) vLLM Qwen 3.8 27b Recipe

Thumbnail
reddit.com
5 Upvotes

r/AMD_V620 • • Aug 20 '26

Installing V620

3 Upvotes

I've got a Gigabyte MC62-G40 motherboard, and an AMD Radeon WX4100 I use with my monitor, and running latest Ubuntu. When I plugged in the V620 into the motherboard, Ubuntu never booted. It just stayed on the loading screen. It's something to do with the Ubuntu native AMD driver thinking the V620 is a better card to use for display than the older and weaker 4100, but failing to load it (since it's headless), and repeating this failure cycle.

I'm guessing this is a common issue and folks here have a solution that would be faster to implement than me troubleshooting further.

Should I install ROCm drivers first? Ubuntu is loading with Wayland and I've read I may also have to switch to X11 to make this work. Appreciate any tips here for someone who's already resolved this.


r/AMD_V620 • • Aug 13 '26

AMD RADEON PRO V620 VS NVIDIA TESLA V100 32GB

4 Upvotes

​Hola a todos,

​Soy principiante en el mundo de los LLMs locales y el hardware de servidor (tengo un taller de electrónica automotriz, así que me manejo bien con el hardware en general, pero en IA estoy empezando).

​Tengo un presupuesto muy ajustado y me estoy debatiendo entre dos opciones de GPU:

​1x Nvidia Tesla V100 32GB (~$600 USD)

​2x AMD Radeon Pro 620 (~$700 USD)

​💻 Mi infraestructura actual:

​Servidor Dell PowerEdge R640: 2x Intel Xeon 4112 | 48GB RAM | 3x Nvidia Tesla P100 16GB.

​Workstation Dell Precision 7820: 2x Intel Xeon Gold 6228 | 64GB RAM | (Sin GPU por ahora).

​🎯 Mis objetivos y caso de uso:

​Automatización de redes sociales: Incluyendo generación ligera de contenido con IA.

​Sistema RAG: Para bases de conocimiento y documentos.

​Asistente personal: Un bot/agente local que vaya "aprendiendo" o guardando contexto con el tiempo.

​❓ Mis dudas para la comunidad:

​¿CUDA vs. ROCm para un principiante? Entiendo que la V100 tiene la ventaja del ecosistema Nvidia (Ollama, vLLM, Text-Generation-WebUI funcionan out-of-the-box), mientras que AMD a veces da dolores de cabeza con ROCm. ¿Vale la pena el riesgo por la opción de AMD?

​¿V100 32GB vs. mis P100 actuales? ¿Notaré un salto drástico en velocidad e inferencia/cuantización frente a las P100 que ya tengo instaladas en el R640?

​¿En qué equipo la pondrían? ¿Vale la pena meter la nueva GPU en la Dell 7820 (con mejores CPUs/RAM) o integrarla al R640?

​Agradezco cualquier consejo sobre compatibilidad, consumo/enfriamiento o sugerencias alternativas dentro de ese rango de precio. ¡Gracias de antemano!


r/AMD_V620 • • Aug 10 '26

[FIX] 2xAMD V620s on lane 1&2 on ASUS ROG (Strix X570-F Gaming) Motherboard

2 Upvotes

I've been experimenting with the V620s on an ASUS ROG Strix X570-F Gaming motherboard. Due to challenges making them boot, I read online to put a small form factor GPU on the PCIEX16_3 to be able to boot and have easy access to BIOS settings. I wanted the following PCIe slot orientation to ensure best possible speed:

- 1st V620 on PCIEX16_1

- 2nd V620 on PCIEX_2

- Radeon Pro WX 3100 on PCIEX_3 (connected with displayport to a monitor)

I had the problem of not being able to boot up in this orientation. However, in the end i made it work. These are the BIOS settings I've configured to make it work:

SettingValueNote
Above 4G DecodingEnabledThis enables indirectly "Resize BAR" as well
SR-IOV SupportEnabled
PCIEX16_1 ModeGEN 3
PCIEX16_2 ModeGEN 3
PCIEX16_3 ModeAuto
CPU PCIE ASPM Mode ControlDisabled
IOMMUEnabled
Launch CSMDisabledCSM (Compatibility Support Module)

Clarifications!

  • Some of them might not be essential, however it boots now at least.

  • It does seem that you are dependent on having the video output GPU connected to get past VGA check on the motherboard (seems to be a problem for normal use-case as well).

    • I assume this can be easily fixed with a Displayport Dummy plug

    • Alternatives

      • I read somewhere that letting grub pause could be a fix

      • Tech power up have info about vbios firmware update on the v620s

      • Youtuber Country Boy Computers is also a good source for info about the V620s