<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - XVMC on nv43 class card broken with recent mesa + kernel." href="https://bugs.freedesktop.org/show_bug.cgi?id=99584#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - XVMC on nv43 class card broken with recent mesa + kernel." href="https://bugs.freedesktop.org/show_bug.cgi?id=99584">bug 99584</a> from <a class="email" href="mailto:randrik@mail.ru" title="Andrew Randrianasulu <randrik@mail.ru>"> Andrew Randrianasulu</a> <pre>Sorry, my mesa tree was not properly cleaned, and this resulted in weird mesa git version string. After running make distclean + git clean -fdx + ./autogen.sh --prefix=/usr --disable-dri3 --with-gallium-drivers=nouveau --enable-texture-float --enable-debug --with-dri-drivers=swrast PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig it shows more correct rendering string : OpenGL version string: 2.1 Mesa 17.1.0-devel (git-ce7a045) but issue with xvmc still here. I tried to boot old Slackware kernel (vmlinuz-huge-smp-3.14.29-smp) and unfortunately it behaved like my 4.2.0 with new mesa/libdrm: no correct image. vmlinuz-huge-smp-4.4.14-smp (new Slackware kernel) behaves like my self-compiled 4.10-rc5: "Creation failed: No such device (-19)" So, I think for now I can conclude new userspace simply doesn't work for xvmc on old kernels on my hardware, and try to move forward by investigating why new kernel failed to create device/object for pmpeg...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>