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: Thu, 09 Nov 2017 20:36:20 +0000	[thread overview]
Message-ID: <bug-99801-502-3WIPYcVpMa@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99801-502@http.bugs.freedesktop.org/>


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

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

--- Comment #18 from Harry Wentland <harry.wentland@amd.com> ---
Can you retest this on either one of the following trees?

Alex's amd-staging-drm-next tree
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next

Dave's drm-next-amd-dc-staging
https://cgit.freedesktop.org/~airlied/linux/log/drivers/gpu/drm/amd/amdgpu?h=drm-next-amd-dc-staging

We believe this issue has been fixed but had trouble identifying the fix. We
only had a Dell 5k display to test with. There's a chance this is monitor
specific.

Please build with CONFIG_DRM_AMD_DC_PRE_VEGA or pass the amdgpu.dc=1 module
option and ensure dc is loaded by checking 'dmesg | grep Display'. You should
get the following:

[drm] Display Core initialized!

If the issue still reproduces we might have to give this another try or see if
we can find that HP z27q panel.

Thanks for your help on this.

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

[-- Attachment #1.2: Type: text/html, Size: 2071 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:[~2017-11-09 20: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 [this message]
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
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-3WIPYcVpMa@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