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 20006] powerpc64: Black screen using RandR12
Date: Mon, 16 Feb 2009 11:08:28 -0800 (PST)	[thread overview]
Message-ID: <20090216190828.A307813005A@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-20006-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

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





--- Comment #24 from Stuart Bennett <sb476-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org>  2009-02-16 11:08:28 PST ---
Ok, a few more things I would like:
1) a copy of the video bios image.  this can be found in /proc/device-tree and
is called "NVDA,BMP"
2) using an *unpatched* copy, change the first "#if 0" of nv_bios.c (around
line 41) to "#if 1", then attach the more verbose xorg.0.log to this bug
(obviously it won't work, as it's unpatched)
3) (from a clean boot, if you've done 2) beforehand), see which of the previous
patches are absolutely necessary.  I imagine just 2+3 will work, and it's
somewhat possible that 3 alone would do


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

  parent reply	other threads:[~2009-02-16 19:08 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08 11:10 [Bug 20006] New: powerpc64: Black screen using RandR12 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-20006-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-02-08 11:10   ` [Bug 20006] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-08 11:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-09  9:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-09 11:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-09 11:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-09 12:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-09 18:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-09 20:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-09 20:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-12  0:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-12  9:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-12  9:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-12  9:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-12 14:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-12 14:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-12 14:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-13 10:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-13 11:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-13 13:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-13 15:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-13 18:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-13 18:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-13 18:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-16 19:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2009-02-17  8:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-17  8:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-17  8:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-17 11:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-18 10:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-18 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-19 14:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-19 20:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-19 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-19 23:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-20 14:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-20 17:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-22 10:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-22 11:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-23 16:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-23 16:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-24 17:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-27 20:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-27 20:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-28 14:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-28 15:30   ` 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=20090216190828.A307813005A@annarchy.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.