low or high in /sys/class/drm/card0/device/power_dpm_force_performance_level
fixes it, I should've tried the arch's AMDGPU wiki page (although the wiki only mentions frequencies of 120+Hz, not mentioning 75Hz, which is also affected).
Thanks for the replies guys.
=> Please post a complete dmesg (covering the issue) and to be sure also your xorg log.
Also try the behavior w/
amdgpu.dc=0 amdgpu.audio=0 amdgpu.dpm=0 amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0
This deactivates the (new) display core driver, audio and various powermanagent - in case this "fixes" it, try to isolate the relevant parameter.
https://wiki.archlinux.org/index.php/Ke … le_options
Also please elaborate on the nature of the flicker (or try to catch it on video, if you can)
]]>Do you absolutely need the 75Hz refresh rate?
I don't absolutely need the 75Hz refresh rate, same way I don't absolutely need KDE, archlinux, or possibly a computer, but I got and use them because I want to.
Thing is I bought this monitor because it could go to 75Hz and it had FreeSync, and I find it glitches on 75Hz so I'd really want to get it to work somehow.
]]>kscreen just gives the options for: 60, 59.94, 50, 74.97 at 1080p.
Using the command to change refresh to 68 triggers it (or choosing 74.97 in kscreen).
'xrandr -q --verbose' shows it being switched to:
1920x1080 (0x59) 174.500MHz +HSync -VSync *current
Since this is a problem that's related to the 75 Hz (74.97) refresh-rate, and not resolutions themselves should I change the subject of this topic?
]]>xrandr --output DisplayPort-0 --mode 1920x1080 --rate 60
is as far as I can go.
xrandr --output DisplayPort-0 --mode 1920x1080 --rate 68
triggers it.
xrandr --output DisplayPort-0 --mode 1920x1080 --rate 54
fixes it, 55 doesn't but I can change to it.
(I can't change to 56,57,58,59.61.62.63,64,65,66,67, monitor doesn't react)
]]>I use KDE's KScreen, it has GUI. (shortcut is 'kcmshell5 kcm_kscreen')
It installed when I installed the plasma group so I use it.
I tried 'xrandr --output DisplayPort-0 --mode 1920x1080 --rate 74' refresh did change to that, the bug was still triggered.
]]>You can btw. select the refresh rate, eg. try to
xrandr --output DisplayPort-0 --mode 1024x768 --rate 60.02
xrandr --output DisplayPort-0 --auto
xrandr --output DisplayPort-0 --mode 1024x768
xrandr --output DisplayPort-0 --mode 1920x1080 --rate 60
xrandr --output DisplayPort-0 --mode 1024x768
xrandr --output DisplayPort-0 --auto
(Do you so far use some GUI to change the resolutions?)
]]>I changed resolution to 1024x768, I don't need to change resolution but if I do it changes refresh rate to the highest one available. (75.03 Hz for 1024x768 is highest for me, so when I change resolution to it refresh changes to that and triggers the bug)
From there I can change resolutions all I want it won't fix it, only way is to change refresh-rate to 50.00 Hz, any other and it won't get fixed (afterwards I can change it to 60, or any other besides ones that start with 7, like 74.97 or it'll start again)
]]>Also, to what resolution do you attempt to change when this happens?
]]>I tried xrandr --props and used the method from before to compare the one where it flickers and where it doesn't and found only 1 difference (I only changed the refresh rate to 74.97 in kscreen, 'kcmshell5 kcm_kscreen'):
Flicker:
1920x1080 60.00 + 74.97* 50.00 59.94
Non-Flicker:
1920x1080 60.00*+ 74.97 50.00 59.94
That's the only difference between the 2.
I can post the whole thing if you want, is there a specific way to post logs here?
Edit:
I just realized that the star * moves to whatever refresh you change to, so that's normal, silly me.
Also I tried switching from DP to HDMI and that made no difference, so I switched back to DP.
]]>xrandr --props
?
You can suspend the compositor altogether (SHIFT+Alt+F12 to toggle) to see whether it's related at all.
[Compositing]
AnimationSpeed=2
Backend=OpenGL
Enabled=true
GLCore=true
GLPreferBufferSwap=a
GLTextureFilter=1
HiddenPreviews=5
OpenGLIsUnsafe=false
WindowsBlockCompositing=true
XRenderSmoothScale=false
That's it.
And adding RefreshRate there manually appears to not do anything.
Edit:
I used the qdbus org.kde.KWin /KWin supportInformation command like V1del recommended and compared them when it flickers and when it doesn't.
The information files in both situations are identical. (I used > to save the information in both situations, then used meld to compare)
]]>