Problem on old pc #59582

Activity

1. opencode-agent commented on Oct 27, 2026

   

   opencode-agentBot

   on Oct 27, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report and for including the full error. I think this is a duplicate of #59522, which has the same Server process terminated by SIGILL error from the v2 desktop app on an older CPU.

   SIGILL means the OpenCode server that the desktop app starts in the background crashed on a CPU instruction your processor doesn't support. The Core 2 Quad Q9650 doesn't have SSE4.2 or POPCNT. As far as we can tell, even the "baseline" runtime OpenCode is built on for older x64 CPUs needs those instructions, so this is probably a hardware limit and not something specific to your setup.

   Related issues, ordered from most to least likely to match:

   • opencode does not work on old cpu SIGILL error #59522: same Desktop IPC handler failed / terminated by SIGILL error on an old CPU with the v2 desktop app, and v1 still works
   • fix: bump pinned Bun to 1.4.1 so x86 CPUs without AVX2 stop crashing with SIGILL #47297: background on older x86 CPUs crashing with SIGILL and the CPU baseline OpenCode's runtime needs
   • opencode Worker subprocess crashes with SIGILL (illegal instruction) on Intel i5-7200U (Kaby Lake), freezing the system #36280, SIGILL crash on AMD Ryzen Zen 3 (no AVX-512 support) — all sessions crash #38986: earlier SIGILL crash reports on CPUs missing newer instruction sets

   It would still help to add your operating system and the exact OpenCode Desktop version to #59522.

   The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
2. opencode-agent

   added

   pending close

   triaging

   on Oct 27, 2026
3. JoeJoeflyn commented on Oct 27, 2026

   

   JoeJoeflyn

   on Oct 27, 2026

   More actions

   I got OpenCode 2.1.2 running on a physical Core 2 Duo U9400 (SSE4.1, no SSE4.2/POPCNT), on Alpine Linux 3.24.3.

   Patches and build commands: https://github.com/JoeJoeflyn/opencode-core2

   The working approach was:

   1. Rebuild Bun 1.4.4 and its matching JavaScriptCore for Penryn (-march=penryn, also propagated to Rust). Rebuilding only OpenCode or using stock prebuilt JavaScriptCore is insufficient.
   2. Keep the target libc/sysroot consistent; the Bun patch includes the local WebKit musl cross-build fix.
   3. Rebuild OpenCode embedding that custom runtime via the small BUN_COMPILE_EXECUTABLE_PATH build-script patch.

   Verified the actual interactive TUI and completed DeepSeek V4.1 Flash Free replies—not just --version. No emulation, remote execution backend, provider substitution or quota bypass was used.

   For your Linux Mint setup: this is a source-build starting point, not a verified Mint/glibc or desktop binary. Our tested build is Alpine/musl CLI/TUI; glibc/desktop packaging needs separate adaptation/testing. Penryn requires SSE4.1, so this is not a universal fix for every older CPU. Avoid stock automatic upgrades replacing the compatible runtime.