Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

allevil669 · 2022-10-22 20:08:35

Hi again.

This issue is, once again, causing me real issues. I have an Nvidia GTX 1660 Ti, and three monitors, connected via HDMI. For the last year and a half, everything has been working exactly as one would expect, but since recently, I the entire setup is broken. I have tried rolling back, downgrading, and everything else I can think of, and so far, nothing is helping.

Current packages:

linux 6.0.2-arch1-1
nvidia 520.56.06-4
nvidia-utils 520.56.06-2
plasma 5.26.1-1

Until recent updates, my multi monitors worked perfectly, with almost zero configuration, but now... Nothing. I can barely get one monitor working correctly, much less more than one.

Last edited by allevil669 (2022-10-22 20:41:56)

seth · 2022-10-22 20:21:14

Install and try the linux-lts kernel and nvidia-lts and post a complete system journal (sudo journalctl -b) and your xorg log, https://wiki.archlinux.org/title/Xorg#General and the output of "xrandr -q"
Also skip the ridiculously over the top pleas for help.

allevil669 · 2022-10-22 20:36:11

With linux-lts, I get no functioning screens at all if I have more than one plugged in. I have to power off, unplug two of my monitors, and reboot just to get to anything functioning. With either nvidia + current kernel or nvidia-open + current kernel, I can at least get to an SDDM login, but only my primary monitor will power up/be recognized. As for logs, here we go.

Journalctl - https://www.dropbox.com/s/mincy7bme5917 … l.log?dl=0
Xorg.0 - https://www.dropbox.com/s/w2864xl5ndp97 … 0.log?dl=0
Xorg.1 - https://www.dropbox.com/s/4xn25x55xzw2r … 1.log?dl=0

As for "over the top"? This issue is literally preventing me from doing the work I'm expected to, and has never once been an issue, so I'm in a rather bad spot right now. So please, forgive my frustration.

jasonwryan · 2022-10-22 20:38:42

Fix your title: https://wiki.archlinux.org/title/Genera … ow_to_post

V1del · 2022-10-22 20:43:36

Remove /etc/X11/xorg.conf and retry. nvidia-xconfig generally creates static configs that are very sensitive to the slightest logic changes and the majority of the stuff in there is useless outdated cruft

Also for LTS to be a useful test you need to install nvidia-lts, did you do that?

Last edited by V1del (2022-10-22 20:50:56)

seth · 2022-10-22 20:52:45

The xorg log has nothing but

[     5.129] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): connected
[     5.129] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): Internal TMDS
[     5.129] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): 300.0 MHz maximum pixel clock
[     5.129] (--) NVIDIA(GPU-0):

I assume that's because you didn't attach any other outputs?
In that case, run KDE w/ all desired outputs attached and post the xorg log from the console (see the 1st link below, dropbox sucks anyway)

Most people show up w/ problems that are severe to them, but littering your post with "please help ui need help really please i need help" achieves nothing but wasting everyones time - yours writing and ours reading through this nonsense.

allevil669 · 2022-10-22 21:14:53

Ok, here is a brand new Xorg.0, with all three plugged in. With all three, I don't even get the central monitor powering up, the monitors all behave like the ports they are plugged into are just, disabled.

https://pastebin.com/2akxB2EK

In response to V1del, yes, I had moved to nvidia-lts as well, with the LTS kernel and drivers, I got no monitors powered up, regardless of the arraingement.

seth · 2022-10-22 21:30:06

Still only

[    18.049] (--) NVIDIA(GPU-0): 
[    18.144] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): connected
[    18.144] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): Internal TMDS
[    18.144] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): 300.0 MHz maximum pixel clock
[    18.144] (--) NVIDIA(GPU-0):

shows up.
wrt

With all three, I don't even get the central monitor powering up, the monitors all behave like the ports they are plugged into are just, disabled

and since you're using pastebin.com, I guess you restarted the X11 server w/ only one output attacahed to post the log, but in that case you need to look at /var/log/Xorg.0.log.old
The server in the log was started at Sat Oct 22 14:04:36 2022

allevil669 · 2022-10-22 21:35:51

seth wrote:

Still only
[    18.049] (--) NVIDIA(GPU-0): 
[    18.144] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): connected
[    18.144] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): Internal TMDS
[    18.144] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): 300.0 MHz maximum pixel clock
[    18.144] (--) NVIDIA(GPU-0): 
shows up.
wrt
With all three, I don't even get the central monitor powering up, the monitors all behave like the ports they are plugged into are just, disabled
and since you're using pastebin.com, I guess you restarted the X11 server w/ only one output attacahed to post the log, but in that case you need to look at /var/log/Xorg.0.log.old
The server in the log was started at Sat Oct 22 14:04:36 2022

