Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 38074] Dual head doesn't work for some combination of monitors (second screen still off)
Date: Tue, 20 Dec 2011 12:05:39 +0000	[thread overview]
Message-ID: <bug-38074-8800-F3B3hMSTGd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-38074-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=38074

--- Comment #15 from Maarten Maathuis <madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2011-12-20 04:05:39 PST ---
Out of curiosity, do the lower resolution modes work for DVI?

If you do xrandr --verbose, there should be something like this:
  1280x1024 (0x64)  108.0MHz +HSync +VSync *current +preferred
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock   64.0KHz
        v: height 1024 start 1025 end 1028 total 1066           clock   60.0Hz

The 108.0MHz is the bandwith required, please choose a mode well below 150 MHz,
something like 100-125 MHz.

Also, you have to switch to "Scaling mode: None"

This snippet from xrandr --verbose shows the default to be Full, which means
your monitor will always recieve native mode.

    scaling mode:    Full
        supported: None         Full         Center       Full aspect

xrandr --output NAME --set "scaling mode" "None"

This command should do the trick if you fill in the right output name, but be
sure to check that the setting is indeed changed.

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

  parent reply	other threads:[~2011-12-20 12:05 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 [this message]
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
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-F3B3hMSTGd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox