From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karol Kozimor Subject: Re: Learning ACPI Date: Sat, 29 Jan 2005 17:13:34 +0100 Message-ID: <20050129161334.GA28055@hell.org.pl> References: <41FA9F93.4090105@cs.ou.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Return-path: Content-Disposition: inline In-Reply-To: <41FA9F93.4090105-5f/76mLIbwCHXe+LvDLADg@public.gmane.org> Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Jim Summers Cc: Listacpi List-Id: linux-acpi@vger.kernel.org Thus wrote Jim Summers: > I guess I am not understanding how, if the acpid is correctly monitoring > the lid state then why would it not fire the events/actions? I can > porvide more info, dmesg output etc... Basically, the lid stat is polled, while the events are interrupt driven. For the record, could you try with an older ( <= 2.6.7) kernel? There seems to be an issue in handling EC interrupts in recent kernels, it might be that. Best regards, -- Karol 'sziwan' Kozimor sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl