Wow, it really works now. Great job. :)
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
You received this bug notification because you are a direct subscriber
of the bug.
-
Retested with 2.6.28 (Ubuntu source), dmesg attached. All the debug
parameters are now present, yet the log looks pretty much the same as
before...
I can also test with an even more recent vanilla kernel if needed. For
that I will need a .hex file again, because I couldn't see any initrd
aml loadi
Ok. I compiled 2.6.24.6 with CONFIG_ACPI_DEBUG and
CONFIG_ACPI_DEBUG_FUNC_TRACE, although /sys/module/acpi/parameters
contains only "acpica_version", "debug_layer" and "debug_level". I did
the test anyway.
** Attachment added: "dmesg-lid.txt"
http://launchpadlibrarian.net/24839385/dmesg-lid.txt
Note that I always wake up the machine using the power button, not lid.
I don't know if this makes a difference though...
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
You received this bug notification because you are a direct subscriber
of t
The lid triggers events normally now, but
/proc/acpi/button/lid/LID0/state prints always "state: unsupported".
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
You received this bug notification because you are a direct subscriber
of the bug.
--
Hmm, the patched DSDT seems to flood ACPI lid events all the time.
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
You received this bug notification because you are a direct subscriber
of the bug.
--
Zhang: Actually, could I have that as an .aml file?
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
You received this bug notification because you are a direct subscriber
of the bug.
-
Thanks. It seems that requires a kernel recompile, I will look on that
soon when I have more time.
Never mind the talk about /etc/acpi, I rechecked and it seems the
problem is present no matter what script is used to suspend.
--
Lid state is incorrect (closed) after resume with lid open
https://
Here goes.
Earlier I posted some more details in bug #44825 which was marked as a
duplicate of this one.
** Attachment added: "acpidump.txt"
http://launchpadlibrarian.net/24186654/acpidump.txt
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
By the way, the lid state is set correctly if using the (I believe now
obsolete) /etc/acpi scripts.
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
You received this bug notification because you are a direct subscriber
of the bug.
-
10 matches
Mail list logo
