https://bugzilla.novell.com/show_bug.cgi?id=849309
https://bugzilla.novell.com/show_bug.cgi?id=849309#c17
Takashi Iwai changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
InfoProvider| |bam@NightStorm.com
--- Comment #17 from Takashi Iwai 2013-11-18 09:17:55 UTC ---
Thanks. AFAIK, the hotkey mask was forcibly set in the old distros in acpid
package. Now it's dropped, and this force setup is gone. This must be the
reason of the regression.
Meanwhile, the volume up/down and mute are actually controlled by the extra
sound hardware on the machine, which is represented as the secondary card.
For example, you can check the extra mixer via
alsamixer -c4
When you press the mute, volume up and down keys, this mixer value will be
changed. It might not be refreshed automatically, so after pressing the key,
try to restart "alsamixer -c4". You should see the value is changed.
(BTW, the mute behavior is no toggle on Thinkpad, as you already know.)
And, thinkpad_acpi driver prevents emitting the key code if this mixer is
enabled as default. Otherwise, the OS would change the volume of the primary
sound device *in addition* to the second one, thus it'll be doubly applied.
The drawback of preventing the key code is that it isn't notified to OS, thus
you'll see no visual feedback on kmixer or whatever. But, the actual output,
at least the speaker output, should be affected without hotkey mask change.
This is the situation you're facing.
That being said, this change in the recent distro version is rather intnetional
to correct the behavior to the upstream way. It's user's choice to set this in
the older way, but the distro default has changed.
Looking at the code, the same effect could be easily achieved by passing a
module option, e.g. in /etc/modprobe.d/50-thinkpad_acpi.conf
options thinkpad_acpi hotkey=0xffffff
Maybe safer to pass 0x7c7fff instead, which enables only the missing mute and
volume up/down bits (0x700000).
Could you try to set up the module option instead?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.