From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 46711] Monitor not turning on after DisplayPort re-plug in Xorg
Date: Fri, 13 Apr 2012 22:28:25 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id F19F59EC15
for ;
Fri, 13 Apr 2012 15:28:24 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=46711
--- Comment #5 from Alex Deucher 2012-04-13 15:28:25 PDT ---
(In reply to comment #4)
> forcing DPMS off and on will restore display. (I have this shell script bound
> to F12 and taping that key will restore the display.)
>
> xset dpms force off
> sleep 1
> xset dpms force on
Are you getting proper hotplug connect/disconnect interrupts? The driver does
exactly the same thing on hotplug interrupts. Assuming the display is active,
on disconnect it calls dpms off, on connect it calls dpms on. It also sends an
event to userspace so it's possible that may be causing a conflict. Take a
look at radeon_connector_hotplug() in radeon_connectors.c in the kernel.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.