Steam Link now available on Raspberry Pi

[slouken]

The Steam Link app is now available on the Raspberry Pi 3 or newer. A wired network is strongly recommended.

To install, run the following from a command line:

sudo apt update
sudo apt install steamlink

Or download and install directly from Valve:

curl -#Of https://media.steampowered.com/steamlink/rpi/latest/steamlink.deb
sudo dpkg -i steamlink.deb

To run, you can launch it from the Games menu, or run the following from a command line:

steamlink

Support and troubleshooting are available here:
https://steamcommunity.com/app/353380/discussions/6/1743354432807054634/

[Waderola]

Hi everyone.

small problem on my side: I hadn't used Steamlink in a while, but when I tried it yesterday, I could not get it to work properly again. I am streaming from a PC to a Raspberry and after connecting to the Raspberry via SSH and starting Steamlink, I can start the connection to the PC on the screen connected to the Raspberry. However, when this connection is started, I get the following message in the SSH-Terminal window:
"OMX_ErrorInsufficientResources"

On the screen connected to the Raspberry, I cannot see the Steam Big Picture or anything else. It does not do anything anymore.

Before, it used to work just fine.

This is my Raspberry Configuration:
Raspberry Pi 3 Model B Rev 1.2
Raspbian Version 10 Buster
Steamlink - Most recent version

Anyone has any ideas? Thanks in advance!

[slouken]

Escrito originalmente por Waderola:

Hi everyone.

small problem on my side: I hadn't used Steamlink in a while, but when I tried it yesterday, I could not get it to work properly again. I am streaming from a PC to a Raspberry and after connecting to the Raspberry via SSH and starting Steamlink, I can start the connection to the PC on the screen connected to the Raspberry. However, when this connection is started, I get the following message in the SSH-Terminal window:
"OMX_ErrorInsufficientResources"

Try doing this in your SSH terminal first:
export DISPLAY=:0

[geoneil]

Escrito originalmente por slouken:

Escrito originalmente por Waderola:

Hi everyone.

small problem on my side: I hadn't used Steamlink in a while, but when I tried it yesterday, I could not get it to work properly again. I am streaming from a PC to a Raspberry and after connecting to the Raspberry via SSH and starting Steamlink, I can start the connection to the PC on the screen connected to the Raspberry. However, when this connection is started, I get the following message in the SSH-Terminal window:
"OMX_ErrorInsufficientResources"

Try doing this in your SSH terminal first:
export DISPLAY=:0

I'd have thought that error would indicate that the Pi's GPU doesn't have enough RAM allocated to it, might be worth changing the gpu_mem value in config.txt

https://www.raspberrypi.org/documentation/configuration/config-txt/memory.md

Though it's also true that if they're using SSH, the Pi could be trying to forward the display over SSH whether or not they use ssh -X or ssh -Y (or have X11 forwarding turned on in PuTTY) but if they have that turned off (are not using -X or-Y) then I'd have thought they'd have got a different error.

[Crashed]

Escrito originalmente por geoneil:

Escrito originalmente por slouken:

Try doing this in your SSH terminal first:
export DISPLAY=:0

I'd have thought that error would indicate that the Pi's GPU doesn't have enough RAM allocated to it, might be worth changing the gpu_mem value in config.txt

https://www.raspberrypi.org/documentation/configuration/config-txt/memory.md

Though it's also true that if they're using SSH, the Pi could be trying to forward the display over SSH whether or not they use ssh -X or ssh -Y (or have X11 forwarding turned on in PuTTY) but if they have that turned off (are not using -X or-Y) then I'd have thought they'd have got a different error.

Doesn't a DISPLAY=:0 mean to use the first X server listening on the calling terminal? Would you have to know the full address of the X server to redirect to the physical display if calling from a remote terminal?

[Waderola]

Escrito originalmente por geoneil:

I'd have thought that error would indicate that the Pi's GPU doesn't have enough RAM allocated to it, might be worth changing the gpu_mem value in config.txt

https://www.raspberrypi.org/documentation/configuration/config-txt/memory.md

Thanks to you all for your responses. The idea from geoneil actually worked for me. I set the allocated mem to 128 and now it works fine! Again, thanks for the great support!

[geoneil]

Escrito originalmente por Waderola:

Escrito originalmente por geoneil:

I'd have thought that error would indicate that the Pi's GPU doesn't have enough RAM allocated to it, might be worth changing the gpu_mem value in config.txt

https://www.raspberrypi.org/documentation/configuration/config-txt/memory.md

Thanks to you all for your responses. The idea from geoneil actually worked for me. I set the allocated mem to 128 and now it works fine! Again, thanks for the great support!

Glad you got it sorted!

[Crashed]

Escrito originalmente por geoneil:

Escrito originalmente por Waderola:

Thanks to you all for your responses. The idea from geoneil actually worked for me. I set the allocated mem to 128 and now it works fine! Again, thanks for the great support!

Glad you got it sorted!

Generally you only want to go below 128 for systems running headless servers and similar loads, when the additional memory is worth the loss of hardware accelerated graphics.

[geoneil]

Escrito originalmente por Crashed:

Escrito originalmente por geoneil:

Glad you got it sorted!

Generally you only want to go below 128 for systems running headless servers and similar loads, when the additional memory is worth the loss of hardware accelerated graphics.

But who runs Steam Link on a headless server?

[Crashed]

Escrito originalmente por geoneil:

Escrito originalmente por Crashed:

Generally you only want to go below 128 for systems running headless servers and similar loads, when the additional memory is worth the loss of hardware accelerated graphics.

But who runs Steam Link on a headless server?

Some users might not realize that reducing VRAM can compromise graphics acceleration. That said I did reduce the VRAM on a device with a tiny touchscreen but that only runs a very basic GUI that doesn't need acceleration.

[Mikuman]

works great

[pathtostair]

Pie.

[Hipokondriak]

Escrito originalmente por FIZZJN:

I have a Raspberry Pi 3B and it works perfectly. Wired connection is most definitely the way to go but Wireless still works.

I have a pi4 with the latest raspbian updates on the 64 bit os, and steamlink is broken

[slouken]

Escrito originalmente por Hipokondriak:

Escrito originalmente por FIZZJN:

I have a Raspberry Pi 3B and it works perfectly. Wired connection is most definitely the way to go but Wireless still works.

I have a pi4 with the latest raspbian updates on the 64 bit os, and steamlink is broken

In what way is it broken? Are you seeing any error messages?

[erilun06]

Escrito originalmente por slouken:

Escrito originalmente por Hipokondriak:

I have a pi4 with the latest raspbian updates on the 64 bit os, and steamlink is broken

In what way is it broken? Are you seeing any error messages?

I found that there is a plugin for osmc (great Kodi distribution btw) that works amazingly

Had to do some setup though

[sam2qwww]

hola