Created attachment 126733 [details] dmesg output with drm.debug=0x1e log_buf_len=1M Hi, I have two monitors connected to my PC one via DVI and one via DP. The monitor connected via DP shows "frequency out of range" when some modes including the preferred one are used. This happens in X and in the KMS framebuffer. For example on the attached logs the preferred mode of 1680x1050 does not work where as 1680x945 works perfectly fine. Kernel: 4.4.11 Xorg: 1.18.2 xf86-video-radeon: 7.7.0 Last working kernel: 3.19 First broken kernel: 4.0 Here is the bisect info, the 4.0 release segfaulted in the radeon driver but the change which broke this was before so I hope the bisect is right: # first bad commit: [e55bca26188e45f209597abf986c87cc5a49894a] radeon/audio: enable DP audio After finding the bad commit I tried booting with radeon.audio=0 this made the display work for 3.19 kernel with that commit but did not work for the 4.4.11 kernel. Attached log files: - dmesg output with drm.debug=0x1e log_buf_len=1M - lspci -vv output - video card bios - Xorg.0.log - xrander --verbose output
Created attachment 126734 [details] lspci -vv
Created attachment 126735 [details] video card bios rom
Created attachment 126736 [details] Xorg log
Created attachment 126737 [details] xrandr --verbose output
I have probably the same issue on 4.14.5. My setup works fine with Redmond OS. This thread helped me to find the workaround under Linux with radeon.audio=0. One additional information about the issue: The out of range error probably comes from a complete miscalculation of the pixel clock. Edid of the monitor is fine, but in the error case, every pixel clock, the radeon wants to setup, is completely off from the edid modes. I checked by comparing the pixel clocks reported by the monitor with the one radeon reports. I can test patches or post more debug info. Cheers.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/744.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.