[Applied][Quantal][SRU][PATCH 0/1] radeon/kms: force rn50 chip to always report connected on analog output

[Leann Ogasawara]

Applied to Quantal master-next.

Thanks,
Leann

On 01/22/2013 08:47 PM, leann.ogasawara at canonical.com wrote:
> From: Leann Ogasawara <leann.ogasawara at canonical.com>
>
> == Quantal SRU Justification ==
> A regression was discovered while testing HP SL4545 G7 systems with the
> recent 3.5.0-22.34 Quantal kernel.  The regression results in a failure
> to display a login screen/prompt upon booting.  Booting into a previous
> 3.5.0-17.28 Quantal kernel confirms the issue does not exit.  This issue
> was bisected and it was determined the following commit introduced the
> regression:
>
> commit 83325d072185899b706de2956170b246585aaec9
> Author: Egbert Eich <eich at suse.de>
> Date: Wed Oct 24 18:29:49 2012 +0200
>
>     DRM/Radeon: Fix Load Detection on legacy primary DAC.
>
> == Fix ==
> After additional testing, it was then confirmed that the following
> upstream commit (which has also been CC'd to stable) resolves the issue:
>
> commit 51861d4eebc2ddc25c77084343d060fa79f6e291
> Author: Jerome Glisse <jglisse at redhat.com>
> Date: Tue Jan 8 18:41:01 2013 -0500
>
>     radeon/kms: force rn50 chip to always report connected on analog output
>
> I would like to propose we pick up this fix as a pre-stable update and
> respin Quantal so that this fix can land in the upcoming 12.04.2 point
> release.
>
> Herton, I assume you'll pick this up through your normal 3.5.y.z
> process as it was CC'd to stable in the original upstream commit.
>
> == Test Case ==
> Boot eg. the 3.5.0-22.34 Quantal kernel on an HP SL4545 G7 system and
> confirm the login screen/prompt is *not* displayed and ssh'ing into the
> system one can see the following message in dmesg output:
>
> [ 5.848056] No connectors reported connected with modes
> [ 5.848059] [drm] Cannot find any crtc or sizes - going 1024x768
>
> Boot a kernel with commit 51861d4e applied on an HP SL4545 G7 system and
> confirm the login screen/prompt is displayed and the above message is
> not seen in dmesg output.
>