Holger,
on 01/30/2006 06:20 AM Holger Macht wrote:
[...]
I'm still getting the following error:
Jan 29 00:29:45 localhost [powersave]: ERROR (PM_Interface:89) Haldaemon
not running. Battery or ac adapter information will not be available.
If you are sure that the hal daemon is running, you can ignore it.
Jan 29 00:29:45 localhost [powersave]: WARNING (ACPI_Interface:49) could
not set battery alarm
Jan 29 00:29:45 localhost [powersave]: ERROR (MainLoop:59) Error setting
up connection to DBus system bus. Aborting...
That's strange. You told us that you could set the cpu frequency policy
with gkrellm-powersave, so there has to be a connection to the system bus.
ok, seems there is misconception here. Yes, the daemon is working, but
only if I start it manually as root.
# /usr/sbin/powersaved -d
then I can do cpu-frequency policy and stuff...
However it _never_ start properly at system boot.
Please verify with 'dbus-monitor --system' as root that you can connect
DBus. Switch the powersave scheme with 'powersave -e <scheme name>' (get
list of schemes with 'powersave -x) as user. If both commands work, I
really have no idea and you can simply ignore those messages.
there is no daemon at this time.
see the note above
and probably because of that that the powersave daemon does not start.
Is there any place (file/parameter) I should check? Any suggestions?
Huh? I thought it started already because you used gkrellm-powersave...
see the note above
[...]
--
regards,
Oleksandr Korneta
/The nice thing about standards is that there are so many to choose from./
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel
