Problem: Cannot connect to Acpid

[Kay Sievers]

On Thu, Dec 29, 2005 at 02:39:09PM +0100, Fabian Zeindl wrote:
> Richard Hughes wrote:
> > Try adding
> > 
> > --disable-acpi-acpid
> > or
> > --disable-acpi-proc
> > 
> > to the configure line. I think the configure line is confusing and needs
> > to be changed:

What is confusing here? You have two possible event sources, HAL can
figure out automatically which one to use. You can "configure" to disable
one of the sources. If you disable both you don't have _any_ event.

> > --disable-acpi-acpid     Use ACPI daemon event source
> > --disable-acpi-proc      Use ACPI kernel-interface directly(the kernel 
> > 			 supports only one listener)
> 
> Ok, when I add both options it works. Weirdly "--disable-acpi-acpi-proc"
> Enables the acpi proc source and --disable-acpi-acpid disables the use
> of acpid. As far as I understood if you want acpi support at all you
> need "--disable-acpi-acpi-proc" and if you don't want to use acpid (=
> use /proc/acpi/event directly) you need "--disable-acpi-acpid too".

Just leave them alone and HAL should work just fine. No need to
configure anything.

> If I'm right, this should be fixed in configure.
> (--disable-acpi-acpi-proc source should be renamed to
> --enable-acpi-acpi-proc)

There is nothing to fix on the option naming. If it doesn't work as
expected it's a bug in the HAL code not in the options. It should work
fine even without any of the options given.

Btw:
These options have been added, cause the guys involved are unable to
find a common solution for powermanagement. In the long run, acpid
should die and entirely replaced by HAL. Acpid is just a too simple
and plain stupid. Events like:
  "ibm/bay MSTR 00000003 00000000"
are close to useless for userspace. HAL must translate that to a
"UnlockDrive" event of the cdrom drive or such a thing, which is
actually some sort of useful to userspace. But it still needs a lot
of work until we reach this...

Kay