lid state?

lid state?

[John Belmonte]

Hello,

What is the correct way to detect the lid state on a lid event?  I've 
seen some mention of using a counter, but as the lid could be closed 
before acpid starts up, it doesn't seem very robust.


-John



-- 
http:// i      .   /



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: lid state?

[Derek Broughton]

From: "John Belmonte" <jvb-ZFKsivP1bGvOQU1ULcgDhA@public.gmane.org>
>
> What is the correct way to detect the lid state on a lid event?  I've
> seen some mention of using a counter, but as the lid could be closed
> before acpid starts up, it doesn't seem very robust.

It's far from ideal, but it's robust enough, because the lid state bears no
connection to acpid.  Whether or not acpid is running, events get generated.
I suppose, conceivably, the lid could be closed when the system boots and
ACPI starts - but how realistic is that?  I can't see it happening on my
system.
--
derek


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: lid state?

[Martijn van de Streek]

On Mon, 07 Oct 2002, Derek Broughton wrote:

> It's far from ideal, but it's robust enough, because the lid state bears no
> connection to acpid.  Whether or not acpid is running, events get generated.
> I suppose, conceivably, the lid could be closed when the system boots and
> ACPI starts - but how realistic is that?  I can't see it happening on my
> system.

It's very well possible to do that. And it breaks any on/off type script
you set up for the lid button.

I'd like separate open and close messages as well actually..

Martijn
-- 
You may be infinitely smaller than some things, but you're infinitely 
larger than others.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: lid state?

[Frank Mehnert]

On Monday 07 October 2002 14:10, Derek Broughton wrote:
> From: "John Belmonte" <jvb-ZFKsivP1bGvOQU1ULcgDhA@public.gmane.org>
>
> > What is the correct way to detect the lid state on a lid event?  I've
> > seen some mention of using a counter, but as the lid could be closed
> > before acpid starts up, it doesn't seem very robust.
>
> It's far from ideal, but it's robust enough, because the lid state bears no
> connection to acpid.  Whether or not acpid is running, events get
> generated. I suppose, conceivably, the lid could be closed when the system
> boots and ACPI starts - but how realistic is that?  I can't see it
> happening on my system.

Very realistic if you have attached an external monitor to your notebook.

Frank
-- 
Frank Mehnert
## Dept. of Computer Science, Dresden University of Technology, Germany ##
## E-Mail: fm3-IG//nw+yl+iQIjdd1DhZXWfrygkm6VTR@public.gmane.org    http://os.inf.tu-dresden.de/~fm3 ##


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: lid state?

[James D Strandboge]

On Mon, 2002-10-07 at 10:22, Frank Mehnert wrote:
> On Monday 07 October 2002 14:10, Derek Broughton wrote:
> > From: "John Belmonte" <jvb-ZFKsivP1bGvOQU1ULcgDhA@public.gmane.org>
> >
> > > What is the correct way to detect the lid state on a lid event?  I've
> > > seen some mention of using a counter, but as the lid could be closed
> > > before acpid starts up, it doesn't seem very robust.
> >
> > It's far from ideal, but it's robust enough, because the lid state bears no
> > connection to acpid.  Whether or not acpid is running, events get
> > generated. I suppose, conceivably, the lid could be closed when the system
> > boots and ACPI starts - but how realistic is that?  I can't see it
> > happening on my system.
> 
> Very realistic if you have attached an external monitor to your notebook.
> 
This would be nice, but as a workaround/solution, I use touch in my
lid.sh script.  Eg:

#!/bin/sh
CLOSEDFILE="/var/run/acpi_lid_closed"

case "$2" in
    LID)
        case "$3" in
            00000080)
                if [ -e "$CLOSEDFILE" ];
                then
                        logger -p daemon.info "ACPI lid: lid is open"
                        rm -f $CLOSEDFILE
                else
                        logger -p daemon.info "ACPI lid: lid is closed"
                        touch $CLOSEDFILE
                fi
                ;;                      
            *)
                logger -p daemon.info "ACPI lid: unknown event $3 (in
$@)"
                ;;
        esac
        ;;
    *)
        logger -p daemon.info "ACPI lid: unknown event $2 (in $@)"
        ;;
esac



Since (on my system) /var/run is cleaned out on boot, this works fine. 
Of course, if the lid is closed when the machine comes on, this is
backwards, but I can't turn my laptop on when the lid is closed, so no
big deal for me.  The script could also check if an external monitor was
connected, etc to make sure that it works in whatever situation.

Jamie Strandboge



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf