All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208947] amdgpu DisplayPort won't recognize all display modes after 5.9 merges
Date: Fri, 21 Aug 2020 02:18:10 +0000	[thread overview]
Message-ID: <bug-208947-2300-R5wpLaALb8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208947-2300@https.bugzilla.kernel.org/>

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

--- Comment #14 from Coleman Kane (ckane@colemankane.org) ---
So diving a bit further it looks like a contributor to this behavior might be
my misbehaving video hardware.

After some reading I did determine that I can add the following to my linux
command line in GRUB and Xorg will recognize the video mode, as well as all the
other video modes supported by the monitor:
video=DP-1:3840x2160@29.97me

So I think at this point, I have a solution that will address the problem for
me. I am not certain whether you think it would make sense to modify the code
to account for this situation or not. The old behavior was still able to get
the video modes from the display despite it coming up "inactive" on boot, but
it seems like the new behavior causes it to throw away all the video modes and
substitute them with some basic SVGA modes.

-- 
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:[~2020-08-21  2:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 21:02 [Bug 208947] New: amdgpu DisplayPort won't recognize all display modes after 5.9 merges bugzilla-daemon
2020-08-18  0:19 ` [Bug 208947] " 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 [this message]
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-R5wpLaALb8@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.