[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

xsf-docs: Changes to 'master'



 howtos/use-xrandr.mdwn |  170 +++++++++++++++++++++++++++++++++++++++++++++++++
 index.mdwn             |    1 
 xsf.css                |    8 ++
 3 files changed, 179 insertions(+)

New commits:
commit 381eeb55a710ad83a899ce9b7558493f7cda96dc
Author: Cyril Brulebois <kibi@debian.org>
Date:   Thu Dec 2 13:49:26 2010 +0100

    Continue typing.

diff --git a/howtos/use-xrandr.mdwn b/howtos/use-xrandr.mdwn
index 5a3d45b..3c161ad 100644
--- a/howtos/use-xrandr.mdwn
+++ b/howtos/use-xrandr.mdwn
@@ -140,3 +140,31 @@ should configure your `xorg.conf` by adding a `Virtual` line to the
       EndSubSection
     EndSection
 
+### Place outputs
+
+Outputs are placed using the following options:
+`--right-of`/`--left-of`/`--above`/`--below`. For instance, to place
+the `VGA1` output virtually-right of the internal panel (`LVDS1`):
+
+    $ xrandr --output VGA1 --right-of LVDS1
+
+Note that hardware and memory limitations may severely restrict the
+size of your virtual screen, see the Caveats section below.
+
+## Adding new modes
+
+Under some circumstances, some modes might be missing. For instance,
+if the monitor does not report correct EDID information. Or if the
+output didn't have a CRTC available at startup because another output
+was using it and you disabled it in the meantime.
+
+If a mode exist, you may add it to one output with:
+
+    $ xrandr --addmode VGA1 800x600
+
+If the mode does not exist, you may first create it by passing a modeline:
+
+    $ xrandr --newmode <ModeLine>
+
+You may create a modeline using the `gtf` or `cvt` tools (shipped in
+the `xserver-xorg-core` package).

commit 87e2ac28207ca023b45e8241259500b1d38623ae
Author: Cyril Brulebois <kibi@debian.org>
Date:   Thu Dec 2 13:17:47 2010 +0100

    Restructure the document.

diff --git a/howtos/use-xrandr.mdwn b/howtos/use-xrandr.mdwn
index 5f90f5d..5a3d45b 100644
--- a/howtos/use-xrandr.mdwn
+++ b/howtos/use-xrandr.mdwn
@@ -1,6 +1,8 @@
 # How to use xrandr
 
-## What is xrandr?
+## Getting started
+
+### What is xrandr?
 
 `xrandr` is a command-line tool to interact with the X `RandR`
 extension [see [x.org](http://www.x.org/wiki/Projects/XRandR),
@@ -12,15 +14,13 @@ etc.) together with the ability to configure outputs dynamically
 
 **FIXME: Status across drivers?**
 
-## What about xorg.conf?
+### What consequences for xorg.conf?
 
 Starting with `squeeze`, removing the `xorg.conf` configuration file
 entirely should work well enough, but in case that doesn’t work out,
 let’s document what can be removed from it from a `RandR` point of
 view.
 
-### Mode detection
-
 With the driver detecting modes automatically, several configuration
 options become useless most of the time in your configuration file
 (xorg.conf). You might want to remove:
@@ -29,7 +29,8 @@ options become useless most of the time in your configuration file
  * Modes from `Display` subsection in `Screen` section.
  * `ModeLine` from the `Monitor` section.
 
-### Static dual-head configuration
+There’s also no need to keep static dual-head configuration. Some
+suggestions to get a tiny `xorg.conf`:
 
  * Drop dual `Device`/`Screen`/`Monitor` sections, a single one is
    needed.
@@ -39,10 +40,7 @@ options become useless most of the time in your configuration file
  * Drop `RightOf`/`LeftOf` indication of the remaining `Screen` line
    in `ServerLayout` section.
 
-## Using xrandr
-
-### Basics
-
+## Basic xrandr usage
 
 Once the configuration file (`xorg.conf`) is removed or updated,
 starting the server should enable some outputs by default. Their
@@ -114,7 +112,9 @@ To get back to the default mode:
 
     $ xrandr --output LVDS1 --auto
 
-### Placing outputs in a virtual screen
+## Placing outputs in a virtual screen
+
+### A bit of configuration for non-KMS setups:
 
 Let’s have a look at the maximal virtual screen size, we see
 `4096x4096` in this example:

commit 26cb076a2e2695f3ee590506e1ea07891d53a394
Author: Cyril Brulebois <kibi@debian.org>
Date:   Thu Dec 2 13:12:25 2010 +0100

    More stuff.

diff --git a/howtos/use-xrandr.mdwn b/howtos/use-xrandr.mdwn
index 8384027..5f90f5d 100644
--- a/howtos/use-xrandr.mdwn
+++ b/howtos/use-xrandr.mdwn
@@ -96,3 +96,47 @@ This may be useful for some buggy application that don’t support
 multiple outputs well. Also, due to CRTC limitations (see the Caveats
 section below), it is often required to disable one output before
 enabling another since most hardware only support 2 at the same time.
+
+### Changing the mode
+
+With the above `xrandr` output, you may change the `LVDS1` mode to
+`1024x768` using:
+
+    $ xrandr --output LVDS1 --mode 1024x768
+
+The refresh rate may also be changed, either at the same time or
+independently:
+
+    $ xrandr --output LVDS1 --mode 1024x768 --rate 75
+    $ xrandr --output LVDS1 --rate 75
+
+To get back to the default mode:
+
+    $ xrandr --output LVDS1 --auto
+
+### Placing outputs in a virtual screen
+
+Let’s have a look at the maximal virtual screen size, we see
+`4096x4096` in this example:
+
+    $ xrandr|head -1
+    Screen 0: minimum 320 x 200, current 1280 x 800, maximum 4096 x 4096
+
+With KMS (**FIXME: Link to a page which explains what KMS is**),
+there's no need to specify any `Virtual` option. With DRI and without
+KMS, that might be needed. Indeed, drivers will often create a default
+virtual screen with small dimensions, for instance `1600x1200`, to
+reduce memory consumption.
+
+If you plan to use multiple outputs displaying different zones, you
+should configure your `xorg.conf` by adding a `Virtual` line to the
+`Display` subsection in the `Screen` section.
+
+    Section "Screen"
+      ...
+      SubSection "Display"
+        Depth 24
+        Virtual 3000 2000
+      EndSubSection
+    EndSection
+

commit 84f8c46e4bc170996a1fc4fbbf94761320fc099d
Author: Cyril Brulebois <kibi@debian.org>
Date:   Thu Dec 2 12:47:07 2010 +0100

    Continue typing.

diff --git a/howtos/use-xrandr.mdwn b/howtos/use-xrandr.mdwn
index 5fb5959..8384027 100644
--- a/howtos/use-xrandr.mdwn
+++ b/howtos/use-xrandr.mdwn
@@ -63,14 +63,36 @@ outputs, just run `xrandr`:
     DVI1 disconnected (normal left inverted right x axis y axis)
     TV1 disconnected (normal left inverted right x axis y axis)
 
-We see 4 outputs: `VGA1`, `LVDS1`, `DVI1`, `TV1`. Only the internal
-panel (`LVDS1`) is connected and it supports 4 modes at 60 Hz, 1 mode
-at 56 Hz.
+Comments:
 
-The mode marked with a star is the current mode.
-
-The one marked with a plus is the preferred one. Most monitors report
-a preferred mode to the driver. And the server/driver will generally
-choose it by default.
+ * We see 4 outputs: `VGA1`, `LVDS1`, `DVI1`, `TV1`.
+ * Only the internal panel (`LVDS1`) is connected and it supports 4
+   modes at 60 Hz, 1 mode at 56 Hz.
+ * The mode marked with a star (`*`) is the current mode.
+ * The one marked with a plus (`+`) is the preferred one. Most
+   monitors report a preferred mode to the driver. And the
+   server/driver will generally choose it by default.
 
 **FIXME: Mention output name conventions?**
+
+When manipulating `VGA1` output properties, you should use:
+
+    $ xrandr --output VGA1 <options>
+
+### Adding/removing heads dynamically
+
+The old days where you had to restart X when plugging a new monitor
+are gone. With `RandR` 1.2, you can plug/unplug monitors whenever you
+want. Running the following line will query all outputs and enable
+them with their default mode:
+
+    $ xrandr --auto
+
+You may also disable one output using:
+
+    $ xrandr --output LVDS1 --off
+
+This may be useful for some buggy application that don’t support
+multiple outputs well. Also, due to CRTC limitations (see the Caveats
+section below), it is often required to disable one output before
+enabling another since most hardware only support 2 at the same time.

commit e376d0f55e18734cf5c0fe2d764cf7b5977c98d4
Author: Cyril Brulebois <kibi@debian.org>
Date:   Thu Dec 2 12:31:53 2010 +0100

    Continue typing.

diff --git a/howtos/use-xrandr.mdwn b/howtos/use-xrandr.mdwn
index e6d51c2..5fb5959 100644
--- a/howtos/use-xrandr.mdwn
+++ b/howtos/use-xrandr.mdwn
@@ -28,3 +28,49 @@ options become useless most of the time in your configuration file
  * `HorizSync` and `VertRefresh` from the `Monitor` section.
  * Modes from `Display` subsection in `Screen` section.
  * `ModeLine` from the `Monitor` section.
+
+### Static dual-head configuration
+
+ * Drop dual `Device`/`Screen`/`Monitor` sections, a single one is
+   needed.
+ * Drop `MonitorLayout` option and `Screen` lines from the remaining
+   `Device` section.
+ * Drop the `ServerLayout` section(s).
+ * Drop `RightOf`/`LeftOf` indication of the remaining `Screen` line
+   in `ServerLayout` section.
+
+## Using xrandr
+
+### Basics
+
+
+Once the configuration file (`xorg.conf`) is removed or updated,
+starting the server should enable some outputs by default. Their
+top-left corners will be at the same part of the image, but their
+modes will probably be different.
+
+All outputs may be configured through `xrandr`. To see the available
+outputs, just run `xrandr`:
+
+    $ xrandr
+    Screen 0: minimum 320 x 200, current 1280 x 800, maximum 4096 x 4096
+    VGA1 disconnected (normal left inverted right x axis y axis)
+    LVDS1 connected 1280x800+0+0 inverted X and Y axis (normal left inverted right x axis y axis) 261mm x 163mm
+       1280x800       59.8*+
+       1024x768       60.0
+       800x600        60.3     56.2
+       640x480        59.9
+    DVI1 disconnected (normal left inverted right x axis y axis)
+    TV1 disconnected (normal left inverted right x axis y axis)
+
+We see 4 outputs: `VGA1`, `LVDS1`, `DVI1`, `TV1`. Only the internal
+panel (`LVDS1`) is connected and it supports 4 modes at 60 Hz, 1 mode
+at 56 Hz.
+
+The mode marked with a star is the current mode.
+
+The one marked with a plus is the preferred one. Most monitors report
+a preferred mode to the driver. And the server/driver will generally
+choose it by default.
+
+**FIXME: Mention output name conventions?**

commit 7d8417aa3becfbf846b494456118571ead127cb9
Author: Cyril Brulebois <kibi@debian.org>
Date:   Thu Dec 2 02:41:10 2010 +0100

    Start a doc on xrandr.

diff --git a/howtos/use-xrandr.mdwn b/howtos/use-xrandr.mdwn
new file mode 100644
index 0000000..e6d51c2
--- /dev/null
+++ b/howtos/use-xrandr.mdwn
@@ -0,0 +1,30 @@
+# How to use xrandr
+
+## What is xrandr?
+
+`xrandr` is a command-line tool to interact with the X `RandR`
+extension [see [x.org](http://www.x.org/wiki/Projects/XRandR),
+[wikipedia](http://en.wikipedia.org/wiki/RandR)], which allows for
+live (re)configuration of the X server (*i.e.* without restarting it):
+It provides automatic discovery of modes (resolutions, refresh rates,
+etc.) together with the ability to configure outputs dynamically
+(resize, rotate, move, etc.).
+
+**FIXME: Status across drivers?**
+
+## What about xorg.conf?
+
+Starting with `squeeze`, removing the `xorg.conf` configuration file
+entirely should work well enough, but in case that doesn’t work out,
+let’s document what can be removed from it from a `RandR` point of
+view.
+
+### Mode detection
+
+With the driver detecting modes automatically, several configuration
+options become useless most of the time in your configuration file
+(xorg.conf). You might want to remove:
+
+ * `HorizSync` and `VertRefresh` from the `Monitor` section.
+ * Modes from `Display` subsection in `Screen` section.
+ * `ModeLine` from the `Monitor` section.
diff --git a/index.mdwn b/index.mdwn
index 24e4f5d..602d3ff 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -4,6 +4,7 @@
 
  * [How to report bugs](howtos/report-bugs.html)
  * [How to use GDB](howtos/use-gdb.html)
+ * [How to configure outputs](howtos/use-xrandr.html)
 
 ## Feedback
 

commit 7ee3513ef1fad1fb4db00e2e120d2820808e9032
Author: Cyril Brulebois <kibi@debian.org>
Date:   Thu Dec 2 02:33:18 2010 +0100

    Specify margins for lists.

diff --git a/xsf.css b/xsf.css
index 03a518f..7a74d4e 100644
--- a/xsf.css
+++ b/xsf.css
@@ -34,6 +34,14 @@ p {
   text-align: justify;
 }
 
+ul {
+  margin-left: 40px;
+}
+
+ol {
+  margin-left: 40px;
+}
+
 pre {
   margin-left: 60px;
 }


Reply to: