Stockfish on Raspberry pi 5

[paolo2504]

At present it seems to me that latest Stockfish 16.1 is not available Raspberry pi 5 64bit. However i noticed that stockfish engine 10 aarch is available in the Engines folder in Arena 3.9 beta package.
Two questions:
is r10 the latest aarch available for raspberry (arm76) ?
no gui packaged 16.1 version for raspberry pi 5 as well ?
Thanks & regards.
paolo

[Disservin]

The armv8 versions should work for raspberry pi 5 https://github.com/official-stockfish/Stockfish/releases.

[paolo2504]

tried armv8 and armv7 in Scid. Error is "error writing file 8: broken pipe".

[vondele]

what happens is you just execute the binary:
./stockfish go depth 10
(or the proper path to your downloaded binary?)

[paolo2504]

nothing happens : no errors and of course no gui.

i just tried to compile it and it works in scid and in Arena.
I downloaded Stockfish_16.1.zip, unzippped it and compiled with command make build ARCH=armv8.
A 66.2 mb executable is generated and it works. Also make build ARCH=armv7 does work.

On the contrary, the executable stockfish-android-armv8 doesn't work and generates errors when installed in Scid or Arena.
I tried other files (armv7... neon... avx2) and noe of them work on rpi 5.
Definitely, compiling the source 16.1 as armv8 works fine in rpi 5 64bit.
regards.

[paolo2504]

Thanks Disservin. I tried android-armv8 already.
launching the executable nothing happens.
no error any case. Are this versions without gUI ?
I tried using scid and Arena pointing at the extracted executable but I am getting a errors.
maybe I’m doing something wrong..

I see that the r10 engine of stock fish is very different in size so I suppose that using the executable of the 16.1 package (67mb) is a mistake.

[Disservin]

Are this versions without gUI ?

We don't develop a GUI

Stockfish does not include a graphical user interface (GUI) that is required to display a chessboard and to make it easy to input moves. These GUIs are developed independently from Stockfish and are available online. Read the documentation for your GUI of choice for information about how to use Stockfish with it.

https://github.com/official-stockfish/Stockfish

[luca-256]

Hi paolo2504, the ARMv8 Dot Product executable of Stockfish 16.1 should run on the Raspberry Pi 5, because the CPU is ARM. The executable is said to be for Android since ARM processors are usually found in smartphones, not desktop computers. Also, note that Stockfish is only a chess engine, not a full-fledged chess application, and it can be installed into a third party chess GUI. I tested if the executable I mentioned worked on the Raspberry Pi 5 and it worked. Perhaps SCID itself has an internal error, or you provided an incorrect path to the executable.

[paolo2504]

Luca-256, thank you for you kind reply.
I confirm the release ...android-armv8 doesn't work on rpi5 either with SCID and Arena-linux.
Solution is to compile it fom the src folder with make build ARCH=armv8; the resulting executable is recognized by SCID and Arena.
regards.

[luca-256]

Okay, I think you're correct after redoing the process of installing the executable myself. The executable does indeed not seem to work on the Raspberry Pi 5. However, you can get Stockfish from your package manager; that can be accomplished with sudo apt install stockfish if you're using a Debian based system like Raspberry Pi OS. Or, as you already mentioned, you can compile the source code yourself. As a side note, adding the parameter ARCH=armv8-dotprod is better than ARCH=armv8, because the CPU of Raspberry Pi 5 has support for dot products. Also, you might want to consider make profile-build which will automatically find what architecture it is that you're on and optimally compile for that.

[paolo2504]

Thanks Luca for your suggestion. I don’t know (for the moment…🙄) what are “dot products” but I’ll give a try for sure and make new compile as per your suggestion.
regards.

[luca-256]

You're welcome!

[paolo2504]

hi Luca, they both work. See attached log of both makes.

log make stockfish.txt

[luca-256]

Good, I'm glad both methods worked! I was also able to compile both ways successfully on my Raspberry Pi 5.