Commit 61e6dff5 authored by 83.24.62.236's avatar 83.24.62.236

disable linking

parent e6ba136a
......@@ -23,12 +23,12 @@ Section "Screen" <==== Remove this second section, if you have son
EndSection (stop removing lines here)
}}}
* If you have a Option "MonitorLayout" or/and "Screen" options in the Device section, remove them
* Also remove the second Screen entry from the ServerLayout section. Example : {{{
* If you have a Option "!MonitorLayout" or/and "Screen" options in the Device section, remove them
* Also remove the second Screen entry from the !ServerLayout section. Example : {{{
Screen 0 "Screen0" 1680 0
Screen 1 "Screen1" LeftOf "Screen0" <= remove this one (for Screen1)
}}}
* Also remove any RightOf/LeftOf indications from the remaining Screen line in the ServerLayout section (see above)
* Also remove any !RightOf/LeftOf indications from the remaining Screen line in the !ServerLayout section (see above)
==== Settings on xorg.conf for Randr12 ====
If you do not preconfigure a left/right/above/below setup in your xorg.xonf (see next section) add {{{Virtual x y}}} to your Display Section: {{{
......@@ -50,7 +50,7 @@ Only the part which the monitors show is used: You can start and use X with one
If you have done the above, you can also preconfigure the two monitors to be side-by-side right from the X startup. With this, you do not even need the "Virtual <x> <y>" line because then, the X server already knows before starting that it has to allocate a virtual framebuffer which fits both Monitors side-by-side.
You need to make the following changes for this to work (simplest way):
* Change the Monitor identifiers in your xorg.conf to the identifiers which "xrandr" reports and add a LeftOf/RightOf to one of the Monitor sections. Example: {{{
* Change the Monitor identifiers in your xorg.conf to the identifiers which "xrandr" reports and add a !LeftOf/RightOf to one of the Monitor sections. Example: {{{
Section "Monitor"
Identifier "DVI-D-0"
...
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment