From: Derek B. <der...@ho...> - 2002-05-24 19:12:58
|
From: "Stefan Bellon" <sb...@sb...> > Derek Broughton wrote: > > From: "Andy Dustman" <an...@du...> > > > On Thu, 2002-05-23 at 11:41, Stefan Bellon wrote: > > [snip] > > > > > vici:/home/sbellon# cat /proc/acpi/event > > > > button/lid LID 00000080 1 > > > > button/lid LID 00000080 2 > > > > button/power PWRF 00000080 1 > > > > button/power PWRF 00000080 2 > > [snip] > > > I've seen this problem too - and thought it was an ACPI issue - but > > it seems from Stefan's experiment that the problem must be in acpid. > > If /proc/acpi/event has things in one order, but acpid processes them > > in another, then acpid has to be the one that's wrong. -- derek > > Ah, I'm not so sure about that. The tests when acpid was not running > didn't put the notebook in S1 obviously. And therefore it's clear that > when opening the lid again, the second lid event occurs. But when acpid > is running, the notebook goes to S1 when the first lid event occurs. > When you open the lid again, the second event /should/ occur, but the > notebook is sleeping. Then you press the power button and /that/ event > is recognised. Perhaps the lid opening is then "remembered" and > inserted into the event queue. Nothing you did _should_ have put the notebook in S1. acpid had to have done that. So I still say acpid is processing things in the wrong order. However, it seems we both may be making an invalid assumption - that is, you simply can't ever recognize any button push except the power button when you are in S1. That's a real bitch... -- derek |