On CPUs without AVX2 (e.g. Intel Ivy Bridge, i5-3210M), the prebuilt `voxtype-bin` package installed by `omarchy voxtype install` crashes immediately with SIGILL — both the AVX2 and AVX-512 binary variants require instructions this CPU class doesn't have, and the installer gives no indication why or what to do about it.

**Workaround (works, documented upstream):** build from source with `RUSTFLAGS="-C target-cpu=native"`. This runs cleanly and dictation works correctly, at the cost of a ~9s end-to-end delay per utterance (CPU-only inference on older hardware).

**Attempted to speed that up via GPU offload:** this machine's iGPU (Intel HD Graphics 4000, same Ivy Bridge generation) does expose a Vulkan device, so we rebuilt with `--features gpu-vulkan` to try cutting the delay. That build crashed immediately and unrecoverably on every start: `ggml_vulkan: device Vulkan0 does not support 16-bit storage` → uncaught `std::runtime_error` → abort, looping through systemd's restart limit. Root cause is a hardware ceiling (this iGPU generation lacks the 16-bit storage buffer support whisper.cpp's Vulkan backend requires), not a config or build issue — so this isn't fixable on this hardware. We rolled back to the working CPU-only build.

Requesting either:
- a CPU feature check before/during install that warns when the target CPU lacks AVX2, with a pointer to the source-build workaround, or
- an automatic source-build fallback when no compatible prebuilt binary exists.

Separately, it may be worth whisper.cpp's Vulkan backend catching the "unsupported device" case and falling back to CPU instead of throwing an uncaught exception — happy to open that against upstream voxtype/whisper.cpp instead if that's a better fit than this Omarchy-side report.