diff --git a/content/Asahi_Linux.md b/content/Asahi_Linux.md index cdb40a6..2ba3fb3 100644 --- a/content/Asahi_Linux.md +++ b/content/Asahi_Linux.md @@ -58,11 +58,6 @@ On my machine, the launch arguments look like: `PRESSURE_VESSEL_FILESYSTEMS_RW=/ There is some extra complication caused my muvm putting its `XDG_RUNTIME_DIR` in a weird spot interfering with monado's ability to connect to itself. Therefore, my reccomended launch order is as follows: -Launch steam from inside a terminal (so that you can see logs when things inevitably work incorrectly): -```sh -steam -``` - Lanuch monado-service: ```sh muvm -it -- bash @@ -75,6 +70,33 @@ chmod 700 /run/user/1000/ XDG_RUNTIME_DIR=/run/user/1000/ ./monado-service ``` +Launch Steam. + +Optionally, `tail -f ~/.steam/steam/logs/console-linux.txt` so you can see errors when a game fails to do the correct thing. + Ensure that `openvrpaths.vrpath` has the correct contents and hasn't been overwritten by steam. -Launch a game. \ No newline at end of file +Launch a game. + +## wivrn + +Due to , the terminal that you're running WiVRn within *must* be the one that's starting the VM. +Therefore, you should start wivrn before you start steam. + +There are also some extra considerations, such as the avahi daemon not being visible within the VM. + +Here's what I did that worked: + +```sh +muvm -it -p 9757/udp -p 9759 -- bash +``` + +```sh +mkdir -p /run/user/1000/ +chmod 700 /run/user/1000/ +# setup the rest of the environment variables, ensuring XRT_DEBUG_UI is *not* enabled. +XDG_RUNTIME_DIR=/run/user/1000/ ./wivrn-server --no-publish-service --no-manage-active-runtime +``` + +On my machines, for some reason, WiVRn produced different commit hashes when applying patches, even though the base monado commit and wivrn commit were the same. +If this happens to you, you can workaround it by adding `IPC_IGNORE_VERSION=1` to your steam launch arguments, *but you should verify that everything was built off of the same commit first.* \ No newline at end of file