On ASUS M6R, laptop lid is always reported as closed

[Martin Böhm]

On my updated Kubuntu 6.10 Edgy beta machine, the new guidance-power-manager reports every time on logon that my laptop lid is closed. That probably means hal cannot recognize the closed/open laptop lid correctly. It causes serious problems when the guidance-power-manager is set to suspend/hibernate when lid is closed.

My notebook is Acer Travelmate 244FX. I can provide more information if necessary.

[Daniel Holbach (dholbach)]

Subscribing 'kubuntu-team'.

Thanks for your bug report. Can you attach the output of lshal and relevant parts of /var/log/syslog?

[Martin Böhm (martin.bohm)]

The lshal output is here.

[Martin Böhm (martin.bohm)]

It seems to me that the only lines in syslog related to my problem are these.

[Piotr Kęplicz (keplicz)]

Looks like the kernel *always* reports the lid as closed (/proc/acpi/button/lid/LID/state). It also happens on an ASUS M6R with vanilla kernels 2.6.16.28 and 2.6.18.1.

However, when closing or opening the lid, two different "button/lid LID" events are reported by acpid.

[Joao Clemente (jpcl)]

Same thing here in a 'LG LS50a'.
/proc/acpi/button/lid/LID0/state always reports "closed".

[pjcraven (pjcraven)]

I am having the same issue with a compaq presario v2000. I have a script that listens for the lid event and then issues the suspend command if it would be of any help.

[DrSpirograph (kubuntu-drspirograph)]

I have a Compaq Presario M2000 (same model?) and have seen the same in both Dapper and Edgy. In Edgy I'm getting that message everytime I logged in, in Dapper when I had it configured to hibernate on lid down it would hibernate as soon as I logged in. After that though, it seemed to detect lid events correctly.

ie, after I restored from the erronious hibernate, the next time I shut the lid, it would hibernate.

[Damien Cassou (cassou)]

This bug has been confirmed by different persons with different architectures using different ubuntu versions.

[Ben Collins (ben-collins)]

It's a confirmed bug, but not confirmed that it is a kernel bug. This could potentially be a buggy BIOS.

Please check if there are any BIOS updates for the machine(s) affected. Also check if there is perhaps an updated DSDT from the acpi website.

[Damien Cassou (cassou)]

After having upgraded my BIOS, the bug still appears. I can't find any updated DSDT.

I'm still unsure if this is a kernel bug, but since I tried the advice, I'll confirm this bug again.

[Joao Clemente (jpcl)]

For the record, I have the same problem with an LG LS50a.

--
           Joao Pedro Clemente
           jpcl @ rnl.ist.utl.pt

On Sun, 14 Jan 2007, Damien Cassou wrote:

> After having upgraded my BIOS, the bug still appears. I can't find any
> updated DSDT.
>
> I'm still unsure if this is a kernel bug, but since I tried the advice,
> I'll confirm this bug again.
>
> ** Changed in: linux-source-2.6.17 (Ubuntu)
> Status: Unconfirmed => Confirmed
>
> --
> On ASUS M6R, laptop lid is always reported as closed
> https://launchpad.net/bugs/66477
>

[Deepak Sarda (antrix)]

Same problem with Kubuntu Feisty {and Edgy} on Dell Inspiron 700m. The lid state {/proc/acpi/button/lid/*/state} is always reported as closed and hal doesn't detect any lid event {no output from `lshal -m`}. `acpi_listen` doesn't detect any events either.

I've searched launchpad and found related bug #70102 and #89860 - the latter bug reporting that the lid is always in 'open' state.

[Brian Murray (brian-murray)]

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

[GattaNegra (gattanegra)]

Hello everyone!
My Prestigio Visconte 1300 has the same problem you are talking about here.
The only difference is that I use kernel 2.6.22-14-generic.

Here are the lshal and /var/log/syslog outputs.
Please help!

[Sergio Zanchetta (primes2h)]

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.