Davidiam,
please try the custom DSDT attached.
** Attachment added: "custom DSDT: Fix a problem that LIDS is always set to 1
during initialization."
http://launchpadlibrarian.net/43399250/dsdt.hex
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/3
please attach the acpidump output, with the latest pmtools at
http://www.lesswatts.org/projects/acpi/utilities.php
--
18 seconds ACPI delay while booting due to DSDT
https://bugs.launchpad.net/bugs/100110
You received this bug notification because you are a direct subscriber
of the bug.
So, this is clearly a BIOS problem to me and we can not fix/workaround it in
kernel.
And I think users need to use the customized DSDT as a workaround.
IMO, the bug can be closed.
thanks,
rui
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
You
hah, I see what the problem is.
this customized DSDT should fix the problem for you, please give it a try.
** Attachment added: "customized DSDT"
http://launchpadlibrarian.net/25174939/DSDT.aml
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
BTW, please clear acpi debug_level and debug_layer before the test.
i.e. additional to the previous test, please
0.5. echo 0 > /sys/module/acpi/parameters/debug_layer
0.6. echo 0 > /sys/module/acpi/parameters/debug_level
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.l
please try a new kernel, say 2.6.29.
I'm not sure if the ACPI trace stuff is introduced in 2.6.24 or not, but try a
vanilla 2.6.29 kernel would be a better choice here.
--
Lid state is incorrect (closed) after resume with lid open
https://bugs.launchpad.net/bugs/34389
You received this bug noti
please make sure that CONFIG_ACPI_DEBUG is set in your kernel config file,
and then try this test,
1. dmesg -c
2. echo 0x > /sys/module/acpi/parameters/trace_debug_layer
3. echo 0x > /sys/module/acpi/parameters/trace_debug_level
4. echo _LID > /sys/module/acpi/parameters/trace_metho
yes, you are right, now how about this DSDT.
** Attachment added: "DSDT.aml"
http://launchpadlibrarian.net/24553306/DSDT.aml
--
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 subscrib
DSDT.aml attached.
** Attachment added: "customized DSDT"
http://launchpadlibrarian.net/24496998/DSDT.aml
--
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.
---
joonas,
could you please try this customized DSDT to see if it helps?
> the lid state is set correctly if using the (I believe now obsolete)
> /etc/acpi scripts.
what do you mean?
the problem only exists when acpid is stopped?
** Attachment added: "customized DSDT -- always refresh the lid stat
okay.
I got some similar problems (wrong lid state) before, and have root caused that
they're BIOS problems and some of them can be fixed by overriding the DSDT.
so it would be great if anyone with this problem can attach the acpidump
here so that I can see if this is a duplicate.
--
Lid state
The incorrect Lid state problem seems like a Linux/ACPI bug.
it would be great if you guys can file a new bug report at
http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
as this is the place we use to track ACPI kernel bugs.
please attach the acpidump output by using the latest pmtools at
http:
12 matches
Mail list logo
