Who it is forA Linux engineer on Strix Halo who wants a reproducible build or needs to debug GPU access before serving models.
The problemROCm and GPU setup on Strix Halo is fragile, and a manual build can drift from the tested toolchain.
The outcomeA built Gufo binary that reports the device status and serves a local GGUF model.
What you need first
- Linux x86-64 machine with AMD Strix Halo (gfx1151) and enough unified memory for the chosen model
- Podman with rootless GPU device access to /dev/kfd and /dev/dri
- Hugging Face CLI (hf) to download model weights
- Several tens of GB of free disk space for model files
Steps
- Clone the Gufo repo and run
nix buildin its root to build the production package. - Run
./result/bin/gufo diagnoseto check the GPU and runtime setup. - Run
./result/bin/gufo serve llm --model /path/to/model.ggufwith your own GGUF model file. - If the build needs the development tools, run
nix developas the README describes for profiling and model download tools. (inferred, check the README)
Prompt for your agent
Clone the gufo repo, run nix build, then run ./result/bin/gufo diagnose and report its full output. Start ./result/bin/gufo serve llm --model <path to GGUF file> and confirm the server reports it is listening.
Caveat. The README states the Nix package includes a ROCr 7.2.3 patch for Strix Halo, so a build on other GPU or ROCm setups is outside the documented target.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for gufo-org/gufo and "Build Gufo from source with Nix and run diagnostics"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer