From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 89155] Dual monitor setup does not initialize Date: Sat, 16 Jan 2016 11:00:06 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1368137069==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A59D56E220 for ; Sat, 16 Jan 2016 03:00:06 -0800 (PST) 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 --===============1368137069== Content-Type: multipart/alternative; boundary="1452942006.d200ECfd0.6809"; charset="UTF-8" --1452942006.d200ECfd0.6809 Date: Sat, 16 Jan 2016 11:00:06 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=89155 --- Comment #6 from Adam Reichold --- Maybe of interest w.r.t this: Running kernel 4.3.3. by now, I found a seemingly reliable workaround, i.e. if the VGA-connected monitor does not initialize after boot, it will always properly initialize when I put the system into suspend-to-memory and wake it up again immediately after that. (But the VGA-connected monitor will sometimes go dark for a few seconds some time after it initialized for the first time.) -- You are receiving this mail because: You are the assignee for the bug. --1452942006.d200ECfd0.6809 Date: Sat, 16 Jan 2016 11:00:06 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 6 on bug 89155 from 
Maybe of interest w.r.t this: Running kernel 4.3.3. by now, I found a seemingly
reliable workaround, i.e. if the VGA-connected monitor does not initialize
after boot, it will always properly initialize when I put the system into
suspend-to-memory and wake it up again immediately after that. (But the
VGA-connected monitor will sometimes go dark for a few seconds some time after
it initialized for the first time.)

You are receiving this mail because:
  • You are the assignee for the bug.
--1452942006.d200ECfd0.6809-- --===============1368137069== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1368137069==--