Missing VDPAU Radeon library?

[tld]

This system has an AMD RYZEN 7 3700X graphics card. I'm unclear as to what may have caused this, but when I run xine I get this:

Code: Select all

This is xine (X11 gui) - a free video player v0.99.14.
(c) 2000-2019 The xine Team.
Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory

I'm pretty sure I wasn't getting that until recently. It might be related to my last kernel upgrade (to gentoo-sources-6.18.12).

First of all a) is that the library that would actually be required for VDPAU for this GPU?, and b) would that normally be provided by x11-libs/libvdpau?, and c) what might I be missing that's causing that?

Thanks!
Tom

[grknight]

This looks like media-libs/mesa needs vdpau USE along with VIDEO_CARDS to include radeonsi.
If more help is required, please show emerge -pv media-libs/mesa

[tld]

I'm not even seeing a vdpau USE for mesa?:

Code: Select all

equery uses mesa
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for media-libs/mesa-25.3.6:
 U I
 + + X                    : Add support for X11
 + - abi_x86_32           : 32-bit (x86) libraries
 + + cpu_flags_x86_sse2   : Use the SSE2 instruction set
 - - debug                : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see
                            https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
 + - llvm                 : Enable LLVM backend for Gallium3D.
 - - llvm_slot_18         : Use LLVM 18.
 - - llvm_slot_19         : Use LLVM 19.
 - - llvm_slot_20         : Use LLVM 20.
 + - llvm_slot_21         : Use LLVM 21.
 + + lm-sensors           : Enable Gallium HUD lm-sensors support.
 - - opencl               : Enable the Rusticl Gallium OpenCL state tracker.
 + - proprietary-codecs   : Enable codecs for patent-encumbered audio and video formats.
 - - sysprof              : Enable profiling data capture support using dev-util/sysprof-capture
 - - test                 : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)
 - - unwind               : Add support for call stack unwinding and function name resolution
 - - vaapi                : Enable Video Acceleration API for hardware decoding
 - - valgrind             : Enable annotations for accuracy. May slow down runtime slightly. Safe to use even if not currently using dev-debug/valgrind
 - - video_cards_asahi    : VIDEO_CARDS setting to build support for Apple AGX GPUs
 - - video_cards_d3d12    : VIDEO_CARDS setting to build driver for Microsoft WSL video cards
 - - video_cards_i915     : VIDEO_CARDS setting to build driver for Intel i915 video cards
 - - video_cards_intel    : VIDEO_CARDS setting to build driver for Intel video cards
 - - video_cards_lavapipe : VIDEO_CARDS setting to build Vulkan software rasterizer using LLVMpipe
 - - video_cards_nouveau  : VIDEO_CARDS setting to build reverse-engineered driver for nvidia cards
 - - video_cards_nvk      : VIDEO_CARDS setting to build nouveau vulkan driver for nvidia cards (Turing and newer)
 - - video_cards_r300     : VIDEO_CARDS setting to build only r300, r400 and r500 based chips code for radeon
 - - video_cards_r600     : VIDEO_CARDS setting to build only r600, r700, Evergreen and Northern Islands based chips code for radeon
 - - video_cards_radeon   : VIDEO_CARDS setting to build driver for ATI radeon video cards
 + + video_cards_radeonsi : VIDEO_CARDS setting to build only Southern Islands based chips code for radeon
 - - video_cards_virgl    : VIDEO_CARDS setting to build driver for virgil (virtual 3D GPU)
 - - video_cards_vmware   : VIDEO_CARDS setting to build driver for vmware video cards
 - - video_cards_zink     : VIDEO_CARDS setting to build Zink OpenGL-over-Vulkan Gallium driver
 - - vulkan               : Add support for 3D graphics and computing via the Vulkan cross-platform API
 - - wayland              : Enable support for dev-libs/wayland
 + - zstd                 : Enable support for ZSTD compression

