Running X with 2 separate displays on Debian 10 (Buster)

Böszörményi Zoltán zboszor at pr.hu
Tue Jan 14 09:28:44 UTC 2020


2020. 01. 14. 9:19 keltezéssel, Thomas Fazekas írta:
> Many thanks for the feedback, unfortunately so far no luck.
> 
> I've modified the proposed configuration as follows :
> Section "Monitor"
>           Identifier      "Monitor-Laptop"
>           Option          "AutoServerLayout" "on"
>           Option          "Rotate" "normal"
> EndSection
> 
> Section "Monitor"
>           Identifier      "Monitor-HP2311x"
>           Option          "AutoServerLayout" "on"
>           Option          "Rotate" "normal"
> EndSection
> 
> Section "Device"
>           Identifier      "Intel0"
>           Driver          "intel"
>           BusID           "PCI:0:2:0"
>           Screen          0
>           Option          "AccelMethod"  "sna"
>           Option          "Monitor-Laptop" "eDP-1"
>           Option          "ZaphodHeads" "0:eDP-1"
>           Option          "TearFree" "on"
> EndSection
> 
> Section "Device"
>           Identifier      "Intel1"
>           Driver          "intel"
>           BusID           "PCI:0:2:0"
>           Screen          1
>           Option          "AccelMethod"  "sna"
>           Option          "Monitor-HP2311x" "DP-2-3"
>           Option          "ZaphodHeads" "1:DP-2-3"

You are using the Intel driver with output names containing dashes
that are named so by the modesetting driver.

Output names from one driver cannot be mixed with a different driver.

If you insist on using the intel driver, then try the below as a complete
configuration file first, with full path as /etc/X11/xorg.conf.d/test.conf
The *.conf file name suffix is important so it actually gets loaded.

Section "Device"
     Identifier      "Intel1"
     Driver          "intel"
     BusID           "PCI:0:2:0"
     Option          "AutoServerLayout" "on"
EndSection

then restart Xorg and run "DISPLAY=:0 xrandr" to make note of all
video outputs correctly.

For completeness, repeat the exercise with

Section "Device"
     Identifier      "Intel1"
     Driver          "modesetting"
     BusID           "PCI:0:2:0"
     Option          "AutoServerLayout" "on"
EndSection

and observe that the output names differ.

Finally, decide on which driver and AccelMethod you want to use
(AccelMethod can be "glamor" for the intel driver, too) and use
the correct output names for the driver.

>           Option          "TearFree" "on"
> EndSection
> 
> Section "Screen"
>           Identifier      "SCREEN0"
>           Option          "AutoServerLayout" "on"
>           Device          "Intel0"
>           Monitor         "Monitor-Laptop"
>           SubSection      "Display"
>                   Modes   "1920x1080"
>                   Depth   24
>           EndSubSection
> EndSection
> 
> Section "Screen"
>           Identifier      "SCREEN1"
>           Option          "AutoServerLayout" "on"
>           Device          "Intel1"
>           Monitor         "Monitor-HP2311x"
>           SubSection      "Display"
>                   Modes   "1920x1080"
>                   Depth   24
>           EndSubSection
> EndSection
> 
> Section "ServerLayout"
>           Identifier      "LAYOUT"
>           Option          "AutoServerLayout" "on"
>           Screen          0 "SCREEN0"
>           Screen          1 "SCREEN1" RightOf "SCREEN0"
> EndSection
> 
> When I start X, it seems to start (it throws no error) but both my screens stay in "text" 
> mode.
> The PCI setting at least is good, the setting in the ZaphodHeads option I'm not certain of.
> 
> In case it might offer additional clues I've attached the xorg logs from a successful 
> start (where all the settings are detected
> but I get a large uninterrupted display) "auto.Xorg.0.log",

Proof from your log that the automatic config uses the modesetting driver:

[ 42190.632] (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) UHD 
Graphics 620 (Kabylake GT2)


> and the logs of my failed  
> start "manual.Xorg.0.log" (with the above
> listed settings).

The files are the same...

