Introduction to Xorg
Xorg is the most widely used implementation of the X Window System in modern Linux distributions. Born as a fork of the XFree86 project in 2004, Xorg was tasked with providing a free and open display server that allows graphical applications to communicate with video hardware and input devices. Its client‑server design separates rendering logic (clients) from hardware management (server), providing flexibility and allowing graphical applications to be run remotely over the network.
Client‑Server Architecture
In the X model, the Xorg server manages access to hardware: graphics cards, keyboards, mice, and screens. Clients, which can be applications such as web browsers, text editors, or desktop environments, connect to the server via the X11 protocol. Each client sends drawing requests (lines, text, images) and receives input events. This separation allows a single server to serve multiple clients simultaneously, even on different machines, as long as network connectivity exists.
Basic Xorg Configuration
Xorg configuration is primarily done via files located in /etc/X11/xorg.conf or inside the directory /etc/X11/xorg.conf.d/. These files allow you to specify input devices, monitor resolutions, video drivers, and acceleration options. Although many distributions today auto‑detect hardware and generate dynamic configurations, understanding the syntax of the xorg.conf file remains useful for troubleshooting resolution issues, multi‑monitor setups, or custom keyboards.
- Section ‘Device’: defines the graphics card and the driver to use.
- Section ‘Monitor’: sets refresh frequencies and resolution ranges.
- Section ‘Screen’: combines Device and Monitor to define display modes.
- Section ‘InputDevice’: configures keyboards and mice, specifying protocol and options.
Drivers and Acceleration
Xorg depends on DDX (Device Dependent X) drivers to interact with video hardware. The most common drivers include those for Intel (i915), AMD (amdgpu), and NVIDIA (nvidia or nouveau). Furthermore, the server can use extensions such as GLX to provide OpenGL acceleration directly through the server, allowing 3D applications to leverage the GPU without leaving the X environment. The choice of driver affects both performance and compatibility with features such as power‑saving modes or support for 4K monitors.
Xorg vs. Wayland
In recent years, Wayland has emerged as a successor intended to replace Xorg, promising a simpler architecture, better security, and lower latency. Wayland eliminates the classic client‑server separation and combines the server and compositor roles into a single process. Despite its advantages, Xorg remains the default choice in many distributions due to its maturity, broad support for legacy applications, and compatibility with remote‑access tools such as SSH X11 forwarding. Many companies and users that rely on specialized software or complex multi‑monitor configurations prefer to keep Xorg while evaluating a gradual transition to Wayland.
Common Troubleshooting
When Xorg fails to start correctly, the first places to check are the logs located in /var/log/Xorg.0.log. There, messages about driver loading, device detection, and possible syntax errors in configuration files are recorded. Some frequent issues include:
- Black screen after starting the server: usually indicates an unsupported resolution mode; try a basic resolution with
xrandr --autoor adjust the xorg.conf file. - Keyboard or mouse not responding: verify that the appropriate input module (evdev, libinput) is loaded and that the InputDevice section is correctly defined.
- GLX acceleration failures: ensure that the DDX driver supports GLX and that the Mesa library package is installed and up to date.
In many cases, simply renaming or deleting the /etc/X11/xorg.conf file allows Xorg to fall back to its auto‑configuration mode and resolve the conflict.
The Future of Xorg
Although Wayland is gaining ground, the Xorg community continues to maintain the server active with security fixes, performance improvements, and support for new hardware. Projects such as Xorg‑rootless and the development of X11 extensions over Wayland (Xwayland) allow X11 applications to run without a native Xorg server, providing a compatibility layer during the transition. For environments that require long‑term stability, such as compute servers, workstations with legacy software, or embedded systems, Xorg will remain a fundamental part of the Linux ecosystem for the years to come.