Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A amd
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,282
    • Issues 1,282
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • drm
  • amd
  • Issues
  • #672

Closed
Open
Created Jan 14, 2019 by Bugzilla Migration User@bugzilla-migration

Flickering and artifacts on dual 4K displays from RX 570

Submitted by Timur Kristóf

Assigned to Default DRI bug account

Link to original bug (#109359)

Description

There are two Dell U2718Q 4K monitors connected to a Sapphire Pulse RX 570 ITX card, one using the DisplayPort output and the other using the HDMI output.

There is a visible flickering artifact on both displays. There is no problem when only a single display is connected.

Searching online yields a couple of results that suggest a workaround: manually increasing the shader and/or memory clock of the GPU. On the RX 570 the following commands can get rid of the problem:

echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level
echo "2" > /sys/class/drm/card0/device/pp_dpm_mclk
echo "5 6 7" > /sys/class/drm/card0/device/pp_dpm_sclk

However, I believe the amdgpu driver should be able to figure out the correct necessary clock settings on its own. The problem exists in Linux 4.19 and 5.0-rc1 as well.

Assignee
Assign to
Time tracking