I do have that radeonsi in my VIDEO_CARDS, and you can see it enabled above. I also did verify that vdpau does require that, as xine fails if I try to use "xine -V vdpau <file>".

Odd one for sure.

Tom

[tld]

Yea...just not getting this:

Code: Select all

grep -i vdpau /var/log/Xorg.0.log
[   105.350] (II) AMDGPU(0): [DRI2]   VDPAU driver: radeonsi

vdpauinfo
display: :0.0   screen: 0
Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1

Tom

[grknight]

Oh, so mesa removed VDPAU support with version 25.3.0

Now anything that depended on it should be removed. Please disable all vdpau on your system.

Edit: Try vaapi instead system-wide. Mesa should provide a vaapi driver for radeonsi

[tld]

Oh, so mesa removed VDPAU support with version 25.3.0

Now anything that depended on it should be removed. Please disable all vdpau on your system.

Oh man. I assume then that I should be using vaapi instead. Does that require anything different in terms of kernel? I would assume not.

Thanks!
Tom

[logrusx]

It doesn't. Just the USE flags and recompile everything affected.

Best Regards,
Georgi

[tld]

I thought as much. Thanks!

Tom

[tld]

Wow...just recompiled with the vaapi USE instead of vdpau. Now I seem to be missing this:

Code: Select all

xine -V vaapi *.mp4
This is xine (X11 gui) - a free video player v0.99.14.
(c) 2000-2019 The xine Team.
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0

So now what am I missing? Mesa clearly has both the vaapi and video_cards_radeonsi USE enabled??

Tom

[logrusx]

Check here: https://wiki.gentoo.org/wiki/Radeon
or here: https://wiki.gentoo.org/wiki/AMDGPU

Best Regards,
Georgi

[tld]

WOW. So the only thing I saw in there that I thought might help is the LIBVA_DRIVER_NAME=radeonsi ENV variable but that doesn't help:

Code: Select all

LIBVA_DRIVER_NAME=radeonsi xine -V vaapi *.mp4
This is xine (X11 gui) - a free video player v0.99.14.
(c) 2000-2019 The xine Team.
libva info: VA-API version 1.22.0
libva info: User environment variable requested driver 'radeonsi'
libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0

I also just realized that the above library IS actually there??

Code: Select all

ls -l /usr/lib64/va/drivers/radeonsi_drv_video.so
lrwxrwxrwx 1 root root 26 Mar 18 10:58 /usr/lib64/va/drivers/radeonsi_drv_video.so -> ../../libgallium-25.3.6.so

Also note that that was just compiled today. Is that library somehow broken of maybe xine??? Running out of ideas here.

Tom

[tld]

Some more on this:

Code: Select all

equery b /usr/lib64/va/drivers/radeonsi_drv_video.so
 * Searching for /usr/lib64/va/drivers/radeonsi_drv_video.so ... 
media-libs/mesa-25.3.6 (/usr/lib64/va/drivers/radeonsi_drv_video.so -> ../../libgallium-25.3.6.so)
media-libs/mesa-25.3.6 (/usr/lib64/libgallium-25.3.6.so)

Code: Select all

