Cited, not verified on our rig

Arch Linux first-run setup

Ubuntu 24.04+ on bare metal is still the measured AMDai path — /setup, /gpus/r9700, /benchmarks. Arch is not on AMD’s ROCm 10.1 official OS row. Everything here is Cited, not verified on our rig and not measured on the local desktop. We do not invent drivers, version pins, tok/s, or prices. llama.cpp first.

Two tracks

Try this

Arch extra packages — the cited Arch path

Arch Linux is not on the ROCm 10.1.0 official OS row (that table names Ubuntu, RHEL, Debian, Oracle Linux, Rocky, and SLES — not Arch). Arch Wiki AMDGPU plus Vulkan is the first-token path: mesa and vulkan-radeon (RADV), with vulkan-icd-loader. Arch Wiki llama.cpp then names llama-cpp plus ggml-vulkan first, ggml-hip second. Arch Wiki GPGPU documents ROCm extra packages and says the official GPU list is short; consumer cards may work with unofficial or partial support. That is not AMD 10.1. Not verified on our rig.

Do not start here

AMD’s package-manager repo — not an Arch extra

AMD’s Install ROCm 10.1.0 page documents apt, dnf, and zypper on listed OS rows. Arch pacman is not one of those methods. Do not drop repo.radeon.com debs or rpms onto Arch and call it official 10.1 support. A tarball or runfile from AMD is a portable option AMD documents for Linux, still not an official Arch row. If you want AMD’s named 10.1 userspace to match the measured AMDai cards, install Ubuntu 24.04.5. Not verified on our rig.

Zero to first token

  1. 1 · Cited, not verified on our rig

    Rolling release and kernel notes

    AMD’s 10.1 matrix does not list Arch. Arch is rolling — there is no “Arch 24.04” row to pin. Prefer the stock linux kernel and the in-tree amdgpu module Arch Wiki AMDGPU documents. A custom kernel, linux-zen experiment, or DKMS amdgpu is not verified on our rig. Dual-boot Ubuntu 24.04.5 if you want the measured local desktop path.

  2. 2 · Cited, not verified on our rig

    render and video groups

    AMD Linux prerequisites add the login to render and video: sudo usermod -aG render,video $USER. Arch Wiki users and groups apply the same idea. Log out, or reboot, before you trust rocminfo or /dev/kfd. Root “works” by skipping the check — that is not the fix. Not verified on our rig.

  3. 3 · Cited, not verified on our rig

    Mesa RADV Vulkan first

    Consumer first token on AMDai is llama.cpp + Vulkan. Arch Wiki AMDGPU and Vulkan: install mesa, vulkan-radeon, vulkan-icd-loader, and vulkan-tools, then vulkaninfo. Look for the discrete Radeon and RADV — not AMDVLK. If vulkaninfo is empty, stop; do not guess a driver. BIOS notes (Above 4G, ReBAR/SAM, CSM off) apply on the same board. Not verified on our rig.

  4. 4 · Cited, not verified on our rig

    ROCm / HIP from Arch packages

    After Vulkan tokens are the goal, Arch Wiki GPGPU documents the extra ROCm packages (HIP / OpenCL on the amdgpu kernel driver). That is Arch’s build, not AMD Core SDK 10.1. Confirm rocminfo prints the gfx the card actually is. Arch Wiki notes ROC_ENABLE_PRE_VEGA=1 for Polaris-era cards — do not set that on gfx1201, and do not invent an HSA override. Rolling upgrades of that extra set are a distro story — see /rocm/upgrade. Not verified on our rig.

  5. 5 · Cited, not verified on our rig

    Verify: vulkaninfo, rocminfo, then a monitor

    Order: vulkaninfo (RADV + discrete Radeon), then rocminfo if you installed Arch ROCm packages. A userspace monitor such as amdgpu_top (Arch extra) can show the card busy after tokens start — it is not required for first token and is not verified on our rig. We do not invent an Arch tok/s.

  6. 6 · Cited, not verified on our rig

    llama.cpp — Vulkan first, then HIP

    Arch Wiki llama.cpp: install llama-cpp plus ggml-vulkan first. HIP is second: ggml-hip only after rocminfo lists this gfx. Or build from ggml-org with the flags build.md documents: cmake -B build-vk -DGGML_VULKAN=ON. Ollama, Strata, and vLLM are not an Arch first-run on AMDai. Not verified on our rig.

  7. 7 · Cited, not verified on our rig

    Pick Q6, Q5, or Q4 — Q3 is a labeled estimate

    Download the same official-instruct GGUF the Ubuntu recipes name. Start at Q6, Q5, or Q4 and check VRAM + KV on the calculator. Q3 stays a labeled estimate unless an Arch run card exists — none does in this repo. Q1/Q2 stay off. Tok/s on /benchmarks and /results are Ubuntu llama-bench on the local desktop. Treat them as comparison, not an Arch promise.

  8. 8 · Cited, not verified on our rig

    Fit VRAM and the two RAM lines

    The calculator prints Minimum system RAM needed (the load at the context you picked) and RAM needed at full context (262144 for the house 35B). Overnight UD-Q5 one-GPU Ubuntu peaks are 37.32 GB at 4K and 42.9 GB at 256K — measured on the local desktop, not an Arch kit. Keep the GGUF on NVMe. Not verified on our rig.

  9. 9 · Cited, not verified on our rig

    First-run command (Ubuntu-measured shape)

    Use the house daily-driver launch from the 35B recipe / tuning guide: ./build-vk/bin/llama-server -m ~/models/Qwen3.6-35B-A3B-UD-Q5_K_XL.gguf -ngl 99 -c 262144 --cache-type-k f16 --cache-type-v f16 --host 127.0.0.1 --port 8080. That command is the Ubuntu local desktop shape. On Arch it is not verified on our rig and not measured on the local desktop — confirm vulkaninfo, then tokens, then a loopback /v1. Do not copy Ubuntu tok/s onto this box. Read the 4K run card to see what “good” looked like on the measured path.

  10. 10 · Cited, not verified on our rig

    When it breaks

    Start from a symptom on /troubleshoot. Paste a log in the error matcher. Cited rows live on /rocm-problems. Firmware: /bios. Jargon: /glossary. Short answers: /faq. Stack Lab remains the Ubuntu companion — packages are not published yet and there is no Arch package. Not verified on our rig.

