dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94315] AMDGPU 290X Refresh rate issue at 144Hz
Date: Fri, 26 Feb 2016 22:50:31 +0000	[thread overview]
Message-ID: <bug-94315-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2082 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=94315

            Bug ID: 94315
           Summary: AMDGPU 290X Refresh rate issue at 144Hz
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: dherault@hotmail.com

Created attachment 121993
  --> https://bugs.freedesktop.org/attachment.cgi?id=121993&action=edit
xrandr + OSD 139Hz

Hello,

I have Arch linux with an asus MG279Q (27 "144Hz) connected in DisplayPort 1.2.
Everything worked with Sapphire 7950 and also R9 Fury. 
Unfortunately I have trouble with my Sapphire 290x. I've tested three 290X to
be sure it's not an hardware issue. 
Of course freesync is off.
I just tested the combo with multiple users 290 (X and not X) + MG279Q.
Sometimes on livecd. Everyone have the issue.

I can't have a real 144Hz with the amdgpu or radeon driver. Everything work
only @60Hz or with FGLRX driver.
At 144Hz , i have a bad 139Hz with artifacts :
http://reho.st/self/b98c1c955cb7d42c3af6f82ea71bbc94be8aee6a.jpg

Glitches on the left. Blur on all screen, Text glitches...

What i've tried :
- Windows 10 : All works !
- FGLRX : All works @144Hz. But other problems make it difficult to use: in
firefox lag among others ... And I love the free driver! Finally ... When he
worked with my 7950
- Kernel mainline : Same issue .
- New mode line with cvt 2560 1440 144 and xrandr --newmode : Same issue.
- Contact Sapphire and upload to a new vbios : Same issue and as long as it
works on windows it's not their problem...

It can be an incompatibility between the MG279Q and the 290X on linux. But
something in FGLRX make my 290X works, but not present on AMDGPU/Radeon driver.

I just tested the combo with multiple users 290 (X and not X) + MG279Q.
Sometimes on livecd. Everyone have the issue.

Thanks for your help

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3522 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

             reply	other threads:[~2016-02-26 22:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 22:50 bugzilla-daemon [this message]
2016-02-26 22:51 ` [Bug 94315] AMDGPU 290X Refresh rate issue at 144Hz bugzilla-daemon
2016-02-26 22:51 ` bugzilla-daemon
2016-02-26 22:51 ` bugzilla-daemon
2016-02-26 22:51 ` bugzilla-daemon
2016-02-26 22:52 ` bugzilla-daemon
2016-02-26 22:54 ` bugzilla-daemon
2016-02-27 14:05 ` 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-94315-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).