Installing v2rayN on LoongArch (Loongson)

From the 3A5000 onwards, Loongson processors use the LoongArch instruction set, which is compatible with neither x86 nor ARM. Binaries built for other architectures simply will not run, so you need the dedicated loong64 build.

Confirm you are on LoongArch

Check the architecture

uname -m

# loongarch64 → modern Loongson, use the loong64 package
# mips64      → 3A4000 and earlier, a MIPS-based design

cat /proc/cpuinfo | grep -i model

Installing

The download is a .deb, matching the Debian-derived distributions common on Loongson hardware (Loongnix, UOS, Deepin):

Install

sudo apt install ./v2rayN-linux-loong64.deb

# on RPM-based LoongArch distributions there is no official rpm;
# convert with alien or build from source

dpkg -L v2rayn | head -20

The core binary must be LoongArch too

This is the pitfall. The interface installs fine, but every server fails and the log complains that the core cannot execute. The cause is an architecture mismatch in bin/.

Check what the core was built for

find / -name "xray" -type f 2>/dev/null

file /path/to/xray

# should mention LoongArch
# x86-64 or ARM aarch64 means it is wrong

If it is wrong, download the LoongArch build from the core project's releases and replace the file under bin/. Note that LoongArch support arrived relatively late upstream, so very old core versions may have no such build.

Every layer has to be loong64

Common problems

Symptom	Cause	Fix
Architecture mismatch on install	Downloaded the x86 or arm64 package	Get the loong64 build
UI opens but every server times out	Core is not a LoongArch build	Replace the binary under `bin/`
Missing graphics libraries	Distribution trimmed desktop dependencies	Use `ldd` to find and install them
Text renders as boxes	No CJK fonts installed	Install a font package such as `fonts-wqy-microhei`

Find missing shared libraries

ldd $(which v2rayN) | grep "not found"

sudo apt install libicu-dev libfontconfig1

Performance expectations

There is no performance concern here — encryption is a light load for any modern CPU, and the real limit is your network route.

What does matter is ecosystem maturity. LoongArch is a young architecture and upstream build coverage is still filling in, so a new release may take a while to appear for it. If you depend on a recent protocol, confirm a LoongArch core build exists before upgrading.