Install steps are a tad misleading, here are mine

[robbarclay]

Figured I would provide this in case anyone else ran into problems.

install required bits

sudo pacman -S cmake ffmpeg git-lfs
paru -S evdi-dkms

clone the virtual display fork

git clone https://github.com/MrOz59/Apollo-Linux.git
cd Apollo-Linux

pull all submodules because they don't ever get pulled otherwise

git submodule update --init --recursive

pull git-lfs content (important for build-deps/ffmpeg)

git lfs install
git lfs pull

patch broken boost hash

perl -pi -e 's/f48b48390380cfb94a629872346e3a81370dc498896f16019ade727ab72eb1ec/67acec02d0d118b5de9eb441f5fb707b3a1cdd884be00ca24b9a73c995511f74/g' cmake/dependencies/Boost_Sunshine.cmake

clean previous failed builds

rm -rf cmake-build-debug

configure build as cuda doesn't work properly for me with apollo on linux

cmake -S . -B cmake-build-debug
-DCMAKE_BUILD_TYPE=Debug
-DSUNSHINE_ENABLE_CUDA=OFF
-DCUDA_FAIL_ON_MISSING=OFF

compile

cmake --build cmake-build-debug -j(nproc)

package/install

makepkg -si

load evdi module

sudo modprobe evdi

[10rb1988]

Thank you so much for creating this guide. It was incredibly helpful.

An issue I am having on the latest CachyOS is that after following these instructions, Apollo will run and the server is discoverable to Moonlight clients on my network, however the WebUI for configuration is just a blank page. There are no errors in the terminal, I have tried running as SU and as a regular user, I have deleted /home/USER/.config/sunshine/, recreated this folder with both root and user permissions / ownership, attempted connecting via HTTP and HTTPS, and deleted the rebuilt everything related to Apollo and Sunshine.

If I then install the latest Apollo through Pacman, the WebUI and server work as expected. Has anyone else seen this behavior? Or am I messing something up.

[robbarclay]

oh i have a fix for that if you get to a blank webpage, i ran into it myself but i thought it was only because i originally had another version of sunshine installed and it was dirtying up install.
These are the commands i ran to make the sym link and shift old configuration if its there:

Apollo currently expects runtime assets here

sudo mkdir -p /usr/local

sudo ln -sfn /usr/share/apollo /usr/local/assets

avoid stale/old Sunshine config breaking first launch

mv ~/.config/sunshine ~/.config/sunshine.backup.apollo 2>/dev/null

systemctl --user daemon-reload

systemctl --user reset-failed apollo

systemctl --user enable --now apollo

[10rb1988]

Hey, thank you again for such a detailed guide. With your help, I have this fork of Apollo running. Now I have to find a way to fix 'Warning: [VDISPLAY] Failed to open EVDI device 0'.

Thanks again.

[robbarclay]

what i found in the end is this branch doesn't actually work when the screen is off (which is probably when you're seeing that error?) for linux, at least not without doing additional steps that would work on the main apollo branch as well.

I ended up doing a workaround where i dump a copy of the monitor’s EDID to disk and tell the NVIDIA driver to permanently associate that EDID with my gpu's primary connector, even when the physical monitor goes to sleep or turns off.
It's a solution I had AI implement and in its current form very specific to my hardware, not really something i can easily share.