Arch Linux

TiZeD

Member

Registered: 2020-04-03

Posts: 13

libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

Archdrivers, hello.

After updating the system, an error appeared when using xfreerdp.

libva: vaGetDriverNameByIndex () failed with unknown libva error, driver_name = (null)
Failed to initialise VAAPI connection: -1 (unknown libva error).

The connection still works, that is, I cling to the machine and work with it without problems. But somehow it is not good to ignore the error.
Also depends on libva:
chromium, firefox, freerdp, gst-libav, simplescreenrecorder, vcl, etc.
Not the worst option now happened from the possible, judging by what I found on the internet, there were more serious things than just a mistake, the software did not work in the principle, for example, the same chromium.
p.s. vainfo command produces:
vaInitialize failed with error code -1 (unknown libva error), exit
Someone has already encountered this, are there solutions?
As an option, only roll back libva itself, until I tried it.

https://sun1-17.userapi.com/yCBmPki9IuC … UxxHsU.jpg

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2020-09-04 16:09:34)

CarbonChauvinist

Member

Registered: 2012-06-16

Posts: 413

Website

Re: libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

More info is needed like what's your graphic stack and what libva drivers you have installed? As well as do you have your env variables set correctly so it knows which driver to use and where to access it from.

$ printenv | grep -i libva
LIBVA_DRIVER_NAME=iHD
LIBVA_DRIVERS_PATH=/usr/lib/dri

Re-read this link and let us know where you stand.

Last edited by CarbonChauvinist (2020-09-05 02:56:28)

---

"the wind-blown way, wanna win? don't play"

TiZeD

Member

Registered: 2020-04-03

Posts: 13

Re: libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

More info is needed like what's your graphic stack and what libva drivers you have installed? As well as do you have your env variables set correctly so it knows which driver to use and where to access it from.

$ printenv | grep -i libva
LIBVA_DRIVER_NAME=iHD
LIBVA_DRIVERS_PATH=/usr/lib/dri

Re-read this link and let us know where you stand.

Good day and thanks for the advice :-)
I am using a native nvidia driver (not nouveau) and a GeForce GTX 1080 card

in /etc/X11/xorg.conf

Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GTX 1080"
EndSection

the output of the commands is as follows:

printenv | grep -i libva
LIBVA_DRIVERS_PATH = / usr / lib / dri /
LIBVA_DRIVER_NAME = vdpau

There were two problems:
1) XDG_RUNTIME_DIR has flown
I find out it using the vainfo command by sudo

now everything is ok -

printenv | grep -i RUNTIME
XDG_RUNTIME_DIR = / run / user / 1000

2) there were problems with libva-vdpau-driver
after reinstalling libva-vdpau-driver - vainfo output works:

vainfo
vainfo: VA-API version: 1.8 (libva 2.8.0)
vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main: VAEntrypointVLD
VAProfileMPEG4Simple: VAEntrypointVLD
VAProfileMPEG4AdvancedSimple: VAEntrypointVLD
<unknown profile>: VAEntrypointVLD
VAProfileH264Main: VAEntrypointVLD
VAProfileH264High: VAEntrypointVLD
VAProfileVC1Simple: VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD

The error with xfreerdp is gone
But now there is a new one ... And now xfreerdp is not working

segmentation fault (core dumped)

I also tried reconfiguring everything to work nouveau, because I thought that this might be a solution, due to the fact that with vdpau freerdp may have problems. It was possible to switch, but wainfo started giving the same error again ... But xfreerdp worked, although it gave the same error as described above in the first message.

I think ... Is it worth continuing to look for a solution based on nouveau or still try to solve the problem using native nvidia and vdpau?

TiZeD

Member

Registered: 2020-04-03

Posts: 13

Re: libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

Total:

a) if there are problems with libva and information output using wainfo? then when using xfreerdp we have an error:

libva: vaGetDriverNameByIndex () failed with unknown libva error, driver_name = (null)
Failed to initialise VAAPI connection: -1 (unknown libva error).

But at the same time xfreerdp works and it is possible to connect to a remote machine!

b) if you configure everything necessary for libva and vdpau to work correctly, then there is no error indicated above at startup, but in this case the xfreerdp functionality does not work, that is, there is no way to connect to a remote machine.

segmentation fault (core dumped).

I would like to have a working video acceleration and a working freerdp.
By the way, remina also does not work if libva is configured and working

Who uses the nvidia card, who has libva and freerdp and everything is ok? Please respond.
I don't think the whole forum is using intel hd or radeon :-).
Have you encountered this? Can you help?

travnick

Member

From: Poland

Registered: 2011-04-24

Posts: 75

Re: libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

Any progress with the issue?

I'm facing the same issue. Maybe a debugging session is required, but I do not have a time for it (and to recompile required packagas in debug mode)

liewkj

Member

Registered: 2019-07-08

Posts: 210

Re: libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

NVIDIA GPUs do not support VA-API, period. Why even complain?

Kenivia

Member

Registered: 2020-12-08

Posts: 1

Re: libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

Yes it is? Copied straight from Wikipedia:

Supported hardware and drivers

As of 2019, VA-API is natively supported by:[6]

Intel Quick Sync open-source drivers for Linux
Mesa open-source drivers for AMD and Intel graphics cards
AMDGPU-PRO drivers for AMD graphics cards on Linux
Nvidia proprietary driver for Nvidia graphics cards on Linux
libva-vdpau-driver for cards supported by VDPAU

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,659

Re: libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

Uhm... You are aware wikipedia is not really an authoritive source for anything right? Especially in this case where they reference, and misinterpret, the Arch wiki page. The only vaapi support is via the libva-vdpau-driver intermediate lib, which tries -- and as seen here -- often fails to map VAAPI over VDPAU

Last edited by V1del (2020-12-08 08:29:54)

travnick

Member

From: Poland

Registered: 2011-04-24

Posts: 75

Re: libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

How about the console output?

 ~ $ vainfo 
vainfo: VA-API version: 1.10 (libva 2.9.1)
vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG4Simple            : VAEntrypointVLD
      VAProfileMPEG4AdvancedSimple    : VAEntrypointVLD
      <unknown profile>               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD

?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,659

Re: libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

Yes and this doesn't disprove anything? That's the aforementioned wrapper, which often has issues when you actually want to use it beyond a "capabilities information check".  It hasn't seen any active development in 8 years and can generally be expected to be broken with more modern vaapi usecases.

TiZeD

Member

Registered: 2020-04-03

Posts: 13

Re: libva: vaGetDriverNameByIndex() failed with unknown libva error, drive

Any progress with the issue?

I'm facing the same issue. Maybe a debugging session is required, but I do not have a time for it (and to recompile required packagas in debug mode)

I think the topic can be closed.

This is the only problem that I could not solve in arch. I've come to terms with that. I am no longer worried about the error that was described at the very beginning of this discussion.

If you disable the ability to use libva and vdpau, that is, all the necessary settings for environment variables, etc., then there will be an error but all applications will continue to work, otherwise - nothing will work, for example xfreerdp. I mentioned this above.

It is necessary to rewrite/fix libva-vdpau-driver. I have no motivation for this, because everything suits me.

I agree with this:

Yes and this doesn't disprove anything? That's the aforementioned wrapper, which often has issues when you actually want to use it beyond a "capabilities information check".  It hasn't seen any active development in 8 years and can generally be expected to be broken with more modern vaapi usecases.