Bug 114731
| Summary: | thinkpad-acpi: unknown version of the HKEY interface: 0x200 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | me |
| Component: | Platform | Assignee: | drivers_platform (drivers_platform) |
| Status: | NEW --- | ||
| Severity: | low | CC: | andre.insead, bugzilla, demure, dusty, laforge, orbanbalage, yaroslav.isakov |
| Priority: | P1 | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Kernel Version: | 4.5.0 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
|
Description
me
2016-03-15 20:31:11 UTC
Same problem for me. I've found this old patch http://www.gossamer-threads.com/lists/linux/kernel/1901769 and it worked perfectly. Why it was not accepted? Oh, forgot to add that I'm on Thinkpad T460s I cleaned the patch up a bit and re-sent it to the maintainers. I am having this issue on my Thinkpad X260 as well, with the special f4, f7-f12. So I assume this is effecting a number of models. FYI, I can confirm that on my X260 there is the same issue. It is currently running BIOS Version 1.17. During kernel boot, there is the "thinkpad_acpi: unknown version of the HKEY interface: 0x200" message. I haven't yet tried the patch from 2014 linked above. However, there seems to be some current (April 2016) discussion about it on https://sourceforge.net/p/ibm-acpi/mailman/message/34988427/ Same here on T460s running Fedora 24 4.6.4-301.fc24.x86_64. Jul 21 17:25:23 localhost kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.25 Jul 21 17:25:23 localhost kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ Jul 21 17:25:23 localhost kernel: thinkpad_acpi: ThinkPad BIOS N1CET40W (1.08 ), EC unknown Jul 21 17:25:23 localhost kernel: thinkpad_acpi: Lenovo ThinkPad T460s, model 20FAS1EF0M Jul 21 17:25:23 localhost kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad Jul 21 17:25:23 localhost kernel: thinkpad_acpi: unknown version of the HKEY interface: 0x200 Jul 21 17:25:23 localhost kernel: thinkpad_acpi: please report this to ibm-acpi-devel@lists.sourceforge.net As of about two weeks ago, on debian sid, my f4, and f7-12 are now work, and show up in `xev`. * F4: XF86AudioMicMute * F7: XF86Display * F8: XF86WLAN * F9: XF86Tools * F10:XF86Search * F11: XF86LaunchA * F12: XF86Explorer (In reply to demure from comment #7) > As of about two weeks ago, on debian sid, my f4, and f7-12 are now work, and > show up in `xev`. What kernel version is that? (In reply to Dusty Mabe from comment #8) > (In reply to demure from comment #7) > > As of about two weeks ago, on debian sid, my f4, and f7-12 are now work, > and > > show up in `xev`. > > What kernel version is that? Ah, sorry. I'm on 4.7.0 rc4 (apt pkg 'linux-image-4.7.0-rc4-amd64'), though I see that 4.7.0 rc7 is out now on sid. Ah, sorry. I'm on 4.7.0 rc4 (apt pkg 'linux-image-4.7.0-rc4-amd64'), though I see that 4.7.0 rc7 is out now, and will check that it continues to work there too. On Sat, Jul 23, 2016 at 05:16:56PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: >https://bugzilla.kernel.org/show_bug.cgi?id=114731 > >--- Comment #8 from Dusty Mabe <dusty@dustymabe.com> --- >(In reply to demure from comment #7) >> As of about two weeks ago, on debian sid, my f4, and f7-12 are now work, and >> show up in `xev`. > >What kernel version is that? > >-- >You are receiving this mail because: >You are on the CC list for the bug. |