Greetings.
It seems my assumptions were misplaced. It seems the ACPI event is
connected to the accelerometer perhaps, since it fired also when tilting
the laptop rather than folding the screen part. That includes tilting
sideways. The accelerometer works fine anyway, so i still dont know what
Hello,
This must have been reported 200 times already, but just to make sure:
Aug 29 17:57:35 kaiku kernel: [ 7850.946751] thinkpad_acpi: unknown
possible thermal alarm or keyboard event received
Aug 29 17:57:35 kaiku kernel: [ 7850.946757] thinkpad_acpi: unhandled
HKEY event 0x60b0
Aug 29 17:57:
Hi, I'm using a ThinkPad x270, Inter(R) Core(TM) i5-6300U CPU @ 2.40GHz.
[ 216.335616] thinkpad_acpi: unknown possible thermal alarm or keyboard
event received
[ 216.335618] thinkpad_acpi: unhandled HKEY event 0x6032
[ 216.335619] thinkpad_acpi: please report the conditions when this event
happ
I have a Lenovo P71 (a new model laptop) running Debian stretch. Among other
things, I have the following packages installed.
cpufrequtils
hibernate
laptop-mode-tools
thinkfan
tpb
tp-smapi-dkms
acpi
acpid
acpi-support
The laptop has four dedicated keys and twelve keys e
[ 216.335616] thinkpad_acpi: unknown possible thermal alarm or keyboard
event received
[ 216.335618] thinkpad_acpi: unhandled HKEY event 0x6032
[ 216.335619] thinkpad_acpi: please report the conditions when this event
happened to ibm-acpi-devel@lists.sourceforge.net
The laptop just reboots afte
Many thinkpad laptops and convertibles provide the GMMS method to
resolve how far the laptop has been opened and whether it has been
converted into tablet mode. This allows reporting a more precise tablet
mode state to userspace.
The current implementation only reports a summarized tablet mode sta
As others, my dmesg gets spammed by:
---
kernel: [289071.533288] thinkpad_acpi: unknown possible thermal alarm or
keyboard event received
kernel: [289071.533291] thinkpad_acpi: unhandled HKEY event 0x60b0
kernel: [289071.533292] thinkpad_acpi: please report the conditions when
this event happe
driver_attribute are not supposed to change at runtime.
Functions driver_create_file/driver_remove_file are working with
const driver_attribute. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/platform/x86/thinkpad_acpi.c | 2 +-
1 file changed, 1 insertion(+), 1
