From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201795] New: [Regression] Wrong 4k resolution detected with DisplayPort to HDMI adapter on amdgpu
Date: Tue, 27 Nov 2018 19:30:46 +0000 [thread overview]
Message-ID: <bug-201795-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=201795
Bug ID: 201795
Summary: [Regression] Wrong 4k resolution detected with
DisplayPort to HDMI adapter on amdgpu
Product: Drivers
Version: 2.5
Kernel Version: 4.19.4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: thomas.lassdiesonnerein@gmx.de
Regression: No
Created attachment 279677
--> https://bugzilla.kernel.org/attachment.cgi?id=279677&action=edit
xrandr output on kernel 4.14
I have a AMD Fury X GPU connected to two 4k monitors.
- one 4k iiyama monitor @DP 1.4
- one 4k LG OLED TV @DP 1.4 to HDMI 2.0 Adapter
both have physical 3840x2160 pixels.
On Kernel 4.14 (Manjaro) I can mirror the screen fine.
Newer Kernels I tested (4.17 to 4.19) mirror too, but on the LG OLED TV with
4096x2160 instead of 3840x2160. The latter res then is not stretched correctly.
I have small black bars left and right as if the driver thinks I would have
4096x2160 physically.If I set 4096x2160 in plasma5 it stretches fine, but then
I have different resolutions on boths screens which is problematic while
mirroring.
--
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:[~2018-11-27 19:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 19:30 bugzilla-daemon [this message]
2018-11-27 19:35 ` [Bug 201795] [Regression] Wrong 4k resolution detected with DisplayPort to HDMI adapter on amdgpu bugzilla-daemon
2018-11-27 19:38 ` bugzilla-daemon
2018-11-27 19:39 ` bugzilla-daemon
2018-11-28 9:24 ` bugzilla-daemon
2018-11-28 19:23 ` bugzilla-daemon
2018-11-28 19:23 ` bugzilla-daemon
2018-11-28 19:24 ` bugzilla-daemon
2018-11-28 19:24 ` bugzilla-daemon
2018-11-29 8:39 ` bugzilla-daemon
2018-11-29 10:04 ` bugzilla-daemon
2018-12-15 7:12 ` bugzilla-daemon
2018-12-15 7:12 ` bugzilla-daemon
2018-12-15 16:53 ` bugzilla-daemon
2019-01-18 19:00 ` bugzilla-daemon
2019-01-23 11:19 ` bugzilla-daemon
2019-02-21 8:40 ` bugzilla-daemon
2019-03-13 11:00 ` bugzilla-daemon
2019-03-13 13:07 ` bugzilla-daemon
2019-03-13 19:13 ` bugzilla-daemon
2019-03-13 20:02 ` bugzilla-daemon
2019-03-15 7:54 ` bugzilla-daemon
2019-03-15 13:07 ` bugzilla-daemon
2019-03-15 13:43 ` bugzilla-daemon
2019-03-18 13:45 ` 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-201795-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.