[ltp] Bluetooth button not working after installing Debian 2.6.29 kernel

[Bjørn Mork]

Henrique de Moraes Holschuh <hmh@hmh.eng.br> writes:
> On Wed, 25 Mar 2009, Bjørn Mork wrote:
>> config thing.  I noticed that Debian now has disabled
>> CONFIG_ACPI_PROC_EVENT.  Could this be related?
>
> Yes.  Without CONFIG_ACPI_PROC_EVENT you will get hotkey events *ONLY*
> through the thinkpad-acpi input device.
>
> It has been that way for more than one year, now.  It is warned everywhere
> in the driver, there is even a backwards compatibility strategy in place,
> which won't help you because acpid never got fixed to deal with netlink
> events.

Thanks for the info.  I guess I should have been able to dig that up by
myself. 

But it's certainly something for the Debian kernel and acpid maintainers
to be aware of.

> Me, I will move my hotkey acpid scripts to HAL one of these days.  It is
> where they belong in the new order (until it becomes the NewNew order and
> HAL beats the dust, that is...).

Right.  I've been trying to avoid using HAL for this.  Guess there's no
way around it anymore.

>
>> Or were there major changes to the thinkpad stuff bwteen 2.6.29-rc6 and
>> the final release?
>
> None.  It is all because of that CONFIG_ACPI_PROC_EVENT change in your
> kernel config.
>
> In fact, CONFIG_ACPI_PROC_EVENT disabled makes Debian acpid USELESS, since
> it has never been updated to deal with netlink events AFAIK.  My guess is
> that it is a bug in the kernel config, and that it was not done on purpos=
e.

I don't think so.  From the changelog:

linux-2.6 (2.6.29-1) unstable; urgency=low
  ..
  [ maximilian attems ]
  ..
  * topconfig unset legacy SCSI_PROC_FS, PCMCIA_IOCTL, ACPI_PROCFS_POWER,
    ACPI_PROC_EVENT.


I believe it was discussed on the debian-kernel list before the release,
but I weren't aware of the acpid problems then.

Do you think this still should be reported as a kernel bug, or is the
correct way forward to fix acpid ASAP?


Bjørn