Hi,
I'm confused as to what my sleep button on my ASUS M6R laptop does. I want it to go into hibernation/suspend2disk for me, but instead it goes into some-sort of suspend2ram. My first problem is that it does not come up again when I press power. Second problem is that I have no clue as to what process/daemon/script catches the sleep button interrupt, so I can't change it.
I have already tried killing acpid, but I still goes into sus2disk. So I guess it's not some acpi script. I also tried disabling the button events in kpowersave. Still no change. Where else could this interrupt be caught?
Point of this is that I want the sleep button to active the uswsusp tools, which are working perfectly for me, to go into suspend2disk. I think that I can solve this with an acpi script since the button does get caught by acpi
So that would probably work, if not for the interrupt to get caught by some other process.
I am running kubuntu gutsy and:
Any help would be appreciated :-D
Thanks in advance, Jasper van Zuijlen
I'm confused as to what my sleep button on my ASUS M6R laptop does. I want it to go into hibernation/suspend2disk for me, but instead it goes into some-sort of suspend2ram. My first problem is that it does not come up again when I press power. Second problem is that I have no clue as to what process/daemon/script catches the sleep button interrupt, so I can't change it.
I have already tried killing acpid, but I still goes into sus2disk. So I guess it's not some acpi script. I also tried disabling the button events in kpowersave. Still no change. Where else could this interrupt be caught?
Point of this is that I want the sleep button to active the uswsusp tools, which are working perfectly for me, to go into suspend2disk. I think that I can solve this with an acpi script since the button does get caught by acpi
Code:
# cat /proc/acpi/event button/sleep SLPB 00000080 00000002 #
I am running kubuntu gutsy and:
Code:
$ uname -a Linux klapdoos 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 GNU/Linux $
Thanks in advance, Jasper van Zuijlen
Comment