2nd DP monitor suddenly only 640x480 and in standby [SOLVED]

millus · 2022-10-29 15:00:57

After some package updating, suddenly my 2nd monitor no longer works at 1920x1920 (yes it's square) but only at 640x480. Well, actually it doesn't work at all! It claims 640x480 and says "active" but remains on standby.
I always use arandr for this.
Primary is Asus ROG and this 2nd one is Eizo, both to a 1080 Ti. How would I start debugging this?

Oh and even though arandr claims the monitor is "active" the monitor itself remains in standby ie doesn't turn on.
I tried a different DP port (DP-4), same problem.

On the forums someone else from 2022 wrote that he found it to be an Archlinux specific problem that he couldn't solve and doesn't happen with other distros, but I don't know about that, since I don't use other distros.

So I tried

$ xrandr
Screen 0: minimum 8 x 8, current 3200 x 1440, maximum 32767 x 32767
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected 640x480+2560+0 (normal left inverted right x axis y axis) 0mm x 0mm
   640x480       59.94*+
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
   2560x1440     59.95*+ 144.00   120.00    99.95    84.98    23.97  
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)

$ cvt 1920 1920
# 1920x1920 59.94 Hz (CVT) hsync: 119.22 kHz; pclk: 314.75 MHz
Modeline "1920x1920_60.00"  314.75  1920 2072 2280 2640  1920 1923 1933 1989 -hsync +vsync

$ xrandr --newmode "1920x1920_60.00"  314.75  1920 2072 2280 2640  1920 1923 1933 1989 -hsync +vsync

$ xrandr --addmode DP-0 "1920x1920_60.00"
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  43
  Current serial number in output stream:  44

Solution:
Turned monitor on again (from complete off state) and it magically worked fine again^^.

Last edited by millus (2022-12-05 03:57:21)

millus · 2022-10-30 17:26:24

uh... help, please!! Any way to contact the people who actually pushed this change through so they might know what they did there and why? The monitor they broke with that package update was expensive, lmao....
How does the review process at Archlinux actually work? Is stuff like this tested somehow or just written off as bad luck, cause not checked beforehand, and just go like "well probably ok, we can never know for sure anyway, so we'll see if someone complains afterwards" ? What's the method with pacman updates, how are they "released"? Whenever a pacman -Syu messes up the system I ponder about these questions, would be nice to actually have some insight there to understand what is going on. Transparency is good.

Last edited by millus (2022-10-30 18:03:02)

seth · 2022-10-30 19:16:40

1. Don't bump, https://wiki.archlinux.org/title/Genera … es#Bumping
2.

