Comment # 5
on bug 97896
from Stefan Müller-Klieser
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.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel