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 17:56:07 +0300 Message-ID: <20100919145607.GX2804@reaktio.net> References: <20100712115301.GP17817@reaktio.net> <20100712165956.GR17817@reaktio.net> <20100726194242.GI17817@reaktio.net> <20100727084112.GN17817@reaktio.net> <20100919111834.GU2804@reaktio.net> <20100919113403.GV2804@reaktio.net> <20100919122547.GW2804@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 E0C589E7EB for ; Sun, 19 Sep 2010 07:56:13 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20100919122547.GW2804@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 03:25:47PM +0300, Pasi K=E4rkk=E4inen wrote: > > > = > > > so "/proc/acpi/button/lid/LID/state" seems to work properly on my lap= top, > > > 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 happen= s when 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 > > = > = > So I added those to rc.local so that they get executed before GDM.. > and I booted up the laptop with the lid closed.. > = > And the result was: lid state "closed", lvds-status "connected" and lvds-= enabled was "enabled".. > = > Does that mean Fedora plymouth is doing it wrong, > or is t possible the driver itself always enabled the lvds, even when the= lid is closed? = > = I did some more investigations. I'm currently using Fedora 13 Linux 2.6.34.= 6-47.fc13.x86_64 kernel. I hacked the initrd image to echo debug stuff right after drm modules are l= oaded, = and *before* plymouth is started (and then sleep for some time so that I ha= ve time to see the debug values.) The result was this: acpi lid/state: closed lvds-1/status: connected lvds-1/enabled: enabled So to me it looks like the problem is in the driver itself.. lvds shouldn't get enabled (turned on) when the lid is closed.. -- Pasi