summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVincent Batts <vbatts@hashbangbash.com>2010-02-08 14:36:40 -0600
committerVincent Batts <vbatts@hashbangbash.com>2010-02-08 14:36:40 -0600
commit543c8661f959dc6eecd6579205be5011dca7efbc (patch)
tree5ad4a0a5bd94daf223aa109e5b84cb86d1a7ab02
parent4e8b4bc9106d4557c33bfa8c56a554be45322a45 (diff)
downloadslackbook-543c8661f959dc6eecd6579205be5011dca7efbc.tar.xz
adding more definition to the chapter-06 X configuration
-rw-r--r--chapter_06.xml20
1 files changed, 19 insertions, 1 deletions
diff --git a/chapter_06.xml b/chapter_06.xml
index afcdccf..a6f1837 100644
--- a/chapter_06.xml
+++ b/chapter_06.xml
@@ -57,7 +57,13 @@ apparent what to do. Just remember that when I started using X, it was
far more primitive than it is today, took far more work to configure,
and often crashed without telling the user what was wrong. If I and
thousands of others got this working back then, you can do it today.
-Fortunately, Slackware includes a default configuration file that works
+</para>
+
+<para>
+Fortunately, with <application>X.Org 1.6.3</application> an
+<filename>/etc/X11/xorg.conf</filename> does not even need to be
+present for <application>X</application> to attempt a working display,
+further, Slackware includes a default configuration file that works
for most computers by using the VESA standard. This offers only the
most basic functions and may not allow your graphics card to operate at
its full potential. You may be limited to low resolutions, fewer
@@ -87,6 +93,18 @@ know exactly what your hardware is, we recommend that you try
</para>
<para>
+Additionally, the <application>X</application> has flags available to
+let <application>X</application> attempt to detect hardware and render
+an <filename>xorg.conf.new</filename> that should work with the hardware
+present. From a virtual terminal call <command>X -configure</command>,
+and the resulting file will be either <filename>/root/xorg.conf.new</filename>
+or <filename>$HOME/xorg.conf.new</filename>. Before moving this new
+configuration to <filename>/etc/X11/</filename>, it can be tested by
+calling <command>X -config /root/xorg.conf.new</command>, then you can
+exit this <application>X</application> session with &lt;CTRL&gt;+&lt;ALT&gt;+&lt;Backspace&gt;.
+</para>
+
+<para>
Lastly, you can manually configure your <application>X</application>
server by modifying <filename>/etc/X11/xorg.conf</filename> with a text
editor. This is not normally a task for the faint of heart, but is