Files
nix-config/home/linux/gui
ryan4yin | 二花 9f092808fd feat(aquamarine): serve Whisper transcription from the NPU (#472)
The goal is speech recognition on the NPU for vinput, and sherpa-onnx cannot
deliver it: every model it loads keeps a dynamic time axis, which the NPU
compiler rejects outright. Qwen3-ASR and SenseVoice both core-dumped in
vpux-compiler ("Got non broadcastable dimensions pair"), and reshaping the ONNX
inputs does not help because the dynamic dimensions sit inside the graph
(WA-037). Whisper is the only family OpenVINO publishes fully static IRs for,
and its fixed 30 s window is exactly what the compiler accepts.

The host now runs an OpenAI-compatible /v1/audio/transcriptions service backed
by whisper-large-v3-turbo int8 on the NPU: 1.5 s for 11 s of audio against
2.1 s on CPU, with the compiled graph cached in /var/cache so only a cold cache
pays the ~60 s NPU compile. vinput on the desktop sends raw PCM to it through a
small provider script.

Only the NPU driver and compiler still come from the unmerged branch in the
`nixpkgs-npu` input (NixOS/nixpkgs#570230), whose nixpkgs also happens to be
the one where openvino-genai 2026.4.0.0 builds at all.

Assisted-by: DeepSeek Harness 0.2.1-rc.2 (deepseek-v4.1-flash)
2026-10-18 08:34:50 +08:00
..

Desktop Environment Configurations

This directory contains desktop environment and window manager configurations managed by Home Manager.

Available Configurations

Window Managers

  • niri: Niri compositor configuration with custom settings, keybindings, spawn-at-startup rules, and window rules
  • i3: Headless X11 session for the computer-use VMs (idols-ruby, idols-kana); see i3/README.md

Base Desktop Environment

  • base: Common desktop configurations shared across all environments, including:
    • Noctalia: native (v5) all-in-one Wayland desktop shell; see base/README.md for the components it replaces
    • Creative tools and media applications
    • Development tools
    • Fcitx5 input method framework
    • Games and gaming utilities
    • GTK theme configurations
    • Immutable file handling
    • Note-taking applications
    • Wayland applications
    • XDG desktop configurations

Why install Desktop Environments in Home Manager instead of NixOS Module?

  1. Configuration Location: Desktop environment configuration files are located in ~/.config, which can be easily managed by Home Manager.

  2. User-specific Services: User-specific systemd services (fcitx5, hypridle, etc.) can be easily managed by Home Manager. If desktop environments were configured via NixOS Module, these user-level services might fail to start automatically. With Home Manager modules, we can control systemd service dependency order more effectively.

  3. System Benefits: By minimizing package installation through NixOS Module:

    • Makes the NixOS system more secure and stable
    • Increases portability to non-NixOS systems, as Home Manager can be installed on any Linux system
    • Allows for easier switching between different window managers without system-level changes