Closed luzfcb closed 3 months ago
I tested pairing Moonlight 2.7.0 with all Sunshine server versions from 19.4 up to v2024.601.193044, but could not pair with any of them.
I wanted to try downgrade Moonlight to 2.6.x to test it, but I don't know how to find a binary compatible with Batocera/Knulli and my Anbernic RG35xx-h.
I'm using The Knulli linux (a batocera fork) https://github.com/knulli-cfw/distribution because it is compatible with the Ambernic RG35xx-h (that uses the Allwinner H700 processor)
I decided to compile Moonlight 2.6. from source using the batocera configuration (https://github.com/knulli-cfw/distribution/tree/knulli-main/package/batocera/emulators/moonlight-embedded) , and I still get the same error with any version of Sunshine. weird error.
Interesting fact: moonlight-embedded 2.6.0 from the original RG35xx-h ROM works as expected, while the batocera/knulli version does not.
The only difference between the two that I could see is that moonlight-embedded 2.6.0 of the original RG35xx-h ROM uses very old versions of OpenSSL (1.x) and libcurl.
I have no idea if this is the cause (incompatibility with some change in OpenSSL or libcurl)
This bug is related to the OpenSSL
and libcurl
versions, and it has already been fixed on Batocera.linux master branch
Related pull-requests:
https://github.com/batocera-linux/buildroot/pull/819 https://github.com/batocera-linux/batocera.linux/pull/11962
Please provide the following info.
NVidia Geforce Experience version: Do not apply. Steam Running on Linux via https://github.com/Steam-Headless/docker-steam-headless and a Sunshine server v0.22.0 (also tested with 0.23.1 and the same problem happened) Moonlight Embedded version: 2.7.0 Moonlight Embedded source: https://github.com/knulli-cfw/distribution/tree/knulli-main/package/batocera/emulators/moonlight-embedded Moonlight Embedded running on: Anbernic RG35xx-h Moonlight Embedded running on distribution: Knulli Linux (it's a fork of Batocera Linux)
Verbose output
-verbose
of Moonlight Embedded:What is the expected result?
Successfully execute the pairing process
What happens instead of that?
I noticed that, for some reason, moonlight 2.7.0 is sending a request to unpair right after it manages to pair. I'm not sure if this is the expected behavior.
Just restating, I'm trying to connect to a Sunshine server v0.22.0 (also tested with 0.23.1 and the same problem happened)
Is there any reason why
uniqueid
is always0123456789ABCDEF
?Related issue: https://github.com/batocera-linux/batocera.linux/issues/11684