Bug#819100: linux-image-4.4.0-1-amd64: Mute and Mic-Mute LEDs no longer work on Thinkpad T410
On 24/03/16 02:10, Alex Goebel wrote: > In 3.19, the way the kernel handles that button was changed from > hardware to software. You'll need > > options thinkpad_acpi software_mute=0 > > in modprobe.d/ to get the old behaviour back. Thanks Alex, that did the trick. Could this be added by default so as not to break existing functionality on upgrade? > > -Alex >
Bug#819100: linux-image-4.4.0-1-amd64: Mute and Mic-Mute LEDs no longer work on Thinkpad T410
On 23/03/16 21:32, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Wed, 2016-03-23 at 18:53 +, Tim Wootton wrote: >> Package: src:linux >> Version: 4.4.6-1 >> Severity: normal >> >> Dear Maintainer, >> >>* What led up to the situation? >> Upgrade from jessie to stretch >>* What exactly did you do (or not do) that was effective (or >> ineffective)? >> Pressing Thnkpad T410's hardware speaker mute button >>* What was the outcome of this action? >> Speaker mutes, but the button's LED does not illuminate >>* What outcome did you expect instead? >> Expected the LED to illuminate >> >> The mic mute button also exhibits the same behavior, but I had not >> tried this under jessie so don't know if it worked before. > It hasn't worked for me on the quite similar T420. > >> The speaker mute certainly did. > [...] > > As far as the kernel is concerned, the mute button is just an ordinary > key on the keyboard (you can see this with the evtest program). You > need a userland daemon to act on it (such as pulseaudio). What desktop > environment are you using? The button is working fine, it's the LED that's not. I see this from the kernel module docs which implies userspace is not the answer. "Audio mute and microphone mute LEDs are supported, but currently not visible to userspace. They are used by the snd-hda-intel audio driver." I'm using KDE5. > > Ben. >
Bug#819100: linux-image-4.4.0-1-amd64: Mute and Mic-Mute LEDs no longer work on Thinkpad T410
In 3.19, the way the kernel handles that button was changed from hardware to software. You'll need options thinkpad_acpi software_mute=0 in modprobe.d/ to get the old behaviour back. -Alex
Bug#819100: linux-image-4.4.0-1-amd64: Mute and Mic-Mute LEDs no longer work on Thinkpad T410
On Wed, 2016-03-23 at 21:32 +, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Wed, 2016-03-23 at 18:53 +, Tim Wootton wrote: > > > > Package: src:linux > > Version: 4.4.6-1 > > Severity: normal > > > > Dear Maintainer, > > > > * What led up to the situation? > > Upgrade from jessie to stretch > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > Pressing Thnkpad T410's hardware speaker mute button > > * What was the outcome of this action? > > Speaker mutes, but the button's LED does not illuminate > > * What outcome did you expect instead? > > Expected the LED to illuminate > > > > The mic mute button also exhibits the same behavior, but I had not > > tried this under jessie so don't know if it worked before. > It hasn't worked for me on the quite similar T420. > > > > > The speaker mute certainly did. > [...] > > As far as the kernel is concerned, the mute button is just an ordinary > key on the keyboard (you can see this with the evtest program). You > need a userland daemon to act on it (such as pulseaudio). Actually I'm not sure that's entirely true - I think that initially the firmware (BIOS) handles the mute button itself, but software can take responsibility for it. There are some hints here for debugging and working around this: https://wiki.archlinux.org/index.php/ThinkPad:_Mute_button Let us know if any of that helps. Ben. > What desktop environment are you using? -- Ben Hutchings Anthony's Law of Force: Don't force it, get a larger hammer. signature.asc Description: This is a digitally signed message part
Bug#819100: linux-image-4.4.0-1-amd64: Mute and Mic-Mute LEDs no longer work on Thinkpad T410
Control: tag -1 moreinfo On Wed, 2016-03-23 at 18:53 +, Tim Wootton wrote: > Package: src:linux > Version: 4.4.6-1 > Severity: normal > > Dear Maintainer, > > * What led up to the situation? > Upgrade from jessie to stretch > * What exactly did you do (or not do) that was effective (or > ineffective)? > Pressing Thnkpad T410's hardware speaker mute button > * What was the outcome of this action? > Speaker mutes, but the button's LED does not illuminate > * What outcome did you expect instead? > Expected the LED to illuminate > > The mic mute button also exhibits the same behavior, but I had not > tried this under jessie so don't know if it worked before. It hasn't worked for me on the quite similar T420. > The speaker mute certainly did. [...] As far as the kernel is concerned, the mute button is just an ordinary key on the keyboard (you can see this with the evtest program). You need a userland daemon to act on it (such as pulseaudio). What desktop environment are you using? Ben. -- Ben Hutchings Anthony's Law of Force: Don't force it, get a larger hammer. signature.asc Description: This is a digitally signed message part
Bug#819100: linux-image-4.4.0-1-amd64: Mute and Mic-Mute LEDs no longer work on Thinkpad T410
Package: src:linux Version: 4.4.6-1 Severity: normal Dear Maintainer, * What led up to the situation? Upgrade from jessie to stretch * What exactly did you do (or not do) that was effective (or ineffective)? Pressing Thnkpad T410's hardware speaker mute button * What was the outcome of this action? Speaker mutes, but the button's LED does not illuminate * What outcome did you expect instead? Expected the LED to illuminate The mic mute button also exhibits the same behavior, but I had not tried this under jessie so don't know if it worked before. The speaker mute certainly did. -- Package-specific info: ** Version: Linux version 4.4.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20160307 (Debian 5.3.1-11) ) #1 SMP Debian 4.4.6-1 (2016-03-17) ** Command line: BOOT_IMAGE=/vmlinuz-4.4.0-1-amd64 root=UUID=39ff419a-8bff-4244-8eb5-99350d8b0857 ro quiet ** Not tainted ** Kernel log: [14809.730381] e1000e: EEE TX LPI TIMER: [14810.141902] PM: suspend of devices complete after 632.222 msecs [14810.157976] PM: late suspend of devices complete after 16.068 msecs [14810.158545] ehci-pci :00:1d.0: System wakeup enabled by ACPI [14810.158676] ehci-pci :00:1a.0: System wakeup enabled by ACPI [14810.158763] e1000e :00:19.0: System wakeup enabled by ACPI [14810.173934] PM: noirq suspend of devices complete after 15.953 msecs [14810.174073] ACPI: Preparing to enter system sleep state S3 [14810.353829] ACPI : EC: EC stopped [14810.353831] PM: Saving platform NVS memory [14810.354875] Disabling non-boot CPUs ... [14810.356197] smpboot: CPU 1 is now offline [14810.367529] smpboot: CPU 2 is now offline [14810.383427] smpboot: CPU 3 is now offline [14810.394876] ACPI: Low-level resume complete [14810.394936] ACPI : EC: EC started [14810.394936] PM: Restoring platform NVS memory [14810.395667] Enabling non-boot CPUs ... [14810.415359] x86: Booting SMP configuration: [14810.415360] smpboot: Booting Node 0 Processor 1 APIC 0x1 [14810.417931] cache: parent cpu1 should not be sleeping [14810.447212] CPU1 is up [14810.467385] smpboot: Booting Node 0 Processor 2 APIC 0x4 [14810.469787] cache: parent cpu2 should not be sleeping [14810.499215] CPU2 is up [14810.519422] smpboot: Booting Node 0 Processor 3 APIC 0x5 [14810.521848] cache: parent cpu3 should not be sleeping [14810.551218] CPU3 is up [14810.553552] ACPI: Waking up from system sleep state S3 [14810.887287] thinkpad_acpi: EC reports that Thermal Table has changed [14810.955420] ehci-pci :00:1a.0: System wakeup disabled by ACPI [14810.955549] sdhci-pci :0d:00.0: MMC controller base frequency changed to 50Mhz. [14810.90] ehci-pci :00:1d.0: System wakeup disabled by ACPI [14810.955826] PM: noirq resume of devices complete after 16.620 msecs [14810.957940] PM: early resume of devices complete after 2.094 msecs [14810.958109] e1000e :00:19.0: System wakeup disabled by ACPI [14810.958675] sd 0:0:0:0: [sda] Starting disk [14810.958701] sd 1:0:0:0: [sdb] Starting disk [14810.958730] iwlwifi :03:00.0: L1 Enabled - LTR Disabled [14810.958961] iwlwifi :03:00.0: L1 Enabled - LTR Disabled [14810.959057] iwlwifi :03:00.0: Radio type=0x1-0x3-0x1 [14810.960304] rtc_cmos 00:02: System wakeup disabled by ACPI [14811.187299] usb 1-1.4: reset full-speed USB device number 3 using ehci-pci [14811.229150] iwlwifi :03:00.0: L1 Enabled - LTR Disabled [14811.229367] iwlwifi :03:00.0: L1 Enabled - LTR Disabled [14811.229457] iwlwifi :03:00.0: Radio type=0x1-0x3-0x1 [14811.291290] ata5: SATA link down (SStatus 0 SControl 300) [14811.299305] ata6: SATA link down (SStatus 0 SControl 300) [14811.351304] usb 1-1.6: reset high-speed USB device number 4 using ehci-pci [14811.447234] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [14811.459303] sdhci-pci :0d:00.0: Will use DMA mode even though HW doesn't fully claim to support it. [14811.461590] PM: resume of devices complete after 503.613 msecs [14811.462070] PM: Finishing wakeup. [14811.462083] Restarting tasks ... [14811.463248] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [14811.465112] ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [14811.465118] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [14811.467131] ata2.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [14811.467136] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [14811.467249] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [14811.467253] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [14811.467533] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded [14811.467537] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [14811.468224] ata2.00: configured for UDMA/133 [14811.473061] done. [14811.474264] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [14811.474271]
