Repository navigation
[Bug]: OpenCode v2 binary crashes with SIGILL (Illegal instruction) on x86-64-v1 CPUs (SSE4.2/POPCNT missing) #60017
Description
Description
Describe the bug
When launching OpenCode v2 (including binaries marked as baseline / linux-x64-baseline), the process crashes immediately at startup with Illegal instruction (core dumped) (signal SIGILL).
This occurs on older but still supported Linux 64-bit systems running x86-64-v1 architecture CPUs (e.g., Intel Core 2 Quad / Penryn series), which support up to SSE4.1, but lack SSE4.2 and POPCNT.
Because the v2 binary is packaged via Bun—which has a hard floor requirement of Nehalem (SSE4.2 + POPCNT) even for baseline targets—the executable cannot initialize on these processors.
System Information
- OS: Ubuntu MATE 24.04.5 LTS (kernel 6.8.x, x86_64)
- CPU: Intel Core 2 Quad Q9400 @ 2.66 GHz
- Architecture Level:
x86-64-v1 - Supported Instructions: MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1
- Missing Instructions: SSE4.2, POPCNT, AVX, AVX2
- Architecture Level:
- RAM: 8 GB DDR2
- GPU: NVIDIA GeForce GT 730 (Kepler) · Driver 470.256.02
- Affected Version: OpenCode v2.x (all recent releases, including
opencode-linux-x64-baseline)
Running under GDB confirms the crash happens during early initialization when executing an unsupported instruction (typically a POPCNT or SSE4.2 instruction within the bundled Bun runtime).
Impact & Context
- Users on legacy hardware can no longer run OpenCode v2.
- While OpenCode v1.9.x can physically execute on this hardware, recent backend changes have disabled free Zen model access on v1 clients (
Error: OpenCode's free tier can only be used from within OpenCode). - For active OpenCode Go subscribers running on older hardware, this creates a total service lockout: v1 is blocked at the gateway level, and v2 cannot launch due to CPU instruction constraints.
Suggested Solutions
- Provide a true generic x86-64-v1 build: A build compiled without SSE4.2/POPCNT hard requirements (or using an alternative baseline target).
- Support a Node.js-based launcher: Allow running the OpenCode CLI via standard
nodeinstead of the compiled Bun single-binary executable for environments where Bun's native requirements fail. - Document minimum CPU requirements: Clearly specify in the system requirements that OpenCode v2 requires a minimum of
x86-64-v2(SSE4.2 / POPCNT).
---
### Plugins
none
### OpenCode version
2.x (latest, including opencode-linux-x64-baseline)
### Steps to reproduce
1. On a machine with an x86-64-v1 processor (no SSE4.2 / POPCNT):
```bash
curl -fsSL https://opencode.ai/v2/install | bash
(or manually download the opencode-linux-x64-baseline release)
2. Attempt to run:
opencode --version- Observe immediate exit:
Illegal instruction (core dumped)
Screenshot
No response
Operating System
Ubuntu MATE 24.04.5 LTS (x86_64, Linux 6.8)
Terminal
mate-terminal / bash
Activity
opencodejr commentedon Oct 28, 2026
Thanks for the detailed report, including the CPU details and the GDB check.
I think this is a duplicate of #59461, where the request to support CPUs without SSE4.2 is being collected. The crash comes from the Bun runtime that OpenCode v2 is built on. Even its
baselinex64 build needs SSE4.2 and POPCNT (x86-64-v2), which the Core 2 Quad Q9400 doesn't have. That's why thelinux-x64-baselinebinary still fails withSIGILL.Possible duplicates and related issues, ordered from most to least likely:
SIGILLon a Core 2 Quad Q9650 under Linux, reported from the desktop app. A community member described there how they got v2 running on a Core 2 Duo by rebuilding Bun and JavaScriptCore with-march=penryn. This isn't official or supported, but it may help in the meantime.Server process terminated by SIGILLfrom the v2 desktop app on an older CPU.Your suggestions (a Node-based launcher and documenting the minimum CPU requirement) are useful additions to #59461. Please add them there.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
opencodejr commentedon Oct 29, 2026
We haven't heard back, so I'm closing this as a duplicate of #59461. That issue is where the request to run OpenCode v2 on CPUs without SSE4.2 or POPCNT is being collected. Please follow it there, and add your suggestions (a Node-based launcher and documenting the minimum CPU requirement) as well.
In the meantime, #59582 has a community write-up on rebuilding Bun for Penryn-class CPUs. It isn't official or supported, but it may get you running.
If this turns out to be a different problem, reply here and we can reopen it. Thanks again for the detailed report.
sedgharib123 commentedon Nov 1, 2026
the same problem and opencode dont wanna fix it