Radeon 3650HD laptop LVDS lid open/closed detection problem

[Pasi Kärkkäinen]

On Sun, Sep 19, 2010 at 02:34:03PM +0300, Pasi Kärkkäinen wrote:
> On Sun, Sep 19, 2010 at 02:18:34PM +0300, Pasi Kärkkäinen wrote:
> > On Tue, Jul 27, 2010 at 11:41:12AM +0300, Pasi Kärkkäinen wrote:
> > > > >>
> > > > >
> > > > > Yes, the lid acpi stuff seems to work:
> > > > >
> > > > > lid closed:
> > > > > $ cat /proc/acpi/button/lid/LID/state
> > > > > state:      closed
> > > > >
> > > > > lid open:
> > > > > $ cat /proc/acpi/button/lid/LID/state
> > > > > state:      open
> > > > >
> > > > > 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 correct?
> > > > 
> > > > Yes.  The LVDS is connected, even if you don't necessarily want to use 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 immediately
> > > > > see everything when I open the lid.. correct colors etc.
> > > > >
> > > > > So what's the component I should start looking at.. gnome-power-manager?
> > > > > or something else?
> > > > >
> > > > > Actually.. I just noticed that already in GDM prompt the internal LVDS
> > > > > 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 from 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 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? 

-- Pasi