Problem: Cannot connect to Acpid

[Kay Sievers]

On Thu, Dec 29, 2005 at 06:52:35PM +0000, Richard Hughes wrote:
> On Thu, 2005-12-29 at 19:23 +0100, Kay Sievers wrote:
> > 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.
> 
> What I meant is the configure.in explanation is odd. Shouldn't the help
> text be:
> 
> --disable-acpi-acpid     Disable the ACPI daemon event source
> --disable-acpi-proc      Disable the ACPI kernel-interface directly (the kernel 
> 			 supports only one listener)

Yeah sure, that sounds a lot better.

Kay