[SOLVED] New vdpauinfo error

0BADC0DE · 2024-08-27 05:36:42

Since some time now I am getting this error at the end of the output when running "vdpauinfo":

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
  Serial number of failed request:  39
  Current serial number in output stream:  39

My current system is like this:

GPU: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
Kernel Version : 6.10.6.zen1-1
Plasma Version : 6.1.4-1
KDE Version : 24.08.0-1
Frameworks Version : 6.5.0-1
Qt5 Version : 5.15.14+kde+r7-1
Qt6 Version : 6.7.2-2
Wayland Version : 1.23.0-1
XOrg/Wayland Version : 24.1.2-1
Mesa Version : 1:24.1.6-1
LibVA Version : 2.22.0-1
VDPAU Version : 1.5-3
LIBVA_DRIVER_NAME=iHD
VDPAU_DRIVER=va_gl

This is a completely new thing in my setup.
Is it just my configuration or am I experiencing some regression?
Any hint?

[NOTE]
VDPAU was actually useless in my case (Intel GPU).
I only left "extra/libvdpau" "interface" package and removed all the other ones (libva-vdpau-driver, libvdpau-va-gl, mesa-vdpau, vdpauinfo).

Last edited by 0BADC0DE (2024-09-02 10:15:20)

Head_on_a_Stick · 2024-08-27 06:04:45

Is the libvdpau-va-gl package installed?

0BADC0DE · 2024-08-27 06:05:43

Head_on_a_Stick wrote:

Is the libvdpau-va-gl package installed?

Yes, it is:

extra/libvdpau-va-gl 0.4.2-4 [0 B 190.24 KiB] [Installed]

Head_on_a_Stick · 2024-08-27 06:11:10

Does https://aur.archlinux.org/packages/libv … er-vp9-git work any better?

Reference: https://bbs.archlinux.org/viewtopic.php?id=284251

0BADC0DE · 2024-08-27 07:10:09

Head_on_a_Stick wrote:

Does https://aur.archlinux.org/packages/libv … er-vp9-git work any better?
Reference: https://bbs.archlinux.org/viewtopic.php?id=284251

Tried: it replaced "libva-vdpau-driver" but no changes.

seth · 2024-08-27 07:33:47

Do you still have "VDPAU_DRIVER=va_gl" set?
1. Why are we trying to use vdpau on an intel chip?
2. The error is fundamentally w/ glx, can you "glxinfo -B"?
3. Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

0BADC0DE · 2024-08-27 10:24:10

seth wrote:

Do you still have "VDPAU_DRIVER=va_gl" set?

Yes, sure.

seth wrote:

1. Why are we trying to use vdpau on an intel chip?

I surely am not a gfx stack guru, but this is how it works on my PC (and I get hw video acceleration).
In the next section you can see it seems pretty OK. Anyway...

seth wrote:

2. The error is fundamentally w/ glx, can you "glxinfo -B"?

Here it comes:

$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Xe Graphics (TGL GT2) (0x9a49)
    Version: 24.1.6
    Accelerated: yes
    Video memory: 11905MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.1.6-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.1.6-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.1.6-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

seth wrote:

3. Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

Hmmm... I am not on X since long now so I have no Xorg log available.
I am on Wayland (see my report in 1st message).

Last edited by 0BADC0DE (2024-08-27 10:32:14)

seth · 2024-08-27 11:59:44

VDPAU is a binary-nvidia thing, in all other cases please use VAAPI, not a shim (or worst case: two)

The OP actually doesn't really say which display server is used, but the error is from GLX, ie. xwayland - so the xorg log would still be relevant.
Do you get the same problem when running KDE on X11?

0BADC0DE · 2024-08-27 13:59:48

seth wrote:

VDPAU is a binary-nvidia thing, in all other cases please use VAAPI, not a shim (or worst case: two)

As I said, I am not a gfx stack guru. I have been referencing to the wiki where I din'd understand that VDPAU is for NVIDIA-only hardware:

Video Decode and Presentation API for Unix (VDPAU) is an open source library and API to offload portions of the video decoding process and video post-processing to the GPU video-hardware, developed by NVIDIA.

Maybe it was just me not to fully understand, though: it doesn't sound like "for NVIDIA-developed GPUs only" or "closed source".
I understood that is was a "translation layer".
Anyway, shall I then remove all vdpau-related packages?
That is:
* extra/libva-vdpau-driver (0.7.4-7)
* extra/libvdpau (1.5-3)
* extra/libvdpau-va-gl (0.4.2-4)
* extra/mesa-vdpau (1:24.1.6-1)
* extra/vdpauinfo (1.5-2)

I think that "libvdpau-va-gl" ("VDPAU driver with OpenGL/VAAPI backend") this should be working even without NVIDIA hw, shouldn't it?

seth wrote:

The OP actually doesn't really say which display server is used, but the error is from GLX, ie. xwayland - so the xorg log would still be relevant.

