SteamLink for Raspberry Pi Released
-
So, this may not be the proper place, but if anyone ends up here wanting a simple solution for steam being integrated in your emulationstation and you're NOT on Pi hardware, this works great and I thought I'd add it here to save you some time.
Install Steam, then add this under <systemslist> in:
etc/emulationstation/es_systems.cfg<system> <name>steam</name> <fullname>Steam</fullname> <path>/home/steve/RetroPie/roms/steam</path> <extension>.jpg</extention> <command>steam -bigpicture</command> <platform>steam</platform> <theme>steam</theme> </system>
Create a "steam" folder in your RetroPie/roms directory and plop a jpg in there.
Simple as that. Any theme that already has eye candy for Steam in your menu knows what to do. Exiting Steam brings you back to emulationstation.
You could install Steam games on the machine you're using for RetroPie or just stream from your main desktop gaming rig with Steam streaming--already a part of the full desktop app. -
@RetroAK I guess you can use Moonlight (it's available also in the experimental packages) if your main PC has an Nvidia video card which support it.
-
@mitu
Moonlight is not yet available officially in the RetroPie experimental section, I hope to submit it as soon as I finish some last polishing that I have in mind.However, moonlight-embedded (the version I'm using in that scriptmodule) is also only available for RPI devices (and potentially other SBCs, just not x86). For a full desktop environment the right one to use should be moonlight-qt:
-
@Purduecoz I'm having the same problem, the day I installed steamlink it worked from Emulation station but now it won't, only from the shell.
-
I had to uninstall xorg and install the legacy version to get this working. I'll say, I'm rather impressed. I tried some version of the steam link app I had to manually install a few months ago and it was just absolute garbage. It couldn't get a good signal despite my pi being next to the router, even then, the skipping made it annoying to use. It wouldn't see my pad either. All's been resolved with this. It's great. I fired up Cuphead np.
-
Looks like entering retropie-setup removes the xorg legacy package. Is there a way to get it working with the latest xorg package? I was getting permission problems with that one.
Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
-
@Darksavior said in SteamLink for Raspberry Pi Released:
Looks like entering retropie-setup removes the xorg legacy package. Is there a way to get it working with the latest xorg package? I was getting permission problems with that one.
Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
Xorg and steamlink should be working correctly without the legacy package (which needs to be removed due to permission issues with Xorg.wrap). I think we'll need more details than a single line to troubleshoot your issue.
-
@psyke83 AH, nevermind. Fixed it. Removed xorg and all its dependencies and reinstalled it all. Works now. No idea why it had permission problems in the first place. I'm using the official image.
-
@psyke83 In reinstalling the
xorg
package, it was also reinstalling the legacy stuff so then my problem restarted. So now I've uninstalledxorg
, auto removed the remaining unused packages, and uninstalled the steamlink app. I then reinstalled the steamlink app and let that install the dependencies. Same permission problem. Here's the log.
https://pastebin.com/B0x2qCig
Legacy was working fine because I edited/etc/X11/Xwrapper.config
and addedallowed_users=anybody
but that only exists for the legacy version? -
@Darksavior said in SteamLink for Raspberry Pi Released:
@psyke83 In reinstalling the
xorg
package, it was also reinstalling the legacy stuff so then my problem restarted. So now I've uninstalledxorg
, auto removed the remaining unused packages, and uninstalled the steamlink app. I then reinstalled the steamlink app and let that install the dependencies. Same permission problem. Here's the log.
https://pastebin.com/B0x2qCig
Legacy was working fine because I edited/etc/X11/Xwrapper.config
and addedallowed_users=anybody
but that only exists for the legacy version?I'm seeing some oddities in your Xorg log. Did you enable the experimental GL (fake/full KMS) driver?
Can you show a more complete list of xorg-related packages you have installed? Mine, for reference:
dpkg -l | grep xorg ii xorg 1:7.7+19 armhf X.Org X Window System ii xorg-docs-core 1:1.7.1-1 all Core documentation for the X.org X Window System ii xorg-sgml-doctools 1:1.11-1 all Common tools for building X.Org SGML documentation ii xserver-xorg 1:7.7+19 armhf X.Org X server ii xserver-xorg-core 2:1.19.2-1+rpt1+deb9u2 armhf Xorg X server - core server ii xserver-xorg-input-all 1:7.7+19 armhf X.Org X server -- input driver metapackage ii xserver-xorg-input-libinput 0.23.0-2 armhf X.Org X server -- libinput input driver ii xserver-xorg-input-wacom 0.34.0-1 armhf X.Org X server -- Wacom input driver rc xserver-xorg-legacy 2:1.19.2-1+rpt1+deb9u2 armhf setuid root Xorg server wrapper ii xserver-xorg-video-all 1:7.7+19 armhf X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu 1.2.0-1+b1 armhf X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati 1:7.8.0-1+b1 armhf X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:0.4.4-1+rvt+b1 armhf X.Org X server -- fbdev display driver ii xserver-xorg-video-fbturbo 1.20170324~143242 armhf X.Org X server -- fbturbo display driver ii xserver-xorg-video-nouveau 1:1.0.13-3 armhf X.Org X server -- Nouveau display driver ii xserver-xorg-video-radeon 1:7.8.0-1+b1 armhf X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa 1:2.3.4-1+b3 armhf X.Org X server -- VESA display driver
-
@psyke83 I installed the complete xorg package (which turned out to be the legacy one) at one time but never enabled GL. The only xorg stuff I have installed now are through whatever the steamlink app installs.
ii xorg 1:7.7+19 armhf X.Org X Window System ii xorg-docs-core 1:1.7.1-1 all Core documentation for the X.org X Window System ii xorg-sgml-doctools 1:1.11-1 all Common tools for building X.Org SGML documentation ii xserver-xorg 1:7.7+19 armhf X.Org X server ii xserver-xorg-core 2:1.19.2-1+rpt1+deb9u2 armhf Xorg X server - core server ii xserver-xorg-input-all 1:7.7+19 armhf X.Org X server -- input driver metapackage ii xserver-xorg-input-libinput 0.23.0-2 armhf X.Org X server -- libinput input driver rc xserver-xorg-legacy 2:1.19.2-1+rpt1+deb9u2 armhf setuid root Xorg server wrapper ii xserver-xorg-video-all 1:7.7+19 armhf X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu 1.2.0-1+b1 armhf X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati 1:7.8.0-1+b1 armhf X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:0.4.4-1+rvt+b1 armhf X.Org X server -- fbdev display driver ii xserver-xorg-video-nouveau 1:1.0.13-3 armhf X.Org X server -- Nouveau display driver ii xserver-xorg-video-radeon 1:7.8.0-1+b1 armhf X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa 1:2.3.4-1+b3 armhf X.Org X server -- VESA display driver
-
Problem solved for real. Not sure what it was since I got sick of changing permissions for xorg-related folders with no results. I changed the dev folder's permission and everything in it and that did it.
-
SteamLink was updated to 1.1.30:
https://steamcommunity.com/app/353380/discussions/6/3362406825533076063/
Will it be updated in RetroPie too? -
@Swampy
steamlink
is installed from the Raspbian repositories, so whenever the update is released on their repositories, it will be available for update in RetroPie also. -
@mitu said in SteamLink for Raspberry Pi Released:
@Swampy
steamlink
is installed from the Raspbian repositories, so whenever the update is released on their repositories, it will be available for update in RetroPie also.You're right - keeping in mind that, similar to the Linux .deb for steam, the package functions only as a bootstrapper to fetch the latest release during launch.
Unfortunately, the bootstrapper also handles dependency resolution which usually requires user input to confirm via command-line when new packages are to be installed; the effect would be that you'd be stuck on the
runcommand
dialog.The new release doesn't seem to have this problem, but it can potentially happen in future. If/when it does, I'll add the dependencies to the scriptmodule.
-
-
-
The controller doesn't work in emulationstation any more after exiting steamlink inside. This happens since the latest update of steamlink. I don't know weather it is a problem with RetroPie or steamlink. Steamlink installs new udev rules. Perhaps, this could be the problem.
I mentioned the problem in the steamlink forum too:
https://steamcommunity.com/app/353380/discussions/6/1737760710137252830/ -
For now I have downgraded to version 1.1.45.105:
STEAMLINK_DATA_HOME="${XDG_DATA_HOME:-$HOME/.local/share}"/SteamLink echo "file://$STEAMLINK_DATA_HOME" >"$STEAMLINK_DATA_HOME/update_url" echo "http://media.steampowered.com/steamlink/rpi/steamlink-rpi3-1.1.45.105.tar.gz" >"$STEAMLINK_DATA_HOME/public_build.txt"
seen in https://steamcommunity.com/app/353380/discussions/6/1660069015242109357/
and in https://steamcommunity.com/app/353380/discussions/6/3681064390585946947/Then I also added " --skip-update" in the last line after "/usr/bin/steamlink" in "/opt/retropie/ports/steamlink/steamlink_xinit.sh".
Now it works again for me.
-
The problem is solved with the newest version 1.1.50.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.