SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have just finished installing suse 9.1 on my new laptop. Now when i log in i get the following message "the powersave deamon is not running or you are not a member of powersave system group. Starting it will improove performance /usr/sbin/rcpowersave start"
I really would like to use powersave features as the machine is a laptop, but in yast/security and users when i open to make me (the user) a member of powersave system group, there is no powersave group to which to make me a member.
Iqually in yast/system/power management (when I try to set it up) I got an error message stating that it can not restart powersave deamon.
Any idea? I really would like to use this features
Do you get any specific error messages? Try to start powersaved from console (type '/etc/init.d/powersave start' as root) and have a look what it says. Otherwise have a look in /var/log/messages.
I've had SuSE 9.2 Pro for about 6 months and in the early days of the many times I unistall / installs I had this error. I cannot be positive how I adressed it, but I do know that I tried to resolve this through YaST with out success.
At the same time there was another message error that I got upon boot -- along with the error message that you are getting -- that told me to adjust my screen size through SAX2. No matter what I tried I'd no success.
With the screen issue, a YaST on-line up-date eliminated this error message -- I can't be positive -- but also the -- again, I think -- the error message that you are getting.
Believe me, 6 months ago, I had no idea what I was doing and I think that an on-line up-date might help. At least it did for me with 9.2 Pro.
First of all I assume that it is not an online or update issue but some configuration thing because when i first installed this linux in the new machine it was working ok. I am now running the second install (i know i could have probably resolved my other problem without reinstalling the system but that is a newbee bad habbit) and I am now having this problem. Anyway i will keep in mind and try if things wont work out.
Ok I have checked out /var/log/masseges but I could not find any interesting entries which referred to this staff. Than I have tried out
/etc/init.d/powersave start but it stated that there is no such file or directory. So I tried the same but with the deamon (i guees)
/etc/init.d/powersaved start and i got the followindg reply
cpureq is allready running stop it first than start service
I suppose if i swith it of it might work
Anyway if you know where to do so (yast/sistem ?) it could save me some time
You shouldn't run cpufreqd together with powersaved. At least thats what SuSE recommends. Have a look in the runlevel editor of yast and deactivate it in case it's running.
Sorry for the wrong command, I wrote the first message from a windows machine and couldn't look at the correct syntax. Maybe the error came up because it was already running...to check this, you could try '/etc/init.d/powersaved restart' instead.
So finally the problem could be res just had to switch of cpufreq in the runlevele editor of yast as you suggested and now i could have a look on my remaning battery time, which earlier did not work
definitely don't run two different powersaving daemons together unless they definitely don't overlap. in other words if powersaved does cpu frequency throttling, kill cpufreqd or you'll just get your cpufreq system constantly changing frequency and governor and not saving you much power
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.