dank/serverAppConfigs
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(frank-tts): record the iGPU cutover, close the NPU question

Browse Source 
The cutover PR merged the runtime; this carries the surface that has to be
true afterwards.

- Engine page: the shape is now `--device Vulkan0` on the gfx1151 as a
  co-tenant beside frank-dragoon; the registry/thread/streaming laws gain a
  fourth — the device law — whose numbers stay in the verdict report, and the
  deploy record gets the cutover steps including the `glslc` configure gate.
  The CPU-era arm/rollback prose keeps the qualitative argument and drops the
  dead numbers per the purpose test.
- Endpoint page: "Where the engine computes" now says iGPU + co-tenancy, and
  states the NPU verdict in one paragraph instead of a research tour.
- Quadlet comment: it claimed supplementary groups are what grant render
  access. On this host the udev rule world-writes the render nodes and the
  container's `id` shows no groups at all, so keep-groups is belt-and-braces;
  the RSS note now matches the device shape instead of the CPU trial.
- Verdict report: gate 2 (contention) recorded as measured after the cutover,
  and the build-stage prediction corrected — the package is `glslc`, not
  `libvulkan-dev glslang-dev`.
- index.md regenerated (one description changed).
This commit is contained in:
Frank
2026-10-19 14:37:29 -07:00
parent 6248f02ca2
commit ea2fc6440b
5 changed files with 98 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files
serverAppConfigs-docs/Dankclaw/Frank TTS.md
+12 -11
View File
@@ -113,17 +113,18 @@ shows up as a failed synthesis, never as a down probe.
## Where the engine computes
CPU, and only CPU is compiled in: `Containerfile.engine` builds `qwentts.cpp` with
`-DGGML_VULKAN=OFF` written out explicitly, so the container carries `libggml-cpu` and no
other backend. The realistic accelerator is the gfx1151 iGPU behind that flag — plus
`/dev/dri` passthrough, the ComfyUI pattern — on the same payload and the same pinned
commit, and the intended shape is **co-tenancy**: the engine resident on the card beside
`frank-dragoon`, not a handover. Memory is not what decides that; shader contention is, and
the census plus both gates are in `report/tts-npu-spike-verdict-2026-10-19.md` §5.
**The Strix Halo NPU is not a door at all**: XDNA2 executes only precompiled AIE
partition programs, and AMD's own Linux runtime opens `/dev/accel/accel0`, succeeds at the
ioctls, then declines this model family's graph without emitting a single log line. The
measured record and the model-side contract live in `report/` at the repo root
The **gfx1151 iGPU**, as a co-tenant beside `frank-dragoon`: the Vulkan build of
`qwentts.cpp` with `--device Vulkan0`, and `/dev/dri` handed to the engine container. That is
the shape since 2026-10-19. The flag, the device name, the render-node trap on this hybrid box
and the one-line CPU rollback are owned by [[Frank TTS Engine]] — read that page before
touching either tenant, because a change to one is a change to both. Co-tenancy was gated with
`frank-dragoon` live on the card (its first token and decode rates unchanged with a synthesis
in flight); both gate recipes are §5 of `report/tts-npu-spike-verdict-2026-10-19.md`.
**The Strix Halo NPU is not a door at all**: XDNA2 executes only precompiled AIE partition
programs, and AMD's own Linux runtime opens `/dev/accel/accel0`, succeeds at the ioctls, then
declines this model family's graph without emitting a single log line. The measured record and
the model-side contract live in `report/` at the repo root
(`tts-npu-spike-verdict-2026-10-19.md`).
## Files