From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 80628] New: The way KMS works doesn't support HDMI/DP well Date: Sat, 28 Jun 2014 13:26:41 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0512459215==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 6AB516E1B2 for ; Sat, 28 Jun 2014 06:26:42 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0512459215== Content-Type: multipart/alternative; boundary="1403962002.Fbfd50.2818"; charset="us-ascii" --1403962002.Fbfd50.2818 Date: Sat, 28 Jun 2014 13:26:42 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=80628 Priority: medium Bug ID: 80628 Assignee: dri-devel@lists.freedesktop.org Summary: The way KMS works doesn't support HDMI/DP well Severity: enhancement Classification: Unclassified OS: Linux (All) Reporter: tom.ty89@gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/other Product: DRI If the machine has no monitor attached at all before boot, KMS couldn't probe the monitor and make it goes into native resolution afterwards. This issue is not very obvious when DVI/VGA are the only connectors available because of their mechanism. When it comes to HDMI/DP, the monitor is considered disconnected when it's powered off. Then the issue become annoying, while we have to make sure that one monitor is connected and switched on before boot. Moreover, display managers have to be started manually under such situation after you turn on your monitor. Not even all DM can start X in optimal resolution without some "xrandr hack" By the way, it's funny that if you got one attached, you can power on others later without getting into the problem. Just that I am not sure if it's because all my monitors have the same optimal resolution. -- You are receiving this mail because: You are the assignee for the bug. --1403962002.Fbfd50.2818 Date: Sat, 28 Jun 2014 13:26:42 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"
Priority medium
Bug ID 80628
Assignee dri-devel@lists.freedesktop.org
Summary The way KMS works doesn't support HDMI/DP well
Severity enhancement
Classification Unclassified
OS Linux (All)
Reporter tom.ty89@gmail.com
Hardware Other
Status NEW
Version XOrg CVS
Component DRM/other
Product DRI

If the machine has no monitor attached at all before boot, KMS couldn't probe
the monitor and make it goes into native resolution afterwards. This issue is
not very obvious when DVI/VGA are the only connectors available because of
their mechanism.

When it comes to HDMI/DP, the monitor is considered disconnected when it's
powered off. Then the issue become annoying, while we have to make sure that
one monitor is connected and switched on before boot.

Moreover, display managers have to be started manually under such situation
after you turn on your monitor. Not even all DM can start X in optimal
resolution without some "xrandr hack"

By the way, it's funny that if you got one attached, you can power on others
later without getting into the problem. Just that I am not sure if it's because
all my monitors have the same optimal resolution.


You are receiving this mail because:
  • You are the assignee for the bug.
--1403962002.Fbfd50.2818-- --===============0512459215== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0512459215==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 80628] The way KMS works doesn't support HDMI/DP well Date: Mon, 14 Oct 2019 13:20:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0927479754==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id BF39A89C8F for ; Mon, 14 Oct 2019 13:20:20 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0927479754== Content-Type: multipart/alternative; boundary="15710592208.a9a0cC65b.29307" Content-Transfer-Encoding: 7bit --15710592208.a9a0cC65b.29307 Date: Mon, 14 Oct 2019 13:20:20 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D80628 Martin Peres changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from Martin Peres --- Hi, Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migr= ated to http://gitlab.freedesktop.org. To avoid migrating out of date bugs, I am now closing all the bugs that did= not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/= drm (use misc by default). Sorry about the noise! --=20 You are receiving this mail because: You are the assignee for the bug.= --15710592208.a9a0cC65b.29307 Date: Mon, 14 Oct 2019 13:20:20 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated <= span class=3D"fn">Martin Peres changed bug 80628<= /a>
What Removed Added
Resolution --- INVALID
Status NEW RESOLVED


You are receiving this mail because:
  • You are the assignee for the bug.
= --15710592208.a9a0cC65b.29307-- --===============0927479754== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0927479754==--