I’m on Nobara Linux and in the Hardware acceleration options my AMD Card is not getting listed. I’ve gotten it to run once, but after beta update 3.4 it stopped working. I know I downloaded a shared ffmpeg thingy with which I replaced the shipped .so files from Teamspeak and it worked flawlessly until I updated. I tried building them myself, but I have no Idea how and where those files end up. I tried using the files from the ffmpeg instance I have installed, but had no luck. I must be doing something wrong, but I have no idea what and the stuff on that conan ffmpeg github page wasn’t helpful to my beginner brain either.
I know that ffmpeg vaapi works because I transcode files with it and obs works without issues, even with av1.
I’ll forward this to our QA department to investigate.
3 Likes
Having the exact same issue on a 9070xt on Nobara Linux
Tried it via Flatpak and the official image downloaded from the Teamspeak website.
Happy to run some troubleshooting if one could point me towards the right location.
If there is anything I can provide I’d be happy to help if I can. I checked what Teamspeak is complaining about and on each start of Teamspeak it tells me that libva errored out because of the wrong “ELF class“, which is 32. Is Teamspeak supposed to use 64 bit libraries? And how would I be able to confirm/fix that?
I got it fixed. To force VA-API to use the lib64 directory where the 64bit mesa driver lies, add this environment variable: LIBVA_DRIVERS_PATH=/usr/lib64/dri:$LIBVA_DRIVERS_PATH
I thought I fixed it for the most part, but Decoding still doesn’t work with this. I don’t see any hardware accelerated decoding options for my AMD hardware. I can stream with AV1 and H.264 though, which is half a win
I found another solution. Apparently amf isn’t blocked behind the amdgpu-pro driver anymore, so you can install its runtime by itself now. If you’re on the Nobara Discord server you can find the download to the .rpm file in the chat history or here.
Haha, I got rid of my Discord for obvious security/privacy related reasons.
Is there a direct link to this RPM package? I would appreciate it 
I assume this fixed it for you?
You’re a step forward, good on you. They sent me the rpm directly and sent the source to it too, but the source is uncompiled. Here’s the link to that if you know what you’re doing.
There is no direct link to the rpm package anymore sadly, but I can send you that file if you let me know how I can contact you (That really only works with trust me bro guarantee). The instructions on the github page are pretty simple though. You should be able to get it running yourself without issues.
Cheers my man. For anyone else that runs into this problem I made a little repo that fixes this via a bash script and does the work for you. GitHub - etsiej/mesa-safe-amf · GitHub
For the Teamspeak team, this is a workaround and should not be the complete solution. Teamspeak should support full VAAPI encoding and decoding on fedora based systems.
1 Like