https://bugs.freedesktop.org/show_bug.cgi?id=105300
Alex Deucher changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #15 from tempel.jul...@gmail.com ---
Issue still exists with current 4.21-wip kernel.
As a workaround, it's enough to force the highest VRAM clock state (Forcing
higher clocks on the GPU itself is not necessary.):
echo "manual" >
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #14 from tempel.jul...@gmail.com ---
73Hz + dynamic clocking work again with recent drm-next-4.19-wip build.
As a sidenote: On Windows (which is installed on the same system as a 2nd OS),
there has never been an issue with 75Hz
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #13 from tempel.jul...@gmail.com ---
Since a month back or so, also 73Hz now shows the artifacts. 72Hz is still
artifact free.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #12 from tempel.jul...@gmail.com ---
Created attachment 139000
--> https://bugs.freedesktop.org/attachment.cgi?id=139000=edit
2560x1440 72Hz edid
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #11 from tempel.jul...@gmail.com ---
One of the recent changes in drm-next-4.17-wip has also introduced this issue
for the old legacy DC.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #10 from tempel.jul...@gmail.com ---
I thought of something similar too. But I'm far away from 330Mhz pixel clock.
I'm just using LCD standard timings, which result in a pixel clock of
304.37MHz:
https://abload.de/img/75hzhgs1d.png
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #9 from Harry Wentland ---
Are you messing with TMDS_MAX_PIXEL_CLOCK as Andrew is doing in this ticket:
https://bugs.freedesktop.org/show_bug.cgi?id=105302 ?
With DC clock switching might happen more
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #8 from tempel.jul...@gmail.com ---
Video which shows the artifacts:
https://youtu.be/it3d6BjpZjU
(can also be quite worse when doing stuff)
It happens with every desktop environment with and without enabled OGL
compositor. In the
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #7 from tempel.jul...@gmail.com ---
Created attachment 137754
--> https://bugs.freedesktop.org/attachment.cgi?id=137754=edit
xrandr.log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #6 from tempel.jul...@gmail.com ---
Created attachment 137753
--> https://bugs.freedesktop.org/attachment.cgi?id=137753=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #5 from tempel.jul...@gmail.com ---
Created attachment 137752
--> https://bugs.freedesktop.org/attachment.cgi?id=137752=edit
dmesg.log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #4 from Harry Wentland ---
Please attach your dmesg, Xorg.0.log and xrandr output.
Are you modifying your monitor's EDIDs to support higher refresh rates?
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #3 from Harry Wentland ---
Good point. Do you mind posting a picture of what you're seeing? It often helps
clarify what sort of corruption is happening and helps us understand which part
of the pipeline is
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #2 from tempel.jul...@gmail.com ---
I think there are some differences:
The user there described that he would have the issue also with the legacy DC,
which is not the case for me. He also had issues with just 60Hz, which is
https://bugs.freedesktop.org/show_bug.cgi?id=105300
--- Comment #1 from Harry Wentland ---
I wonder if what you're seeing is related to this:
https://bugs.freedesktop.org/show_bug.cgi?id=102646#c22
It's a different ASIC but also does not reproduce when clocks are forced
https://bugs.freedesktop.org/show_bug.cgi?id=105300
Bug ID: 105300
Summary: amd-staging-drm-next-git 4.16 & RX 560 DL-DVI:
corruption with refreshrates >73Hz when DPM changing
VRAM clock
Product: DRI
Version:
17 matches
Mail list logo