[SOLVED] iGPU Triple Monitor Setup

demencia · 03-24-2020, 12:03 PM

Hello everyone, I recently set up my 3 screen setup on my computer by enabling the integrated graphics card on the Bios. On windows 10 it was plug and play, but I can't figure how to get it going on Manjaro and I can't seem to hit the right post with the information needed either. I read somewhere that it worked out of the box for someone with the nouveau drivers but it wasn't my case, although it was as close as I got (for a split second everything on my screens was messed up but there was some stuff showing on the screen plugged on the iGPU socket. If nouveau is the only option I'll take it but I would love to make the best out of my gpu using the nvidia drivers instead. Btw, I'm running an RTX 2070 with one screen connected on DP and another through HDMI, then on the on board graphic card I got a screen connected through HDMI. I can provide any other relevant information needed.

Sorry for the wall post and thank you for your time!

mrmazda · 03-24-2020, 10:58 PM

Not every IGP can be used when a PCIe GPU is installed. It depends on whether the BIOS supports that configuration.

I have two PCs with 4 video outputs each driven by Intel HD Graphics 630. Both support 3 displays simultaneously with no fuss from the default modesetting DDX in the distros I use on them, openSUSE, Fedora, Debian, Mint & Ubuntu, e.g. http://fm.no-ip.com/SS/Xorg/magnoliais-2560x3690.jpg

To be able to help maybe we need a bit more detail on your installed hardware,

Code:

inxi -SGxx
xrandr --listproviders

output run from a GUI terminal and pasted here enclosed in code tags.

demencia · 03-25-2020, 05:25 PM

Hello! Thank you for your reply! I know this setup is possible because I got it working on my Windows partition. The iGPU is the same as yours, Intel HD 630. To sort this problem easier, let's make it about two screens only, one on dGPU (nvidia RTX 2070 through DP) and one on the iGPU (Intel HD 630 through HDMI).

Here's the output of

Code:

inxi -SGxx

Code:

System:
  Host: demencia-manjaro Kernel: 5.4.27-1-MANJARO x86_64 bits: 64 
  compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.0 wm: gnome-shell dm: GDM 
  Distro: Manjaro Linux 
Graphics:
  Device-1: Intel UHD Graphics 630 vendor: Micro-Star MSI driver: i915 
  v: kernel bus ID: 00:02.0 chip ID: 8086:3e98 
  Device-2: NVIDIA TU106 [GeForce RTX 2070] vendor: Gigabyte driver: nvidia 
  v: 440.64 bus ID: 01:00.0 chip ID: 10de:1f02 
  Display: x11 server: X.org 1.20.7 driver: nvidia compositor: gnome-shell 
  resolution: <xdpyinfo missing> 
  OpenGL: renderer: GeForce RTX 2070/PCIe/SSE2 v: 4.6.0 NVIDIA 440.64 
  direct render: Yes

Here's the output of

Code:

xrandr --listproviders

Code:

Providers: number : 1
Provider 0: id: 0x1b8 cap: 0x1, Source Output crtcs: 4 outputs: 8 associated providers: 0 name:NVIDIA-0

Although I'm pretty sure while trying many things before reinstalling manjaro I got it to display 2 providers (both gpu's)

If there's anything else I can add please let me know.

mrmazda · 03-26-2020, 08:28 PM

I don't know what to suggest about your xrandr --listproviders count of only 1 being inconsistent with an inxi showing of 2 devices. Maybe some BIOS change is required.

3 screens work for me automatically, no configuration required, for Xorg side-by-side-by-side display configuration with an ancient GeForce on openSUSE with the upstream Xorg default DDX driver (neither intel DDX nor nouveau DDX):

Code:

# inxi -SMGxx
System:    Host: ab250 Kernel: 5.4.12-1-default x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: IceWM 1.6.3 dm: startx 
           Distro: openSUSE Tumbleweed 20200319 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B250M-C v: Rev X.0x serial: 171013077301155 UEFI: American Megatrends 
           v: 1608 date: 10/21/2019 
Graphics:  Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5912 
           Device-2: NVIDIA G84 [GeForce 8600 GT] vendor: XFX Pine driver: nouveau v: kernel bus ID: 01:00.0 
           chip ID: 10de:0402 
           Display: server: X.Org 1.20.7 driver: modesetting unloaded: fbdev,vesa alternate: intel,nouveau,nv,nvidia 
           resolution: 1680x1050~60Hz, 1920x1200~60Hz, 2560x1440~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.1 compat-v: 3.0 direct render: Yes
# xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x47; cap: 0xf (Source Output, Sink Output, Source Offload, Sink Offload); crtcs: 3; outputs: 5; associated providers: 1; name: modesetting
    output DP-1
    output HDMI-1
    output HDMI-2
    output HDMI-3
    output DP-2
Provider 1: id: 0x96; cap: 0x2 (Sink Output); crtcs: 2; outputs: 2; associated providers: 1; name: modesetting
    output DVI-I-1-1
    output DVI-I-1-2
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
Screen 0: minimum 320 x 200, current 6160 x 1440, maximum 16384 x 16384
DVI-I-1-2 connected 2560x1440+3600+0 (normal left inverted right x axis y axis) 598mm x 336mm
DVI-I-1-1 connected 1920x1200+1680+0 (normal left inverted right x axis y axis) 519mm x 324mm
DP-1 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
   2560x1440     59.95*+
   1920x1200     59.95*+
   1680x1050     59.97*+  74.89  
# xdpyinfo | grep dimen
  dimensions:    6160x1440 pixels (1303x304 millimeters)

Only the small screen connected to the Intel DisplayPort lights up on the vttys.

demencia · 03-27-2020, 12:07 AM

Wow, thank you very much for setting all that up to try it. It helped me think it was possible and get it to work!
So, googling "xrandr listproviders only one" brought me to this post https://www.reddit.com/r/archlinux/c...vider_missing/
which led me here -> https://wiki.archlinux.org/index.php...utput_provider

I moved /etc/X11/xorg.conf.d/90-mhwd.conf to 90-mhwd.conf.bak and rebooted, and my 3rd screen was working!!
Thank you so much!

mrmazda · 03-27-2020, 01:08 AM

Quote:

Originally Posted by demencia

I moved /etc/X11/xorg.conf.d/90-mhwd.conf to 90-mhwd.conf.bak and rebooted, and my 3rd screen was working!!

I'm sorry I forgot to bring up the subject of config files early on. Their creators mean well, but they can certainly backfire, as the post you found implied, and is not unusual. Automagic works so well in recent years it's quite rare that FOSS users need any of them, and I suspect most NVidia driver users don't need the bulk of what theirs contain either.

What exactly is/was the content of 90-mhwd.conf? That is a filename I can't recall encountering on Debian, Fedora, Gentoo, Knoppix, Mageia, Mint, openSUSE, Puppy, Slax, Ubuntu or anywhere else.

demencia · 03-27-2020, 06:36 PM

Don't apologise, I got to the solution thanks to your replies! Thanks a lot!
MHWD is a Manjaro tool that helps to deal with drivers. It's actually pretty good, but it doesn't take into account very specific setups like the one I was going for I guess?
Here's the content of the file:

Code:

 nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 440.64

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
	Option "NoLogo" "1"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Extensions"
    Option         "COMPOSITE" "Enable"
EndSection

 
Section "InputClass"
    Identifier          "Keyboard Defaults"
    MatchIsKeyboard        "yes"
    Option              "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection

mrmazda · 03-27-2020, 09:25 PM

Section "Device" may be the only one to cause trouble, but the rest mostly look like hard-coding what automagic and defaults do, likely unnecessary.