Ok, here is the Xorg.0.old

https://pastebin.com/eRkMxjj9

seth · 2022-10-22 21:59:39

[     5.930] (--) NVIDIA(GPU-0): Acer K243Y (DFP-1): connected
[     5.930] (--) NVIDIA(GPU-0): Acer K243Y (DFP-1): Internal TMDS
[     5.930] (--) NVIDIA(GPU-0): Acer K243Y (DFP-1): 300.0 MHz maximum pixel clock
[     6.023] (--) NVIDIA(GPU-0): Acer K243Y (DFP-3): connected
[     6.023] (--) NVIDIA(GPU-0): Acer K243Y (DFP-3): Internal TMDS
[     6.023] (--) NVIDIA(GPU-0): Acer K243Y (DFP-3): 300.0 MHz maximum pixel clock
[     6.116] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): connected
[     6.116] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): Internal TMDS
[     6.116] (--) NVIDIA(GPU-0): Acer KA272U (DFP-6): 300.0 MHz maximum pixel clock
[     6.116] (--) NVIDIA(GPU-0): 
[     6.289] (==) NVIDIA(0): 
[     6.289] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[     6.289] (==) NVIDIA(0):     will be used as the requested mode.
[     6.289] (==) NVIDIA(0): 
[     6.290] (II) NVIDIA(0): Validated MetaModes:
[     6.290] (II) NVIDIA(0):    
[     6.290] (II) NVIDIA(0):     "DFP-6:nvidia-auto-select,DFP-1:nvidia-auto-select,DFP-3:nvidia-auto-select"
[     6.290] (II) NVIDIA(0): Virtual screen size determined to be 6400 x 1440

There're three outputs and they're all used.
There's no error but then

[     6.934] (II) NVIDIA(0): Setting mode "DP-5: nvidia-auto-select @2560x1440 +0+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}, DP-1: nvidia-auto-select @1920x1080 +2560+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[     7.073] (II) NVIDIA(0): Setting mode "DP-5: nvidia-auto-select @2560x1440 +0+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}"

something configures the output for DP-5 ad DP-1 and ultimately we end at

[    19.655] (II) NVIDIA(0): Setting mode "NULL"

I suppose because those outputs don't exist.
Start the X11 server w/ all three outputs, switch to another VT (ctrl+alt+F2) and check "xrandr --display :0 -q"

I guess this is some SDDM startup script?

allevil669 · 2022-10-22 22:15:19

Start the X11 server w/ all three outputs, switch to another VT (ctrl+alt+F2) and check "xrandr --display :0 -q"

That results in a response of...

> xrandr --display :0 -q
Invalid MIT-MAGIC-COOKIE-1 key
Can't open display :0

I guess this is some SDDM startup script?

I do have an SDDM Xsetup script, and your mention of it made me think "what if that's the issue?", so I renamed it, rebooted, and tried again.

> xrandr --display :0 -q
Invalid MIT-MAGIC-COOKIE-1 key
Can't open display :0

Unfortunately, same results.

EDIT: I'm currently searching for the error, but all I am finding is related to X forwarding, and running GUI application as root. I will continue to comb through results.

Last edited by allevil669 (2022-10-22 22:21:12)

seth · 2022-10-23 06:31:18

The "Invalid MIT-MAGIC-COOKIE-1 key" thing happens because you're running this as the "wrong" user, the session is probably held by sddm.
Try to sudo it, but in doubt

sudo env DISPLAY=:0 xhost +

should™ open the server and allow you to access it as any user.

so I renamed it, rebooted, and tried again

The xsetup script would not be related to the xauthority issue, but the question is whether it has impact on your monitor situation.

If you can finally xrandr, you might find all outputs to be disabled and then "xrandr --output <output name> --auto" should enable them for you.
The most critical question is actually whether you still get visual output on the console while multiple outputs are attached.

You can perhaps also boot and login w/ one output, then attach the others and activate them from there.

allevil669 · 2022-10-23 06:45:02

seth wrote:

The "Invalid MIT-MAGIC-COOKIE-1 key" thing happens because you're running this as the "wrong" user, the session is probably held by sddm.
Try to sudo it, but in doubt
sudo env DISPLAY=:0 xhost +
should™ open the server and allow you to access it as any user.

I know you didn't mention this, and it may be completely unrelated... Could groups be an issue? I noticed that my main login isn't in the "video" group. Also, going to try the xhost command. I'll report back in a bit.

