On Mon 30. Jan 08:55:33, oleksandr korneta wrote:
> 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.
Then I think the sequence in which dbus, hal and powersaved are started is
wrong. Make sure that at first dbus, then acpid, then hal and finally
poweraved is started.
Oh I see that there has to be done some more work for the init script. But
I still hope that someone more familiar with FC4 would do this. If not,
we have to do it on our own...
[...]
Regards,
Holger
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel
