"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">\r
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">\r
<head>\r
-<link rel="icon" type="image/png" href="/favicon.png">\r
+<link rel="icon" type="image/x-icon" href="/favicon.ico">\r
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />\r
-<meta name="generator" content="AsciiDoc 8.6.6" />\r
+<meta name="generator" content="AsciiDoc 8.6.8" />\r
<title>i3: The multi-monitor situation</title>\r
<link rel="stylesheet" href="/css/style.css" type="text/css" />\r
<link rel="stylesheet" href="/css/xhtml11.css" type="text/css" />\r
<script type="text/javascript">\r
/*<![CDATA[*/\r
-window.onload = function(){asciidoc.footnotes(); asciidoc.toc(2);}\r
+document.addEventListener("DOMContentLoaded", function(){asciidoc.footnotes(); asciidoc.toc(2);}, false);\r
/*]]>*/\r
</script>\r
<script type="text/javascript" src="/js/asciidoc-xhtml11.js"></script>\r
<h1>The multi-monitor situation</h1>\r
<span id="author">Michael Stapelberg</span><br />\r
<span id="email"><tt><<a href="mailto:michael@i3wm.org">michael@i3wm.org</a>></tt></span><br />\r
-<span id="revdate">July 2012</span>\r
+<span id="revdate">April 2013</span>\r
<div id="toc">
<div id="toctitle">Table of Contents</div>
<noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
</div>\r
<div id="preamble">\r
<div class="sectionbody">\r
-<div class="paragraph"><p>…or: oh no, I have an nVidia graphics card!</p></div>\r
+<div class="paragraph"><p>Please upgrade your nVidia driver to version 302.17 or newer and i3 will just\r
+work. This document is kept around for historic reasons only.</p></div>\r
</div>\r
</div>\r
<div class="sect1">\r
<h2 id="_the_quick_fix">1. The quick fix</h2>\r
<div class="sectionbody">\r
<div class="paragraph"><p>If you are using the nVidia binary graphics driver (also known as <em>blob</em>)\r
-you need to upgrade to at least version 302.17 (released in June 2012).</p></div>\r
-<div class="paragraph"><p>In case you cannot update the driver to 302.17 or newer on your machine for\r
-some reason, use the <tt>--force-xinerama</tt> flag (in your .xsession) when starting\r
-i3, like so:</p></div>\r
+before version 302.17, you need to use the <tt>--force-xinerama</tt> flag (in your\r
+.xsession) when starting i3, like so:</p></div>\r
<div class="listingblock">\r
<div class="title">Example:</div>\r
<div class="content">\r
<div class="sect1">\r
<h2 id="_the_explanation">2. The explanation</h2>\r
<div class="sectionbody">\r
-<div class="paragraph"><p>Starting with version 3.ε (March 2010), i3 uses the RandR (Rotate and Resize)\r
-API instead of Xinerama. The reason for this, is that RandR provides more\r
-information about your outputs and connected screens than Xinerama does. To be\r
-specific, the code which handled on-the-fly screen reconfiguration (meaning\r
-without restarting the X server) was a very messy heuristic and most of the\r
-time did not work correctly — that is just not possible with the little\r
-information Xinerama offers (just a list of screen resolutions, no identifiers\r
-for the screens or any additional information). Xinerama simply was not\r
-designed for dynamic configuration.</p></div>\r
+<div class="paragraph"><p>Starting with version 3.ε, i3 uses the RandR (Rotate and Resize) API instead\r
+of Xinerama. The reason for this, is that RandR provides more information\r
+about your outputs and connected screens than Xinerama does. To be specific,\r
+the code which handled on-the-fly screen reconfiguration (meaning without\r
+restarting the X server) was a very messy heuristic and most of the time did\r
+not work correctly — that is just not possible with the little information\r
+Xinerama offers (just a list of screen resolutions, no identifiers for the\r
+screens or any additional information). Xinerama simply was not designed\r
+for dynamic configuration.</p></div>\r
<div class="paragraph"><p>So RandR came along, as a more powerful alternative (RandR 1.2 to be specific).\r
It offers all of Xinerama’s possibilities and lots more. Using the RandR API\r
made our code much more robust and clean. Also, you can now reliably assign\r
(position inside the list of screens, which could change, and so on…).</p></div>\r
<div class="paragraph"><p>As RandR has been around for about three years as of this writing, it seemed\r
like a very good idea to us, and it still is a very good one. What we did not\r
-expect, however, was the nVidia binary driver. It did not support RandR until\r
-mid 2012, even though nVidia had announced that it will support RandR\r
-previously. What does missing RandR support mean for you? First of all, you are\r
-stuck with TwinView and cannot use <tt>xrandr</tt>. While this ruins the user\r
-experience, the more grave problem is that the nVidia driver not only does not\r
-support dynamic configuration using RandR, it also does not expose correct\r
-multi-monitor information via the RandR API. So, in some setups, i3 will not\r
-find any screens; in others, it will find one large screen which actually\r
-contains both of your physical screens (but it will not know that these are two\r
-screens).</p></div>\r
+expect, however, was the nVidia binary driver. It still does not support RandR\r
+(as of March 2010), even though nVidia has announced that it will support RandR\r
+eventually. What does this mean for you, if you are stuck with the binary\r
+driver for some reason (say the free drivers don’t work with your card)? First\r
+of all, you are stuck with TwinView and cannot use <tt>xrandr</tt>. While this ruins\r
+the user experience, the more grave problem is that the nVidia driver not only\r
+does not support dynamic configuration using RandR, it also does not expose\r
+correct multi-monitor information via the RandR API. So, in some setups, i3\r
+will not find any screens; in others, it will find one large screen which\r
+actually contains both of your physical screens (but it will not know that\r
+these are two screens).</p></div>\r
<div class="paragraph"><p>For this very reason, we decided to implement the following workaround: As\r
long as the nVidia driver does not support RandR, an option called\r
<tt>--force-xinerama</tt> is available in i3 (alternatively, you can use the\r
projects / i3 / i3.github.io / blobdiff