[Bug 45968] New: [RADEON:KMS:RS780:HD3200] l 2560x1440 detected by monitor as 1280x1440, every second pixel missing
https://bugs.freedesktop.org/show_bug.cgi?id=45968
Bug #: 45968 Summary: [RADEON:KMS:RS780:HD3200] l 2560x1440 detected by monitor as 1280x1440, every second pixel missing Classification: Unclassified Product: DRI Version: unspecified Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: ranma+freedesktop@tdiedrich.de
My new monitors native resolution is 2560x1440 which requires dual-link. I'm using the DVI-Cable that came with the monitor. KMS/Xorg claims to have set the resolution to 2560x1440.
Debian/unstable Linux 3.3.0-rc3 (built from source) libdrm 2.4.31-0 (built from source) xserver-xorg 1:7.6+11 xserver-xorg-video-radeon 1:6.14.3-2 (tried building from source, had the same problem) Gigabyte GA-MA78GPM-DS2H
As a workaround, custom 2560x1440@30 and 2560x1440@24 modelines work, but seems very suboptimal...
https://bugs.freedesktop.org/show_bug.cgi?id=45968
--- Comment #3 from Tobias Diedrich ranma+freedesktop@tdiedrich.de 2012-02-13 08:13:07 UTC --- Created attachment 56975 --> https://bugs.freedesktop.org/attachment.cgi?id=56975 xrandr --verbose output
https://bugs.freedesktop.org/show_bug.cgi?id=45968
--- Comment #1 from Alex Deucher agd5f@yahoo.com 2012-02-13 05:27:57 PST --- Please attach your xorg log, dmesg output, and xrandr --verbose output.
https://bugs.freedesktop.org/show_bug.cgi?id=45968
--- Comment #2 from Tobias Diedrich ranma+freedesktop@tdiedrich.de 2012-02-13 08:12:35 PST --- Created attachment 56974 --> https://bugs.freedesktop.org/attachment.cgi?id=56974 Xorg log
https://bugs.freedesktop.org/show_bug.cgi?id=45968
--- Comment #4 from Tobias Diedrich ranma+freedesktop@tdiedrich.de 2012-02-13 08:16:57 PST --- Created attachment 56977 --> https://bugs.freedesktop.org/attachment.cgi?id=56977 dmesg output
https://bugs.freedesktop.org/show_bug.cgi?id=45968
--- Comment #5 from Tobias Diedrich ranma+freedesktop@tdiedrich.de 2012-02-13 08:18:44 PST --- Created attachment 56979 --> https://bugs.freedesktop.org/attachment.cgi?id=56979 video bios rom
https://bugs.freedesktop.org/show_bug.cgi?id=45968
--- Comment #6 from Alex Deucher agd5f@yahoo.com 2012-02-13 08:22:51 PST --- Does it work ok with a pre3.3 kernel (e.g., 3.2, 3.1, etc.)? If so, does reverting this commit fix the issue?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=...
https://bugs.freedesktop.org/show_bug.cgi?id=45968
--- Comment #7 from Tobias Diedrich ranma+freedesktop@tdiedrich.de 2012-02-13 08:27:05 PST --- (In reply to comment #6)
Does it work ok with a pre3.3 kernel (e.g., 3.2, 3.1, etc.)? If so, does reverting this commit fix the issue?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=...
It didn't work with 3.2.4, which is why tried 3.3-rc.
https://bugs.freedesktop.org/show_bug.cgi?id=45968
--- Comment #8 from Tobias Diedrich ranma+freedesktop@tdiedrich.de 2012-02-13 08:28:23 PST --- (In reply to comment #7)
(In reply to comment #6)
Does it work ok with a pre3.3 kernel (e.g., 3.2, 3.1, etc.)? If so, does reverting this commit fix the issue?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=...
It didn't work with 3.2.4, which is why tried 3.3-rc.
Looking at the mentioned patch I should actually retry HDMI, which with 3.2.4 only supported up to 1920xsomething
https://bugs.freedesktop.org/show_bug.cgi?id=45968
--- Comment #9 from Tobias Diedrich ranma+freedesktop@tdiedrich.de 2012-02-14 03:00:35 PST --- FWIW using HDMI on 3.3-rc I can go up to 2560x1440@48, but 2560x1440@60 is above the 340MHz pixelclock limit for one link.
I installed XP yesterday and found that it shows the same problem with dual-link not working properly, so this seems to be just a case of bad HW.
https://bugs.freedesktop.org/show_bug.cgi?id=45968
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NOTOURBUG
--- Comment #10 from Alex Deucher agd5f@yahoo.com 2012-02-14 06:01:56 PST --- Seems like the oem may not have wired up the DVI port correctly for duallink.
https://bugs.freedesktop.org/show_bug.cgi?id=45968
--- Comment #11 from Roland Scheidegger sroland@vmware.com 2012-02-14 10:04:35 PST --- (In reply to comment #9)
FWIW using HDMI on 3.3-rc I can go up to 2560x1440@48, but 2560x1440@60 is above the 340MHz pixelclock limit for one link.
I'm surprised this old hw supports 340Mhz pixelclock on hdmi, I thought only Tahiti could do that, and monitors wouldn't support it neither typically (though I know some hw tolerates overclocking tmds quite well). In any case 2560x1440@60Hz should be clearly below 340Mhz with reduced blanking (around 250Mhz).
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org