On Sat, 2014-10-25 at 23:34 +0200, Michael Biebl wrote:
> Am 25.10.2014 um 23:12 schrieb ~Stack~:
> > On 10/25/2014 04:01 PM, ~Stack~ wrote:
> >> On 10/24/2014 10:55 AM, Michael Biebl wrote:
> >>> Am 24.10.2014 um 17:23 schrieb Michael Biebl:
> >>>> What do you get if your that program when your lid is closed/opened?
> >>>
> >>> The output of
> >>> $ cat /proc/acpi/button/lid/LID/state
> >>> when lid is closed / open would be helpful as well.
> >>>
> >>> If you don't have an external monitor, you can run
> >>>
> >>> sleep 30 && cat /proc/acpi/button/lid/LID/state
> >>>
> >>> and then quickly close your lid.
> >>
> >> Greetings,
> >>
> >> I ran:
> >> $(for i in {0..100}; do cat /proc/acpi/button/lid/LID/state ; sleep 1; done)
> >>
> >> I get "state: open" when the lid is open and "state: closed" when closed.
> >
> > Eureka!! I think I have a lead!
> >
> > So when I do a fresh reboot and have _not_ closed the lid but run the
> > code you send and cat'ing the state, it seems to think the lid is
> > closed. When I close the lid the state remains as a closed lid. When I
> > open the lid, it finally triggers as being open.
> >
> > So now the question is, why does it think my laptop lid is closed on a
> > fresh boot?
>
> That sounds like either a bug in the firmware or in the kernel.
>
> Ben, what's your take on this?
You're probably right but I don't know how to debug such things.
Ben.
--
Ben Hutchings
I'm not a reverse psychological virus. Please don't copy me into your sig.
Attachment:
signature.asc
Description: This is a digitally signed message part