Most applications (window managers / composers, games etc.) which access RANDR extension are still unaware that they should also consider "Monitors" instead of or in addition to "Outputs".What would be the use cases for this? Why would you want to treat regions of the same physical display as separate entities in the context of RANDR functionality? What purpose would this serve? There is no good reason to expose a tiled display as separate displays to X/RANDR.
#Amd firepro w4100 +chroma settings drivers#
(and recent NVIDIA drivers started to expose that TILE property to RANDR) Which is a very odd solution in my opinion. There is a “solution” in X.org and RANDR 1.5 - (see also this page for links to some initial implementation patches and comments: ) - which introduced the concept of “Monitor” objects (in addition to all other concepts in RANDR) and exposure of the TILE property from EDID.
#Amd firepro w4100 +chroma settings driver#
(+ there is this statement which I guess applies to Windows only: : “The NVIDIA driver automatically detects 4K 60Hz tiled format, so no special user set up is required.”) So, NVIDIA developers, why did you choose to torture us - Linux users - with this? ) I tried the same setup in Windows 10 and it just works, the display is exposed as one 5120x2880 panel as it should be. Moreover, this problem does not exist in Windows. Start seeing single-tile 4k displays soon, fixing the problem “forever”. Hopefully, the situation with current 4k monitors is temporary and we’ll And this problem is not going away as mentioned by X.org developers on their mailing list: Tiled displays turn out to be a real pain in Linux for no good reason.
(connected to two DP ports of a GTX 1080 card in my case) I also have a 5K Dell UP2715K which is connected via two display ports and is exposed to the X server as two 2560x2880 tiles. This problem has been mentioned many times before.