From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 87796] radeonsi 120Hz graphic glitches
Date: Sun, 28 Dec 2014 14:00:44 +0000 [thread overview]
Message-ID: <bug-87796-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1556 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=87796
Bug ID: 87796
Summary: radeonsi 120Hz graphic glitches
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: magolobel@yahoo.com.br
Created attachment 111427
--> https://bugs.freedesktop.org/attachment.cgi?id=111427&action=edit
video screenshot of the glitch
When I enable 120Hz refresh rate in the Radeon R9 290 card, with my Benq
XL2420T monitor, I get horizontal glitches in the image. That happens in KDE,
Unity, XFCE (all with or without compositing), and games. Without compositing,
the windows decorations in KDE show artifacts in 60 and 120Hz.
60Hz refresh rate works okay. Fglx proprietary driver works okay with 120Hz. I
also have a Radeon HD 6970 with the radeon OSS driver and it also works okay in
120Hz in my system.
Currently I am using Kubuntu 14.10, kernel 3.19RC1 and Mesa git from this PPA:
https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa
The card is a Sapphire Radeon R9 290 4GB Tri-X.
This bug is happening since I got this card, in September.
I cant get a direct screenshot nor taking photos (with a smartphone) of the
glitch happening, so I take a video of it with a phone and then take a
screenshot.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2996 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-12-28 14:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 14:00 bugzilla-daemon [this message]
2014-12-29 16:47 ` [Bug 87796] radeonsi 120Hz graphic glitches bugzilla-daemon
2015-01-07 7:44 ` bugzilla-daemon
2015-01-13 18:57 ` bugzilla-daemon
2015-01-13 19:12 ` bugzilla-daemon
2015-01-13 19:32 ` bugzilla-daemon
2015-01-13 20:40 ` bugzilla-daemon
2015-01-13 20:49 ` bugzilla-daemon
2015-01-13 20:49 ` bugzilla-daemon
2015-01-13 21:04 ` bugzilla-daemon
2015-01-13 21:15 ` bugzilla-daemon
2015-01-13 21:24 ` bugzilla-daemon
2015-01-13 21:44 ` bugzilla-daemon
2015-01-13 22:02 ` bugzilla-daemon
2015-01-14 2:15 ` bugzilla-daemon
2015-01-14 14:26 ` bugzilla-daemon
2015-01-14 16:38 ` bugzilla-daemon
2015-01-14 17:05 ` bugzilla-daemon
2015-01-15 0:08 ` bugzilla-daemon
2015-01-22 17:28 ` bugzilla-daemon
2015-02-18 14:06 ` bugzilla-daemon
2015-02-18 14:23 ` bugzilla-daemon
2015-02-18 14:24 ` bugzilla-daemon
2015-03-17 18:15 ` bugzilla-daemon
2015-03-18 14:07 ` bugzilla-daemon
2015-03-18 14:25 ` bugzilla-daemon
2015-03-18 14:55 ` bugzilla-daemon
2015-03-18 18:59 ` bugzilla-daemon
2015-03-18 21:08 ` bugzilla-daemon
2015-03-19 1:00 ` bugzilla-daemon
2015-04-12 15:20 ` bugzilla-daemon
2015-04-12 20:37 ` bugzilla-daemon
2015-04-12 21:41 ` bugzilla-daemon
2015-04-12 23:00 ` bugzilla-daemon
2019-11-19 9:00 ` bugzilla-daemon
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=bug-87796-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--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.