All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99584] XVMC on nv43 class card broken with recent mesa + kernel.
Date: Sun, 29 Jan 2017 21:42:34 +0000	[thread overview]
Message-ID: <bug-99584-8800-GUaOXNi3b8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99584-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1249 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99584

--- Comment #3 from Andrew Randrianasulu <randrik-JGs/UdohzUI@public.gmane.org> ---
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...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2058 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-01-29 21:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29  7:27 [Bug 99584] New: XVMC on nv43 class card broken with recent mesa + kernel bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-99584-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-01-29  7:29   ` [Bug 99584] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-29  7:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-29 21:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-03-19  2:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-26  3:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-26  5:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-26  6:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-25 12:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-99584-8800-GUaOXNi3b8@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.