| • Science | • People | • Locations | • Timeline |
When XFree86 starts, it creates a logfile which contains information about what happened when XFree86 started. It contains information about what modules were loaded, which color depth that is used etc. The file is especially useful when something goes awry, as reading it can help you find exactly what went wrong.
The file almost always resides in "/var/log/XFree86.0.log" but, of course, where it is placed is configurable.
The log begins with a section with some general system information before the actual work of starting the X server begins. It looks something like the following:
02] Release Date: 27 February 2003 03] X Protocol Version 11, Revision 0, Release 6.6 04] Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] 05] Build Date: 27 February 2003 06] Build Host: porky.devel.redhat.com 07] 08] Before reporting problems, check http://www.XFree86.Org/ 09] to make sure that you have the latest version. 10] Module Loader present 11] OS Kernel: Linux version 2.4.20-8 (bhcompile@porky.devel.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 12] Markers: (--) probed, (**) from config file, (==) default setting, 13] (++) from command line, (!!) notice, (II) informational, 14] (WW) warning, (EE) error, (NI) not implemented, (??) unknown. 15] (==) Log file: "/var/log/XFree86.0.log", Time: Sat May 15 02:55:42 2004 16] (==) Using config file: "/etc/X11/XF86Config"
(Line markers
Line 1-2: Those lines tells us that this is version 4.3.0 and that it was released on February 27, 2003. It's modern enough, although 4.4.0 has been released ( February 29, 2004).
Line 3: The X protocol hasn't changed for ages and it is unlikely that it will change anytime soon.
Line 4-6: Build information. That the Build Host is "porky.devel.redhat.com" means that the user, unless he or she is an employee at Red Hat, probably installed XFree86 from a binary rpm package .
Line 10: X managed to find the module loader, which is essential if X is going to use things like hardware accelerated graphics. Further down in the file, X tries to load all modules specified in Section "Module" in XF86Config .
Line 12-14: The different types of messages printed in the log. Lines beginning with
Line 15-16: Where the files are. In this log, they are both in the default location. The time field specifies the date and time of the execution that caused the log.
02] (**) |-->Screen "Screen0" (0) 03] (**) | |-->Monitor "Monitor0" 04] (**) | |-->Device "NVIDIA GeForce 2 MX (generic)" 05] (**) |-->Input Device "Mouse0" 06] (**) |-->Input Device "Keyboard0"
After the initial messages, X begins to process the ServerLayout section in the XF86Config. What is outputted in the log closely corresponds to what is written in the configuration file. The section defines what devices are used by the X server. In this case, a mouse, a keyboard and a monitor with a GeForce 2 graphics card. There may be multiple ServerLayout sections in the XF86Config, but only the first one will be parsed.
The first line, (==) ServerLayout "Anaconda Configured" means that Red Hat's configuration tool Anaconda was used to generate the initial XF86Config file. The file may still have been changed manually afterwards. Other often seen values are "XFree86 Configure" meaning that XFree86's configuration tool xf86config was used, "Main Layout" or "Default Layout".