All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111876] AMD 5700 XT / Navi - BenQ XL2420G - No EDID read with DP connector, HDMI works fine
Date: Tue, 01 Oct 2019 14:11:22 +0000	[thread overview]
Message-ID: <bug-111876-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 111876
           Summary: AMD 5700 XT / Navi - BenQ XL2420G - No EDID read with
                    DP connector, HDMI works fine
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: not set
          Priority: not set
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: christopherjordan87@gmail.com

Created attachment 145598
  --> https://bugs.freedesktop.org/attachment.cgi?id=145598&action=edit
dmesg output when using DP

I recently built a new machine (specs below), but I'm having trouble using the
display port connector with my old monitor (BenQ XL2420G) - I get the following
EDID error:

[drm:dc_link_detect [amdgpu]] *ERROR* No EDID read.

Following instructions to manually use an EDID appears to do nothing
(https://wiki.archlinux.org/index.php/kernel_mode_setting). I generated an EDID
with the "read-edid" package after modprobe-ing i2c-dev and HDMI connected, as
well as my old machine's nvidia card via "acquire EDID" in nvidia-settings.

I'm not sure how quirky other G-Sync or high-refresh-rate monitors are, but
this one *only* allows a 144 Hz refresh rate with display port. However, using
HDMI, everything appears to be fine. My Windows partition in the same machine
appears quite happy to use DP at 144 Hz, so I'm particularly baffled as to why
linux is struggling. After scouring the internet, it appears no one else has
the same issue, so it is possible that this monitor is simply not playing
nicely.

I have supplied my lspci output, as well as dmesg outputs with "drm.debug=0x1e
log_buf_len=4M" for both DP and HDMI connected. I am running up-to-date
archlinux, using linux-firmware from the testing repo (which should just be
neatly providing the navi firmware in a non-AUR package) and a bunch of
packages from the mesa-git repo. My pacman -Q is also attached.

Any help would be greatly appreciated! Many thanks in advance.

ASUS TUF Gaming X570-PLUS WiFi
AMD Ryzen 3900X
Powercolor Red Devil 5700 XT

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

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

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

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

             reply	other threads:[~2019-10-01 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 14:11 bugzilla-daemon [this message]
2019-10-01 14:12 ` [Bug 111876] AMD 5700 XT / Navi - BenQ XL2420G - No EDID read with DP connector, HDMI works fine bugzilla-daemon
2019-10-01 14:12 ` bugzilla-daemon
2019-10-01 14:13 ` bugzilla-daemon
2019-10-01 14:29 ` bugzilla-daemon
2019-11-19  9:56 ` 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-111876-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.