>>> That was my assumption also, since my earlier 3-liner patch was doing >>> this exactly: trying to wake up on a regular 0xCE event. And it did work. One more ouput for tonight. After doing a diff of the acpidump from both BIOS versions, I've found explicit references to the two 0xCE and 0xCF values right in the delta, in the dsdt.dsl files. Here is the section that seems relevant in the newer one, for v1.1.31: If (Local1 & 0x08) { Local1 = ECBT (One, 0x04) If (Local1) { If (OSYS >= 0x07DF) { Notify (\_SB.HIDD, 0xCE) // Hardware-Specific } ElseIf (CondRefOf (\_SB.PCI0.LPCB.ECDV.VGBI)) { Notify (\_SB.PCI0.LPCB.ECDV.VGBI, 0xC0) // Hardware-Specific } } ElseIf (OSYS >= 0x07DF) { Notify (\_SB.HIDD, 0xCF) // Hardware-Specific } ElseIf (CondRefOf (\_SB.PCI0.LPCB.ECDV.VGBI)) { Notify (\_SB.PCI0.LPCB.ECDV.VGBI, 0xC1) // Hardware-Specific } } If (Local1 & 0x0100) { Local1 = ECBT (One, 0x10) If (Local1) { Notify (\_SB.HIDD, 0xC6) // Hardware-Specific } Else { Notify (\_SB.HIDD, 0xC7) // Hardware-Specific } } I'm new to ACPI but could that ECBT mean "EC Button" maybe? Jerome -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html