https://bugzilla.novell.com/show_bug.cgi?id=849309 https://bugzilla.novell.com/show_bug.cgi?id=849309#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bam@NightStorm.com --- Comment #1 from Takashi Iwai 2013-11-07 07:07:58 UTC --- When you login twm or such basic session, run xev, and press volume or mute buttons. Does xev report any corresponding key events? If xev reports proper key events, the problem lies in KDE. If xev doesn't report, it's anything else in a lower layer. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=849309 https://bugzilla.novell.com/show_bug.cgi?id=849309#c3 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bam@NightStorm.com --- Comment #3 from Takashi Iwai 2013-11-11 17:16:47 UTC --- Test it rather on a bare desktop environment like twm or icewm. On GNOME, you don't see such key events because GNOME itself grabs the audio key events before reaching to xev. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=849309 https://bugzilla.novell.com/show_bug.cgi?id=849309#c5 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bam@NightStorm.com --- Comment #5 from Takashi Iwai 2013-11-12 06:48:00 UTC --- OK. Just to be sure, also check "showkey -s" output on Linux console (e.g. go to VT1 via ctl-alt-F1). I guess this won't show the audio hotkey events, too. I'm not sure whether TP60's audio hotkey is handled over the individual ALSA device or it's emitting key events. In the former case, you should have an independent ALSA mixer device and the hotkey control only that. The volume is affected on the output on the top of normal sound devices, so this will be invisible in the KDE mixer interface. In the latter case, it should generate a key event as we've tested. Run alsa-info.sh with --no-upload option, and also give the kernel message (output of dmesg), attach both to this bugzilla. In alsa-info.sh output, you'll see a thinkpad-specific sound card entry if it's handled in that way. Then you can check whether this mixer value changes via audio hot keys. BTW, which SUSE versions have you tested? You mentioned it worked on 11.1, but it's a very old one. Did 12.3 work? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=849309 https://bugzilla.novell.com/show_bug.cgi?id=849309#c7 Bruce Mallett changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bam@NightStorm.com | --- Comment #7 from Bruce Mallett 2013-11-12 14:24:45 UTC --- The showkey -s, as predicted, produced no output. I did a "dmesg -clear", then ran the alsa-info.sh --no-upload and have attached that. I then did a "dmesg" but nothing was present (the alsa-info.sh produced no logging). I just tried a KDE-live 12.3 USB stick on the laptop and it does not work, so perhaps it has not worked in some time. If there is some -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=849309 https://bugzilla.novell.com/show_bug.cgi?id=849309#c9 --- Comment #9 from Bruce Mallett 2013-11-12 15:06:30 UTC --- Created an attachment (id=567112) --> (http://bugzilla.novell.com/attachment.cgi?id=567112) dmesg output from T60p -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=849309 https://bugzilla.novell.com/show_bug.cgi?id=849309#c11 --- Comment #11 from Takashi Iwai 2013-11-12 15:25:18 UTC --- OK, so it's the missing hotkey enablement on your machine by some reason, likely a BIOS issue. I guess we had some workaround in OS level, but it was dropped during systemd integration or acpi proc deprecation or such. We can certainly fix this in either OS level or better in the driver level. Could you give the output of dmidecode, too? (It's in dmidecode package.) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=849309 https://bugzilla.novell.com/show_bug.cgi?id=849309#c13 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bam@NightStorm.com --- Comment #13 from Takashi Iwai 2013-11-15 14:23:59 UTC --- Thanks. At least, the firmware looks older than thinkpad_acpi expects. But this missing volume key mask might be irrelevant from that. Which value does hotkey_enable sysfs file have? Also, how about others, hotkey_*_mask files? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=849309 https://bugzilla.novell.com/show_bug.cgi?id=849309#c15 --- Comment #15 from Takashi Iwai 2013-11-17 09:21:23 UTC --- Just to be sure: was this taken before you do run "cp /sys/...." hack, right? That is, hotkey_mask 0x008c7fff is the initial value? -- 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.

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.

https://bugzilla.novell.com/show_bug.cgi?id=849309 https://bugzilla.novell.com/show_bug.cgi?id=849309#c19 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #19 from Takashi Iwai 2013-11-18 17:19:52 UTC --- OK. So, I think we can close this bug as WONTFIX. As mentioned in the previous comment, it's user's configuration whether to emit the key code or not. As default, we changed not to do it since the recent distro versions. Thanks for your quick tests! -- 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.