equery uses mesa
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for media-libs/mesa-25.3.6:
 U I
 + + X                    : Add support for X11
 + + abi_x86_32           : 32-bit (x86) libraries
 + + cpu_flags_x86_sse2   : Use the SSE2 instruction set
 - - debug                : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see
                            https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
 + + llvm                 : Enable LLVM backend for Gallium3D.
 - - llvm_slot_18         : Use LLVM 18.
 - - llvm_slot_19         : Use LLVM 19.
 - - llvm_slot_20         : Use LLVM 20.
 + + llvm_slot_21         : Use LLVM 21.
 + + lm-sensors           : Enable Gallium HUD lm-sensors support.
 - - opencl               : Enable the Rusticl Gallium OpenCL state tracker.
 + + proprietary-codecs   : Enable codecs for patent-encumbered audio and video formats.
 - - sysprof              : Enable profiling data capture support using dev-util/sysprof-capture
 - - test                 : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)
 - - unwind               : Add support for call stack unwinding and function name resolution
 + + vaapi                : Enable Video Acceleration API for hardware decoding
 - - valgrind             : Enable annotations for accuracy. May slow down runtime slightly. Safe to use even if not currently using dev-debug/valgrind
 - - video_cards_asahi    : VIDEO_CARDS setting to build support for Apple AGX GPUs
 - - video_cards_d3d12    : VIDEO_CARDS setting to build driver for Microsoft WSL video cards
 - - video_cards_i915     : VIDEO_CARDS setting to build driver for Intel i915 video cards
 - - video_cards_intel    : VIDEO_CARDS setting to build driver for Intel video cards
 - - video_cards_lavapipe : VIDEO_CARDS setting to build Vulkan software rasterizer using LLVMpipe
 - - video_cards_nouveau  : VIDEO_CARDS setting to build reverse-engineered driver for nvidia cards
 - - video_cards_nvk      : VIDEO_CARDS setting to build nouveau vulkan driver for nvidia cards (Turing and newer)
 - - video_cards_r300     : VIDEO_CARDS setting to build only r300, r400 and r500 based chips code for radeon
 - - video_cards_r600     : VIDEO_CARDS setting to build only r600, r700, Evergreen and Northern Islands based chips code for radeon
 - - video_cards_radeon   : VIDEO_CARDS setting to build driver for ATI radeon video cards
 + + video_cards_radeonsi : VIDEO_CARDS setting to build only Southern Islands based chips code for radeon
 - - video_cards_virgl    : VIDEO_CARDS setting to build driver for virgil (virtual 3D GPU)
 - - video_cards_vmware   : VIDEO_CARDS setting to build driver for vmware video cards
 - - video_cards_zink     : VIDEO_CARDS setting to build Zink OpenGL-over-Vulkan Gallium driver
 - - vulkan               : Add support for 3D graphics and computing via the Vulkan cross-platform API
 - - wayland              : Enable support for dev-libs/wayland
 + + zstd                 : Enable support for ZSTD compression

Everything looks right there as far as I can tell??

That aside....HELP!! I want to test this in other players like mpv and/of vlc but I CANNOT find any options to force the video driver in either of those??!!

If anyone knows that PLEASE let me know.

Tom

[tld]

It appears that vlc IS using that driver:

Code: Select all

vlc *.mp4
VLC media player 3.0.23 Vetinari (revision 3.0.23-2-0-g79128878dd)
[000055b041a81590] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[000055b041ba2ca0] qt interface error: Unable to load extensions module
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
[00007f8c04c68e90] avcodec decoder: Using Mesa Gallium driver 25.3.6 for AMD Radeon RX 5500 XT (radeonsi, navi14, LLVM 21.1.8, DRM 3.64, 6.18.12-gentoo) for hardware decoding

But again, xine fails:

Code: Select all

export LIBVA_DRIVER_NAME=radeonsi
xine -V vaapi *.mp4
This is xine (X11 gui) - a free video player v0.99.14.
(c) 2000-2019 The xine Team.
libva info: VA-API version 1.22.0
libva info: User environment variable requested driver 'radeonsi'
libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
echo $?
1

Any clues would be appreciated.

Tom

[grknight]

But again, xine fails:

Code: Select all

export LIBVA_DRIVER_NAME=radeonsi
xine -V vaapi *.mp4
This is xine (X11 gui) - a free video player v0.99.14.
(c) 2000-2019 The xine Team.
libva info: VA-API version 1.22.0
libva info: User environment variable requested driver 'radeonsi'
libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
echo $?
1

How does it "fail"? All signs point to success here ("returns 0" is success)

[logrusx]

Are you sure your command is OK? Because as grknight pointed out, the library is successfully opened. The 1 return code comes from the xine command, not from opening the library. Can you try with something that's not *.mp4 or other wildcard?

