AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Mayhew <neil_mayhew-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: 21:9 monitor resolution incorrect since 4.14 kernel
Date: Wed, 30 Oct 2019 12:07:38 -0600	[thread overview]
Message-ID: <10434d28-490d-ebbd-ab66-d3adb3a2e1de@users.sourceforge.net> (raw)
In-Reply-To: <32e595a2-fdc1-7b13-2e33-c2b8752c60f2-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>


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

I enabled kms debugging with drm.debug=4 on the kernel command line.
This enabled me to see that the relevant modes are being rejected with
error 11 which is DC_EXCEED_DONGLE_CAP. Sure enough, I see that there's
a dongle detected that's rated at 165MHz and my preferred modes are all
above that.

However, if I switch the monitors around everything is fine, because I
can use a lower resolution monitor with the dongle and get the 21:9
resolution on another output without a dongle.

The dongle is actually a passive DP to HDMI cable, and I need it because
one of my outputs is DP and I don't have any monitors with DP inputs. I
was told somewhere that I'd need to use the DP output to get the clock
speeds needed for 21:9, but apparently that's not true. Clearly the
cable can go above 165MHz since the 4.14 kernel can drive the display at
the preferred resolution using it, but thankfully I don't need to
concern myself with that now.

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

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

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2019-10-30 18:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 22:01 21:9 monitor resolution incorrect since 4.14 kernel Neil Mayhew
2019-10-29 22:01 ` Neil Mayhew
     [not found] ` <32e595a2-fdc1-7b13-2e33-c2b8752c60f2-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
2019-10-30 18:07   ` Neil Mayhew [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=10434d28-490d-ebbd-ab66-d3adb3a2e1de@users.sourceforge.net \
    --to=neil_mayhew-rn4veauk+akrv+lv9mx5uipxlwaovq5f@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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