Graphics related bug after new update(s)?

br1ck · 2025-08-16 21:57:23

Hi! I'm trying to update my system (using yay -Syu), but when I do (and reboot), I run into some graphical issues:

One of my monitors becomes stuck in a low resolution & refresh rate
My other monitor sometimes goes black completely
Some of my applications also become low res/unusable

.
Rolling back my packages to August 1st brings it back to normal. I've searched to try and find more info to see what's broken, but I can't find anything. I'm still relatively new to Arch, so I might also be missing something.

For reference, I have an NVIDIA GTX 1660 GPU, and here's my pacman -Qs nvidia:

local/egl-gbm 1.1.2.1-1
    The GBM EGL external platform library
local/egl-wayland 4:1.1.20-1
    EGLStream-based Wayland external platform
local/egl-x11 1.0.3-1
    NVIDIA XLib and XCB EGL Platform Library
local/libvdpau 1.5-3
    Nvidia VDPAU library
local/linux-firmware-nvidia 20250808-1
    Firmware files for Linux - Firmware for NVIDIA GPUs and SoCs
local/nvidia-open-dkms 580.76.05-4
    NVIDIA open kernel modules - module sources
local/nvidia-utils 580.76.05-4
    NVIDIA drivers utilities

Originally, I thought it was one of "linux linux-firmware" because it had started to bug when I rolled back and only updated those, but I've tried updating everything except for those & still have the issue (though I may have missed one?). I also tried switching to linux-lts for my kernel, but just switching to it while rolledback on all my packages caused the bug to occur.

I should also probably mention that when I was trying to update it the first time, my power went out so I went back and deleted a .lock & a directory in my cache that was preventing me from yay -Scc-ing and freeing up space.

What can I do to update packages without it breaking?

Thanks in advance!

seth · 2025-08-17 13:28:50

https://bbs.archlinux.org/viewtopic.php … 8#p2256418 ?

Otherwise

One of my monitors becomes stuck in a low resolution & refresh rate

What display server and what's the output of "xrandr -q" in that case?

br1ck · 2025-08-17 17:45:12

I'm on Wayland + SDDM.

I tried adding a delay to my sddm.service to try and get rid of the race condition, but that doesn't solve the low-res & refresh rate issue or the issue with some of my applications not running correctly. I haven't gotten a black screen on my other monitor in the several reboots I've tried with this change, though, so it might've solved that issue.

Here's my xrandr (monitor with issues is DP-3, but it's the exact same monitor model as HDMI-A-3): https://termbin.com/bcdp

My journal (zed is one of the applications that fails, which should be shown here): https://termbin.com/0cib

Please let me know if there's anything else I can provide!

seth · 2025-08-17 20:19:40

Aug 17 10:04:02 yaopc sddm[702]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
Do you have the same problem w/ a KDE/X11 session?

Do you get this w/ the non-open nvidia kernel module?

There was a case where the output didn't show up w/ an EDID anymore (I'll have to look up the thread), so please also add

for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

You'll need https://archlinux.org/packages/extra/x86_64/v4l-utils/

br1ck · 2025-08-18 05:19:18

Yes, it also happens with a KDE/X11 session. In fact, my monitor starts telling me it's getting an unsupported refresh rate when I get to my greeter.

This first started happening while I was on the non-open nvidia kernel and I was hoping the open would fix it, but it doesn't.

Here's my Xorg: https://termbin.com/aq2z

And here's my EDID: https://termbin.com/sial

Super sorry for the delayed replies, I've got some really horrible hours at work right now. I really appreciate your help!

seth · 2025-08-18 08:18:52

EDID looks fine, hybrid graphics, X11 runs on nvidia where both Sceptre F27 outputs are attached.

Adding /etc/X11/xorg.conf.d/20-nvidia_debug.conf

Section "Device"
   Identifier "nvidia debug"
   Driver "nvidia"
   Option "ModeDebug" "True"
EndSection

should™ make the driver print the modeline processing (and the reasons why it filters modes) to the xorg log.

Edit: you btw. don't have to apologize, not in general and certainly not for 9h "delays" - this is an asynchronous communication, runs mostly at your pace and it might easily take me a day or longer to respond.

Last edited by seth (2025-08-18 08:20:33)

br1ck · 2025-08-20 07:43:12

Here's my Xorg log with the debug stuff: https://termbin.com/6jdb

Thanks!

seth · 2025-08-20 14:06:15

[     9.899] (--) NVIDIA(GPU-0): Sceptre F27 (DFP-4): 600.0 MHz maximum pixel clock
[     9.994] (II) NVIDIA(GPU-0): --- Building ModePool for Sceptre F27 (DFP-4) ---
[     9.996] (II) NVIDIA(GPU-0):   Validating Mode "1920x1080_60":
[     9.996] (II) NVIDIA(GPU-0):     Mode Source: EDID
[     9.996] (II) NVIDIA(GPU-0):     1920 x 1080 @ 60 Hz
[     9.996] (II) NVIDIA(GPU-0):       Pixel Clock      : 148.50 MHz
[     9.996] (II) NVIDIA(GPU-0):       HRes, HSyncStart : 1920, 2008
[     9.996] (II) NVIDIA(GPU-0):       HSyncEnd, HTotal : 2052, 2200
[     9.996] (II) NVIDIA(GPU-0):       VRes, VSyncStart : 1080, 1084
[     9.996] (II) NVIDIA(GPU-0):       VSyncEnd, VTotal : 1089, 1125
[     9.996] (II) NVIDIA(GPU-0):       Sync Polarity    : +H -V 
[     9.996] (II) NVIDIA(GPU-0):     DSCPassThrough: No
[     9.996] (II) NVIDIA(GPU-0):     DualHead Mode: No
[     9.996] (II) NVIDIA(GPU-0):     Viewport                 1920x1080+0+0
[     9.996] (II) NVIDIA(GPU-0):       Horizontal Taps        2
[     9.996] (II) NVIDIA(GPU-0):       Vertical Taps          2
[     9.996] (II) NVIDIA(GPU-0):     Mode "1920x1080_60" is valid.
[    10.027] (II) NVIDIA(GPU-0):   HorizSync   : 31.469-84.373 kHz
[    10.027] (II) NVIDIA(GPU-0):   VertRefresh : 50.000-75.029 Hz
[    10.027] (II) NVIDIA(GPU-0):     (HorizSync from EDID)
[    10.027] (II) NVIDIA(GPU-0):     (VertRefresh from EDID)

