Steam Link

Steam Link

Raspberry Pi OS with Desktop Kernel 5.10 Bullseye - Can't Start Steam Link
I've just updated to the 2021-10-30 Raspberry Pi OS bullseye release.

I had to install Steam Link via the below commands as "sudo apt install steamlink" couldn't find the package.

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

Once installed, I then ran Steam Link and it began to update to the latest stable version.

When I now try and start Steam Link, it tries to install the required libgcc1 package. However, the system finds libgcc-s1 and switches to that and finds it doesn't need updating. Steam Link still thinks it needs libgcc1 though. I tried forcing the install of libgcc1 with "sudo -f install libgcc1" but it again switches to libgcc-s1 and states it's already up-to-date.

Ideas on what to try next would be greatly appreciated.

*EDIT*
Marked slouken's reply as an answer. Streaming is now working from the console on Bullseye. Full streaming capabilities still a little flakey but main problem has been resolved. Thanks slouken!
Originally posted by slouken:
The latest beta has experimental support for running on the console on Bullseye.
< >
Showing 1-15 of 24 comments
I have the same problem, The the way I managed to make it to work (sort of) is installing the beta version. The "stable" version has some issues with the dv4 3D driver that is included on bullseye...
Yeah, I had to change the boot/config.txt to have:
dtoverlay=vc4-fkms-v3d
instead of:
dtoverlay=vc4-kms-v3d

That allowed me to pass a V3D error that came up. If I commented out the whole line I would lose the taskbar.

I then stumbled into this error I'm having now. How do I install the beta? I can't use "echo beta >~/.local/share/SteamLink/.update_branch".
That's how I did it, But I used the echo command right after installing the stable Deb. And I managed to get the view of my computer (even with vc4 enabled)...
It crashes when I open my computer :steamfacepalm:
I guess we'll have to wait until steam link caches up with bullseye... :(
For easier vc4 and kms and fkms switch, you can use "Commander Pi"
I must have typed the command wrong earlier as I have the beta running now. No luck getting a connection to my desktop though. Steam link just restarts. Like you say, a wait might be in order.
Did you guys resolve this issue? I have the exact same problem...
Nope. Just waiting for Valve to get round to it as I don't think there is anything we can do.
I've just hit the same thing - also seeing a "shell: error while loading shared libraries: libbrcmGLESv2.so: cannot open shared object file: No such file or directory" error after getting past the libgcc1 error.
Good shout, I forgot to update saying I got that message. Hopefully, this will be looked at soon enough.

*EDIT*
Just went back and checked what errors I was getting. I start Steam Link and try and connect to my desktop. Steam Link then restarts. The below image shows what is left in the terminal.

https://ibb.co/NZYvPqV

I think I did get the shell error up until switching Steam Link to the beta build. Are you using the beta build @v21?
Originally posted by Mary-Jane Rottencrotch:
Good shout, I forgot to update saying I got that message. Hopefully, this will be looked at soon enough.

*EDIT*
Just went back and checked what errors I was getting. I start Steam Link and try and connect to my desktop. Steam Link then restarts. The below image shows what is left in the terminal.

https://ibb.co/NZYvPqV

I think I did get the shell error up until switching Steam Link to the beta build. Are you using the beta build @v21?
I have 100% the same issues and it was the same thing for me with the shell error: it was gone when I opted in for the beta.
I am getting this when i try to run steamlink.

Packege cec-utils needs to be installed
Packege libffi6:armhf needs to be installed
Packege libgcc1:armhf needs to be installed
shell: error while loading shared libraries: libbrcmGLESv2.so: cannot open shared object file: No such file or directory
I fixed this issue by installing the previous Raspberry OS: Buster. Working like a charm now. I'll go back to Bullseye when this will be fixed by Valve.
We can only hope Bullseye hasn't left Valve with too much to update.

If Valve happen to be reading, do you know if these issues will be looked at anytime soon?
I can at least get steam link to open on Raspberry Pi OS Bullseye, streaming isn't working but maybe I can get that figured out also.

Make sure you've got the update branch set to beta. You can do this by ensuring that
~/.local/share/SteamLink/.update_branch
and it contains
beta

Edit
~/.local/share/SteamLink/steamlinkdeps.txt
and change the line
libgcc1:armhf
to
libgcc-s1:armhf

This will stop that install from always trying to happen.

It opens fine now, but crashes when I try to stream from my linux box.
This could be down to the fact Pi OS Bullseye now uses the standard Linux KMS video driver and not its own bespoke driver as in Pi OS Buster.

This led me to think could we just try installing the Linux version of Steam Link and see if that works? I quickly attempted this last night via flatpak which is what is used to distribute the Linux version of Steam Link but I think flatpak recognises I'm on Pi OS and states it can't find the Steam Link package.
The author of this thread has indicated that this post answers the original topic.
The latest beta has experimental support for running on the console on Bullseye.
< >
Showing 1-15 of 24 comments
Per page: 1530 50