Prev: unionsfs or aufs
Next: "yenc" encoding
From: Tuxedo on 16 Jan 2010 06:46
Hi,

I recently installed Slackware 12.2 on a notebook. I first did a test
install using the speakup kernel. At the time I found the
suspension/hibernation worked out of the box with the hardware, like
it does in XP on the same system. Shutting the lid simply makes the system
suspend or hibernate or go on a stand-by and activated by a button again.

I did a reinstall of 12.2 as I think I broke some other things while
experimenting with the original installation. For this second installation
I'm now using the smp kernel. I've not compiled a custom kernel or
anything, just running it our of the box so to speak. However, for some
reason the suspension, hibernation or stand-by feature does not work, which
may or may not have anything to with the different kernel option.

As root, I can check or uncheck various options via the ACPI config tab of
the Laptop Battery section in the KDE Control Center. These are the
available options:

* Enable Standby
* Enable Suspend
* Enable Hibernate
* Enable performance profiles
* Enable CPU throttling

I tested each individual option as well as all together, but with no effect.
If log into KDE as a non-root user, the above options are inactive and
cannot be changed and there is a note that says:

"If the above boxes are disabled then there is no 'helper' application set
up to help change ACPCI states, there are two ways you can enable this
application, either make the file /proc/acpci/sleep writeable by anyone
every time your system boots or use the button below to make the KDE ACPCI
helper application set-uid root."

Button: [ Setup Helper Appication ]

If I click above, there is an alert which says: ...

"The /usr/bin/klaptop_acpci_helper application does not seem to have the
same checksun as when it was compiled we do NOT recommend you proceed with
making it setuid-root without further investigation."

[ Run Nevertheless ] [ Cancel ]


.... which doesn't sound good, so I press Cancel.

Anyway, ACPI is obviously not a KDE only application. Where could the error
be and what could I look for to try and make the power-down/up ACPI
features work?

Thanks for any tips.

Tuxedo




From: allend on 16 Jan 2010 09:59
Have you made appropriate entries in the 'power' group?
From: Tuxedo on 16 Jan 2010 13:24
allend wrote:

> Have you made appropriate entries in the 'power' group?

Thanks for thinking of that, a good point. In fact, I had to double check in
case I had forgotten to add the power group at the install stage, but found
that the 'groups' command return the following groups for me as a user,
which includes 'power':

users floppy audio video cdrom plugdev power

While if I'm root, the groups command return:

root bin daemon sys adm disk wheel floppy audio video cdrom tape plugdev

I guess it must be something else than a missing group permission.

Tuxedo
From: Tuxedo on 16 Jan 2010 16:44
I wrote:

> I guess it must be something else than a missing group permission.

I clicked the "Setup Helper Application" button
(/usr/bin/klaptop_acpci_helper) in spite of the checksum warning and the
various sleep modes appear to work, although not exactly as originally by
simply closing the lid, but at least I can hypernate and fall asleep by
clicking the KDE KLaptop battery monitor :-).

Tuxedo


From: Tuxedo on 16 Jan 2010 17:58
I wrote:

> clicking the KDE KLaptop battery monitor :-).

Actually, I found the lid-switch: K -> Power Control -> Laptop Battery ->
Button Actions -> Lid Switch Closed:
( ) Suspend
( ) Hibernate
( ) System Power Off
( ) Log Out
(*) Off
[ ] CPU throttle

No wonder it didn't work, it was off!

Now I can sleep by simply closing the lid. Slackware is totally userfriendly
after all, despite popular opinion it might not be.

Tuxedo



 | 
Pages: 1
Prev: unionsfs or aufs
Next: "yenc" encoding