From: Dominik Brodowski <devel-JhLEnvuH02M@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: ehikory-Ru1csStN2yCTnpBtbRfDVg@public.gmane.org
Subject: no events with acpi-20020821-2.4.19 (fwd)
Date: Sat, 24 Aug 2002 19:55:36 +0200 [thread overview]
Message-ID: <20020824195536.C587@brodo.de> (raw)
----- Forwarded message from ehikory-Ru1csStN2yCTnpBtbRfDVg@public.gmane.org -----
My mail provider does not comply with RFC822, and my mail to
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org was rejected. Would you be
kind enough to forward this message to the list? I will check the
archives to follow the thread. Thank you.
-------- Forwarded Message ---------
Subject: No events with acpi-20020821-2.4.19
After installing a 2.4.19 kernel with the acpi-20020821-2.4.19 patch, I get
no events reported from /proc/acpi/events. Events were being reported with the
ACPI support in the vanilla kernel. I'm running on a Sony VAIO PCG-Z505HE, and
`acpidmp FACP | acpitbl` reports OEMID: Sony, TableID: Z1, revision: 0x20000222.
My syslog looks clean (ACPI loads, with lots of detail, but no errors).
Additionally, although sleep didn't work quite right with the vanilla kernel
(no wakeup functions), I now get no response from `echo 1 > /proc/acpi/sleep` and
receive a "write error: no such device" when using `cat foo > /proc/acpi/sleep`,
where foo contains only the numeral "1".
Has anyone else experienced this behavior, or do I just need to update my
BIOS? Any pointers to additional documentation would also be welcome. Also,
if anyone wants detailed debugging information, I would be happy to send it
off-list: just let me know what you need.
--
Emmet Hikory
ehikory-Ru1csStN2yCTnpBtbRfDVg@public.gmane.org
--------- End of Forwarded Message ---------
----- End forwarded message -----
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
reply other threads:[~2002-08-24 17:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020824195536.C587@brodo.de \
--to=devel-jhlenvuh02m@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ehikory-Ru1csStN2yCTnpBtbRfDVg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox