[Engine] Build for 6000 series does not support 6650 XT #5261

Activity

1. github-actions

   added

   needs-formatTitle or template does not follow CONTRIBUTING.md yetTitle or template does not follow CONTRIBUTING.md yet

   on Nov 5, 2026
2. github-actions commented on Nov 5, 2026

   

   github-actionsBot

   on Nov 5, 2026 – with GitHub Actions

   More actions

   Thanks for the issue. To keep the tracker readable, every item needs an area prefix in the title and the parts of the issue form filled in. This one is missing:

   • Start the title with its area: [Engine], [GUI], [TUI], [Benchmark], [Docs] or [Other], then a short description. Example: "[Engine] decode stops after 2 minutes".

   Edit the issue (title and description) and this note goes away on its own. If it is still missing parts in 5 days it will be closed, which is not a rejection: fix it and comment /reopen.

   Details: CONTRIBUTING.md
3. TuxArchi

   changed the title [-]Build for 6000 series does not support 6650 XT[/-] [+][Engine] Build for 6000 series does not support 6650 XT[/+] on Nov 5, 2026
4. github-actions

   removed

   needs-formatTitle or template does not follow CONTRIBUTING.md yetTitle or template does not follow CONTRIBUTING.md yet

   on Nov 5, 2026
5. github-actions commented on Nov 5, 2026

   

   github-actionsBot

   on Nov 5, 2026 – with GitHub Actions

   More actions

   Thanks, this follows the format now.
6. TuxArchi commented on Nov 5, 2026

   

   TuxArchi

   on Nov 5, 2026

   Author

   More actions

   Tested on the same card on Linux (Arch, kernel 7.2.11; RX 6650 XT, 1002:73ef, gfx1032, 8 GB; app 0.2.10 / engine 0.1.56; ROCm 7.13.0a20260515 from the TheRock gfx103X-all wheels).

   What I found:

   • The rx6000 package is built for gfx1030/gfx1031 only, and the selector requires an exact arch match, so no feed package fits gfx1032. That is the whole first-run failure.
   • The engine itself builds and runs for gfx1032. I built the package with VARIANT=rx6000 ARCHS='gfx1030;gfx1031;gfx1032':
     • 1080.8 MiB, 455 manifest files, rocBLAS kernels for all three archs.
     • package_engine.py --verify OK; env -i ./strata --version -> strata 0.1.56.
     • strata-device --list-devices -> gfx1032 wave32 (compiled for gfx1032); --selftest OK.
   • Installed locally in ~/.local/share/strata/components/engine/ (unsigned package), the app recognizes it: /api/engine/first-run -> status: installed; strata components engine -> usable, archs: [gfx1030, gfx1031, gfx1032].
   • End to end: Qwen3.8-Flash-Next Q2_0 (--mmap-experts, 128K context) served "Hello!" (19 prompt / 3 output tokens in 14.3 s). The app's 200-token benchmark: 5.8 tok/s after the cache warmed. Q2_0 needs ~48 GB RAM and this PC has 31 GB, so those numbers are SSD-streaming bound, not a gfx1032 performance claim.
   • For the app's native model list, two pieces are needed: gfx1032 in AMD_ARCHS (PR [Engine] HIP: the RX 6600 / 6650 XT (gfx1032) in setup's cards #2784) and in KFD_SUPPORTED (tools/strata_mcp.py). Without the latter the catalog still says no NVIDIA RTX 20-series-or-newer GPU found (nvidia-smi did not list one) even with the engine installed. I tested with a local Control 0.1.56.1 carrying both.

   The package is local/unsigned; the signed feed still needs a release with the gfx1032 arch. This is evidence that the package is buildable and runs, not that it is published.

   Related: #5209 (Linux prebuilt request), #2784 (setup card list), #4650 (Windows).
7. TuxArchi commented on Nov 6, 2026

   

   TuxArchi

   on Nov 6, 2026

   Author

   More actions

   Confirmed still present in 0.2.11 (fresh install, Linux, RX 6650 XT / gfx1032, 8 GB).

   1) Engine selection

   • The signed feed (sequence 121) only offers 0.1.57-linux-x86_64-hip-rx6000, with archs: ["gfx1030","gfx1031"].
   • I downloaded that package (sha256 4a0ed26fcfd16b87fe693f4ede7bd7751c16e6f37d431d303350ef91bbd903cb, 205,633,740 bytes): it contains 0 files with gfx1032 in the name. So it is not the selector; the binary is not built for the card.
   • The app stops at first run with "Strata can't pick an engine for this PC from its update list".

   2) Model install

   • The app's native install uses the bundled setup.py and stops at Step 1 with:
     [X] no NVIDIA GPU found (nvidia-smi did not answer) ... AMD (gfx1100, ..., gfx1031, gfx1151): --backend hip
   • Cause: AMD_ARCHS in Control 0.1.57 still does not contain gfx1032, so the AMD card is discarded and the code falls through to the NVIDIA branch. KFD_SUPPORTED in tools/strata_mcp.py also omits it.
   • This blocks every native model install on this card, not only Qwen3.6 (the model I tried).

   A local unsigned 0.1.56 rx6000 build with archs: ["gfx1030","gfx1031","gfx1032"] is accepted by Control 0.1.57 and the engine runs, so the missing piece is the official gfx1032 build/metadata.

   Could the rx6000 package be published with gfx1032 (and AMD_ARCHS / KFD_SUPPORTED updated)? I can test the release artifact on the card the same day.