my 2nd monitor no longer works at 1920x1920 (yes it's square)

and

Primary is Asus ROG and this 2nd one is Eizo, both to a 1080 Ti

don't seem to add up? What is "1080 Ti"? Vertical resolution?
3.

On the forums someone else from 2022 wrote that he found it to be an Archlinux specific problem that he couldn't solve and doesn't happen with other distros

Link or didn't happen - "Some people say" is meaning- and pointless FUD.
4.

The monitor they broke with that package update was expensive, lmao...

unless you punched it, nobody "broke" your monitor.
5.

Any way to contact the people who actually pushed this change through so they might know what they did there and why?

Who did what? It's not even clear where the issue is, but you demand to talk to the responsible manager? How's that ever gonna work?

So let's try to get this somewhere above the level of a rambling rant, (feel free to see https://terms.archlinux.org/docs/code-of-conduct/ ) - notably by you providing some actual data on the situation.
Start w/ your xorg log and a complete system journal:
https://wiki.archlinux.org/title/Xorg#General

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Also elaborate on

this 2nd one is Eizo

- the exact model would certainly be helpful.

millus · 2022-10-31 10:28:44

seth wrote:

1. Don't bump, https://wiki.archlinux.org/title/Genera … es#Bumping
2.
my 2nd monitor no longer works at 1920x1920 (yes it's square)
and
Primary is Asus ROG and this 2nd one is Eizo, both to a 1080 Ti
don't seem to add up? What is "1080 Ti"? Vertical resolution?

That's a "1080 Ti" graphics card by the company "NVidia", there are basically two big brands of GPUS: 1) NVidia 2) AMD.. NVidia has series like 9xx, 10xx, 20xx, 30xx and new for a few weeks 40xx, and models that go a bit above the tier indicated by "xx" part carry the "Ti" suffix.

seth wrote:

3.
On the forums someone else from 2022 wrote that he found it to be an Archlinux specific problem that he couldn't solve and doesn't happen with other distros
Link or didn't happen - "Some people say" is meaning- and pointless FUD.

Let it become truth thanks to the holy linkagehttps://bbs.archlinux.org/viewtopic.php?id=276138

seth wrote:

4.
The monitor they broke with that package update was expensive, lmao...
unless you punched it, nobody "broke" your monitor.

ELI5: It did work. Person X changes something in the packages. It does not work anymore. -> Person X broke it. Although you could argue that I was the one breaking it by acting in good faith when entering that "sudo pacman -Syu".

seth wrote:

So let's try to get this somewhere above the level of a rambling rant, (feel free to see https://terms.archlinux.org/docs/code-of-conduct/ ) - notably by you providing some actual data on the situation.
Start w/ your xorg log and a complete system journal:
https://wiki.archlinux.org/title/Xorg#General
sudo journalctl -b | curl -F 'file=@-' 0x0.st

Thanks, but it seems the file is too large, it stopped with an error that it exceeds the 512MB max size.

seth wrote:

Also elaborate on
this 2nd one is Eizo
- the exact model would certainly be helpful.

Eizo Flexscan EV2730Q

What I did try meanwhile is adding an xorg.conf that has the specs of both monitors and adds a modeline derived from cvt 1920 1920 but that completely stopped X from even starting up.

Last edited by millus (2022-10-31 10:39:21)

seth · 2022-10-31 13:04:24

Thanks, but it seems the file is too large, it stopped with an error that it exceeds the 512MB max size.

Did you issue the "-b"? 512MB is faaaaar to massive for a single boot journal.
Also the Xorg journal is certainly not of that size.

The post you linked is on an [AMD/ATI] Cezanne and complains about it, so it's likely not the problem.
Edit: also that was 6 months ago - I assume you update the system more often than that?

Ftr.

Person X changes something in the packages. It does not work anymore

is an assuption, we don't know at all what happened and won't before you can produce any kind of logs about the system.

Last edited by seth (2022-10-31 13:12:14)

millus · 2022-12-05 03:54:45

Thanks.
Yes, I did issue "-b", I'm familiar with commandline sort of, making bash scripts and stuff, definitely not missing a detail here from your command.
I noticed I got LOOOOOTS of "devilspie" errors in dmesg though, insane spam. Maybe that inflated it.
Well, I was a bit too low on time to pursue this problem further, was not at home anyway cause of holidays.
However, today I turned on the 2nd monitor again and suddenly it works fine again as if nothing ever happened..lol.
(And for the record all other "solutions" that people posted on linux forums or reddit didn't work at all. And creating an xorg.conf, as someone suggested on some forum, actually completely breaks the system. I NEED to delete any xorg.conf for Archlinux to work.)

Edit:
Btw is there some script that auto-removes personal info from that dump? I noticed it may contain some. Just wondering.

Last edited by millus (2022-12-05 11:24:55)

Arch Linux

#1 2022-10-29 15:00:57

2nd DP monitor suddenly only 640x480 and in standby [SOLVED]

#2 2022-10-30 17:26:24

Re: 2nd DP monitor suddenly only 640x480 and in standby [SOLVED]

#3 2022-10-30 19:16:40

Re: 2nd DP monitor suddenly only 640x480 and in standby [SOLVED]

#4 2022-10-31 10:28:44

Re: 2nd DP monitor suddenly only 640x480 and in standby [SOLVED]

#5 2022-10-31 13:04:24

Re: 2nd DP monitor suddenly only 640x480 and in standby [SOLVED]

#6 2022-12-05 03:54:45

Re: 2nd DP monitor suddenly only 640x480 and in standby [SOLVED]

Board footer