[Libva] Permission problem using vaapi.

Emil Velikov emil.l.velikov at gmail.com
Fri Jul 22 14:16:46 UTC 2016


On 22 July 2016 at 09:01, Víctor M. Jáquez L. <vjaquez at igalia.com> wrote:
>
> On 07/22/16 at 06:33am, Xiang, Haihao wrote:
>> > Hi,
>> >      This's a fairly common problem. As root --
>> >
>> > ./vainfo
>> > libva info: VA-API version 0.39.2
>> > libva info: va_getDriverName() returns 0
>> > libva info: Trying to open
>> > /home/de/small/temp_small/libva/root/lib/dri/i965_drv_video.so
>> > libva info: Found init function __vaDriverInit_0_39
>> > libva info: va_openDriver() returns 0
>> > vainfo: VA-API version: 0.39 (libva 1.7.1)
>> > vainfo: Driver version: Intel i965 driver for Intel(R) Ironlake
>> > Mobile -
>> > 1.7.1
>> > vainfo: Supported profile and entrypoints
>> >        VAProfileMPEG2Simple            : VAEntrypointVLD
>> >        VAProfileMPEG2Main              : VAEntrypointVLD
>> >        VAProfileH264ConstrainedBaseline: VAEntrypointVLD
>> >        VAProfileH264Main               : VAEntrypointVLD
>> >        VAProfileH264High               : VAEntrypointVLD
>> >        VAProfileNone                   : VAEntrypointVideoProc
>> >
>> > As user --
>> > ./vainfo
>> > libva info: VA-API version 0.39.2
>> > libva info: va_getDriverName() returns 1
>> > libva error: va_getDriverName() failed with operation
>> > failed,driver_name=i965
>> > vaInitialize failed with error code 1 (operation failed),exit
>
> One simple thing to figure out what file doesn't have the right permissions is
> to run vainfo with strace and find where the program fails. As Xiang
> mentioned, it could be a misconfiguration in the dev filesystem or in the
> drivers, etc.
>
>> >
>>
>> According to the above info, I presume you are using vaapi on X11, is
>> that right? Does vainfo work for you if no X11?
>
> It works with only drm, no X11 is required.
>
To summarise/elaborate/clear some confusions:

The code handling the authorisation (the one that's failing here) is
winsys/platform specific. Meaning that different code paths leading to
different reasons for failure. Checking with strace the exact path
used and resulting error is the first step.

Even if you "use only drm, no X11" and/or "run vainfo as root" you can
get auth. failure(s).

Good luck :-)
-Emil


More information about the Libva mailing list