dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201795] [Regression] Wrong 4k resolution detected with DisplayPort to HDMI adapter on amdgpu
Date: Mon, 18 Mar 2019 13:45:51 +0000	[thread overview]
Message-ID: <bug-201795-2300-zU0lmWvGXV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201795-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=201795

--- Comment #22 from thomas.lassdiesonnerein@gmx.de ---
I investigated further and the culprit seems to be that kernel =4.14 ignores
what xrandr *wrongly* detects and sets the connected TV correctly to its native
3840x2160@60hz without black bars. Xrandr detects only 30hz in both 4k
resolutions on all kernels. Kernel 4.14 still manages somehow to give me
3840x2160@60hz without black bars. So could this be a xrandr-bug?

Kernel >4.14 seems to respect xrandr and sets: 4096x2160@30hz without black
bars - maybe my HDMI2.0-to-DP adapter is reporting this setting.
I also can get 3840x2160@30hz without black bars with your xrandr workaround,
but not 60hz.


In more detail:

kernel =4.14
-------------
xrandr --props reports that scale-mode is "None". But still no black bars,
because the *native* resolution of the TV is 3840x2160 (listed in the panel
specs here: https://www.lg.com/us/support-product/lg-OLED65B7P)

So if I change to 4096er resolution the desktop is bigger than the screen.
Also I have 60hz on both displays, while xrandr *wrongly* reports only 30hz
available on the TV. The difference between 60 and 30hz is very visible when
moving the mouse and e.g. supertuxkart confirms 60hz in the FPS-overlay.


kernel >4.14
--------------
The TV sets only 30hz, on 4096 and 3840 res. When I force a 60hz-modeline via
xorg.conf.d like described here
https://wiki.archlinux.org/index.php/xrandr#Adding_undetected_resolutions I get
no signal or a switch back to 30hz, when cloning in the GUI.

Then the 3840-black-bar workaround only works if I create this file: 

cat /etc/xdg/autostart/Scaling.desktop

[Desktop Entry]
Type=Application
Name=Scaling
Exec=xrandr --output DisplayPort-0  --set "scaling mode" "Full"


Putting it in xorg.conf had no effect. This is what my xorg.conf now looks
like. Note that the VRR Option works as expected, so its not as if the file is
completely ignored:


cat /etc/X11/xorg.conf.d/10-monitor.conf 

Section "Monitor"
    Identifier "DisplayPort-0"
    Option "scaling mode" "Full" 
    Option "PreferredMode" "3840x2160"
EndSection

Section "Screen"
   Identifier "Screen0"
  Device "AMD"
EndSection

Section "Device"
    Identifier "AMD"
    Driver "amdgpu"
  Option "DRI"         "3"
    Option "TearFree"    "true"
   Option "VariableRefresh" "true"
EndSection

-- 
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

      parent reply	other threads:[~2019-03-18 13:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 19:30 [Bug 201795] New: [Regression] Wrong 4k resolution detected with DisplayPort to HDMI adapter on amdgpu bugzilla-daemon
2018-11-27 19:35 ` [Bug 201795] " 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 [this message]

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-zU0lmWvGXV@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).