From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 38074] [NV96] Dual head doesn't work for some combination of monitors (second screen still off)
Date: Wed, 05 Feb 2014 06:51:21 +0000 [thread overview]
Message-ID: <bug-38074-8800-OWfbjk255v@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-38074-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 446 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=38074
--- Comment #26 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
A patch went into 3.14-rc1 that helped other NV96 users with a similar problem
for HDMI due to a problem with executing IO_CONDITION instructions in the VBIOS
script. Worth testing out 3.14-rc1 to see if this issue is fixed there.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1291 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2014-02-05 6:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 14:30 [Bug 38074] New: Dual head doesn't work for some combination of monitors (second screen still off) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-38074-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-06-08 14:35 ` [Bug 38074] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-08 14:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-08 14:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-27 16:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-27 23:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-28 16:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-28 17:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-28 17:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-28 19:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-28 22:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-29 12:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-29 12:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-29 12:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-29 12:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-19 11:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-20 8:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-20 12:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-20 16:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 16:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 14:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 14:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 14:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 14:44 ` [Bug 38074] [NV96] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 17:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 18:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-01 16:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-04 12:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-11 21:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 6:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-04-21 14:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-21 14:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-21 14:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-21 14:53 ` [Bug 38074] [NV96] Dual head doesn't work for some combination of Dual DVI connected " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-21 14:53 ` [Bug 38074] [NV96] Dual head doesn't work for some combination of " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-21 15:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-09 12:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-28 14:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:26 ` 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-38074-8800-OWfbjk255v@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.