Bug 54471 - one of three monitors will not light up post-kms on radeon 5770
Summary: one of three monitors will not light up post-kms on radeon 5770
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-04 00:43 UTC by Gabriel Somlo
Modified: 2019-11-19 07:36 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg output (208.06 KB, text/plain)
2012-09-04 00:43 UTC, Gabriel Somlo
no flags Details
xorg log (59.86 KB, text/plain)
2012-09-04 00:43 UTC, Gabriel Somlo
no flags Details

Description Gabriel Somlo 2012-09-04 00:43:12 UTC
Created attachment 66584 [details]
dmesg output

I have the MacPro5,1 version of Radeon 5770 (see http://www.amazon.com/gp/product/B003Z6QH6M), and have three Dell U2412M monitors connected to it (two via miniDP-to-DP cables, the third one using the DVI cable included with the monitor).

X11 sees all three monitors (DisplayPort-0, DisplayPort-1, and DVI-0), but immediately after KMS during boot, DisplayPort-1 goes into powersave and cannot be "woken up". DisplayPort1 is the first screen that "lights up" when the machine is powered on. Once grub kicks in, both DisplayPort-0 and DisplayPort-1 are mirrored, with DVI-0 being off. After KMS, DVI-0 lights up, and DisplayPort-1 goes to sleep.

Tinkering with the Gnome display settings and/or xrandr will sometimes wake up DisplayPort-1, but always at the expense of turning off either DisplayPort-0 or DVI-0 instead. I could never get all three of them to light up under Linux.

I'm using up-to-date stock F16 (3.4.9-2.fc16.x86_64), but have also tried 3.6-rc4 with the same results.

I'm attaching my dmesg output and Xorg.0.log.
Comment 1 Gabriel Somlo 2012-09-04 00:43:36 UTC
Created attachment 66585 [details]
xorg log
Comment 2 Alex Deucher 2012-09-04 01:05:14 UTC
Please try the latest 3.6.0 kernels or my 3.6 fixes tree:
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-fixes-3.6
There are a number of modesetting fixes that may help.
Comment 4 Gabriel Somlo 2012-09-04 17:43:16 UTC
(In reply to comment #3)
> You might also try this patch:
> http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-3.7-wip&id=c1857e07e8abac2c19fda9b1da96ac461ec55827

This (on top of 3.6-rc4, which already contains everything you point to in comment #2, and which I had already tried before opening this) fixes the problem and lights up all three of my monitors --Thanks !
Comment 5 Florian Mickler 2012-10-15 20:45:05 UTC
A patch referencing this bug report has been merged in Linux v3.7-rc1:

commit f3dd8508d459a2d0d0bc426144b92f1696d4fe86
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Fri Aug 31 11:56:50 2012 -0400

    drm/radeon: rework pll selection (v4)
Comment 6 Florian Mickler 2012-10-15 20:50:44 UTC
A patch referencing this bug report has been merged in Linux v3.6-rc6:

commit 985f61f7ee647ad570c05eab0b74915da2ac8e19
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Fri Aug 31 11:56:50 2012 -0400

    drm/radeon: rework pll selection (v3)
Comment 7 Florian Mickler 2012-10-15 21:18:34 UTC
A patch referencing a commit referencing this bug report has been merged in Linux v3.6-rc7:

commit 2f1f4d9b60396d2df4cff829bd5376ffc8ed9a2c
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Mon Sep 17 17:26:24 2012 -0400

    Revert "drm/radeon: rework pll selection (v3)"
Comment 8 Martin Peres 2019-11-19 07:36:00 UTC
-- 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/xorg/driver/xf86-video-ati/issues/39.


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.