deloptes composed on 2015-12-30 23:55 (UTC+0100): > Felix Miata wrote: >> IMO it hasn't been made clear that there is any bug, unless it's with lack >> of clear howto docs anywhere. Was KDE3 ever able to do the configuration >> of multiple displays? I'm not sure even KDE4 ever was able to. This WFM at >> the Xorg level, but without any laptops I'm not able to precisely >> duplicate OP's hardware configuration. Before filing, better to be sure >> through discussion here what the bug is, or maybe move discussion to >> [trinity-devel]. > KDE3 or KDE4 are able to do as much as xrandr can do. All boils down to the > chipset, the driver and the display. To be clear, my meaning WRT KDE3 & up was configuring, not utilizing what has been pre-configured via xrandr startup script or xorg.conf*. > It took my couple of hours to configure mine (attached). Perhaps it could > give you some ideas. > Section "Files" ... Irrelevant to the subject. IME, automagic fully handles this in every case, while manual inclusion provides opportunity to miss some obscurely installed fonts. > Section "Module" ... Usually not relevant to configuring display configuration. > Section "InputDevice" > Section "InputDevice" > Section "InputDevice" ... Irrelevant to the subject. IME, automagic generally handles these satisfactorily. > Section "Monitor" > Identifier "eDP1" > Section "Monitor" > Identifier "DP2" ... Relevant. > Modeline "1920x1080@..." 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync ... Modelines are nearly always handled automagically as well as , so I repeat: I've NEVER EVER needed to put any modeline in any distro's xorg.conf, and I do a LOT of testing with different distro versions, Xorg versions, CRT and LCD displays, gfxchips and video drivers. Xorg calculates the modelines it needs if it has any valid data about the hardware. Usually EDID is sufficient. When not (e.g. invalid EDID), all it needs is the display's HorizSync and VertRefresh ranges, and the desired resolution. I every case, providing Xorg with HorizSync and VertRefresh ranges, and desired resolution (PreferredMode in server versions since it was created; previously, and currently with non-KMS drivers via 'Subsection "Display"'s 'Modes'), provided all that was needed. Again, Xorg's built in modeline calculator works as well as gtf or cvt, and does so automatically, so manual modeline generation should be an absolute last resort only when all else fails. Manual calculation is an absolute and complete waste of time otherwise. IOW, don't waste your time on modelines unless you like wasting more time on an already tedious task, or you've tried absolutely everything else, without success. And don't bloat an already confusing subject by suggesting to an OP otherwise. > Section "Monitor" ... Relevant. > Modeline "1920x1080@..." 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync ... Irrelevant > Section "Monitor" ... Relevant. > Modeline "1920x1080@..." 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync ... No. > Section "Monitor" > Identifier "HDMI1" ... Relevant. > Section "Monitor" > Identifier "HDMI2" Relevant. > Section "Device" > # http://wiki.ubuntuusers.de/Grafikkarten/Intel > ### Available Driver options are:- > ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", > ### <string>: "String", <freq>: "<f> Hz/kHz/MHz", > ### <percent>: "<f>%" > ### [arg]: arg optional > #Option "NoAccel" # [<bool>] > #Option "AccelMethod" # <str> > Option "AccelMethod" "uxa" > #Option "Backlight" # <str> > Option "DRI" "on" # <str> > #Option "ColorKey" # <i> > #Option "VideoKey" # <i> > #Option "Tiling" # [<bool>] > #Option "LinearFramebuffer" # [<bool>] > #Option "SwapbuffersWait" # [<bool>] > #Option "TripleBuffer" # [<bool>] > #Option "XvPreferOverlay" # [<bool>] > Option "HotPlug" "on" # [<bool>] > Option "ReprobeOutputs" "on" # [<bool>] > #Option "XvMC" # [<bool>] > #Option "ZaphodHeads" # <str> > #Option "TearFree" # [<bool>] > #Option "PerCrtcPixmaps" # [<bool>] > #Option "FallbackDebug" # [<bool>] > #Option "DebugFlushBatches" # [<bool>] > #Option "DebugFlushCaches" # [<bool>] > #Option "DebugWait" # [<bool>] > #Option "BufferCache" # [<bool>] > Option "Backlight" "intel_backlight" > Identifier "Card0" > Driver "intel" > BusID "PCI:0:2:0" > EndSection Most options, and BusID, and usually even driver (some driver versions have been a bit broken), are irrelevant WRT configuring resolution and position. The section is necessary, but quite often with nothing more than identifier. The rest is usually no more than obfuscation and opportunity for typos. > Section "ServerFlags" More handled adquately via automagic. > Section "Screen" > Identifier "Screen0" > Device "Card0" > Monitor "Monitor-eDP1" > Monitor "Monitor-DP2" #RightOf "Monitor-eDP1" More than the above in this section is usually nothing but obfuscation confusing the path to success. Xorg is smart enough to handle the rest automagically. > Section "Screen" > Identifier "Screen1" > Device "Card0" > Monitor "Monitor1" Ditto. > Section "DRI" > Mode 0666 > EndSection That's the default, so also handled via automagic. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/