From 543c8661f959dc6eecd6579205be5011dca7efbc Mon Sep 17 00:00:00 2001 From: Vincent Batts Date: Mon, 8 Feb 2010 14:36:40 -0600 Subject: adding more definition to the chapter-06 X configuration --- chapter_06.xml | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) (limited to 'chapter_06.xml') 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 + + + +Fortunately, with X.Org 1.6.3 an +/etc/X11/xorg.conf does not even need to be +present for X 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 @@ -86,6 +92,18 @@ know exactly what your hardware is, we recommend that you try xorgsetup first. + +Additionally, the X has flags available to +let X attempt to detect hardware and render +an xorg.conf.new that should work with the hardware +present. From a virtual terminal call X -configure, +and the resulting file will be either /root/xorg.conf.new +or $HOME/xorg.conf.new. Before moving this new +configuration to /etc/X11/, it can be tested by +calling X -config /root/xorg.conf.new, then you can +exit this X session with <CTRL>+<ALT>+<Backspace>. + + Lastly, you can manually configure your X server by modifying /etc/X11/xorg.conf with a text -- cgit v1.2.3