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 24668] New: KMS does not work with nva8
Date: Wed, 21 Oct 2009 18:25:38 -0700 (PDT)	[thread overview]
Message-ID: <bug-24668-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=24668

           Summary: KMS does not work with nva8
           Product: xorg
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: jb17bsome-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


I have a g210 (nva8) and kms does not work at all/no signal. 
I am using the latest git as of 10/20/2009.

I created an mmio trace and sent it to the mmio dumps account.  I did make an
attempt at the voodo/ctxvals but I am not sure it really matters for this.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2009-10-22  1:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22  1:25 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-24668-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-10-22  1:26   ` [Bug 24668] KMS does not work with nva8 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-22  1:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-22  1:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-22 11:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-22 11:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-22 13:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-22 13:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-27  0:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-27  1:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-10-27  1:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-20  0:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-20  2:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-03  6:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-04  1:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-04  1:54   ` 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-24668-8800@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.