From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208947] New: amdgpu DisplayPort won't recognize all display modes after 5.9 merges
Date: Mon, 17 Aug 2020 21:02:51 +0000 [thread overview]
Message-ID: <bug-208947-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=208947
Bug ID: 208947
Summary: amdgpu DisplayPort won't recognize all display modes
after 5.9 merges
Product: Drivers
Version: 2.5
Kernel Version: 5.9 staging-testing, rc1, and latest linux.git
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: ckane@colemankane.org
Regression: No
I've got an AMD Ryzen 7 1700 and a POLARIS10 Radeon RX 580M GPU in an ASUS ROG
GL702ZC laptop.
I'm using the regular 5.8.1 kernel on Arch linux, and also have been tracking
in-development kernel changes via the "staging-testing" branch on the
gregkh/staging.git Linux tree as well as the torvalds/linux.git tree.
Sometime during the course of the 5.9 updates getting merged into those trees,
the 5.9 kernels I build no longer recognize all of the graphics modes for my 4K
(3840x2160) monitor when it is plugged into the DisplayPort. Instead, the
highest mode reported available is 1024x768, and Xorg also gets limited to
these choices.
This behavior appears limited to the monitor being plugged in via its
DisplayPort input. When I use an HDMI input, all of the supported graphics
modes are reported properly. I am using /sys/class/drm/card0-DP-1/modes to
display the available modes, and also starting Xorg to test it as well.
Would be happy to test patches if this is a known regression, or would
appreciate some help/direction in tracking down potential likely culprits of
the problem so I can try to diagnose it myself. I am somewhat familiar with
kernel development, so I'm capable of hacking on it a bit if anyone can point
me in a good direction. I'm just not too familiar with the inner workings of
the AMDGPU, KMS, or DRM code. Not even certain if this is an issue specific to
AMDGPU or something agnostic to the specific video hw.
I also tried dumping the /sys/class/drm/card0-DP-1/edid after booting into
5.8.1 and then 5.9-latest and I get exactly the same data for both, so it seems
like the EDID data is at least being fetched properly. I also tried saving that
EDID data to a *.bin file and manually loading that via kernel arguments
(drm.edid_firmware): verified it was loading properly for DP-1, but I still got
the same results (no high-resolution video modes).
Let me know what data would be helpful to attach to this issue, as well.
Thanks,
Coleman Kane
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-08-17 21:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 21:02 bugzilla-daemon [this message]
2020-08-18 0:19 ` [Bug 208947] amdgpu DisplayPort won't recognize all display modes after 5.9 merges bugzilla-daemon
2020-08-18 13:28 ` bugzilla-daemon
2020-08-18 18:22 ` bugzilla-daemon
2020-08-18 18:24 ` bugzilla-daemon
2020-08-18 18:27 ` bugzilla-daemon
2020-08-18 18:29 ` bugzilla-daemon
2020-08-18 18:30 ` bugzilla-daemon
2020-08-18 23:30 ` bugzilla-daemon
2020-08-19 22:22 ` bugzilla-daemon
2020-08-19 22:53 ` bugzilla-daemon
2020-08-20 3:20 ` bugzilla-daemon
2020-08-20 5:01 ` bugzilla-daemon
2020-08-20 23:22 ` bugzilla-daemon
2020-08-20 23:31 ` bugzilla-daemon
2020-08-21 2:18 ` bugzilla-daemon
2020-08-21 2:51 ` bugzilla-daemon
2020-08-21 19:52 ` bugzilla-daemon
2020-08-22 22:52 ` bugzilla-daemon
2021-01-02 3:22 ` bugzilla-daemon
2021-01-03 8:59 ` bugzilla-daemon
2021-01-03 9:05 ` bugzilla-daemon
2021-01-10 22:59 ` 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-208947-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.