search for: va_opendriv

...dri.so ... s3g_drv_video.so -> vdpau_drv_video.so ... swrast_dri.so ... vdpau_drv_video.so ... virtio_gpu_dri.so ... vmwgfx_dri.so $ icecat ... libva info: VA-API version 0.39.2 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: va_openDriver() returns -1 libva info: VA-API version 0.39.2 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: va_openDriver() returns -1 libva info: VA-API version 0.39.2 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/...

...tory) $ ll /usr/lib64/dri/nouveau_drv_video.so ls: cannot access '/usr/lib64/dri/nouveau_drv_video.so': No such file or directory $ vainfo libva info: VA-API version 0.39.2 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # ln -s vdpau_drv_video.so nouveau_drv_video.so $ ll /usr/lib64/dri/nouveau_drv_video.so ... /usr/lib64/dri/nouveau_drv_video.so -> vdpau_drv_video.so $ file /usr/...

.... swrast_dri.so > ... vdpau_drv_video.so > ... virtio_gpu_dri.so > ... vmwgfx_dri.so > > > $ icecat > ... > libva info: VA-API version 0.39.2 > libva info: va_getDriverName() returns 0 > libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so > libva info: va_openDriver() returns -1 > libva info: VA-API version 0.39.2 > libva info: va_getDriverName() returns 0 > libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so > libva info: va_openDriver() returns -1 > libva info: VA-API version 0.39.2 > libva info: va_getDriverName() returns 0 &g...

...ools/Messages: vdpau_avcodec error: decoder profile not supported: 8 I think it might be related to the noveau video driver: $ vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit

...t;> >> I think it might be related to the noveau video driver: >> $ vainfo >> libva info: VA-API version 0.40.0 >> libva info: va_getDriverName() returns 0 >> libva info: Trying to open >> /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so >> libva info: va_openDriver() returns -1 >> vaInitialize failed with error code -1 (unknown libva error),exit I didn't need firmware before but it looks like I do now. I will look into that. $ dmesg | grep nouveau [ 1.600146] fb: switching to nouveaufb from VESA VGA [ 1.600264] nouveau 0000:01:00.0: NVIDIA...

...api is happily transcoding off the intel on the headless machine if I'm reading the ffmpeg logs correctly > Do you see any errors in dmesg after running vainfo? > > nope. > Cheers, > > -ilia > Any suggestions on how to trace the config issues? Do I have to debug the va_openDriver() function? -- Analabha Roy Assistant Professor Department of Physics <http://www.buruniv.ac.in/academics/department/physics> The University of Burdwan <http://www.buruniv.ac.in/> Golapbag Campus, Barddhaman 713104 West Bengal, India Emails: daneel at utexas.edu, aroy at phys.buruni...

On Tue, 1 Sep 2020 at 18:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Tue, Sep 1, 2020 at 9:10 AM Analabha Roy <hariseldon99 at gmail.com> > wrote: > > Any suggestions on how to trace the config issues? Do I have to debug > the va_openDriver() function? > > My guess, without reading any code, is that DRI_PRIME isn't doing what > you want it to, and the nouveau driver is being handed an intel > device. This does not work well. Fixing this will require tracing > through the va winsys code which to figure out how it i...

