From: Dave Jones <davej@codemonkey.org.uk>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: Radeon Verde displayport failure.
Date: Fri, 15 May 2015 08:44:59 -0400 [thread overview]
Message-ID: <20150515124459.GA30134@codemonkey.org.uk> (raw)
In-Reply-To: <5555B98B.9040705@daenzer.net>
On Fri, May 15, 2015 at 06:16:59PM +0900, Michel Dänzer wrote:
> On 15.05.2015 12:52, Dave Jones wrote:
> >
> > The only remaining problem is there are some visible glitches, mostly noticable
> > while scrolling a terminal.
>
> What kind of glitches? If it's tearing, with current xf86-video-ati Git
> you can try Option "TearFree".
Hard to describe, just sort of.. bursts of coloured sparkle noise in
random positions.
They don't remain part of the image permanently, and only appear for a
split second. They are pretty constant when scrolling though.
I'll see if I can get video of it when I'm in front of it again on Monday.
One other bug I noticed: Once it goes into DPMS, I can't wake it up again
and need to reboot. Likewise if I power off the monitor and back on,
it goes into power saving again.
Dave
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-05-15 12:45 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
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 [this message]
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=20150515124459.GA30134@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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.