On Tue 31. Jan 00:30:30, oleksandr korneta wrote:
> 
> 
> on 01/30/2006 09:42 AM Holger Macht wrote:
> 
> >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.
> hm... seems like changing
> /etc/rc5.d/S92powersave
> to
> /etc/rc5.d/S98powersave
> did the trick. Now it really starts after hal.
>  the only errors are
> Jan 31 00:04:27 localhost [powersave]: ERROR (PM_Interface:89) Haldaemon 
> not running. Battery or ac adapter information will not be available.

This is caused by a non existant pid file. We test for
/var/run/haldaemon.pid to be sure that hal is running (hal might run but
does not export its information yet). Notsice, therefore it will change...

> Jan 31 00:04:27 localhost [powersave]: WARNING (ACPI_Interface:49) could 
> not set battery alarm

This warning got removed in newer versions, because it really doesn't
matter whether setting the battery alarm succeeded (which is not possible
on all systems). Hal polls the battery information anyway.

> 
> I do suspect that this is some kind of cosmetic error, but just curious 
> what does it mean or what is the reason.

See above.

> 
> 
> >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...
> I would be glad to help but I've never done it before, therefore it 
> might take a while. Sorry :)

No problem. I did not ment that you should write it, I just wanted to
point out that distribution specific things maybe have to be done by the
distributions or their users themselves.


Thanks for your feedback,
       Holger
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel

Reply via email to