OpenCode cannot Launch on Debian Trixie(Proxmox,LXC)

[0xc0000142]

Description

After Upgrade To v1.1.52 with command opencode upgrade ,OpenCode cannot launch on my mechine.
I try to remove all userdata find / -name "*opencode*" -exec rm -r {} \; ,upgrade my system and change nodejs version to v24,again
After this,I try to fix opencode use vim $(which opencode) and add a new line console.info(resolved) (pic1) to get opencode bin path /root/.local/share/nvm/v24.13.0/lib/node_modules/opencode-ai/node_modules/opencode-linux-x64/bin/opencode
but this bin cannot launch

fish: Job 2, '/root/.local/share/nvm/v24.13.0…' terminated by signal SIGILL (Illegal instruction)

After this , i try the command find / -name "*opencode*" 2>/dev/null
this command return some bin path
I try to start any bin with param --version (pic2)
I confirm that this bug was added in version 1.1.52(pic3)

Here is some info may helpful:
uname -a: Linux Dev 6.14.11-5-pve #2 SMP PREEMPT_DYNAMIC PMX 6.14.11-5 (2025-12-15T08:44Z) x86_64 GNU/Linux
CPU: Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
CPU Flags:

Flags:                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_p
                             erfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 pop
                             cnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm id
                             a arat pln pts vnmi md_clear flush_l1d

OpenCode Install method : npm i -g opencode-ai
Node.JS install method: nvm
Shell: fish

Plugins

none (i just remove my userdata and opencode.json)

OpenCode version

1.1.52

Steps to reproduce

No response

Screenshot and/or share link

Operating System

Debian 13

Terminal

Proxmox XTerm.JS / Windows Terminal

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Remove BUN #12410: Shows "Illegal instruction" error similar to your SIGILL symptom - appears to be a Bun runtime issue on systems with older CPU instruction sets
• AUR Source PKGBUILD fails for x64-baseline #12114: AUR Source PKGBUILD fails for x64-baseline - indicates CPU baseline compatibility issues in v1.1.52
• new version destroy all CANT LOAD ANY #12327: Another report of v1.1.52 breaking OpenCode on launch with similar failure symptoms

The common thread appears to be v1.1.52 and CPU instruction set compatibility, particularly on systems with older processors (like your Intel Xeon E5-2690 v2) that lack certain CPU flags needed by the new Bun runtime.

Feel free to ignore if none of these address your specific case.

[shuans]

my system is ubuntu , opencode cannot launch from version 1.1.53

[moewah]

system ubuntu 24.04, opencode cannot launch from version 1.1.53

[alpo]

Opencode v1.1.53 crashes with SIGILL on Intel(R) Celeron(R) CPU N3350, glibc Void Linux due to missing AVX CPU instructions. Workaround is to install baseline binary using npm install -g opencode-linux-x64-baseline and symlink to ~/.local/bin/

[shuans]

Currently, OpenCode forces automatic upgrades to the latest version, which would be disastrous if there are any bugs.

[yilisharcs]

@shuans try this

{
        "$schema": "https://opencode.ai/config.json",
        "autoupdate": false
}

[fwelland]

Fedora 43 -- opencode > 1.1.51 will not start (cli/tui). dmesg has something about a 'invalid trap'.

oddly and fwiw:

I have two fedora 43 workstations: older gen, Del blah-blah/XPS xeon something workstation. It is ok with OpenCode 1.1.51 (with copilot integration) but crashes on any updates > 1.1.51

The 2nd workstation is a more modern Intel laptop i7/12thGen . This works fine with OpenCode upto and including 1.1.61. This uses OpenAI/Codex NOT copilot.

..grr...

[github-actions]

To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.