Unable to get multi head working like before

jamess7995 · 2021-11-16 01:26:35

Hey all, today my problems started after one of the two things I did
1. sudo pacman -Syu to get kernel 5.15
2. ran something like lm_sensors --detect to view cpu temps, it ran some scans on different stuff and I feel like that could've maybe caused the issue

Right now I can't get my second monitor detected in xrandr properly, but normally I use KDE system settings anyways and it's not seeing the other monitor either. I've got integrated graphics, GTX1050Ti and RTX2070, but for right now I'm just using the RTX2070 until I have time to setup a VM that will be taking that. I can provide the xrandr and lspci --nnk output here and here , but I don't know what else to provide to help you help me. I'm about to head off for the night and I'm hoping when I log back on tomorrow I'll have stuff to provide based on responses overnight.

seth · 2021-11-16 07:52:41

Are all outputs wired to the RTX2070?
Xorg log? https://wiki.archlinux.org/title/Xorg#General

jamess7995 · 2021-11-16 15:07:26

seth wrote:

Are all outputs wired to the RTX2070?
Xorg log? https://wiki.archlinux.org/title/Xorg#General

Right now they are, in troubleshooting I've tried using the 2070 for primary and the 1050Ti for the secondary monitor, no change in behavior, just a different output shows as connected but no resolution in xrandr
Here's xorg log

seth · 2021-11-16 15:18:27

The log shows an Acer EB321HQU C and an Acer S240HL - the latter one for most of the time connected to the 1050 and only in the end both are connected to the 2070
Also there's a static server config in /etc/X11/xorg.conf that references Monitor0 what most likely is one cause of the issue.
Post the /etc/X11/xorg.conf and

output shows as connected but no resolution in xrandr

also "xrandr -q"

jamess7995 · 2021-11-16 15:40:43

seth wrote:

The log shows an Acer EB321HQU C and an Acer S240HL - the latter one for most of the time connected to the 1050 and only in the end both are connected to the 2070
Also there's a static server config in /etc/X11/xorg.conf that references Monitor0 what most likely is one cause of the issue.
Post the /etc/X11/xorg.conf and
output shows as connected but no resolution in xrandr
also "xrandr -q"

So I left my computer 14 hours ago, in the 2 hours leading up to that, I'm sure the 1050 had something plugged into it a lot while I was trying different things. I did just double check though, it is connected to the 2070 and has been for about 14 hours. The EB Acer monitor is the working one. I went to do your xrandr -q command, I've been doing both "xrandr" and xrandr -q" while trying different stuff last night. For the first time I saw a resolution and I went into display settings through KDE, and was able to enable my other monitor and it's working for now... weird.
xorg conf
Here's the xrandr -q
Here's the "new" xorg log

seth · 2021-11-16 21:16:40

So the xorg.conf is the nvidia-settings generated mess plus some unused Intel screen that references the dummy Monitor0… get rid of that.

See https://wiki.archlinux.org/title/PRIME# … rimary_GPU for an example. Obviously replace "nouveau" w/ nvidia and you won't need the "xrandr --setprovideroutputsource" because the outputs are attached to the nvidia chip and you just don't want to use the intel one (?)
But especially make sure to target the PCI BusID to select the nvidia GPU you want to use because atm. that's more or less random.

jamess7995 · 2021-11-16 22:50:01

seth wrote:

So the xorg.conf is the nvidia-settings generated mess plus some unused Intel screen that references the dummy Monitor0… get rid of that.
See https://wiki.archlinux.org/title/PRIME# … rimary_GPU for an example. Obviously replace "nouveau" w/ nvidia and you won't need the "xrandr --setprovideroutputsource" because the outputs are attached to the nvidia chip and you just don't want to use the intel one (?)
But especially make sure to target the PCI BusID to select the nvidia GPU you want to use because atm. that's more or less random.

Okay so even though I've now got the monitors working I still wanted to follow your instructions, I've now got this xorg conf. I'm now about to restart xorg, if it fails I'm going to restore my previous xorg conf and report back, if I don't respond back after this, we've got working monitors.

jamess7995 · 2021-11-16 23:02:07

jamess7995 wrote:

seth wrote:
So the xorg.conf is the nvidia-settings generated mess plus some unused Intel screen that references the dummy Monitor0… get rid of that.
See https://wiki.archlinux.org/title/PRIME# … rimary_GPU for an example. Obviously replace "nouveau" w/ nvidia and you won't need the "xrandr --setprovideroutputsource" because the outputs are attached to the nvidia chip and you just don't want to use the intel one (?)
But especially make sure to target the PCI BusID to select the nvidia GPU you want to use because atm. that's more or less random.
Okay so even though I've now got the monitors working I still wanted to follow your instructions, I've now got this xorg conf. I'm now about to restart xorg, if it fails I'm going to restore my previous xorg conf and report back, if I don't respond back after this, we've got working monitors.

Okay, so that was pretty easy to "fix" I ran systemctl restart display-manager and was stuck at a blank screen, went into tty2, tried to start sddm, and got this output when I checked it's status. So I moved my old config file back and restarted display manager and got back to two monitors for my login. Here's the latest xorg log.

seth · 2021-11-17 08:26:10

It would have been more interesting to see the log of the failing server, but

    BusID          "PCI:02:00.0"

is not a legal BusID token (dot instead of colon and stray "0") - try

    BusID          "PCI:2:0:0"

Also remove teh InputDevice cruft, the referenced drivers don't exist anymore since a decade.

Arch Linux

#1 2021-11-16 01:26:35

Unable to get multi head working like before

#2 2021-11-16 07:52:41

Re: Unable to get multi head working like before

#3 2021-11-16 15:07:26

Re: Unable to get multi head working like before

#4 2021-11-16 15:18:27

Re: Unable to get multi head working like before

#5 2021-11-16 15:40:43

Re: Unable to get multi head working like before

#6 2021-11-16 21:16:40

Re: Unable to get multi head working like before

#7 2021-11-16 22:50:01

Re: Unable to get multi head working like before

#8 2021-11-16 23:02:07

Re: Unable to get multi head working like before

#9 2021-11-17 08:26:10

Re: Unable to get multi head working like before

Board footer