Correct, even though I never mention Xorg server version.
According to xlsclients tool I currently have no application running under xwayland, even though I have this thing installed. In any case, there is no Xorg server running and I cannot find any Xorg-related log in any usual place like /var/log or ~/.local/share.
I have even tried to check with journalctl!

seth wrote:

Do you get the same problem when running KDE on X11?

So, I should install and run a complete X11, right (I have none) to make a test?

Last edited by 0BADC0DE (2024-08-27 14:01:23)

seth · 2024-08-27 14:07:20

Anyway, shall I then remove all vdpau-related packages?

There's no need to remove them, you just don't want to use them for accelerated video playback - VAAPI is simply preferred for your HW/driver and generally supported/used. You'll rather require vaapi->vdpau layers to be able to use VAAPI w/ the binary nvidia drivers.

So, I should install and run a complete X11, right (I have none) to make a test?

I assume you at most lack xorg-server? (Though it's a hard dependency of SDDM)

V1del · 2024-08-27 14:13:33

FWIW if you drop libvdpau-va-gl and get rid of the VDPAU_DRIVER environment variable (maybe also of the one for LIBVA, none of those should generally need to be set), what happens if you just have mesa-vdpau installed? That's afaik built upon gallium and recent intel drivers should™️ be able to make use of that just the same.

A bit more checking makes me think that you'd still need some driver specific pieces for iris, so that's unlikely to work.

But generally speaking VDPAU was never intel driver's strong suit, there are well working implementations for nouveau and radeon and as already mentioned by seth, you should prefer vaapi whenever possible anyway, since that makes up the majority of the modern open HWVA stack and is also what's implemented by chromium and firefox.

Last edited by V1del (2024-08-27 14:18:39)

seth · 2024-08-27 14:43:28

Ftr, libva-vdpau-driver is the wrong direction and translates VDPAU to VAAPI, you don't want to use that at all.
It's also virtually unmaintained - make sure that's nowhere installed on your system.

libvdpau-va-gl is limited to h264 acceleration, so that's not great.
mesa-vdpau is only for AMD and nvidia (nouveau)

There's no real-world reason having to use vdpau with your system.
One wants to use VDPAU with the binary nvidia driver to avoid the translation layer and in all other context use VAAPI, which is likely the default or only option anywhere anyway.

Wrt. whether you "shall" remove the vdpau packages: no, but I would. Remove all VDPAU support to not accidentally use it and deal with any problem of its absence iff and when they arrive.

0BADC0DE · 2024-08-28 20:09:57

error: failed to prepare transaction (could not satisfy dependencies)
:: removing libvdpau breaks dependency 'libvdpau' required by ffmpeg
:: removing libvdpau breaks dependency 'libvdpau' required by ffmpeg4.4
:: removing libvdpau breaks dependency 'libvdpau' required by mpv

I cannot remove it without breaking fat least fmpeg and, in an avalanche or dependencies, firefox and falkon (via qt6-webengine) .
I do need to have that vdpau!

seth · 2024-08-28 20:26:46

That's simply the interface library, it doesn't provide a VDPAU implementation in and by itself.
You can keep that

0BADC0DE · 2024-08-29 10:09:06

seth wrote:

That's simply the interface library, it doesn't provide a VDPAU implementation in and by itself.
You can keep that

Thanks for clarifying. I suspect that some more details in the wiki on how all those bits are stacked would help a lot.
You rock, Seth!

seth · 2024-08-29 12:31:01

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2024-08-27 05:36:42

[SOLVED] New vdpauinfo error

#2 2024-08-27 06:04:45

Re: [SOLVED] New vdpauinfo error

#3 2024-08-27 06:05:43

Re: [SOLVED] New vdpauinfo error

#4 2024-08-27 06:11:10

Re: [SOLVED] New vdpauinfo error

#5 2024-08-27 07:10:09

Re: [SOLVED] New vdpauinfo error

#6 2024-08-27 07:33:47

Re: [SOLVED] New vdpauinfo error

#7 2024-08-27 10:24:10

Re: [SOLVED] New vdpauinfo error

#8 2024-08-27 11:59:44

Re: [SOLVED] New vdpauinfo error

#9 2024-08-27 13:59:48

Re: [SOLVED] New vdpauinfo error

#10 2024-08-27 14:07:20

Re: [SOLVED] New vdpauinfo error

#11 2024-08-27 14:13:33

Re: [SOLVED] New vdpauinfo error

#12 2024-08-27 14:43:28

Re: [SOLVED] New vdpauinfo error

#13 2024-08-28 20:09:57

Re: [SOLVED] New vdpauinfo error

#14 2024-08-28 20:26:46

Re: [SOLVED] New vdpauinfo error

#15 2024-08-29 10:09:06

Re: [SOLVED] New vdpauinfo error

#16 2024-08-29 12:31:01

Re: [SOLVED] New vdpauinfo error

Board footer