From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 14991] New: randr12 not working with nv25
Date: Thu, 13 Mar 2008 08:33:52 -0700 (PDT) [thread overview]
Message-ID: <bug-14991-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=14991
Summary: randr12 not working with nv25
Product: xorg
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: pl4nkton-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=15091)
--> (http://bugs.freedesktop.org/attachment.cgi?id=15091)
xlog
if randr12 is enabled xserver hung with black screen.
drm debug output is the same as without.
(II) NOUVEAU(0): EDID vendor "ENC", prod id 6022
(II) NOUVEAU(0): nv_analog_output_detect is called.
-- black screen - nothing happen for some time
(II) NOUVEAU(0): Setting owner: 0x0.
(II) NOUVEAU(0): Setting owner: 0x0.
-- still no image - stop x
(II) NOUVEAU(0): NVCloseScreen is called.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2008-03-13 15:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 15:33 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-14991-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-03-13 17:05 ` [Bug 14991] randr12 not working with nv25 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-13 23:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-18 20:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 17:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 20:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 21:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 21:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 21:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 21:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 22:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 22:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-26 22:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-03 22:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-04 11:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-26 23:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-27 0:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-27 22:52 ` 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-14991-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.