All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roy Spliet <r.spliet-oe7qfRrRQfeEZXFvZSAUrfP6llvjuJOh@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: NV34 on Fedora 17 with Mesa 8.1-devel
Date: Sun, 01 Jul 2012 22:58:01 +0200	[thread overview]
Message-ID: <4FF0B9D9.402@student.tudelft.nl> (raw)
In-Reply-To: <4FF0A8B5.7010703-H+0wwilmMs3R7s880joybQ@public.gmane.org>

Nouveau is in fairly good shape, just not for the card you're testing. 
This behaviour is known, but nobody had time to dive into it yet.

Op 01-07-12 21:44, mwesten schreef:
> Good day.  I'd like to inquire about the use of the latest 
> Nouveau+Mesa code on a recent distribution such as Fedora 17.  I've 
> pulled the source and built it, which appeared to go smoothly, but I 
> am having issues during use.
>
> glxinfo:
> OpenGL vendor string: nouveau
> OpenGL renderer string: Gallium 0.4 on NV34
> OpenGL version string: 1.5 Mesa 8.1-devel (git-db2b6ca)
>
> I see many of these messages:
> [ 2137.524453] [drm] nouveau 0000:01:04.0: PGRAPH - ERROR nsource: 
> DATA_ERROR nstatus: BAD_ARGUMENT
> [ 2137.524469] [drm] nouveau 0000:01:04.0: PGRAPH - ch 3/7 class 
> 0x0697 mthd 0x0208 data 0x04060348
>
> In GNOME-Shell, I'm seeing several things.  The most immediately 
> obvious is the lack of a background behind the date/calendar pop-down 
> and the entire user menu.  I also get a crash in gnome-control-center 
> every time I try to open System Settings.
>
> Please advise.  Thanks!
> _______________________________________________
> Nouveau mailing list
> Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau
>

  parent reply	other threads:[~2012-07-01 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-01 19:44 NV34 on Fedora 17 with Mesa 8.1-devel mwesten
     [not found] ` <4FF0A8B5.7010703-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2012-07-01 20:58   ` Roy Spliet [this message]
2012-07-01 21:07   ` Marcin Slusarz

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=4FF0B9D9.402@student.tudelft.nl \
    --to=r.spliet-oe7qfrrrqfeezxfvzsaurfp6llvjujoh@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.