Suse/NovellThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Ok as i was just saying how happy i am about saving power with the acpi and powersaving in suse 9.2.. suddenly powersaved is locking up left and right. causes the whole system to come to such a crawl its almost locked, and almost as often it actually does lock. running "top" can see powersaved is the culprit, if i kill it all is well. I can even restart it and it'll run fine for a while. So what I've noticed is that powersaving is still working just fine (must be acpid) without powersaved. it was having the nice kpowersaved icon for a quick change of settings . is this a known issue and/or is there any other software out thats better with power management? Im using suse 9.2 (looks like 9.3 came out TODAY) and the version of powersaved thats current off my suse install source via yast (i did try removing and reinstalling for hahas, didnt even get that out of the process). i did a quick search online and i did see someone else looking for a script to see if powersaved was hung and to restart it if so.
So when you kill powersaved, acpid is running? AFAIK, you should never run powersaved and acpid in parallel, since they are interfering each other. I think acpid is the previous powermanagment before SuSE switched to powersaved in 9.1.
I have heard reports (not sure if any of this is true), that acpid runs better on laptops.
no kidding, i wonder. it was the default settings installing suse 9.2 so that would be a surprise but certainly possible i guess. ive been doing some further testing and from what i see its not locking up without kpowersaved running so maybe it was just that and not the actual powersaved (or im having a lucky stretch).
is there a home/project page for powersaved so i can find out more that anyone knows?
to answer your question yes: acpid,kacpid and powersaved are all running right now (i killed kpowersaved). Oddly power management is happening as i can see it with the external battery monitor i have hooked up, it will show me exactly how much power the pc is using so that will be useful to troubleshoot this. i will try later killing acpi (im not sure what the kacpid is, a frontend?)
I found the source of my previous information. This is from /usr/share/doc/packages/powersave/README_POWERSAVE:
This package unifies the control of power managing facilities on your
PC. It supports hardware based on ACPI, APM, IDE-disks and CPU
frequency scaling techniques. It takes over functionalities of the
APMD, ACPID, OSPMD and CPUFREQD (now called CPUSPEED) packages.
Therefore you should not install at least you must not run daemons from
these packages when you run the powersave daemon!
Note that acpid is not equal to acpi. Sure does powersave support acpi, but it does not run together with acpid, which has the same functionality. It is strange that both daemons are installed per default on your system.