public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.15.0-rc2 radeon HD 7480D [Aruba] blank display
Date: Mon, 21 Apr 2014 22:05:02 +0100	[thread overview]
Message-ID: <20140421210502.GA27983@milliways> (raw)
In-Reply-To: <CADnq5_OhN7B2FG_tHSJq-FCnqVUz4Bwh1EDXwTqCtv0zrAiDKQ@mail.gmail.com>

On Mon, Apr 21, 2014 at 04:54:15PM -0400, Alex Deucher wrote:
> On Mon, Apr 21, 2014 at 4:32 PM, Ken Moffat <zarniwhoop@ntlworld.com> wrote:
> >  I've just built 3.15.0-rc2 on this box, and discovered that I get a
> > blank screen.  The boot appears to complete (it sends me information
> > from SMART which is from my last bootscript), and it responds to
> > MagicSysRQ to reboot.  I tried to login and run startx, but that
> > didn't seem to make any difference - possibly something went wrong,
> > it wasn't in my history when I booted a good kernel.
> >
> >  This machine uses a regular old VGA cable to connect it, the
> > following lines in dmesg make me think it has chosen the wrong
> > connector:
> 
> VGA is implemented as a DP to VGA bridge on APUs.
> 
> >
> > Apr 21 19:32:45 bluesbreaker kernel: [    1.273246]
> > [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed
> > Apr 21 19:32:45 bluesbreaker kernel: [    1.273247]
> > [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
> > Apr 21 19:32:45 bluesbreaker kernel: [    1.295116] Console:
> > switching to colour frame buffer device 85x34
> >
> >  On a boot with 3.14.0 and earlier I get a different console size -
> > Apr 21 20:42:44 bluesbreaker kernel: [    1.445992] Console:
> > switching to colour frame buffer device 133x54
> >
> >  My console font is 12x22, and my screen is 1600x1200 but it looks
> > as if 3.15-rc2 has fallen back to trying to use 1024x768.
> >
> >  I'm attaching what look like the relevant parts of the messages
> > from the system logs for 3.15-rc2 and 3.14.0.
> >
> >  Any ideas, please ?  This is an AMD A4-5300 APU and not the world's
> > fastest machine for bisecting :-(
> 
> I'd guess it's either the pll rework patches or the switch to the
> common dp helper code patches.  It would be helpful if you could
> bisect.
> 
> Alex

 OK, I guess I can do the builds on a faster machine.

ĸen
-- 
das eine Mal als Tragödie, dieses Mal als Farce

  reply	other threads:[~2014-04-21 21:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 20:32 3.15.0-rc2 radeon HD 7480D [Aruba] blank display Ken Moffat
2014-04-21 20:54 ` Alex Deucher
2014-04-21 21:05   ` Ken Moffat [this message]
     [not found] ` <5549363.XIKIYZeGzc@grover>
     [not found]   ` <20140422023106.GA1709@milliways>
2014-04-22  2:34     ` Ken Moffat
2014-04-22  5:54       ` Alex Deucher
2014-04-22 15:34         ` Ed Tomlinson
2014-04-29  0:04         ` Ken Moffat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140421210502.GA27983@milliways \
    --to=zarniwhoop@ntlworld.com \
    --cc=alexdeucher@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox