From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Radeon 3650HD laptop LVDS lid open/closed detection problem Date: Sun, 19 Sep 2010 14:34:03 +0300 Message-ID: <20100919113403.GV2804@reaktio.net> References: <87y6e8zbb0.fsf@riseup.net> <20100712115301.GP17817@reaktio.net> <20100712165956.GR17817@reaktio.net> <20100726194242.GI17817@reaktio.net> <20100727084112.GN17817@reaktio.net> <20100919111834.GU2804@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from smtp.tele.fi (smtp.tele.fi [192.89.123.25]) by gabe.freedesktop.org (Postfix) with ESMTP id 179859E7EF for ; Sun, 19 Sep 2010 04:34:09 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20100919111834.GU2804@reaktio.net> 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: Alex Deucher Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On Sun, Sep 19, 2010 at 02:18:34PM +0300, Pasi K=E4rkk=E4inen wrote: > On Tue, Jul 27, 2010 at 11:41:12AM +0300, Pasi K=E4rkk=E4inen wrote: > > > >> > > > > > > > > Yes, the lid acpi stuff seems to work: > > > > > > > > lid closed: > > > > $ cat /proc/acpi/button/lid/LID/state > > > > state: =A0 =A0 =A0closed > > > > > > > > lid open: > > > > $ cat /proc/acpi/button/lid/LID/state > > > > state: =A0 =A0 =A0open > > > > > > > > I also verified that the initial lid state is "closed" when > > > > the lid has been closed all the time during system startup > > > > and only external DVI display is in use. > > > > > > > > (I modified /etc/rc5.d/S01sysstat to sleep+print+sleep > > > > so I can check it during system startup before X starts). > > > > > > > > When the lid is closed xrandr says "LVDS connected", is that correc= t? > > > = > > > Yes. The LVDS is connected, even if you don't necessarily want to us= e it. > > > = > > = > > That's what I was thinking of. But good to get confirmation :) > > = > > > > > > > > I think LVDS actually is ON when lid is closed, since I can immedia= tely > > > > see everything when I open the lid.. correct colors etc. > > > > > > > > So what's the component I should start looking at.. gnome-power-man= ager? > > > > or something else? > > > > > > > > Actually.. I just noticed that already in GDM prompt the internal L= VDS > > > > gets enabled/turned on, even when the lid is closed.. I think. > > > = > > > Yes, it's up to to gdm, gnome-power-manager, etc. to decide the > > > display policy based on the lid state. > > > = > > = > > Ok. Is there a way to monitor the status of drm from /proc or /sys or f= rom somewhere? = > > = > = > Back to this.. > = > so "/proc/acpi/button/lid/LID/state" seems to work properly on my laptop, > but is there a way to monitor the state of the drm/kms outputs from /proc= , /sys or from somewhere? = > = > I'd like to see the state before X is started, and verify what happens wh= en GDM is started etc.. = > (ie. if outputs are enabled/active or not). > = Ah, found it: $ ls /sys/class/drm/card0 card0-DVI-D-1 card0-LVDS-1 dev power uevent card0-HDMI Type A-1 card0-VGA-1 device subsystem $ cat /sys/class/drm/card0/card0-LVDS-1/status = connected $ cat /sys/class/drm/card0/card0-LVDS-1/enabled = enabled $ cat /sys/class/drm/card0/card0-LVDS-1/modes = 1680x1050 1400x1050 1280x1024 1440x900 1280x960 1280x854 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 -- Pasi