X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=docs%2Fmulti-monitor;h=cafe569103b6c3f88a08615b697c4f176bb9c137;hb=9a53d65e1886034fdb059e47febc59cbf1e41d51;hp=ec0256c053c70c5aeee874a710dda7622cdf1b41;hpb=96128c9cfbda0029775cabaa22b82b97a0a1f2f3;p=i3%2Fi3 diff --git a/docs/multi-monitor b/docs/multi-monitor index ec0256c0..cafe5691 100644 --- a/docs/multi-monitor +++ b/docs/multi-monitor @@ -1,21 +1,24 @@ The multi-monitor situation =========================== -Michael Stapelberg -March 2010 +Michael Stapelberg +April 2013 -…or: oh no, I have an nVidia graphics card! +Please upgrade your nVidia driver to version 302.17 or newer and i3 will just +work. This document is kept around for historic reasons only. == The quick fix If you are using the nVidia binary graphics driver (also known as 'blob') -you need to use the +--force-xinerama+ flag (in your .xsession) when starting -i3, like so: +before version 302.17, you need to use the +--force-xinerama+ flag (in your +.xsession) when starting i3, like so: .Example: ---------------------------------------------- exec i3 --force-xinerama -V >>~/.i3/i3log 2>&1 ---------------------------------------------- +…or use +force_xinerama yes+ in your configuration file. + == The explanation Starting with version 3.ε, i3 uses the RandR (Rotate and Resize) API instead @@ -50,9 +53,13 @@ these are two screens). For this very reason, we decided to implement the following workaround: As long as the nVidia driver does not support RandR, an option called -+--force-xinerama+ is available in i3. This option gets the list of screens -*once* when starting, and never updates it. As the nVidia driver cannot do -dynamic configuration anyways, this is not a big deal. ++--force-xinerama+ is available in i3 (alternatively, you can use the ++force_xinerama+ configuration file directive). This option gets the list of +screens *once* when starting, and never updates it. As the nVidia driver cannot +do dynamic configuration anyways, this is not a big deal. + +Also note that your output names are not descriptive (like +HDMI1+) when using +Xinerama, instead they are counted up, starting at 0: +xinerama-0+, +xinerama-1+, … == See also