...id above, this should no longer be needed. > > $ icecat > ... > libva info: VA-API version 0.39.2 > libva info: va_getDriverName() returns 0 > libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so > libva info: Found init function __vaDriverInit_0_39 > libva info: va_openDriver() returns 0 > icecat: pushbuf.c:727: nouveau_pushbuf_data: Assertion `kref' failed. > Aborted (core dumped) > > https://bugzilla.redhat.com/attachment.cgi?id=1174453 > >From a quick guess - MT and/or GL VAAPI interop related ? If so, these two [1] patches could help. -Emil...

...anguage version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: vainfo: vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/X11R7/lib/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Mesa Gallium driver 19.2.0-devel for NV92 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Ma...

...oder profile not supported: 8 > > I think it might be related to the noveau video driver: > $ vainfo > libva info: VA-API version 0.40.0 > libva info: va_getDriverName() returns 0 > libva info: Trying to open > /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so > libva info: va_openDriver() returns -1 > vaInitialize failed with error code -1 (unknown libva error),exit > > _______________________________________________ > Nouveau mailing list > Nouveau at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/nouveau

...it might be related to the noveau video driver: >>> $ vainfo >>> libva info: VA-API version 0.40.0 >>> libva info: va_getDriverName() returns 0 >>> libva info: Trying to open >>> /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so >>> libva info: va_openDriver() returns -1 >>> vaInitialize failed with error code -1 (unknown libva error),exit >> >> What GPU do you have? For video acceleration (i.e. va-api and vdpau), >> did you install the necessary firmware? >> > > I didn't need firmware before but it looks li...

On Tue, Sep 1, 2020 at 9:10 AM Analabha Roy <hariseldon99 at gmail.com> wrote: > Any suggestions on how to trace the config issues? Do I have to debug the va_openDriver() function? My guess, without reading any code, is that DRI_PRIME isn't doing what you want it to, and the nouveau driver is being handed an intel device. This does not work well. Fixing this will require tracing through the va winsys code which to figure out how it invokes the loader. http...

...orporation GP104GL [Quadro P4000] (rev a1) There's no acceleration support for video decoding past Kepler. FWIW I don't get a crash with a GP108 when running vainfo: $ vainfo libva info: VA-API version 1.8.0 libva info: Trying to open /usr/lib64/va/drivers/nouveau_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit with Mesa 20.2.0-rc2. Not sure if your issue has been fixed (and now it errors), or if you're hitting something else. Either way, most likely an issue with the common code if it indeed persists. Cheers, -ilia

...l PCH Mic (/dev/input/event8) [ 18.441] (II) config/udev: Adding input device HDA Intel PCH Headphone Front (/dev/input/event9) Vainfo fails: vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit [root at nuc5cdev2 tmp]# ls /usr/lib64/dri/ i915_dri.so i965_dri.so kms_swrast_dri.so nouveau_dri.so r300_dri.so r600_dri.so radeonsi_dri.so swrast_dri.so virtio_gpu_dri.so vmwgfx_dri.so [root at nuc5cdev2...

...> > > On Tue, 1 Sep 2020 at 18:59, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > >> On Tue, Sep 1, 2020 at 9:10 AM Analabha Roy <hariseldon99 at gmail.com> >> wrote: >> > Any suggestions on how to trace the config issues? Do I have to debug >> the va_openDriver() function? >> >> My guess, without reading any code, is that DRI_PRIME isn't doing what >> you want it to, and the nouveau driver is being handed an intel >> device. This does not work well. Fixing this will require tracing >> through the va winsys code which to...

...4 rpm -qa | grep vdpau libva-vdpau-driver-0.7.4-19.el7.x86_64 libvdpau-1.1.1-3.el7.x86_64 vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAPro...

Hi, If I am reading the featurematrix <https://nouveau.freedesktop.org/wiki/FeatureMatrix/> right, VAAPI is supported for nouveau on the GeForce650M (my card). Here is the output of inxi -F System: Host: MediaServer Kernel: 5.4.0-42-generic x86_64 bits: 64 Console: tty 1 Distro: Ubuntu 18.04.5 LTS Machine: Device: laptop System: SAMSUNG product: 300E4C/300E5C/300E7C v: 0.1 serial:

LANG=C DRI_PRIME=1 vainfo libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/X11R7/lib/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Mesa Gallium driver 20.3.0-devel for NVA3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple...

Hi, I'm hitting that issue since Mesa 20.0.6 and it is present still in latest version 20.1.7 ``` [tkloczko at barrel SPECS]$ coredumpctl gdb 3926866 PID: 3926866 (test_va_api) UID: 1000 (tkloczko) GID: 1000 (tkloczko) Signal: 11 (SEGV) Timestamp: Sun 2020-09-13 18:57:06 BST (32s ago) Command Line: ./test_va_api Executable:

...ion 0.37.1 libva info: va_getDriverName() returns 0 libva info: User requested driver 'gallium' libva info: Trying to open /usr/local/lib/dri/gallium_drv_video.so libva info: Found init function __vaDriverInit_0_37 libva error: /usr/local/lib/dri/gallium_drv_video.so init failed libva info: va_openDriver() returns 2 vaInitialize failed with error code 2 (resource allocation failed),exit "vl_screen_create" calls "dd_create_screen" which returns NULL because the block #if defined(GALLIUM_NOUVEAU) if (strcmp(driver_name, "nouveau") == 0) return pipe_nouveau_c...