Qwen3.5-9B Q4_K_M on the Radeon RX 9060 XT 8GB (Linux)
Candidate
Candidate Linux single-card configuration for RX 9060 XT 8 GB; no published fit or performance result.
What will be tested
| Card | 1 × AMD Radeon RX 9060 XT 8GB |
|---|---|
| Operating system | Linux |
| Backend | Not yet selected |
| Model | Qwen3.5-9B (Apache-2.0) |
| Model file | Unsloth GGUF conversion, Q4_K_M |
| Context | 16,384 tokens |
| Concurrent requests | 1 (one request at a time) |
| Placement | Full GPU |
| Reviewed | Not yet |
| Sources | Upstream model · GGUF file page |
What to expect
No published results yet. Measured results appear here only after testing and review.
Install
Candidate — no installer yet.
Overview
This Linux candidate pairs the RX 9060 XT 8 GB with the pinned model and quantization named above at the catalog's 16,384-token context. The 8 GB variant has much less room for weights and context state than its 16 GB sibling. This Q4 9B profile tests whether the lower-memory card can serve a useful text workload without assuming the same outcome as the 16 GB version. It is a test plan, not a claim of load, full-GPU placement, answer quality or speed.
Requirements
The current Linux path is a private, supervised source-checkout workflow for one recognized Vulkan GPU and a loopback server. It requires explicit artifact consent. No physical Linux AMD serving outcome is qualified. Check the card's currently reported free GPU memory, not just the number printed on its box. A longer prompt, more active requests and the desktop can change the memory budget. Keep the exact driver and operating-system build with any later test.
The pinned GGUF is 5,680,522,464 bytes (5.68 GB decimal). Keep more free local SSD space than the artifact itself for verified acquisition and cache maintenance; no fixed extra margin or host-RAM minimum has been qualified. Review the exact model license before acquisition. A planned trial must record the actual free-memory budget, selected device, loaded context, host and GPU buffers, delivered output and representative answers. The catalog context is an intended setting, not a demonstrated maximum.
Limitations
- The exact-card load, context, GPU/host buffers, response quality and speed have no published qualification result.
- The Linux path is a private source-checkout single-card workflow, not physically qualified on this card or released to consumers.
- This candidate requests full-GPU placement; it is not a verified physical-residency or all-operations-on-GPU claim.