Toshiba Satellite A70 always reports lid as closed

Bug #70102 reported by Jonathan Jesse
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Won't Fix
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kde-guidance-powermanager

running a Toshiba Satellite A70 and everytime I boot up, I receive a message that the Laptop Lid is closed doing nothing. However if I use the power manager to suspend the laptop when the lid is closed, the laptop will always close.

here is the link to my Hardware from the Hardware Database: http://hwdb.ubuntu.com/?xml=a3ed923ad9cc9c09e1657059da6e8083 I hope that helps.
Let me know if you need further information. This is high priority problem for me as power control does not work correctly.

Revision history for this message
Jonathan Jesse (jjesse) wrote :

This is logged in /var/log/acpid each time I reboot, I hope that helps

cat /var/log/acpid | grep lid

[Mon Nov 6 20:27:16 2006] received event "button/lid LID 0000080 00000001"
[Mon Nov 6 20:27:17 2006] executing action "/etc/acpi/lid.sh"
[Mon Nov 6 20:27:21 2006] completed evedn "button/lid LID 0000080 000001"

Don't know if that helps

Revision history for this message
Sebastian Kügler (sebasje) wrote : Re: [Bug 70102] Re: Problems w/ Laptop always suspending

On Tuesday 07 November 2006 03:04, Jonathan Jesse wrote:
> This is logged in /var/log/acpid each time I reboot, I hope that helps
>
> cat /var/log/acpid | grep lid
>
> [Mon Nov 6 20:27:16 2006] received event "button/lid LID 0000080 00000001"
> [Mon Nov 6 20:27:17 2006] executing action "/etc/acpi/lid.sh"
> [Mon Nov 6 20:27:21 2006] completed evedn "button/lid LID 0000080 000001"
>
>
> Don't know if that helps

Doesn't look like it's powermanager-related, but that acpid wants to suspend
your machine. Maybe it's configured in

/etc/acpi/powerbtn.sh

?

Cheers,
--
sebas

 http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Great people talk about ideas. Average people talk about things. Small people
talk about people. (Dave Marinaccio)

Revision history for this message
Jonathan Jesse (jjesse) wrote : Re: Problems w/ Laptop always suspending

Lure asked me to attach lshal to help out with this bug, which I'm doing

Revision history for this message
Luka Renko (lure) wrote :

Jonathan, this lshal output is with opened lid?

The problem is that ACPI/hal claims the following:

udi = '/org/freedesktop/Hal/devices/acpi_LID'
  info.udi = '/org/freedesktop/Hal/devices/acpi_LID' (string)
  linux.hotplug_type = 4 (0x4) (int)
  button.has_state = true (bool)
  button.state.value = true (bool)
  info.capabilities = {'button'} (string list)
  info.category = 'button' (string)
  info.product = 'Lid Switch' (string)
  button.type = 'lid' (string)
  info.parent = '/org/freedesktop/Hal/devices/computer' (string)
  linux.acpi_type = 10 (0xa) (int)
  linux.acpi_path = '/proc/acpi/button/lid/LID' (string)

The problem is that button.state.value is true, which mean that lid is closed. This means that the problem is not in powermanager, but most probably in kernel/ACPI/HAL. Can you also provide the output of the following:

cat /proc/acpi/button/lid/*/*

This is what kernel thinks about you lid and should match what lshal reports: if they match, the problem is in kernel/ACPI/HW, but if they do not match, then the bug is in HAL.

Revision history for this message
Jonathan Jesse (jjesse) wrote :

Luka,

Thanks for help me out w/ this bug. Yes the laptop lid is open. Each time I turn on the computer I see a greyish box in the right corner that says "the lid is closed" or something to that effect.

This what cat /proc/acip/button/lid/*/* said when I was typing this bug report

Revision history for this message
Jonathan Jesse (jjesse) wrote :

D'oh forgot to paste it, sorry

jjesse@jjesse-laptop:~$ cat /proc/acpi/button/lid/*/*
type: Lid Switch
state: closed
jjesse@jjesse-laptop:~$

Revision history for this message
Luka Renko (lure) wrote :

Since /proc/acpi/button/lid provides wrong info it is problem in the kernel (or buggy laptop ACPI).
Do you still have dapper (or at least dapper kernel) to try it there?

Revision history for this message
Jonathan Jesse (jjesse) wrote :

Can I just install the Dapper Kernel and see if it works? Would a Desktop CD of Dapper report the same information? I know it would be easier to talk via IRC over this, but IRC is blocked at work :(

Revision history for this message
Luka Renko (lure) wrote :

I think Desktop CD would be fine (it will not have latest kernel, but still)

Revision history for this message
Sebastian Kügler (sebasje) wrote : Re: [Bug 70102] Re: Problems w/ Laptop always suspending

On Tuesday 07 November 2006 19:55, Jonathan Jesse wrote:
> type:                    Lid Switch
> state:      closed

A kernel problem then.
--
sebas

 http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Beware of bugs in the above code; I have only proved it correct, not tried
it. - Donald Knuth

Revision history for this message
Jonathan Jesse (jjesse) wrote :

Booted in a Dapper Desktop CD and this is the output of cat /proc/acpi/button/lid/*/*