Best Regards,
Georgi

EDIT: I just emerged it but it starts and then dumps core. Maybe xine is problematic? Did you update it recently? Can you try with the older version?

EDIT: found it. This is a wrong command:

Code: Select all

xine -V vaapi *.mp4

When I run this command it returns 1, but when I omit selecting a video driver it starts but breaks and dumps core. It might be something with my particular installation, but since I don't use it I don't want to dig deeper.

Also why not just use mpv?

Best Regards,
Georgi

[tld]

Are you sure your command is OK? Because as grknight pointed out, the library is successfully opened. The 1 return code comes from the xine command, not from opening the library. Can you try with something that's not *.mp4 or other wildcard?

Best Regards,
Georgi

EDIT: I just emerged it but it starts and then dumps core. Maybe xine is problematic? Did you update it recently? Can you try with the older version?

To be clear, up until now I've NEVER used xine except with VDPAU, which I just had to abandon given that mesa no longer supports it. So this is the first I've even tried it with vaapi. So it's not as though it used to work or the like.

I think xine is the problem, but have no clue why. As I was saying, VLC seems fine with it.

Does anyone know how to specify a driver with the mpv player?? I've been going nuts trying to figure out if it's using it.

Tom

[logrusx]

Are you sure your command is OK? Because as grknight pointed out, the library is successfully opened. The 1 return code comes from the xine command, not from opening the library. Can you try with something that's not *.mp4 or other wildcard?

Best Regards,
Georgi

EDIT: I just emerged it but it starts and then dumps core. Maybe xine is problematic? Did you update it recently? Can you try with the older version?

To be clear, up until now I've NEVER used xine except with VDPAU, which I just had to abandon given that mesa no longer supports it. So this is the first I've even tried it with vaapi. So it's not as though it used to work or the like.

I think xine is the problem, but have no clue why. As I was saying, VLC seems fine with it.

Does anyone know how to specify a driver with the mpv player?? I've been going nuts trying to figure out if it's using it.

Tom

Code: Select all

~ mpv *.mp4 --vo=vaapi
Playing: 10. Section Summary.mp4
 ● Video  --vid=1  (h264 1280x720 30 fps) [default]
 ● Audio  --aid=1  (aac 2ch 44100 Hz 128 kbps) [default]
 ● Subs   --sid=1  'srt' (subrip) [external]
[vo/vaapi] Warning: this compatibility VO is low quality and may have issues with OSD, scaling, screenshots and more.
[vo/vaapi] vo=gpu-next is the preferred choice in any case and includes VA-API support via hwdec=vaapi or vaapi-copy.
AO: [pipewire] 44100Hz stereo 2ch doublep
VO: [vaapi] 1280x720 yuv420p
AV: 00:00:18 / 00:03:46 (8%) A-V:  0.000
Exiting... (Quit)

~ mpv *.mp4 --vo=gpu-next
Playing: 10. Section Summary.mp4
 ● Video  --vid=1  (h264 1280x720 30 fps) [default]
 ● Audio  --aid=1  (aac 2ch 44100 Hz 128 kbps) [default]
 ● Subs   --sid=1  'srt' (subrip) [external]
AO: [pipewire] 44100Hz stereo 2ch doublep
VO: [gpu-next] 1280x720 yuv420p
AV: 00:00:10 / 00:03:46 (5%) A-V:  0.000
Exiting... (Quit)

Look at the line starting with VO, but why do you need to select the driver manually? It automatically selects the correct one, at least for me:

Code: Select all

~ mpv *.mp4
Playing: 10. Section Summary.mp4
 ● Video  --vid=1  (h264 1280x720 30 fps) [default]
 ● Audio  --aid=1  (aac 2ch 44100 Hz 128 kbps) [default]
 ● Subs   --sid=1  'srt' (subrip) [external]
AO: [pipewire] 44100Hz stereo 2ch doublep
VO: [gpu-next] 1280x720 yuv420p
AV: 00:00:03 / 00:03:46 (1%) A-V:  0.000
Exiting... (Quit)

