https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c2 --- Comment #2 from Holger Sickenberg --- Created attachment 867946 --> https://bugzilla.suse.com/attachment.cgi?id=867946&action=edit xrandr-samsung.txt -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c4 --- Comment #4 from Holger Sickenberg --- Created attachment 867948 --> https://bugzilla.suse.com/attachment.cgi?id=867948&action=edit xrandr-verbose-samsung.txt -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c6 --- Comment #6 from Holger Sickenberg --- Created attachment 867950 --> https://bugzilla.suse.com/attachment.cgi?id=867950&action=edit xrandr-philips.txt -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c8 Holger Sickenberg changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com Priority|P5 - None |P3 - Medium Hardware|Other |x86-64 Found By|--- |Development --- Comment #8 from Holger Sickenberg --- Adding a modline created with

cvt -r 1920 1080 with: xrandr --newmode "1920x1080R" 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync xrandr --addmode DP-3 "1920x1080R" xrandr --output DP-3 --mode 1920x1080R

will result in having monitor displaying the correct resolution -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c10 --- Comment #10 from Stefan Dirsch --- Looks like it uses some weird DoubleScan mode here ... maybe that's a feature of latest driver(s) on Leap 15.5 kernels. 1920x1080 60.01* 59.97 59.96 60.00 50.00 59.94 59.93 1920x1080 (0x4b) 356.375MHz -HSync +VSync DoubleScan h: width 1920 start 2080 end 2288 total 2656 skew 0 clock 134.18KHz v: height 1080 start 1081 end 1084 total 1118 clock 60.01Hz 1920x1080 (0x4c) 266.500MHz +HSync -VSync DoubleScan h: width 1920 start 1944 end 1960 total 2000 skew 0 clock 133.25KHz v: height 1080 start 1081 end 1084 total 1111 clock 59.97Hz 1920x1080 (0x4d) 173.000MHz -HSync +VSync h: width 1920 start 2048 end 2248 total 2576 skew 0 clock 67.16KHz v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz 1920x1080 (0xc1) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0xc2) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0xc3) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1920x1080 (0x4e) 138.500MHz +HSync -VSync *current h: width 1920 start 1968 end 2000 total 2080 skew 0 clock 66.59KHz v: height 1080 start 1083 end 1088 total 1111 clock 59.93Hz -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c12 --- Comment #12 from Holger Sickenberg --- Created attachment 867952 --> https://bugzilla.suse.com/attachment.cgi?id=867952&action=edit IMG_20230703_180130037.jpg Same behavior as with regular 15.5 kernel - see photo -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c14 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |holgi@suse.com Flags| |needinfo?(holgi@suse.com) --- Comment #14 from Takashi Iwai --- BTW, does this happen with Wayland, too? I stumbled on the existing report: https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/68 and it says it's X who adds DoubleScan modes. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c16 --- Comment #16 from Stefan Dirsch --- If Holger really uses the amdgpu X driver and removing xf86-video-amdgpu packages fixes the issue, it's indeed the amdgpu driver. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c18 --- Comment #18 from Takashi Iwai --- Also, I built a test kernel with a hackish patch to limit the doublescan for HDMI. Could you try the kernel in OBS home:tiwai:bsc1212954 repo? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c19 Holger Sickenberg changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(holgi@suse.com) | --- Comment #19 from Holger Sickenberg --- Created attachment 868854 --> https://bugzilla.suse.com/attachment.cgi?id=868854&action=edit dmesg-5.14.21-150500.1.g08214d9-default.txt Unfortunately, still same behavior with your test kernel -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c21 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(holgi@suse.com) Status|NEW |IN_PROGRESS --- Comment #21 from Stefan Dirsch --- (In reply to Stefan Dirsch from comment #15)

Ok. But that would mean that Holger runs amdgpu X driver. Holger, have you installed xf86-video-amdgpu package. Could you attach your X logfile, please?

Could you still check this, please? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c23 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(holgi@suse.com) --- Comment #23 from Stefan Dirsch --- Ok. So obviously it's not the amdgpu X driver. So either Xserver itself or amdgpu kernel driver. If it doesn't happen with Wayland we can safely assume it's the Xserver. Can you try this, Holger. Easiest would be to install gdm+GNOME and try with a GNOME session. Check what you're runnng with ... # echo $XDG_SESSION_TYPE x11 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c25 --- Comment #25 from Stefan Dirsch --- Any news on that one? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1212954 https://bugzilla.suse.com/show_bug.cgi?id=1212954#c27 --- Comment #27 from Stefan Dirsch --- (In reply to Holger Sickenberg from comment #26)

Unfortunately enabling of Wayland did not work as expected, even using gdm.

Yes, we don't know why. gdm/Gnome for some reasons the hardware isn't capable of handling a Wayland desktop. -- You are receiving this mail because: You are on the CC list for the bug.