Steam Link

Steam Link

No hardware decode on AMD: INFO: CVAAPIAccel: Couldn't load libva.so.1
I'm not getting hardware decode with the Linux SteamLink app on my AMD Renoir laptop.

When I run:
flatpak run com.valvesoftware.SteamLink
in the terminal I can see the following in the output:

INFO: CVAAPIAccel: Couldn't load libva.so.1

if I run
flatpak run --command=bash com.valvesoftware.SteamLink
to get a terminal in the SteamLink runtime I can see that in /lib/x86_64-linux-gnu there is a libva.so.2 but no libva.so.1. It looks like SteamLink is trying to use an old version of libva that isn't shipped with the Freedesktop runtime. You'll either need to start using libva.so.2 or ship libva.so.1 with the app.
< >
Showing 1-8 of 8 comments
Having the same trouble, with Intel but I don't think it makes much of a difference. Hope this gets addressed soon, none of this matters if there isn't at least hardware acceleration.
This problem still exists in 1.1.75.
It's because your system is probably libva2 based, like mine...whereas steam link is using libva

--edit, read the end of the post now, and realised you already said that, just ignore me :)
I'm seeing the same symptom:

INFO: CVAAPIAccel: Couldn't load libva.so.1

I'd prefer to use the Steam Link app instead of full steam for now because of the proper 30fps support.

The 60fps (Defualt) in full fat steam only gives half the bitrate when capped at 30fps edit: and has an inconsistent frame time when targeting 30fps.
I updated to 1.1.80.197 and VAAPI is working now, Thanks!

sudo flatpak update com.valvesoftware.SteamLink
Unfortunately, while we're making progress VAAPI is still broken on my system. The relevant output on the console is as follows:

INFO: ffmpeg verbose: Opened VA display via X11 display :99.0. INFO: ffmpeg verbose: libva: VA-API version 1.8.0 INFO: ffmpeg error: libva: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) INFO: ffmpeg error: Failed to initialise VAAPI connection: -1 (unknown libva error). INFO: CVAAPIAccel: av_hwdevice_ctx_create() failed INFO: libavcodec software decoding with 4 threads

If I try to force the driver using LIBVA_DRIVER_NAME=radeonsi then the system completely locks up and needs to be restarted using the physical power button.

So, it looks like what's happening is that while the UI is now running under Wayland, the actual streaming is still using XWayland, and VAAPI on Radeon is broken under XWayland. This https://gitlab.freedesktop.org/mesa/mesa/-/issues/3656 appears to be the relevant upstream issue, but it doesn't look like much progress has been made in the last six months.

If ffmpeg was using Wayland instead of X, though, I believe everything would be working fine, since VAAPI + Wayland does work.

For anyone still trying (tried this with the AUR package, but presume it will work with flatpak as well): start steamlink, options, streaming, more, more, hardware decode -> disable. It should then work.
Originally posted by Masqueey:
For anyone still trying (tried this with the AUR package, but presume it will work with flatpak as well): start steamlink, options, streaming, more, more, hardware decode -> disable. It should then work.
Hi,
Thank you.
This was driving me crazy. I was accessing steam like this. Windows laptop -->xrdp to Linux Desktop running steam client --> main steam computer.
I was getting unable to open display issues. This fixed it but software render is very slow.
But now I know where the problem lies.
Thanks
< >
Showing 1-8 of 8 comments
Per page: 1530 50