Download Xorg
Meryl Humerick
The last full release of the entire X.Org stack was X11R7.7 - since then individual X.Org modules have been released independently as needed - see the xorg-announce archives for details of those releases, and for downloads. Information about all releases is available. (Important: If you have an older release, please see the Security page for information on security updates.)
Xorg uses a configuration file called xorg.conf and files ending in the suffix .conf for its initial setup: the complete list of the folders where these files are searched can be found in xorg.conf(5), together with a detailed explanation of all the available options.
The /etc/X11/xorg.conf.d/ directory stores host-specific configuration. You are free to add configuration files there, but they must have a .conf suffix: the files are read in ASCII order, and by convention their names start with XX- (two digits and a hyphen, so that for example 10 is read before 20). These files are parsed by the X server upon startup and are treated like part of the traditional xorg.conf configuration file. Note that on conflicting configuration, the file read last will be processed. For this reason, the most generic configuration files should be ordered first by name. The configuration entries in the xorg.conf file are processed at the end.
Udev, which is provided as a systemd dependency, will detect hardware and both drivers will act as hotplugging input driver for almost all devices, as defined in the default configuration files 10-quirks.conf and 40-libinput.conf in the /usr/share/X11/xorg.conf.d/ directory.
When an application is misbehaving or stuck, instead of using kill or killall from a terminal and having to find the process ID or name, xorg-xkill allows to click on said application to close its connection to the X server. Many existing applications do indeed abort when their connection to the X server is closed, but some can choose to continue.
When Xorg is run in rootless mode, Xorg logs are saved to /.local/share/xorg/Xorg.log. However, the stdout and stderr output from the Xorg session is not redirected to this log. To re-enable redirection, start Xorg with the -keeptty flag and redirect the stdout and stderr output to a file:
Some programs only work with bitmap fonts. Two major packages with bitmap fonts are available, xorg-fonts-75dpi and xorg-fonts-100dpi. You do not need both; one should be enough. To find out which one would be better in your case, try xdpyinfo from xorg-xdpyinfo, like this:
If X terminates with error message SocketCreateListener() failed, you may need to delete socket files in /tmp/.X11-unix. This may happen if you have previously run Xorg as root (e.g. to generate an xorg.conf).
With version 1.17 a generic method for mode-setting was mainlined. The xf86-video-modesetting package, the Debian-package being called xserver-xorg-video-modesetting, was retired, and the generic modesetting DDX it contained was moved into the server package to become the KMS-enabled default DDX, supporting the vast majority of AMD, Intel and NVidia GPUs.
Most drivers implement acceleration using the XAA module. XAA is on by default, though acceleration of individual functions can be switched off as needed in the server configuration file (XF86Config or xorg.conf).
With version 1.16, the X.Org Server obtained support for the libinput library in form of a wrapper called xf86-input-libinput.[26] At the XDC 2015 in Toronto, libratbag was introduced as a generic library to support configurable mice.[27][28] xserver-xorg-input-joystick is the input module for the X.Org server to handle classic joysticks and gamepads, which is not meant for playing games under X, but to control the cursor with a joystick or gamepad.[29][30]
Even though a single user can utilize multiple monitors connected to the different ports of a single graphics card (cf. RandR), the method which is based on multiple instances of the xorg-server seems to require multiple PCI graphics cards.
after updating xorg-server, xorg-server-common and xorg-server-xvfb (1.19.6+13+gd0d1a694f-2 => 1.20.0-2) xorg is not usable anymore ending up in an unusable system without GUI. The only chance is to downgrade back to xorg-server prior to 1.20. This case seems to be the actual worst case for many users since a few days. I'm disappointed that there is no hint and help for someone who has to deal with a Linux distro that can't be used after a simple software update of some central packages anymore.
My solution can't be a solution for a long time to keep these packages downgraded always getting this warning of pacman that some packages are ignored. We need either another version of xorg-server or an updated driver for nvidia-340xx users like me having an old but good Geforce 8800GT that only can be used with this legacy 340xx driver since a few years.
The devtalk says that the glvnd implementation isn't guaranteed to be implemented, they will likely provide a fix down the line even without implementing glvnd. Also that people with old hardware are kicked to the wayside because of modern software stack incompatibilities is normal. Catalyst users have had this "problem" for ages. The alternative is to install nouveau, which has seen many improvements and might be a usable replacement for old cards like these, or an older xorg for the time being.
Also, and just ftr, Aaron indeed *does* promise that "Yes, we'll get one out eventually." in the devtalk - in reply to "any hope of a 340.xxx release with xorg 1.20 support"
How you come to a deviating conclusion is beyond me.
I don't think switching to nouveau is a solution. I use nouveau (not nvidia) and the latest xorg-server update broke my system as well. I downgraded and told pacman to ignore xorg-server updates until a fix is available. I know this is a nvidia thread but wanted to say that this seems to be a wider issue with xorg - and isn't just limited to the nvidia driver...
Actually, as said above, there is no alternative at all. The only "solution" is just a workaround of not upgrading to xorg-server 1.20. The nouveau driver (1.0.15-3) is affected in the same way as the nvidia binary blobs.
Fortunately the primary use of OpenSuse at the moment is as a Vmware server and a Citrix client, so all I have to install are 1 server and 1 app. I installed 11.1, installed the Nvidia drivers and configured the monitors. Saved the xorg.conf to a USB drive and did a fresh install of 11.2. Installed the Nvidia drivers, ran the Nvidia config and created an xorg.conf file and then promptly over-wrote it with the one from 11.1 and all is well in my world again.
Instead of removing let's say /FolderInHome/usr/lib/xorg, I did cd /FolderInHome and then rm -rf /usr/lib/xorg, it said Permission denied. I thought, maybe it has something to do with the target user being root and the files having the user rights set wrongly, so I did sudo -rm /usr/lib/xorg and done, it worked... Oops.
The content of the directory /usr/lib/xorg is a little harder to replace than the single binary file /usr/bin/Xorg. You can still do it by just reinstalling packages, but it's made up of many packages, some of which won't apply to you.
All good. I tried calling startx without any custom xinitrc and I
saw 3 (I suspect) xterm windows and could not select any of them nor
type anywhere, my mouse cursor was frozen. Had to restart. By checking
Xorg logs at /.local/share/xorg/Xorg.0.log I figured that it
struggles to load some OpenGL libraries, so I found
GitHub - guibou/nixGL: A wrapper tool for nix OpenGL application. After I installed nixGLDefault, I
tried to start my x-es like this:
My primary screen comes on line after a reboot, but I still get something on the external display. I can confirm that there is a displaylink_drv.so located in my /usr/lib/xorg/modules/drivers directory.
Wanted to say thanks for the prompt reply (on a weekend no less!). What described was half of what I needed to get the device rolling. The other half I figured out from checking my xorg log files. It seems that setting
No, all the CPU usage goes to that xorg process, that internally are all clock_gettime syscalls. Every other process is mostly idle. Once I disable hybrid mode and only use Nvidia, the problem is gone. The desktop is more responsive, the CPU usage goes back to normal, but of course battery usage increases.
When an update is available for xorg-server, it is possible that a normal -up world command will produce blocker messages with xorg drivers. When this happens, rebuilding x11 modules can help proceed with the update Ex:
@marulkan: as a workaround for the issue with xorg-server-common-1.20, please do the changes to /.ICAClient/All_Regions.ini as described here: _ICA_Client/#Problembehebung chapter: Probleme mit Seamless Fenstern
A smaller version of the X system suitable for experienced users is available in x11/xorg-minimal.Most of the documents, libraries, and applications will not be installed.Some applications require these additional components to function.
Video cards, monitors, and input devices are automatically detected and do not require any manual configuration.Do not create xorg.conf or run a Xorg -configure step unless automatic configuration fails.
And likewise with the freefont or other collections.To have the X server detect these fonts, add an appropriate line to the X server configuration file (/usr/local/etc/X11/xorg.conf.d/90-fonts.conf), which reads:
Xorg has built in support for rendering TrueType fonts.There are two different modules that can enable this functionality.The freetype module is used in this example because it is more consistent with the other font rendering back-ends.To enable the freetype module just add the following line to the "Module" section of /usr/local/etc/X11/xorg.conf.d/90-fonts.conf.
I know I have to add the pci id of the 3070 to xorg.conf file. The pci id is 1.00.0. Searching by a pci section, I can found one with "PCI::: " After edit it, according with some info founded, like PCI 1:0:0, it still not working.
dca57bae1f