From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 18234] c51 lvds script failure in randr12 mode. if I start the X server the screen is black and the framebuffer too because it trys to link the whole output to the monitor
Date: Sun, 26 Oct 2008 16:46:01 -0700 (PDT) [thread overview]
Message-ID: <20081026234602.7382C13014F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-18234-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
http://bugs.freedesktop.org/show_bug.cgi?id=18234
--- Comment #1 from Stuart Bennett <sb476-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org> 2008-10-26 16:45:59 PST ---
Created an attachment (id=19872)
--> (http://bugs.freedesktop.org/attachment.cgi?id=19872)
randr12 enabled, blank/black screen xorg.log
Attaching log posted to pastebin for posterity
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2008-10-26 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 22:43 [Bug 18234] New: c51 lvds script failure in randr12 mode. if I start the X server the screen is black and the framebuffer too because it trys to link the whole output to the monitor bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-18234-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-10-26 23:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2008-10-27 0:07 ` [Bug 18234] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-27 0:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-27 0:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-27 19:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-28 0:10 ` 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=20081026234602.7382C13014F@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.