[     9.994] (--) NVIDIA(GPU-0): Sceptre F27 (DFP-6): 340.0 MHz maximum pixel clock
[    10.027] (WW) NVIDIA(GPU-0):   Validating Mode "1920x1080_60":
[    10.027] (WW) NVIDIA(GPU-0):     Mode Source: EDID
[    10.027] (WW) NVIDIA(GPU-0):     1920 x 1080 @ 60 Hz
[    10.027] (WW) NVIDIA(GPU-0):       Pixel Clock      : 148.50 MHz
[    10.027] (WW) NVIDIA(GPU-0):       HRes, HSyncStart : 1920, 2008
[    10.027] (WW) NVIDIA(GPU-0):       HSyncEnd, HTotal : 2052, 2200
[    10.027] (WW) NVIDIA(GPU-0):       VRes, VSyncStart : 1080, 1084
[    10.027] (WW) NVIDIA(GPU-0):       VSyncEnd, VTotal : 1089, 1125
[    10.027] (WW) NVIDIA(GPU-0):       Sync Polarity    : +H -V 
[    10.027] (WW) NVIDIA(GPU-0):     Mode is rejected: HorizSync (67.500 kHz) out of range
[    10.027] (WW) NVIDIA(GPU-0):     (28.000-55.000 kHz).
[    10.027] (WW) NVIDIA(GPU-0):     GPU extended capability check failed.
[    10.027] (WW) NVIDIA(GPU-0):     Mode "1920x1080_60" is invalid.
[    10.048] (II) NVIDIA(GPU-0): --- Done building ModePool for Sceptre F27 (DFP-6) ---
[    10.048] (II) NVIDIA(GPU-0): 
[    10.048] (II) NVIDIA(GPU-0): Frequency information for Sceptre F27 (DFP-6):
[    10.048] (II) NVIDIA(GPU-0):   HorizSync   : 28.000-55.000 kHz
[    10.048] (II) NVIDIA(GPU-0):   VertRefresh : 29.970-75.029 Hz
[    10.048] (II) NVIDIA(GPU-0):     (HorizSync from Conservative Defaults)
[    10.048] (II) NVIDIA(GPU-0):     (VertRefresh from EDID)

The two monitors have slightly different EDIDs, my main concern would be why the one on the displayport only shows up w/ 340MHz pclk.
Can you swap them and does the mode restriction follow the monitor to the output (ie. is the same monitor the problem regardless whether you attach it via HDMI or DP or is it always the DP-attached one that has a too small resolution)?

br1ck · 2025-08-22 17:08:34

It is the same monitor that has the issue.

Xorg log: https://termbin.com/hjgb

Also, several of my applications don't start correctly while on the new version. journalctl only has this when I start those applications:

Aug 22 10:06:20 yaopc xdg-desktop-portal-kde[1078]: xdp-kde-settings: Namespace  "org.gnome.desktop.interface"  is not supported

Could this also be related to the display issue?

seth · 2025-08-22 19:21:41

What "applications" and how "not correctly", but that's probably some gnome clients trying to use xdg-desktop-portal features privy to the gnome implementation.

It is the same monitor that has the issue.

Steal the EDID from the other output (you can straight up "cp /sys/class/drm/card*-whateveroutput/edid /usr/lib/firmware/bette_edid.bin" and apply https://wiki.archlinux.org/title/Kernel … s_and_EDID (edid-decode will tell you whether it's the good one)
Does the output start to behave?

Edit: the edid of the monitor from 2020, http://0x0.st/KiWy.bin

Last edited by seth (2025-08-22 19:26:49)

Arch Linux

#1 2025-08-16 21:57:23

Graphics related bug after new update(s)?

#2 2025-08-17 13:28:50

Re: Graphics related bug after new update(s)?

#3 2025-08-17 17:45:12

Re: Graphics related bug after new update(s)?

#4 2025-08-17 20:19:40

Re: Graphics related bug after new update(s)?

#5 2025-08-18 05:19:18

Re: Graphics related bug after new update(s)?

#6 2025-08-18 08:18:52

Re: Graphics related bug after new update(s)?

#7 2025-08-20 07:43:12

Re: Graphics related bug after new update(s)?

#8 2025-08-20 14:06:15

Re: Graphics related bug after new update(s)?

#9 2025-08-22 17:08:34

Re: Graphics related bug after new update(s)?

#10 2025-08-22 19:21:41

Re: Graphics related bug after new update(s)?

Board footer