Repository navigation
serve: drop the ONNX route and its packaging - #529
Conversation
The engine ships no ONNX Runtime of its own any more. Lemonade carries ONNX wherever it exists (its ryzenai-llm backend on Windows, its onnxruntime backend on the CPU), and the engine's NPU route is its own engine (--device npu). The Linux ONNX route (#386) had done its job: the OGA data it was built to collect is recorded, and the NPU-side work continues on the engine's own stack. Removed: --device onnx in serve (a removed-device message names Lemonade's backends), ONEBIT_ONNX and the onnx_npu_smoke test, scripts/build-onnx.sh and the SIGTERM shim, the third_party/ryzenai-server submodule, docs/onnx.md, the onnx/ directory of the Linux package and its weekly checks, the ryzenai-server pin in the weekly changes, and the ryzenai-server / ONNX Runtime entries in NOTICE. A model directory with genai_config.json is no longer recognised. Lemonade's own onnxruntime:cpu backend in the 1bit OS image is untouched. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
"llama-server devices" means
Will it fit?Before any llama-server starts ( A load that does not fit prints the same line as The estimate (
The context is Free is
ctest
ctest When a backend hangsA hung GPU dispatch (a wedged HRX queue, a #315 fault) stops llama-server's main loop, while its |
…ot parse) (#535) #529 removed the ONNX block from scripts/package-linux.sh but left its `done` and `fi` behind. `bash -n` fails on line 54 ("syntax error near unexpected token `done'"), so the whole script never runs and the release's package stage stops one second in, before packing anything: [09:14:05] package rc-2026-10-23: the engine (into the Lemonade + onebit package) work/src/scripts/package-linux.sh: line 54: syntax error near unexpected token `done' Delete the two orphan lines. No other file in scripts/ or os/mini/ is left broken by #529 (checked every .sh with bash -n and every tools/*.py with py_compile). Co-authored-by: bong-water-water-bong <bong-water-water-bong@1bit.gg> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
The engine ships no ONNX Runtime of its own any more (owner, 2026-10-23). Lemonade carries ONNX wherever it exists: its ryzenai-llm backend on Windows and its onnxruntime backend on the CPU. The engine's NPU route is its own engine (
--device npu), and the hybrid mode for Linux is being built on it (Gantt phyb1-3).The Linux ONNX route (#386) had done its job: the data it was built to collect is recorded, and nothing in Lemonade's onebit backend references the engine's
onnx/directory.Removed
--device onnxin serve; the flag now fails with a removed-device message that names Lemonade's backends, likevulkan,zincandmlx. A model directory withgenai_config.jsonis no longer recognised.ONEBIT_ONNX, theonnx_npu_smoketest,scripts/build-onnx.sh, the SIGTERM shim, thethird_party/ryzenai-serversubmodule,docs/onnx.md.onnx/directory of the Linux package, its weekly package checks, the ryzenai-server pin in the weekly changes, and the ryzenai-server / ONNX Runtime entries in NOTICE.Untouched: Lemonade's own
onnxruntime:cpubackend in the 1bit OS image, and the ONNX-export vocabulary of the model census.Checked on ryzen: configure + build of
onebit,smoke_serve,watchdog_serveandmetrics_servepass;1bit serve --device onnxprints the removed-device message;--helpmentions no ONNX.🤖 Generated with Claude Code