All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Steven Ward <nightcast2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: vdpau problems and logging
Date: Tue, 12 Mar 2013 22:22:40 +0100	[thread overview]
Message-ID: <513F9CA0.3020100@canonical.com> (raw)
In-Reply-To: <CADXEQv8Ta0dUCeUxP4P5uJyNrfJ8qMfCvoXCF_7H0FAQpqtbEw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hey,
\
Op 12-03-13 20:18, Steven Ward schreef:
> Dear all,
>              I'm writing about  setup  vdpau firmware with  the nouveau
> driver according to this page:
>
> http://nouveau.freedesktop.org/wiki/NVC0_Firmware  I have  installed  the
> nvidia-313 binary drver to attempt  to extract  the firmware. I have
> obtained another mmiotrace  using  my  default  kernel I have installed  on
> my Chakra  Distrobution.  I  have  used  the  instructions  on the  wiki
> page.
>
>
> I  had some mixed results using the instructions. I didn't get anywhere
> with  using the demmio  from rnn  in envytools, but  I have  got some
> output using  the demmio  command.
>
> I will  be  uploading the output  in different files.  I did only once get
> lucky with the last instructions, valgrind , but I can't seem to  get any
> more "vuc" files. I hae saved the ones  I have and put them into
> "/lib/firmware/nouveau"  and  I have copied  them into my external hardrive.
>
> I  have tried  playing a  .mkv video which  I know it works  with the  313
> binary driver.
> I know it doesn't work  with  the  nouveau  driver and the "vuc" files I
> extracted.
>
> I will  upload  all  the  output I have created In tar.xz  format  attached
> to a  series  of e-mails.
>
Are you on an ancient xserver-xorg-video-nouveau by any chance? Anything from
2012 or later should be good enough, it's commit d575a28a502 that tells it to
load libvdpau_nouveau.so instead of nvidia. You might need to update libvdpau too.

The vuc files are probably ok, but it's not going to work without the kernel firmware files.

The ones I'm getting are:
vuc-h264-0  vuc-mpeg12-0  vuc-mpeg4-0  vuc-mpeg4-1  vuc-vc1-0  vuc-vc1-1  vuc-vc1-2

This is enough for all codecs, but it will just fail later on without userspace codecs. It should
attempt to create the kernel stuff first, which it doesn't from what I can tell from your logs.


~Maarten

  parent reply	other threads:[~2013-03-12 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 19:18 vdpau problems and logging Steven Ward
     [not found] ` <CADXEQv8Ta0dUCeUxP4P5uJyNrfJ8qMfCvoXCF_7H0FAQpqtbEw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-12 21:22   ` Maarten Lankhorst [this message]
     [not found] <CADXEQv_oL6zh4mzpWsd-gH5fcm05vCothJe-CsT0O11kBwzfag@mail.gmail.com>
     [not found] ` <514170D3.90102@canonical.com>
     [not found]   ` <CADXEQv9sMiwwzdbdi13TvX_S6sWyfSjejrBd2w7y-5pEp3CkDg@mail.gmail.com>
     [not found]     ` <CADXEQv9sMiwwzdbdi13TvX_S6sWyfSjejrBd2w7y-5pEp3CkDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-14  9:56       ` Maarten Lankhorst

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=513F9CA0.3020100@canonical.com \
    --to=maarten.lankhorst-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
    --cc=nightcast2000-Re5JQEeQqe8AvxtiuMwx3w@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.