Problems with laptop after switching to Discrete Graphics RNING: GPU:0: CMN (DP-2): G-SYNC Compatible: EDID min refresh rate invalid

Hello Everybody,

Due to experiencing issues with Hybrid Graphics mode, I’ve recently re-configured my laptop in Discrete Graphics mode (Lenovo ThinkPad P52), but this is giving me other issues.

I’m receiving the following error message in dmesg (this message appears 6 - 7 times):
nvidia-modeset: WARNING: GPU:0: CMN (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.

The thing is that my laptop has no minimal refresh rate (afaik) and the only supported resolution is 1920x1080@60. This causes my laptop to flicker several times, before starting an X.org session. After entering my password it will flicker back and forth between the console and the graphical interface too.

Is there any way to resolve the issue? Is there a way to disable G-Sync in GRUB_CMDLINE_LINUX?

Kernel: 5.15.59-gentoo
Driver: 515.65.01
Other: nvidia-drm.modeset=1 is set in the GRUB_CMDLINE_LINUX

Those messages are quite common and usually don’t have bad consequences so might be a red herring. Please run nvidia-bug-report.sh as root and attach the resulting nvidia-bug-report.log.gz file to your post.

nvidia-bug-report.log.gz (389.9 KB)

Well, it reports this already on the CLI (before SDDM starts) and I had to force a DPI of 96 x 96 using:

Section “Device”
Identifier “LCD”
Driver “nvidia”
Option “DPI” “96 x 96”
EndSection

Otherwise the KDE taskbar took almost 1/4th of my screen, so I think there’s definitely something off. Applications like Microsoft Teams still have this issue that everything is extremely big (it seems they’re not obeying the DPI settings). That next to the flickering xorg-x11 happening 3 - 4 times before SDDM starts and 3 - 4 times while logging in.

The messages about gsync are only a symptom, the monitors get redetected due to xrandr events. On Xserver start, there are 3 different modes/monitor arrangements set shortly after another. Do you have anything added in some xinitrc/xsession script?

[  7127.974] (II) NVIDIA(0): Setting mode "DP-2: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-0.2: nvidia-auto-select @1920x1200 +3840+0 {ViewPortIn=1920x1200, ViewPortOut=1920x1200+0+0}, DP-0.3: nvidia-auto-select @1920x1200 +3840+0 {ViewPortIn=1920x1200, ViewPortOut=1920x1200+0+0}"
[  7129.641] (II) NVIDIA(0): Setting mode "DP-2: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-0.2: nvidia-auto-select @1920x1200 +3840+0 {ViewPortIn=1920x1200, ViewPortOut=1920x1200+0+0}, DP-0.3: nvidia-auto-select @1920x1200 +1920+0 {ViewPortIn=1920x1200, ViewPortOut=1920x1200+0+0}"
[  7131.167] (II) NVIDIA(0): Setting mode "DP-2: nvidia-auto-select @1920x1080 +0+60 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-0.2: nvidia-auto-select @1920x1200 +3840+0 {ViewPortIn=1920x1200, ViewPortOut=1920x1200+0+0}, DP-0.3: nvidia-auto-select @1920x1200 +1920+0 {ViewPortIn=1920x1200, ViewPortOut=1920x1200+0+0}"

nvidia-bug-report.log.gz (257.2 KB)

No I do not have any xinitrc or xsession script, other than the provided configuration. This could occur however, because my Thunderbolt dock with 2 external screens was connected. I ran the tool again. This time without the dock attached (where the system is still displaying the symtoms

Really all xrandr events came from the dock. The logs are clean now so nothing that explains the flicker and redetection of the panel…