All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: "Koenig, Christian" <Christian.Koenig@amd.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: Radeon Verde displayport failure.
Date: Mon, 11 May 2015 14:40:28 -0400	[thread overview]
Message-ID: <20150511184028.GA1526@codemonkey.org.uk> (raw)
In-Reply-To: <20150508154055.GA2760@codemonkey.org.uk>

On Fri, May 08, 2015 at 11:40:55AM -0400, Dave Jones wrote:
 > On Fri, May 08, 2015 at 01:23:59PM +0000, Deucher, Alexander wrote:
 
 >  > > I just bought a new radeon (1002:682c), to pair with my shiny new displayport
 >  > > monitor.
 >  > > It shows a display during through the BIOS POST, and grub, but when the
 >  > > kernel
 >  > > starts up, it's a coin toss whether or not I get anything.
 >  > > Sometimes it just goes straight into power saving.
 >  > > 
 >  > > When I do get something on the console, it continues to boot and then X
 >  > > starts up and
 >  > > puts it into power saving too. Trying to flip back to tty1 doesn't light up the
 >  > > display again.
 >  > > 
 >  > > I'm running On debian stable, with copied-by-hand verde_* firmware files
 >  > > from the linux-firmware git tree.
 >  > > Here's a log from the 4.0-rc2 kernel.
 >  > > 
 >  > > Any other info I can provide ?
 >  > 
 >  > The link training with the monitor seems to fail periodically.  You may have to play with the timing in the link training sequence.  It looks like you also have some power management related issues.  Does booting with radeon.dpm=0 on the kernel command line in grub help?  Also does the monitor support audio?  You might also try radeon.audio=0.
 > 
 > Pretty much the same story with those options..
 > 
 > [    8.162285] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_enable_smc_cac failed
 > [    8.170753] [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed
 > [    8.170778] [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed
 > 
 > I did manage to get it to display something for a while. By disabling DP1.2 with the
 > LCDs OSD, but then it would only do a maximum of 1024x768. And after a reboot,
 > I saw the same messages above, and straight to power saving.

I tried tweaking the delays in drm_dp_link_train_clock_recovery_delay, without any noticable
difference.  Is there something else I can try to make it try harder before giving up?

	Dave

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-05-11 18:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 23:47 Radeon Verde displayport failure Dave Jones
2015-05-08 13:23 ` Deucher, Alexander
2015-05-08 15:40   ` Dave Jones
2015-05-11 18:40     ` Dave Jones [this message]
2015-05-11 19:59       ` Alex Deucher
2015-05-11 23:33         ` Dave Jones
2015-05-12 22:38         ` Dave Jones
2015-05-13  0:04         ` Dave Jones
2015-05-14 13:49           ` Alex Deucher
2015-05-14 15:09             ` Dave Jones
2015-05-15  3:52             ` Dave Jones
2015-05-15  9:16               ` Michel Dänzer
2015-05-15 12:44                 ` Dave Jones
2015-05-20 22:03               ` Alex Deucher

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=20150511184028.GA1526@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.