Also I think xine is to be blamed for this failure. The current release is three years old already.

Best Regards,
Georgi

p.s. why did you need to use xine and why with vdpau?

[tld]

Thanks! You were correct in that mpv WAS using vaapi be default and yes that works.

Yea...no clue what's up with xine. To be clear however xine-lib (which is likely where the issue would be) is less than a year old. Clearly something's screwed there.

Thanks again!
Tom

[tld]

Running xine with --verbose at least clearly indicates an error:

Code: Select all

xine -V vaapi --verbose *.mp4
This is xine (X11 gui) - a free video player v0.99.14.
(c) 2000-2019 The xine Team.
Built with xine library 1.2.13 (1.2.13-20230125hg15249)
Found xine library version: 1.2.13 (1.2.13-20230125hg15249).
...etc...
video_out_vaapi vaapi_open: Deinterlace : 0
video_out_vaapi vaapi_open: Render surfaces : 50
libva info: VA-API version 1.22.0
libva info: User environment variable requested driver 'radeonsi'
libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva info: va_openDriver() returns 0
video_out_vaapi Error : vaQuerySubpictureFormats(): unknown libva error
main: video driver <vaapi> failed

So yea...clearly an issue there.

Thanks again!
Tom

[logrusx]

To be clear however xine-lib (which is likely where the issue would be) is less than a year old.

According to its homepage it's released in Jan 2023: https://sourceforge.net/projects/xine/f ... ib/1.2.13/

Also you didn't answer why you needed to select the driver manually. I sense the real issue might be somewhere else if you need to do that.

Best Regards,
Georgi

[tld]

Also you didn't answer why you needed to select the driver manually. I sense the real issue might be somewhere else if you need to do that.

Best Regards,
Georgi

As it turned out I didn't. I just wasn't sure that it was using it. I hadn't noticed the "VO: [gpu] 1920x1080 yuv420p" line in the console.

And yea, I see what you mean as to xine-lib being old. May have to just move away from using it.

Thanks!
Tom

[grknight]

I would suggest to try xine-lib-1.2.9999 as there are fixes for VAAPI radeonsi specifically after the release.

Otherwise maybe use opengl as the backend for xine-lib. We know vlc works so xine is just being left behind with minimal maintenance when it comes to VAAPI.

[tld]

I would suggest to try xine-lib-1.2.9999 as there are fixes for VAAPI radeonsi specifically after the release.

Yea, I'd like to try that. Question however...I'm actually not sure I've ever run into this. What does the red dash indicate when I look at that:

Code: Select all

equery list -p =media-libs/xine-lib-1.2.9999
 * Searching for xine-lib1.2.9999 in media-libs ...
[-P-] [ -] media-libs/xine-lib-1.2.9999:1

Drawing a blank on that one. That's not just an ordinary mask correct? How do I enable that?

Thanks!
Tom

[grknight]

I would suggest to try xine-lib-1.2.9999 as there are fixes for VAAPI radeonsi specifically after the release.

Yea, I'd like to try that. Question however...I'm actually not sure I've ever run into this. What does the red dash indicate when I look at that:

Code: Select all

equery list -p =media-libs/xine-lib-1.2.9999
 * Searching for xine-lib1.2.9999 in media-libs ...
[-P-] [ -] media-libs/xine-lib-1.2.9999:1

Drawing a blank on that one. That's not just an ordinary mask correct? How do I enable that?

Because it is a from repository build which may fail with every commit, the keywords are removed for safety.
To enable and allow build:

Code: Select all

=media-libs/xine-lib-1.2.9999 **

[tld]

To enable and allow build:

Code: Select all

=media-libs/xine-lib-1.2.9999 **

Thanks! Yes, that did enable it for me.

Unfortunately the emerge failed wildly and can't even get through preparing the source. I think I'm giving up on that one.

Thanks!
Tom