ubuntu@ubuntu:/proc/acpi/button/lid/LID$ cat /proc/acpi/button/lid/*/*
type: Lid Switch
state: closed
ubuntu@ubuntu:/proc/acpi/button/lid/LID$

Also attaching lshal as well

Revision history for this message
Luka Renko (lure) wrote :

This may be duplicate of bug 43391

Revision history for this message
Konstantinos Kostarellis (kostacooker) wrote :

Well I got the exactly same effect on my laptop: Samsung X20 since kde 3.5.5 (dapper/edgy) ...

It's all working fine in gnome but in kde since 3.5.5 i get this grey box about the a closed lid.

When having Suspend Option activated first thing that happens on login is my laptop going to suspend. After re-activating everything is fine ... the laptop even susupends after closing the lid ;)

well I don't know what it is but I wanted to notice that gnome does handle the laptop lid right.

Changed in linux-source-2.6.17:
status: Unconfirmed → Confirmed
Revision history for this message
Jonathan Jesse (jjesse) wrote :

If it is indeed a kernel bug, as mentioned in comment #10, how does one go about fixing it? I would love to use suspend correctly and get things working right. Any suggestions on this one?

Revision history for this message
Jonathan Jesse (jjesse) wrote :

Use Herd 1 Desktop CD still gettign same message upon startup.
If I do a cat /var/log/acpid | grep lid returns no information
If I do a cat /proc/acpi/button/lid/*/* it shows the Lid Switch is in a state closed

Will attach lshal in a minute, but is there anything else I can do to work on getting this bug closed?

Revision history for this message
Jonathan Jesse (jjesse) wrote :

attaching lshal

Revision history for this message
Jonathan Jesse (jjesse) wrote :

Using Herd3 Live CD still reports as laptop lid is closed. Is any work being done on this?

Revision history for this message
Konstantinos Kostarellis (kostacooker) wrote :

Hi Jonathan,

as mentioned before I got the similiar behaviour on a Samsung X20. But its working on gnome flawlessness nevertheless

cat /proc/acpi/button/lid/*/*
type: Lid Switch
state: closed

So I guess its something Sebastian Kügler (sebas at kde dot org) could fix easily. Its the guy that wrote the python skript used in kubuntu and as he is working at cononical he should be easily getting access on how gnome powermanagement is handeling this different

Revision history for this message
dany-r5 (dany-r5) wrote :

Same problem with Kubuntu Edgy Eft running on a Samsung R50 laptop.
Looking forward for a solution.
p.d.: Neither suspending run on my lap.

Revision history for this message
dany-r5 (dany-r5) wrote :

Tested with kernels: 2.6.18-4-686 (on Debian Etch) and 2.6.17-12-generic (Ubuntu Edgy).
Also in PCLinuxOS (I don't remember which kernel version).
The same problem in all of them. I hope someone will patch it for next kernel versions.
p.d.: suspending to ram is not related.

Revision history for this message
Jonathan Jesse (jjesse) wrote :

I didn't realize this bug was still open, I no longer have the Toshiba A70 to test this any further to see if there is still a problem. Could someone that has a Toshiba verify if this bug is still a problem in Gutsy?

Thanks,

JOnathan

Revision history for this message
Brian Murray (brian-murray) wrote :

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 .

Changed in linux-source-2.6.17:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Jonathan Jesse (jjesse) wrote :

Is there anyone who can test this to verify if this is still a problem? I no longer have a Toshiba to test either Hardy or Gutsy

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

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.

Changed in linux-source-2.6.17:
status: Confirmed → Invalid
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

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.

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Kevin Colyer (kevin-ywambrussels) wrote :

I have a A70 and I have the same problem. I am running Hardy 8.04.1. cat /proc/acip/button/lid/*/* reports lid closed always whether depressed or not. Will try Intrepid when I have a chance.

Kevin

Revision history for this message
alistair (alistair-tyeurgain) wrote :

I now have this problem on an HP Compaq nx7400 having upgraded to 8.10RC.

The following is produced whether the lid is open or closed.

cat /proc/acpi/button/lid/*/*
type: Lid Switch
state: open

This is a regression, since the lid switch was properly detected on 8.04.

A

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

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.

Revision history for this message
Manoj Iyer (manjo) wrote :

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks.

Revision history for this message
Irving Leonard (irvingleonard) wrote :

This is still an issue in 8.04.2 with kernel:
#uname -a
Linux miriam-laptop 2.6.24-24-generic #1 SMP Wed Apr 15 15:54:25 UTC 2009 i686 GNU/Linux
kernel package version: 2.6.24-24.53
laptop model: PSA70C-DD100E (http://www.toshiba.ca/web/product.grp?lg=en&section=1&group=223&product=3150&part=2631#spectop)

Revision history for this message
Bryan Wu (cooloney) wrote :

@Ivring, could you please try latest Jaunty release as Manoj said? if it fails, please also try our latest mainline build from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.5/ or http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30/

Revision history for this message
Bryan Wu (cooloney) wrote :

Here is the stock reply for this bug:

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . If the issue remains in Jaunty, Please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-2.6.28-11-generic <bug #>

If you could also test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.
-Bryan

Bryan Wu (cooloney)
tags: added: needs-kernel-logs
removed: cft-2.6.27 edgy-close
tags: added: needs-upstream-testing
Revision history for this message
Colin Ian King (colin-king) wrote :

This bug report was marked as Incomplete a while ago and has not had any feedback to provide the requested information. As a result this bug is being closed. Please reopen if this is still an issue in the latest Karmic 9.10 Alpha release http://cdimage.ubuntu.com/releases/karmic/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
Changed in linux:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.