I'm getting a screen corruption with the resolutions 1400x1050 1440x900 on a RV350, using kernel-3.0.4, libdrm-2.4.26. A photograph of the corrupted screen under X is attached, though the corruption also appears using tests/modetest w/o X started. -------- # lspci -nns1:0.0 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M10 NT [FireGL Mobility T2] [1002:4e54] (rev 80) --------
Created attachment 51894 [details] Corrupted screen
Created attachment 51895 [details] dmesg output of a modetest run with 1400x1050 resolution and drm.debug=15
The issue is also present in the latest git kernel from today, 3.1.0-rc8+, commit 9b13776977d45505469edc6decc93e9e3799afe2
Created attachment 51898 [details] complete dmesg for 3.1.0-rc8+
Can you attach the output of xrandr --verbose? Note that Full aspect scaling is not implemented for pre-avivo asics, so make sure you are not using that. Center and Full do work however.
Created attachment 52020 [details] xrandr --verbose with several 'scaling mode' properties Appearently the scaling mode property was set to "Full" by default. There is no difference in the visible image between "Full" and "Full aspect" scaling mode, "Center" does enable the backlight but the screen stays black, "None" shows the FB at coords (0,0) and a cloned portion of it below separated by a black horizontal bar as the native display resolution of 1600x1200 is used (so I'd say that one works). I've attached xrandr --verbose outputs for "Full", "None" and the non-working "Center" scaling modes using 1400x1050 resolution. If those outputs for 1440x900 would help, too, I'll upload them as well. Thank you for taking a look at this issue.
-- 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/215.
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.