RAM lines (Ubuntu-measured)

Use the calculator before you download a second quant. The two labels stay Minimum system RAM needed and RAM needed at full context. The house 35B peaks below are Ubuntu, not Arch.

Daily driver · 35B llama.cpp · 262K

Minimum system RAM needed

42.9 GB

Measured · 42.9 GiB raw · 256K context

local-desktop-20261012-2314-35b-udq5kxl-1gpu-256k-llamacpp-f16

RAM needed at full context

42.9 GB

Measured · 42.9 GiB raw · 256K full context

local-desktop-20261012-2314-35b-udq5kxl-1gpu-256k-llamacpp-f16

Measured peak system RAM on the local desktop: 42.9 GB (Linux GiB labeled GB). Measured, pending re-verify after RAM fix.

Breakdown
Offloaded weights ·
0 GiB
Separable embed in RAM ·
0 GiB
KV in RAM at selected ·
0 GiB
KV in RAM at full context ·
0 GiB
Runtime / backend ·
0.85 GiB
OS / desktop baseline ·
8.00 GiB
Headroom ·
16.0 GiB

Open in Stack Lab

Stack Lab remains Ubuntu-first. The button is the allowlisted scheme. There is no Arch package and no public download.

Open in Stack Lab

If the app is not installed, packages are not published yet. There is no public download URL. Read the Stack Lab install notes . If Stack Lab is already running on this machine, open the local app .

Sources

How we test — Measured cells cite official amdai-bench/run@1 cards. Estimates stay labeled. Q3 is estimate-only. Q1/Q2 stay off.

Next steps

Real pages on this site. We do not invent a next click.

Last updated

esc

Type to filter. Enter opens the first match. Full-text search lives on /search.