LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Laptop and Netbook (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/)
-   -   Laptop suspends, but then shutsdown on wakeup (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/laptop-suspends-but-then-shutsdown-on-wakeup-421999/)

jturnbul 03-05-2006 09:04 PM

Laptop suspends, but then shutsdown on wakeup
 
Im using a Toshiba Satellite M30 laptop, with FC4 and the latest kernel.

I have Klaptop configured to suspend when the lid closes. I have also used the command

$ echo -n "mem" > /sys/power/state

which I believe is the same thing. In any case the laptop appears to go in suspension without any issues, but when I bring it out of suspension, my laptop wakes up for a brief second where my screen restores, and I can see my desktop, and even move my mouse. This last for maybe 1 second at best. Then my screen goes blank, and after 10-15 seconds of hard drive action, my system powers down.

If you look in my /var/log/acpid it I notice that after the laptop comes out of suspend, the command is given to shutdown -h now

That is obviously the culprit, but how do I stop it??? I have tried looking through the file system where these commands are found, for some type of file to edit, but have yet to find one that has the shutdown command in it to edit out.

The real funny part of this is, I used to have FC1 or 2 on my laptop awhile back, and it worked perfectly, before I switched to slackware for a year. I had no problems with acpi on slack. I switched back to Fedora, because I found I was spending to much time configurring slack, then using my laptop for enjoyment. Now im using FC4, and everything works flawless but suspend. I cant win.

any ways here's my log. I've printed two logs

[Sun Mar 5 10:23:30 2006] received event "button/lid LID 00000080 00000001"
[Sun Mar 5 10:23:30 2006] notifying client 2236[0:0]
[Sun Mar 5 10:23:30 2006] completed event "button/lid LID 00000080 00000001"
[Sun Mar 5 10:27:50 2006] received event "button/power PWRF 00000080 00000001"
[Sun Mar 5 10:27:50 2006] notifying client 2236[0:0]
[Sun Mar 5 10:27:50 2006] executing action "/sbin/shutdown -h now"
[Sun Mar 5 10:27:50 2006] BEGIN HANDLER MESSAGES
[Sun Mar 5 10:27:55 2006] END HANDLER MESSAGES
[Sun Mar 5 10:27:55 2006] action exited with status 0
[Sun Mar 5 10:27:55 2006] completed event "button/power PWRF 00000080 00000001"
[Sun Mar 5 10:27:55 2006] received event "battery BAT1 00000080 00000001"
[Sun Mar 5 10:27:55 2006] notifying client 2236[0:0]
[Sun Mar 5 10:27:55 2006] completed event "battery BAT1 00000080 00000001"
[Sun Mar 5 10:27:57 2006] exiting
[Sun Mar 5 10:29:41 2006] starting up
[Sun Mar 5 10:29:41 2006] 1 rule loaded
[Sun Mar 5 10:29:43 2006] received event "battery BAT1 00000080 00000001"
[Sun Mar 5 10:29:43 2006] completed event "battery BAT1 00000080 00000001"
[Sun Mar 5 10:29:54 2006] client connected from 2279[0:0]
[Sun Mar 5 10:29:54 2006] 1 client rule loaded


[Sun Mar 5 10:41:34 2006] received event "button/lid LID 00000080 00000001"
[Sun Mar 5 10:41:34 2006] notifying client 2279[0:0]
[Sun Mar 5 10:41:34 2006] completed event "button/lid LID 00000080 00000001"
[Sun Mar 5 10:43:19 2006] received event "button/power PWRF 00000080 00000001"
[Sun Mar 5 10:43:19 2006] notifying client 2279[0:0]
[Sun Mar 5 10:43:19 2006] executing action "/sbin/shutdown -h now"
[Sun Mar 5 10:43:19 2006] BEGIN HANDLER MESSAGES
[Sun Mar 5 10:43:24 2006] END HANDLER MESSAGES
[Sun Mar 5 10:43:24 2006] action exited with status 0
[Sun Mar 5 10:43:24 2006] completed event "button/power PWRF 00000080 00000001"
[Sun Mar 5 10:43:24 2006] received event "battery BAT1 00000080 00000001"
[Sun Mar 5 10:43:24 2006] notifying client 2279[0:0]
[Sun Mar 5 10:43:24 2006] completed event "battery BAT1 00000080 00000001"
[Sun Mar 5 10:43:24 2006] received event "battery BAT1 00000080 00000001"
[Sun Mar 5 10:43:24 2006] notifying client 2279[0:0]
[Sun Mar 5 10:43:24 2006] completed event "battery BAT1 00000080 00000001"
[Sun Mar 5 10:43:27 2006] exiting
[Sun Mar 5 10:46:54 2006] starting up
[Sun Mar 5 10:46:54 2006] 1 rule loaded
[Sun Mar 5 10:47:07 2006] client connected from 2254[0:0]
[Sun Mar 5 10:47:07 2006] 1 client rule loaded

Simon Bridge 03-05-2006 09:30 PM

Hmmm, that's the culprit all right.

Can you suspend from the logout menue instead of the lid button?
Meanwhile - I'll check.

jturnbul 03-05-2006 11:02 PM

using KDE its not even an option.
end current session
turn off computer
restart computer

thats my choices.

jturnbul 03-06-2006 04:54 PM

For what ever reason its giving two commands when the lid opens.

"button/lid LID"
"button/power PWRF"

Dont ask me why it would be programmed to even run that event when the lid is opened, but it is default, cause I havee not messed with any configuration of that nature.

Simon Bridge 03-07-2006 03:38 AM

Just a thought - when you open the lid, do it carefully and slowly and watch exactly what happens around the power button.

It could be that your lid fits so closely, thet it is brushing the power button when it is opened. (especially if the lid has taken a knock at some point in its life) This would have exactly the effect described.

Of course, and in any rate, you could work around this trouble by disabling the power button. In this case, though, you would have to power-off from the logout menue.

jturnbul 03-07-2006 09:23 AM

Some how I found a solution.

I downloaded acpitool.

and messed around with the command.
Code:

acpitool -W x
my wakeup config origianlly looked like this
Code:

[root@jnt-laptop ~]# acpitool -w
  Device      Sleep state    Status
  ---------------------------------------
  1. USB1          3            disabled
  2. USB2          3            disabled
  3. USB4          3            disabled
  4.  LAN          4            disabled
  5. MPC0          3            disabled
  6. MPC1          3            disabled
  7. VIY0          3            disabled
  8. AMDM          3            disabled
  9.  LID          4            * enabled
  10. PWRB        4            * enabled

after playing around it looked like this, and I couldnt restore it to defaults. The tool seems quirky
Code:

[root@jnt-laptop ~]# acpitool -w
  Device      Sleep state    Status
  ---------------------------------------
  1. USB1          3            disabled
  2. USB2          3            disabled
  3. USB4          3            disabled
  4.  LAN          4            enabled
  5. MPC0          3            enabled
  6. MPC1          3            enabled
  7. VIY0          3            enabled
  8. AMDM          3            disabled
  9.  LID          4            * enabled
  10. PWRB        4            * enabled

I left it like that, and now it works. So I guess I cant complain.

The real funny part is, when I checked acpitool -w right now for this post, it now looks like the origianl. Yet my suspend still works, so go figure.

Thanks for the help.


All times are GMT -5. The time now is 12:43 PM.