This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in supported
series, please file a new bug.
** Changed in: linux (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a me
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is a subscriber of a duplicate bug (26615).
https://bugs.lau
Thank you! it is working now!
--
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 member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
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
Rui Could you please fix my DSDT vaio vpcw120al, it detects de Lid state
correct , open and close but at boot it always state close so if I unplug power
cord it goes to sleep unless y intensionally close and open the lid before I
unplug the cord then it works correctly , so apparently at boot do
I can also confirm this bug is still present with 2.6.31.13-386 kernel
in Ubuntu 9.10rc on my Dell Inspiron 700m.
--
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 member of Ubuntu
Bugs, which
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
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 member of Kubuntu
Bugs, which is a subscriber of a duplicate bug.
--
kubuntu-bugs mailing list
kubuntu
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
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
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
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
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
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 member of Kubuntu
Bugs
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 member of Ubuntu
Bugs, which is a
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 member of Kubun
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 member of Kubuntu
Bugs, which is a subscriber of a duplicate bug.
--
kubunt
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 member of Ubuntu
Bugs, which is a
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 member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bu
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://
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
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 member of Ubuntu
Bugs, which is a direct sub
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
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
Rui, it is best for the bugs to be reported here on the Ubuntu bug-
tracker in the first instance since they may be related to Ubuntu Sauce
or other patches to the kernel, or may even be some by-product of user-
space tools and configuration.
If after we've analysed a report we can be sure there i
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:
** Summary changed:
- Lid state is incorrect on Dell Inspiron 700m
+ Lid state is incorrect (closed) after resume with lid open
--
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 member of Kubun
28 matches
Mail list logo
