[Pkg-acpi-devel] Bug#560702: Brightness keys do not work on Thinkpad X301 with kernel 2.6.30

Christopher Desjardins cddesjardins at gmail.com
Fri Dec 11 16:17:36 UTC 2009 

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 <
cddesjardins at gmail.com> wrote:

> 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 Set 2 keyboard) opened successfully
> /dev/input/event10 (SynPS/2 Synaptics TouchPad) opened successfully
> /dev/input/event11 (TPPS/2 IBM TrackPoint) opened successfully
> /dev/input/event2 (ThinkPad Extra Buttons) opened successfully
> /dev/input/event3 (Power Button (FF)) opened successfully
> /dev/input/event4 (Lid Switch) opened successfully
> /dev/input/event5 (Sleep Button (CM)) opened successfully
> /dev/input/event6 (Video Bus) opened successfully
> /dev/input/event7 (Video Bus) opened successfully
>
> add_connection(): Too many connections.
> /dev/input/event8 (UVC Camera (17ef:4807)) opened successfully
>
> add_connection(): Too many connections.
> /dev/input/event9 (PC Speaker) opened successfully
>
> add_connection(): Too many connections.
> Netlink ACPI Family ID: 17
> Netlink ACPI Multicast Group ID: 1
> netlink opened successfully
> add_connection(): Too many connections.
> Press Escape to exit, or Ctrl-C if that doesn't work.
> Input Layer:  Type: 4  Code: 4  Value: 28
> Input Layer:  Type: 1  Code: 28  Value: 0
> Input Layer:  Sync
> /proc/acpi/event: ibm/hotkey HKEY 00000080 00001010
> /proc/acpi/event: video LCD0 00000086 00000000
> Input Layer:  Type: 1  Code: 225  Value: 1
> Input Layer:  Sync
> Input Layer:  Type: 1  Code: 225  Value: 0
> Input Layer:  Sync
> /proc/acpi/event: ibm/hotkey HKEY 00000080 00001010
> /proc/acpi/event: video LCD0 00000086 00000000
> Input Layer:  Type: 1  Code: 225  Value: 1
> Input Layer:  Sync
> Input Layer:  Type: 1  Code: 225  Value: 0
> Input Layer:  Sync
> /proc/acpi/event: ibm/hotkey HKEY 00000080 00001011
> /proc/acpi/event: video LCD0 00000087 00000000
> Input Layer:  Type: 1  Code: 224  Value: 1
> Input Layer:  Sync
> Input Layer:  Type: 1  Code: 224  Value: 0
> Input Layer:  Sync
> /proc/acpi/event: ibm/hotkey HKEY 00000080 00001011
> /proc/acpi/event: video LCD0 00000087 00000000
> Input Layer:  Type: 1  Code: 224  Value: 1
> Input Layer:  Sync
> Input Layer:  Type: 1  Code: 224  Value: 0
> Input Layer:  Sync
> /proc/acpi/event: ibm/hotkey HKEY 00000080 00001011
> /proc/acpi/event: video LCD0 00000087 00000000
> Input Layer:  Type: 1  Code: 224  Value: 1
> Input Layer:  Sync
> Input Layer:  Type: 1  Code: 224  Value: 0
> Input Layer:  Sync
> /proc/acpi/event: ibm/hotkey HKEY 00000080 00001010
> /proc/acpi/event: video LCD0 00000086 00000000
> Input Layer:  Type: 1  Code: 225  Value: 1
> Input Layer:  Sync
> Input Layer:  Type: 1  Code: 225  Value: 0
> Input Layer:  Sync
> /proc/acpi/event: ibm/hotkey HKEY 00000080 00001010
> /proc/acpi/event: video LCD0 00000086 00000000
> Input Layer:  Type: 1  Code: 225  Value: 1
> Input Layer:  Sync
> Input Layer:  Type: 1  Code: 225  Value: 0
> Input Layer:  Sync
> /proc/acpi/event: ibm/hotkey HKEY 00000080 00001010
> /proc/acpi/event: video LCD0 00000086 00000000
> Input Layer:  Type: 1  Code: 225  Value: 1
> Input Layer:  Sync
> Input Layer:  Type: 1  Code: 225  Value: 0
> Input Layer:  Sync
> /proc/acpi/event: ibm/hotkey HKEY 00000080 00001011
> /proc/acpi/event: video LCD0 00000087 00000000
> Input Layer:  Type: 1  Code: 224  Value: 1
> Input Layer:  Sync
> Input Layer:  Type: 1  Code: 224  Value: 0
> Input Layer:  Sync
> /proc/acpi/event: ibm/hotkey HKEY 00000080 00001011
> /proc/acpi/event: video LCD0 00000087 00000000
> Input Layer:  Type: 1  Code: 224  Value: 1
> Input Layer:  Sync
> Input Layer:  Type: 1  Code: 224  Value: 0
> Input Layer:  Sync
>
> Code 225 corresponds to Fn+Home (up brightness) and Code 224 corresponds to
> Fn+End (down brightness)
>
>
>
>
> On Fri, Dec 11, 2009 at 10:07 AM, Christopher Desjardins <
> cddesjardins at gmail.com> wrote:
>
>> 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 emulation) opened successfully
>> /dev/input/event1 (AT Translated Set 2 keyboard) opened successfully
>> /dev/input/event10 (HDA Intel Mic) opened successfully
>> /dev/input/event11 (HDA Intel Headphone) opened successfully
>> /dev/input/event12 (SynPS/2 Synaptics TouchPad) opened successfully
>> /dev/input/event13 (TPPS/2 IBM TrackPoint) opened successfully
>> /dev/input/event2 (Power Button) opened successfully
>> /dev/input/event3 (Lid Switch) opened successfully
>> /dev/input/event4 (Sleep Button) opened successfully
>> /dev/input/event5 (ThinkPad Extra Buttons) opened successfully
>> /dev/input/event6 (UVC Camera (17ef:4807)) opened successfully
>> add_connection(): Too many connections.
>> /dev/input/event7 (PC Speaker) opened successfully
>> add_connection(): Too many connections.
>> /dev/input/event8 (HDA Intel Headphone) opened successfully
>> add_connection(): Too many connections.
>> /dev/input/event9 (HDA Intel Mic) opened successfully
>> add_connection(): Too many connections.
>> Netlink ACPI Family ID: 17
>> Netlink ACPI Multicast Group ID: 1
>> netlink opened successfully
>> add_connection(): Too many connections.
>> Press Escape to exit, or Ctrl-C if that doesn't work.
>> Input Layer:  Type: 4  Code: 4  Value: 28
>> Input Layer:  Type: 1  Code: 28  Value: 0
>> Input Layer:  Sync
>>
>> When I press the brightness keys w/o the function key held down I get:
>>
>> Input Layer:  Type: 4  Code: 4  Value: 199
>> Input Layer:  Type: 1  Code: 102  Value: 1
>> Input Layer:  Sync
>> ^[OHInput Layer:  Type: 4  Code: 4  Value: 199
>> Input Layer:  Type: 1  Code: 102  Value: 0
>> Input Layer:  Sync
>> Input Layer:  Type: 4  Code: 4  Value: 207
>> Input Layer:  Type: 1  Code: 107  Value: 1
>> Input Layer:  Sync
>> ^[OFInput Layer:  Type: 4  Code: 4  Value: 207
>> Input Layer:  Type: 1  Code: 107  Value: 0
>> Input Layer:  Sync
>>
>> However, when I hold down Fn+Home or Fn+End I get no response.  I do get
>> response from holding down Fn+<other thinkpad keys>. This is the same thing
>> with xev.
>>
>> Regarding your acpi-netlink ... is that a package I should install? Should
>> I run kacpimon w/ the 2.6.26 and report those values to this report?
>>
>> Thanks again for the spending response I really appreciate it!
>> Chris
>>
>>
>> On Fri, Dec 11, 2009 at 9:10 AM, Ted Felix <ted at tedfelix.com> wrote:
>>
>>>  Gnome bypasses acpid, so it sounds like the 2.6.30 kernel doesn't have
>>> thinkpad support turned on, and that's needed for your brightness keys.
>>>
>>>  Try running kacpimon and see if you get any events for the brightness
>>> keys at all.
>>>
>>> http://tedfelix.com/linux/kacpimon-20091120.tar.gz
>>>
>>>  Also see my acpid page for the latest news.
>>>
>>> http://tedfelix.com/linux/acpid-netlink.html
>>>
>>> Ted.
>>>
>>> Christopher David Desjardins wrote:
>>>
>>>> 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 when
>>>> upgrading the kernel and acpid from backports. I then reinstalled and
>>>> upgraded to squeeze and used the acpid and kernel image from the testing
>>>> repository and it had the same effect.
>>>> Just for fun, I threw in a Ubuntu CD (9.10) to see if my brightness keys
>>>> would work and they do. I am curious what Ubuntu does here that's
>>>> different than Debian? I am curious if CONFIG_ACPI_PROC_EVENT is still
>>>> disabled from the kernel?
>>>>
>>>> I also think that bug 521280 is similar to this report. However, that
>>>> bug appears fixed and thus why I'm opening a new report.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-acpi-devel/attachments/20091211/e4d659fd/attachment-0001.htm>

More information about the Pkg-acpi-devel mailing list