search for: vainfo

...uire tracing > through the va winsys code which to figure out how it invokes the > loader. > > > https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/frontends/va/context.c#n111 > > For the DRM/rendernodes "platform", it will just take whatever fd it > is given. vainfo appears to give it a fixed device: > > > https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 > > However it looks like you can pass in --device /dev/dri/renderD129 or > whatever the right one is, which should pass in the right render node, > as seen her...

...$ file /usr/lib64/dri/nouveau_drv_video.so /usr/lib64/dri/nouveau_drv_video.so: cannot open `/usr/lib64/dri/nouveau_drv_video.so' (No such file or directory) $ 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...

...event10) [ 18.438] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event11) [ 18.440] (II) config/udev: Adding input device HDA Intel 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/...

Hi, Try: DRI_PRIME=1 LIBVA_DRIVER_NAME=nouveau vainfo --display drm --device /dev/dri/renderD129 Also try with and without the --device option, the important one is --display drm Cheers Julien On Tue, Sep 1, 2020 at 10:49 AM Analabha Roy <hariseldon99 at gmail.com> wrote: > > > On Tue, 1 Sep 2020 at 18:59, Ilia Mirkin <imirkin at...

...> > > > I have installed nouveau, and extracted the firmware from the prop > nvidia drivers separately as per instructions on > https://nouveau.freedesktop.org/wiki/VideoAcceleration/ > > See installed firmware @ https://pastebin.com/Gaqxb88g > > > > But running vainfo yields error: https://pastebin.com/NyULBhXt > > > > Does the error mean that VAAPI is unsupported, or does it indicate a > config problem? > > As Karol suggests, using the onboard CPU's decoding capabilities will > yield better results. However if there's some specif...

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

...firmware from the prop nvidia drivers separately as per instructions on https://nouveau.freedesktop.org/wiki/VideoAcceleration/ <https://nouveau.freedesktop.org/wiki/VideoAcceleration/> See installed firmware @ https://pastebin.com/Gaqxb88g <https://pastebin.com/Gaqxb88g> But running vainfo yields error: https://pastebin.com/NyULBhXt Does the error mean that VAAPI is unsupported, or does it indicate a config problem? Thanks, AR -- Analabha Roy Assistant Professor Department of Physics <http://www.buruniv.ac.in/academics/department/physics> The University of Burdwan <http:/...

...lrepo.x86_64 nvidia-x11-drv-340xx-340.107-1.el7.elrepo.x86_64 rpm -qa | grep libva libva-vdpau-driver-0.7.4-19.el7.x86_64 libva-utils-1.8.3-4.el7.x86_64 libva-devel-1.8.3-1.el7.x86_64 libva-1.8.3-1.el7.x86_64 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-D...

...ersion string: 3.30 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.2.0-devel (git-4fd8161773) OpenGL ES profile shading language 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 versio...

...odec also. The one that used to work shows this in Tools/Messages: vdpau_avcodec error: decoder profile not supported: 7 The new one that doesn't work shows this in Tools/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

...45 Advanced Data: N/A out of X > > > I have installed nouveau, and extracted the firmware from the prop nvidia drivers separately as per instructions on https://nouveau.freedesktop.org/wiki/VideoAcceleration/ > See installed firmware @ https://pastebin.com/Gaqxb88g > > But running vainfo yields error: https://pastebin.com/NyULBhXt > > Does the error mean that VAAPI is unsupported, or does it indicate a config problem? As Karol suggests, using the onboard CPU's decoding capabilities will yield better results. However if there's some specific reason you want/need to us...

...lum.mit.edu> wrote: >> >> What hardware are you using? > > > 0000:18:00.0 VGA compatible controller: NVIDIA Corporation 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)...

...sages: >> vdpau_avcodec error: decoder profile not supported: 7 >> >> The new one that doesn't work shows this in Tools/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...

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

....org Reporter: liewkj at yahoo.com QA Contact: nouveau at lists.freedesktop.org Tested hardware: Geforce 9300 mGPU (NVAC), GT730-GK208B (NV106) VA-API apps: gstreamer-vaapi, Chromium-vaapi-bin(AUR) OS: ArchLinux x86_64 kernel 5.2.2-arch1-1-ARCH GUI: GNOME/Wayland using nouveau - vainfo & vdpauinfo SIGSEV due to NULL pointer ArchLinux discussion thread https://bbs.archlinux.org/viewtopic.php?id=247466 - h264 video decode failed with assertion and tendency to crash GNOME/GUI Test h264 clip: $ youtube-dl -f mp4 https://www.youtube.com/watch?v=azvR__GRQic Gstreamer command line...

...work shows this in Tools/Messages: > vdpau_avcodec error: decoder profile not supported: 7 > > The new one that doesn't work shows this in Tools/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 > > _...

...codec error: decoder profile not supported: 7 >>> >>> The new one that doesn't work shows this in Tools/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 erro...

...es not work well. Fixing this will require tracing through the va winsys code which to figure out how it invokes the loader. https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/frontends/va/context.c#n111 For the DRM/rendernodes "platform", it will just take whatever fd it is given. vainfo appears to give it a fixed device: https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 However it looks like you can pass in --device /dev/dri/renderD129 or whatever the right one is, which should pass in the right render node, as seen here: https://github.com/intel/libv...

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #15 from Stefan Ringel <mail at stefanringel.de> --- Created attachment 97014 --> https://bugs.freedesktop.org/attachment.cgi?id=97014&action=edit correct profile in vdpauinfo + vainfo -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140407/97013512/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=77102 --- Comment #16 from Stefan Ringel <mail at stefanringel.de> --- (In reply to comment #15) > Created attachment 97014 [details] > correct profile in vdpauinfo + vainfo dmseg: [ 97.292274] nouveau T[ PBSP][0000:01:00.0] inc() == 4 [ 97.341821] nouveau T[ PBSP][0000:01:00.0] use(+1) == 1 [ 97.341827] nouveau T[ PBSP][0000:01:00.0] initialising... [ 97.341831] nouveau T[ PBSP][0000:01:00.0] resetting... [ 97.341840] nouveau D[ PBSP][0000:01...