Ubuntu
linux-ubuntu-modules-2.6.24 package

  1. Bug #181177
  2. Comment #4

Comment 4 for bug 181177

Revision history for this message
Jerone Young (jerone) wrote :

So it's not thinkpad-acpi . The issue is very strange but basically any kernel past 2.6.22 displays it.

Now here is the kicker. The mute button actually mutes the. But the software (Gnome or KDE) does not pick it up when running on a kernel past 2.6.22. So the mixers are not aware that things have been muted. So you have no visual that things are muted.

Had a discussion on ibm-acpi-devel but it's not archived SO I'll past my results here:

System:
       Thinkpad T61
       Vendor: LENOVO
       Firmware Version: 7LETA7WW (2.07)
       EC Version: 1.08

Here are my test results (These are kernel.org kernels):

kernel 2.6.22.15 (w/ thinkpad-acpi v0.14) = Works great Gnome can see
                                                                      mute button pressed

Kernel 2.6.22.15 (with thinkpad-acpi v0.19) = Works great Gnome can see
                                                                        mute button pressed

kernel 2.6.23.13 (w/ thinkpad-acpi v0.16) = Gnome does NOT see mute is pressed
                                                              Mute button is not recogonized when try to
                                                               associate it with a keyboard action
                                                               using gnome-keybing-properties

kernel 2.6.24-rc7 (w/ thinkpad-acpi v0.17) = Gnome does NOT see mute is pressed
                                                              Mute button is not recogonized when try to
                                                              associate it with a keyboard action using
                                                               gnome-keybing-properties

Kernel 2.6.24-rc7 (with thinkpad-acpi v0.19) = Gnome does NOT see mute is pressed
                                                              Mute button is not recogonized when try to
                                                              associate it with a keyboard action using
                                                               gnome-keybing-properties