If one decides to run both acpid and hald, acpid must be started before hald, otherwise hald will steal the /proc/acpi/event before acpid has an opportunity to take it. Last I checked, if hald sees acpid running when it starts, it will instead connect to the acpid socket. Having working acpid is important to nvidia users as the nvidia binary driver relies on it to provide power management notifications. Reproducible: Always
Created attachment 132482 [details, diff] Patches the init script Sorry, I patched the installed init script as opposed to the source in portage. Apply this change to portage/sys-power/acpid/files/acpid-*-init.d
Thank you very much, committed. This fix is also needed for stable.
x86 stable
This fix is wrong. HAL already has had "use acpid" for ages. Which works with both baselayout-1 and baselayout-2 for ensuring acpid is started before HAL is started. As long as you stick them in the same runlevel. Since HAL and acpid both belong in the default runlevel is should be a non-issue. As such, this fix is wrong.
ia64 stable
amd64 done.
where can I find info on properly dealing with this anyway? I've had acpid installed for ages. It worked like a charm. Along came hald and all of a sudden acpid fails to get /proc/acpi/events, which I suppose makes sense, as hald is using it now. Actually, the /proc/acpi, and /proc/acpi/events specifically, are since 2.6.23 depreciated. So I suppose that hald will use the /sys interface as such. However I have not found an acpid that utilizes hal to listen for such power events etc. Where is updated info to be found on this issue?
