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 15206] [dualhead, randr12, ppc] Second head displays nothing
Date: Sat, 21 Jun 2008 14:39:35 -0700 (PDT)	[thread overview]
Message-ID: <20080621213935.819E8130056@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-15206-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

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





--- Comment #13 from Robin Johnson <robbat2-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>  2008-06-21 14:39:34 PST ---
Ok, I made some very significant progress now. The memory allocation issue was
a bug in x11-drm, and was fixed by commit
1915de2c56d71bbd04a7c085cbd35fbe8e33af9d.

The display does come up [1], and xrandr thinks that both outputs work.
However, when I do "xrandr --output DVI-D-1 --right-of DVI-D-0", while the
taskbar etc all expand, nothing goes onto the second display. The power LED
continues it's blinking to indicate there is no signal.

[1] Additionally, the bswap hack seems to have mucked up colors. White comes
out as yellow. Magenta and cyan are reversed. Red and green are reversed.
Attachment coming soon.


-- 
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:[~2008-06-21 21:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26  8:34 [Bug 15206] New: [dualhead, randr12, ppc] Second head displays nothing bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-15206-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-03-26  8:34   ` [Bug 15206] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26  8:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26  9:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26  9:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26  9:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-05-06 18:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-05 18:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-05 18:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-17  9:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-20  5:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21  2:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21  2:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21  2:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21  3:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21 21:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2008-06-21 21:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-21 23:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-07 23:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-08  5:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-08 14:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-15 11:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-15 21:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-31 10:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-04-23 21:17   ` 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=20080621213935.819E8130056@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.