search for: vainiti

...c 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

...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 GK107 (0e7060a2) [ 1.714219]...

...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 > > _______________________________________________ > Nouveau mailing list > Nouveau at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/nouveau

...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 like I do now. > I will look into t...

...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

...8) [ 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 tmp]# [root at nuc5cdev...

...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/lib64/dri/nouveau_drv_v...

nouveau_drv_video.so - what should it be? https://koji.fedoraproject.org/koji/buildinfo?buildID=722316 ... 0.7.4-13 - Revert symlinks - should be handled by mesa rhbz#1271842 https://bugzilla.redhat.com/show_bug.cgi?id=1271842 ... 0.7.4-12 - Add symlinks for radeonsi,r600,nouveau - rhbz#1264499 https://bugzilla.redhat.com/show_bug.cgi?id=1264499 $ rpm -q

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:

...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_create_screen(fd); e...

https://bugs.freedesktop.org/show_bug.cgi?id=70354 Priority: medium Bug ID: 70354 Assignee: nouveau at lists.freedesktop.org Summary: Failed to initialise context object: 2D_NVC0 (0) (for my GeForce GT 750M) QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: