prerequisites for running OpenSpace on Raspberry Pi

Initially, when I powered up the Pi, it showed a low-voltage warning on the Desktop (which I was accessing via RealVNC.) Disconnecting the powered USB hub, booting up with a 60W mobile charger - still the same warning. Then tried switching the USB-C cable to the charger's thicker cable as per
https://forums.raspberrypi.com/viewtopic.php?t=380368. That worked, no further warnings.

Check if mesa (software opengl rendering) is already the latest,

https://en.linuxadictos.com/table-23-3-arrives-with-official-support-for-rpi-5-experimental-support-for-nvk-and-more.html

On earlier pis, it used to be Fake KMS (KMS = Kernel Module Setting.)

https://forums.raspberrypi.com/viewtopic.php?t=255478

Comparison of Raspberry pi 5 with and without fan

https://www.digitec.ch/en/page/raspberry-pi-5--is-the-active-cooler-or-the-housing-with-fan-worth-it-31545

and lots of info in the comments of

https://www.raspberrypi.com/news/heating-and-cooling-raspberry-pi-5/

including the chart,

https://www.raspberrypi.com/app/uploads/2023/10/Screenshot-2023-10-04-at-23.15.30.png

About OpenGL compatibility -   

The VideoCore VII is capable of OpenGL ES 3.1 and Vulkan 1.2 according to

https://www.phoronix.com/review/raspberry-pi-5-graphics

and according to

https://docs.openspaceproject.com/releases-v0.20/contribute/development/compiling/index.html#hardware-requirements

OpenGL 3.3 is required.

So, we might need to use mesa software rendering,

https://raspberrypi.stackexchange.com/questions/75071/running-modern-opengl-on-raspberry-pi

OpenGL 3.3 is "mostly interoperable" with ES 2.0 - 

https://stackoverflow.com/questions/4519264/opengl-es-versus-opengl/11172984#11172984

Just in case this fake KMS is required on pi5

https://raspberrypi.stackexchange.com/questions/75071/running-modern-opengl-on-raspberry-pi

or just use qemu on pi?

https://raspberrypi.stackexchange.com/questions/4296/can-i-emulate-x86-cpu-to-run-teamspeak-3-server
https://marko97it.github.io/rpi5-qemu-win11/userguide/

(TPM mentioned above, is Trusted Platform Module.)

"AMD64 QEMU is currently way too broken to run a stable chroot"

in the comments of 

https://thepi.io/how-to-run-x86-programs-on-the-raspberry-pi/

and

https://github.com/ptitSeb/box86

is also 32 bit,

from https://raspberrypi.stackexchange.com/questions/108360/how-can-we-run-amd64-architecture-on-a-raspberry-pi-4

https://www.novaspirit.com/2019/04/15/run-x86-arm/

But "forget trying to run windows on it"

from

https://forums.raspberrypi.com/viewtopic.php?t=242211

Another possibility may be to cross compile.

https://earthly.dev/blog/cross-compiling-raspberry-pi/

Just try box64 first?

https://github.com/orgs/AppImage/discussions/1294

box64 with prebuilt binaries,

box64/docs/COMPILE.md at main · ptitSeb/box64

Error:

Cannot mount AppImage, please check your FUSE setup : r/debian

apt install fuse led to

The following packages will be removed:

fuse3 gvfs-fuse ntfs-3g xdg-desktop-portal xdg-desktop-portal-gtk xdg-desktop-portal-wlr

The following NEW packages will be installed:

  fuse

0 upgraded, 1 newly installed, 6 to remove and 4 not upgraded.

But even with that, the same fuse error for the x86-64 appimage running on box64. So, put back fuse3, ntfs-3g, and others. The warnings / errors seen are:

[BOX64] Binary search path: ./:bin/:/usr/local/sbin/:/usr/local/bin/:/usr/sbin/:/usr/bin/:/sbin/:/bin/:/usr/local/games/:/usr/games/

[BOX64] Looking for /media/user/SSD256GB01/rpiOpenSpace/OpenSpace-0.20.1-1-x86_64.AppImage

[BOX64] Rename process to "OpenSpace-0.20.1-1-x86_64.AppImage"

[BOX64] Warning, CALL to 0x0 at 0x401efd (0x401efc)

This doesn't look like a squashfs image.

[BOX64] Warning: Unsupported Syscall 0x54h (84)

Cannot mount AppImage, please check your FUSE setup.

You might still be able to extract the contents of this AppImage 

if you run it with the --appimage-extract option. 

See https://github.com/AppImage/AppImageKit/wiki/FUSE 

for more information