Goran Ristic wrote: > Hi Derek! > > On Thu, 28 Mar 2002, Derek Broughton wrote: > > |> I don't think so. He's got an 8000, not an 8100, and I believe it's > |> APM. You definitely can't do half the ACPI stuff on a 2500 you can do > |> on an 8100, because our BIOS is buggy - but if I ever manage to get a > |> working ASL compile, then we can make a new DSDT and enable pretty much > |> everything on the 2500 (except perhaps fan controls). > > I could need this for the i81k, too. ;) > I'd like to know, what in causal EJT is? - I can identifier LID, PWR DCK > and BAY.
Thinking about this, it occurs that there is no reason for those names to be fixed - they're whatever _your_ BIOS/DSDT says they are. Mine is PWRF not PWR, and I don't have DCK, BAY or EJT. DCK & BAY seem obvious, but I can't guess at EJT either. > |> that there isn't an open/closed setting, it's just a counter that > |> increments every time the lid is opened or closed, so you want it to > |> trigger only when the value is an odd number. > > Sorry, but I can not find any other numbers than S0 to S5. Where should > the odd/even numbers be? > With the following in /etc/acpi/events/lid: event=button LID.* action=logger ACPI %e I get this in my syslog: casio logger: ACPI button LID 00000080 00000006 (on LID open - on the previous close the final number was 00000005) Again, it isn't really guaranteed what gets written to /proc/acpi/events by a particular BIOS, so yours could differ. -- derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
