Bug#560702: Brightness keys do not work on Thinkpad X301 with kernel 2.6.30

2009-12-11 Thread Christopher Desjardins
Perhaps this is also relevant from /var/log/kern.log: Dec 11 10:51:03 debian kernel: [6.186288] thinkpad_acpi: ThinkPad ACPI Extras v0.23 Dec 11 10:51:03 debian kernel: [6.186294] thinkpad_acpi: http://ibm-acpi.sf.net/ Dec 11 10:51:03 debian kernel: [6.186298] thinkpad_acpi: ThinkPad B

Bug#560702: Brightness keys do not work on Thinkpad X301 with kernel 2.6.30

2009-12-11 Thread Christopher Desjardins
Also Ted, would using your package solve this issue for me and if so how do I install it? As far as I can tell all I run is 'make' but where would I put the resulting module (is that the right word?)? On Fri, Dec 11, 2009 at 10:11 AM, Christopher Desjardins < cddesjard...@gmail.com> wrote: > For

Bug#560702: Brightness keys do not work on Thinkpad X301 with kernel 2.6.30

2009-12-11 Thread Christopher Desjardins
For completeness I ran kacpimon in the 2.6.26 kernel and here's what I got: debian:/home/lontra/Desktop/kacpimon# ./kacpimon Kernel ACPI Event Monitor... /proc/acpi/event opened successfully /dev/input/event0 (Macintosh mouse button emulation) opened successfully /dev/input/event1 (AT Translated S

Bug#560702: Brightness keys do not work on Thinkpad X301 with kernel 2.6.30

2009-12-11 Thread Christopher Desjardins
Hi Ted, Thanks for the quick response. Running ./kacpimon as root I get: debian:/home/lontra/Desktop/kacpimon# ./kacpimon Kernel ACPI Event Monitor... open for /proc/acpi/event: No such file or directory (2) (ACPI proc filesystem may not be present) /dev/input/event0 (Macintosh mouse button emul

Bug#560702: Brightness keys do not work on Thinkpad X301 with kernel 2.6.30

2009-12-11 Thread Christopher David Desjardins
Package: acpid Version: 1.0.10-4 I was running Lenny and needed to upgrade my kernel to 2.6.30 for my wireless card. However, after upgrading my kernel to 2.6.30 my brightness keys no longer worked. I was also unable to adjust the brightness with gnome-power-manager. I initially noticed the issue