From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 39683] radeon "hd6770 flex" dpms fails to unblank one display sometimes Date: Sat, 6 Aug 2011 03:45:40 -0700 (PDT) Message-ID: <20110806104540.78C72130129@annarchy.freedesktop.org> 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 9274B9E7E4 for ; Sat, 6 Aug 2011 03:45:40 -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=39683 --- Comment #7 from aaron 2011-08-06 03:45:40 PDT --- i checked the settings and found nothing, so i decided to switch the displays around to see what happens... original layout (1): dvi -> 1 hdmi -> 2 dp -> 3 layout 2: dvi -> 2 hdmi -> 1 dp -> 3 ran xset dpms force off via ssh all 3 turned back on but "3" was distinctly after 1,2 (under setup 1 they all turn back on at about the same time the second time round) xset -q says displays off same result every time layout 3: dvi -> 3 hdmi -> 2 dp -> 1 same result as layout 1 but it starts at a different point in the loop - xrandr says display on but display 3 is off immediately after starting X it may have something to do with a race condition relating to the speeds the dislays "start" ( i probably have no idea what i am talking about...) as when setting up xorg.conf if i used "right-of" it complained about missing modes or something - it only worked as i expected it to when "left-of"'d from display 3 will investigate further in the next few days -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.