<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cuda on AiSlackin</title><link>https://aislackin.com/tags/cuda/</link><description>Recent content in Cuda on AiSlackin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 28 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aislackin.com/tags/cuda/index.xml" rel="self" type="application/rss+xml"/><item><title>wimpy-setup: a dual-GPU inference box you can rebuild from scripts</title><link>https://aislackin.com/posts/2026-06-28-wimpy-dual-gpu-inference/</link><pubDate>Sun, 28 Jun 2026 00:00:00 +0000</pubDate><guid>https://aislackin.com/posts/2026-06-28-wimpy-dual-gpu-inference/</guid><description>&lt;p&gt;This is not a guide. It&amp;rsquo;s the actual, ordered, idempotent script set that builds my inference server — shared because rebuilding from memory is how homelabs die. Wimpy is a Ryzen 7 7700 with two GPUs serving LLM inference &lt;em&gt;at the same time&lt;/em&gt;: an AMD Radeon AI PRO R9700 (32GB, ROCm) and an NVIDIA RTX 5060 Ti (16GB, CUDA), behind one llama-swap endpoint.&lt;/p&gt;&#10;&lt;p&gt;The dual-GPU part is the reason this repo exists. HIP and CUDA backends of llama.cpp share library filenames, so they can&amp;rsquo;t coexist in one prefix — there are two isolated builds (&lt;code&gt;/usr/local&lt;/code&gt; for ROCm, &lt;code&gt;/opt/llama-cuda&lt;/code&gt; for CUDA) and one llama-swap config with two non-exclusive groups. A &lt;code&gt;-cuda&lt;/code&gt; model entry is the same GGUF as its AMD twin with a different binary and device pin, so either card can serve it. GPUs are pinned by UUID (the Ryzen iGPU also enumerates as a ROCm device and will happily steal your workloads if you let it).&lt;/p&gt;</description></item></channel></rss>