EDIT: No dice on any of that. The xhost command didn't change anything, nor did adding me to the "video" group. Hotplugging any of the monitors causes the entire video card to "crash", and xrandr shows the monitors, but cannot work with them at all. I'm again at a complete loss.

Last edited by allevil669 (2022-10-23 06:56:11)

seth · 2022-10-23 07:05:08

Define "crash", notably if "xrandr shows the monitors" and "cannot work with them at all"
Does it work if you suspend the compositor (SHIFT+Alt+F12)?

Edit: this might be a pure plasma issue, https://bbs.archlinux.org/viewtopic.php?id=280645

Last edited by seth (2022-10-23 07:12:20)

allevil669 · 2022-10-23 07:33:52

Crash probably isn't the best word, when I attempt to hotplug, it causes an unrecoverable (unplugging doesn't revert, can't switch to a TTY, etc) black screen for all monitors. If I boot with all three, only one, monitor "DP-1" turns on, even though SDDM shows up on all three. When I try to configure the monitors with screen management, they show up, and allow me to configure them, they configuration doesn't work, and doesn't stay after closing the configuration applet. Switching compositing off and on doesn't change anything. If I try xrandr with more than one monitor connected, they all show up when I list monitors, but trying to configure them with xrandr gives a "can't open display" message.

Last edited by allevil669 (2022-10-23 07:34:21)

seth · 2022-10-23 07:50:58

"can't open display" is because outside the context of the GUI session you'll have to explicitly specify the DISPLAY (":0") but that would apply to "xrandr --listmonitors" as well.
To figure whether this is an X11 problem or a Plasma problem, install eg. openbox, configure your xinitrc to start that (last link below ;-) and then boot into the multi-user.target (2nd link), log in and run startx.

allevil669 · 2022-10-23 22:32:04

Ok, thanks for your patience.

sudo systemctl disable sddm.service

Restart. All screens come up with a cloned TTY, so far, so good.

startx

Errors out, becasue I never installed TWM or xterm, fix that and

startx

again. BOOM, all monitors up and running in X11. Good, very good. So, then I try

xrandr --output DP-5 --mode 2560x1440 --rate 75 --primary

... Perfect.

xrandr --output DP-1 --mode 1920x1080 --rate 75 --rotate right --right-of DP-5

... Also perfect... I think you know where this leads.

It's now really looking like a Plasma issue, isn't it?

More edits: I have done some more testing. When I have Plasma launch from startx, I can use xrandr commands to get the monitors configured, however, the kscreen2 configuration program is not working correctly.

Last edited by allevil669 (2022-10-23 22:46:24)

seth · 2022-10-24 06:30:11

How do you start plasma from startx? (Cause "exec startplasma-x11" in the xinitrc would have been my next suggestion to see whether this is only an SDDM issue)

Also nb. the last link below - if you don't source /etc/X11/xinit/xinitrc.d/50-systemd-user.sh you'll end up w/ a broken session.

allevil669 · 2022-10-24 07:05:31

seth wrote:

How do you start plasma from startx? (Cause "exec startplasma-x11" in the xinitrc would have been my next suggestion to see whether this is only an SDDM issue)
Also nb. the last link below - if you don't source /etc/X11/xinit/xinitrc.d/50-systemd-user.sh you'll end up w/ a broken session.

To be honest, I simply used the .xinitrc method found in section 2.2 of the KDE/Plasma ArchWiki page. Other than PAM not unlocking my KWallet, everything seems to be working as intended. I think this is an issue with SDDM, or something related to it.

Last edited by allevil669 (2022-10-24 07:06:08)

seth · 2022-10-24 07:36:03

pacman -Qikk sddm
ls /usr/share/sddm/scripts/
ls /etc/sddm/scripts/
ls -R /etc/sddm.conf*

allevil669 · 2022-10-24 17:08:47

seth wrote:

pacman -Qikk sddm
ls /usr/share/sddm/scripts/
ls /etc/sddm/scripts/
ls -R /etc/sddm.conf*

Results:

> pacman -Qikk sddm
Name            : sddm
Version         : 0.19.0-8
Description     : QML based X11 and Wayland display manager
Architecture    : x86_64
URL             : https://github.com/sddm/sddm
Licenses        : GPL
Groups          : None
Provides        : display-manager
Depends On      : qt5-declarative  xorg-xauth  xorg-server  ttf-font
Optional Deps   : None
Required By     : sddm-kcm
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 4.45 MiB
Packager        : Antonio Rojas <arojas@archlinux.org>
Build Date      : Thu Feb 3 13:26:58 2022
Install Date    : Sat Feb 5 10:20:17 2022
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