> 
> I'm not sure whether it makes any difference but my hardware setup is as follows : I have 
> a Thinkpad T580 connected through
> a USB-C connector to a lenovo docking station to which an external screen is attached (HP) 
> via VGA cable.
> 
> Is is possible that my failure of getting this config off the ground is due to my windows 
> manager ? (cinnamon).
> Ultimately what I want to achieve is to have to separate displays each with its own (but 
> the same type) of windows manager and
> more importantly with it's own workspace switcher (so I can switch workspaces independently)
> 
> Any support is welcome.
> 
> On Fri, Jan 10, 2020 at 6:42 PM Böszörményi Zoltán <zboszor at pr.hu <mailto:zboszor at pr.hu>> 
> wrote:
> 
>     2020. 01. 08. 11:30 keltezéssel, Thomas Fazekas írta:
>      > Dear all,
>      >
>      > I'm sitting in front of a brand new Debian Buster install with 2 monitor setup (the
>     one
>      > fro the laptop and a main screen).
>      > Both are working well, in (what I believe is called) xinerama mode, meaning I have
>     wide
>      > desktop of  3840 x 1080 size.
>      >
>      > Now what I would like to have is (I believe) 2 separate displays. I understand that
>     this
>      > would come with the limitation that I won't be able to drag windows/applications
>     between
>      > the screens.
> 
> 
>     Something like this should work for you, too:
> 
>     Section "Monitor"
>               Identifier      "Monitor-DP1"
>               Option          "AutoServerLayout" "on"
>               Option          "Rotate" "normal"
>     EndSection
> 
>     Section "Monitor"
>               Identifier      "Monitor-VGA1"
>               Option          "AutoServerLayout" "on"
>               Option          "Rotate" "normal"
>     EndSection
> 
>     Section "Device"
>               Identifier      "Intel0"
>               Driver          "intel"
>               BusID           "PCI:0:2:0"
>               Screen          0
>               Option          "AccelMethod"  "sna"
>               Option          "Monitor-DP1" "DP1"
>               Option          "ZaphodHeads" "1:DP1"
>               Option          "TearFree" "on"
>     EndSection
> 
>     Section "Device"
>               Identifier      "Intel1"
>               Driver          "intel"
>               BusID           "PCI:0:2:0"
>               Screen          1
>               Option          "AccelMethod"  "sna"
>               Option          "Monitor-VGA1" "VGA1"
>               Option          "ZaphodHeads" "0:VGA1"
>               Option          "TearFree" "on"
>     EndSection
> 
>     Section "Screen"
>               Identifier      "SCREEN"
>               Option          "AutoServerLayout" "on"
>               Device          "Intel0"
>               Monitor         "Monitor-DP1"
>               SubSection      "Display"
>                       Modes   "1024x768"
>                       Depth   24
>               EndSubSection
>     EndSection
> 
>     Section "Screen"
>               Identifier      "SCREEN1"
>               Option          "AutoServerLayout" "on"
>               Device          "Intel1"
>               Monitor         "Monitor-VGA1"
>               SubSection      "Display"
>                       Modes   "1024x768"
>                       Depth   24
>               EndSubSection
>     EndSection
> 
>     Section "ServerLayout"
>               Identifier      "LAYOUT"
>               Option          "AutoServerLayout" "on"
>               Screen          0 "SCREEN"
>               Screen          1 "SCREEN1" RightOf "SCREEN"
>     EndSection
> 
>     Now, the ZaphodHeads setting is something you need to
>     set up for your own machine, since vendors can wire
>     up video outputs differently. Look for messages like this
>     in /var/log/Xorg.0.log:
> 
>     [ 42699.692] (II) intel(0): switch to mode 1024x768 at 60.0 on DP1 using pipe 0, position
>     (0,
>     0), rotation normal, reflection none
> 
>     There will be one such line for every connected video output
>     but autodetected when there's no explicit configuration.
>     You need to specify the pipe number along with the output name
>     in Option "ZaphodHeads" for every Device section in the config.
> 
>     Also, BusID should match your machine, not the above quoted example.
> 
>     Another thing is that with using the Intel driver, the outputs
>     are called DPI1, VGA1 and so on, with the output type and number
>     written as you see. With the modesetting driver, they become
>     DPI-1, VGA-1.
> 
>     Best regards,
>     Zoltán Böszörményi
> 
> 
>      >
>      > My hardware  (inxi -GxxS) :
>      > System:    Host: thobian Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
>      > Desktop: Cinnamon 3.8.8 dm: startx
>      >             Distro: Debian GNU/Linux 10 (buster)
>      > Graphics:  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel
>     bus ID:
>      > 00:02.0 chip ID: 8086:5917
>      >             Display: tty server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
>      >             resolution: 1920x1080~60Hz, 1920x1080~60Hz
>      >             OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5
>     Mesa
>      > 18.3.6 compat-v: 3.0
>      >             direct render: Yes
>      >
>      > As far as I'm concerned there is currently no xorg.conf configuration file that  would
>      > store any X config, everything comes from the "auto config"
>      >
>      > Thanks in advance
>      >
>      > _______________________________________________
>      > xorg at lists.x.org <mailto:xorg at lists.x.org>: X.Org support
>      > Archives: http://lists.freedesktop.org/archives/xorg
>      > Info: https://lists.x.org/mailman/listinfo/xorg
>      > Your subscription address: %(user_address)s
>      >
> 
> 
> _______________________________________________
> xorg at lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
> 



More information about the xorg mailing list