dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99801] Rx480 doesn't output properly onto z27q at 5120x2880
Date: Sat, 31 Mar 2018 01:36:10 +0000	[thread overview]
Message-ID: <bug-99801-502-KAFMj5iLXT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99801-502@http.bugs.freedesktop.org/>


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

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

--- Comment #25 from Matthew Treinish <mtreinish@kortar.org> ---
(In reply to Jean-Yves Avenard from comment #21)
> Adding some likely unhelpful info.
> But I've had similar (though not the same) problem since I got this screen.
> However, unlike most comments, I do not get two steady, mis-aligned image on
> each half of the screen.
> 
> The effect is an enormous flickering, mostly on the left half, with colour
> cycling. The screen internal menu can no longer be displayed.
> 
> Any long exposure to that mode would cause seizure to any healthy person.
> 
> The only work around to get out of that mode is to disable one of the screen
> and set the remaining half to 2560x1440 resolution only. 
> 
> Typically, after entering this corrupted mode, the screen will flicker
> continuously sometimes for hours. One day, I even thought I broke the screen
> as it was still flickering one day later and got HP to replace it.
> The new model did that same thing (actually all 4 HPz27q I got, as it took a
> while to get one without stuck pixels)
> 
> I get the same effect with both a mac pro 2013 (dual AMD D500 aka AMD 7800)
> or with a PC with an AMD Vega 64.
> 
> I'll take a picture of what it looks like and upload.

FWIW, this description is more or less exactly what I'm experiencing on my
display as well. (although I never tried the screen internal menu piece) I
probably just didn't do a good job taking a picture and/or describing it.

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

[-- Attachment #1.2: Type: text/html, Size: 2556 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

  parent reply	other threads:[~2018-03-31  1:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-99801-502@http.bugs.freedesktop.org/>
2017-02-14  6:09 ` [Bug 99801] Rx480 doesn't output properly onto z27q at 5120x2880 bugzilla-daemon
2017-02-14 16:59 ` bugzilla-daemon
2017-07-06 15:26 ` bugzilla-daemon
2017-07-16 23:09 ` bugzilla-daemon
2017-10-16  2:25 ` bugzilla-daemon
2017-10-27 17:24 ` bugzilla-daemon
2017-10-27 19:07 ` bugzilla-daemon
2017-11-09 20:36 ` bugzilla-daemon
2017-11-14  0:20 ` bugzilla-daemon
2017-11-14  0:21 ` bugzilla-daemon
2018-03-21  9:35 ` bugzilla-daemon
2018-03-26  8:01 ` bugzilla-daemon
2018-03-26  8:13 ` bugzilla-daemon
2018-03-26  8:14 ` bugzilla-daemon
2018-03-26  8:16 ` bugzilla-daemon
2018-03-31  1:36 ` bugzilla-daemon [this message]
2019-11-19  8:14 ` 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-99801-502-KAFMj5iLXT@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