warning: sddm: /usr/share/sddm/scripts/Xsetup (No such file or directory)
sddm: 228 total files, 1 altered file

> ls /usr/share/sddm/scripts/
wayland-session*  Xsession*  Xsetup.OLD*  Xstop*

The Xsetup.OLD is where I have my pre-login monitor setup. I renamed it, thinking it could be the issue.

> ls /etc/sddm/scripts
ls: cannot access '/etc/sddm/scripts': No such file or directory

> ls -R /etc/sddm.conf*
/etc/sddm.conf

/etc/sddm.conf.d:
kde_settings.conf

V1del · 2022-10-24 17:41:12

_OLD will still be loaded. Remove it entirely/replace it with defaults if you don't want it to trigger or comment the setup lines. Maybe also post the file, you might run some racy stuff or so..

Last edited by V1del (2022-10-24 17:43:00)

allevil669 · 2022-10-24 17:48:03

V1del wrote:

_OLD will still be loaded. Remove it entirely/replace it with defaults if you don't want it to trigger or comment the setup lines. Maybe also post the file, you might run some racy stuff or so..

Well, the contents of the Xsetup.OLD are as follows...

#!/bin/sh
# Xsetup - run as root before the login dialog appears

xrandr --output DP-3 --off
xrandr --output DP-5 --mode 2560x1440 --rate 75.0 --rotate normal --primary
xrandr --output DP-1 --off

As you can see, nothing out of the ordinary. It was working quite well until recently. When I would log in from SDDM, kscreen2 would take over, and set my monitors up how I wanted them after login.

seth · 2022-10-24 19:35:29

Maybe not out of the ordinary, but the xrandr calls are SUPER prone to cause your situation, notably if the DP count changed.
Did you ever post an "xrandr -q" output?

Edit: instead of renaming the file, just comment the xrandr calls and see what happens.

Last edited by seth (2022-10-24 19:36:44)

allevil669 · 2022-10-24 19:38:38

seth wrote:

Maybe not out of the ordinary, but the xrandr calls are SUPER prone to cause your situation, notably if the DP count changed.
Did you ever post an "xrandr -q" output?
Edit: instead of renaming the file, just comment the xrandr calls and see what happens.

I don't think I have posted the output of xrandr -q... So, let's do that.

> xrandr -q
Screen 0: minimum 8 x 8, current 4720 x 1920, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected 1080x1920+3640+0 right (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080     60.00 +  74.97*   59.94    50.00  
   1680x1050     59.95  
   1440x900      59.89  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x800      59.81  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94    59.93  
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 connected 1080x1920+0+0 left (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080     60.00 +  74.97*   59.94    50.00  
   1680x1050     59.95  
   1440x900      59.89  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x800      59.81  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94    59.93  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 connected primary 2560x1440+1080+240 (normal left inverted right x axis y axis) 597mm x 336mm
   2560x1440     74.60*+  59.95  
   1920x1080     60.00    59.94    50.00  
   1680x1050     59.95  
   1440x900      59.89  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x800      59.81  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94    59.93

I'll also let you know what happens when I just comment out things.

EDIT: Ok, with the Xsetup file replaced, and the xrandr commands commented out, it appears to be working almost like it was before. I'm going to assume that the offending commands are the "xrandr --output DP-3 --off" lines... But why would they be an issue now, and not an issue for over a year? Was there a change that I didn't hear about?

Last edited by allevil669 (2022-10-24 19:45:08)

Arch Linux

#1 2022-10-22 20:08:35

Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#2 2022-10-22 20:21:14

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#3 2022-10-22 20:36:11

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#4 2022-10-22 20:38:42

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#5 2022-10-22 20:43:36

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#6 2022-10-22 20:52:45

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#7 2022-10-22 21:14:53

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#8 2022-10-22 21:30:06

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#9 2022-10-22 21:35:51

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#10 2022-10-22 21:59:39

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#11 2022-10-22 22:15:19

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#12 2022-10-23 06:31:18

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#13 2022-10-23 06:45:02

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#14 2022-10-23 07:05:08

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#15 2022-10-23 07:33:52

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#16 2022-10-23 07:50:58

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#17 2022-10-23 22:32:04

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#18 2022-10-24 06:30:11

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#19 2022-10-24 07:05:31

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#20 2022-10-24 07:36:03

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#21 2022-10-24 17:08:47

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#22 2022-10-24 17:41:12

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#23 2022-10-24 17:48:03

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#24 2022-10-24 19:35:29

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

#25 2022-10-24 19:38:38

Re: Nvidia + Plasma + 3 monitor multihead isn't functioning as intended.

Board footer