You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using moonlight version 2.5.0 for Raspbian/OSMC on a raspberry pi 3 with raspberry pi OS 64 (just became stable). Moonlight is installed from the bullseye repository and i've disable the default display driver as described in the wiki. I'm using an xbox one controller (model 1914) in combination with the xpadneo driver.
the client connects to an windows 10 PC with latest drivers (511.65) and GFE 3.25.0.84.
It works very well for 10 minutes and the crashes on the pi.
Are there known issues with the 64 bit version of raspberry pi bullseye?
For now I'm switching back to my Raspberry pi Bullseye 32 bit. That one seems to work just as well, but doesn't crash :).
The text was updated successfully, but these errors were encountered:
Hmm, I definitely never saw that behavior, though I only tested the 64-bit version on the Pi 4. It's possible that there's some hardware or driver difference causing the crashes.
Tried my 64bit version again. There were some updates on both the client and host side, so i wanted to see if it fixed stuff. It didn't. This time I'll post some more info. It crashed and said:
Hi!
I'm using moonlight version 2.5.0 for Raspbian/OSMC on a raspberry pi 3 with raspberry pi OS 64 (just became stable). Moonlight is installed from the bullseye repository and i've disable the default display driver as described in the wiki. I'm using an xbox one controller (model 1914) in combination with the xpadneo driver.
the client connects to an windows 10 PC with latest drivers (511.65) and GFE 3.25.0.84.
It works very well for 10 minutes and the crashes on the pi.
Are there known issues with the 64 bit version of raspberry pi bullseye?
For now I'm switching back to my Raspberry pi Bullseye 32 bit. That one seems to work just as well, but doesn't crash :).
The text was updated successfully, but these errors were encountered: