http://bugzilla.opensuse.org/show_bug.cgi?id=1190563 Bug ID: 1190563 Summary: Problems with acpi_call package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: popov895@ukr.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I'm using a ThinkPad which supports advanced battery management via TLP, like charging thresholds and recalibration. To enable these features, I followed the instructions in the TLP docs (https://linrunner.de/tlp/installation/opensuse.html) and installed packages tlp, tlp-rdw and acpi_call (to install acpi_call I added repository https://download.opensuse.org/repositories/Base:System/openSUSE_Tumbleweed/B...). But after that `sudo tlp-stat -b` reported me that acpi_call is not installed:
$ sudo tlp-stat -b --- TLP 1.3.1 --------------------------------------------
+++ Battery Features: Charge Thresholds and Recalibrate natacpi = active (data, thresholds) tpacpi-bat = inactive (kernel module 'acpi_call' not installed) tp-smapi = inactive (ThinkPad not supported)
+++ ThinkPad Battery Status: BAT0 /sys/class/power_supply/BAT0/manufacturer = LGC /sys/class/power_supply/BAT0/model_name = 01AV445 /sys/class/power_supply/BAT0/cycle_count = 250 /sys/class/power_supply/BAT0/energy_full_design = 45000 [mWh] /sys/class/power_supply/BAT0/energy_full = 38140 [mWh] /sys/class/power_supply/BAT0/energy_now = 38140 [mWh] /sys/class/power_supply/BAT0/power_now = 0 [mW] /sys/class/power_supply/BAT0/status = Full
/sys/class/power_supply/BAT0/charge_start_threshold = 65 [%] /sys/class/power_supply/BAT0/charge_stop_threshold = 65 [%]
Charge = 100.0 [%] Capacity = 84.8 [%]
+++ Recommendations * Install acpi_call kernel module for ThinkPad battery recalibration
Also `sudo modprobe acpi_call` reported me that acpi_call kernel module was not found:
$ sudo modprobe acpi_call modprobe: FATAL: Module acpi_call not found in directory /lib/modules/5.14.1-1-default
After that, using `rpm -ql acpi_call`, I found that acpi_call doesn't install the kernel module:
$ rpm -ql acpi_call /usr/libexec/modules-load.d /usr/libexec/modules-load.d/acpi_call.conf /usr/share/doc/packages/acpi_call /usr/share/doc/packages/acpi_call/README.md
Further, after some researching, I found that in addition to acpi_call I need to install acpi_call-kmp-default package, which actually installs the required kernel module:
$ rpm -ql acpi_call /lib/modules/5.14.1-1-default /lib/modules/5.14.1-1-default/updates /lib/modules/5.14.1-1-default/updates/acpi_call.ko
But now the output of `sudo tlp-stat -b` looks like this:
$ sudo tlp-stat -b /usr/share/tlp/func.d/35-tlp-func-batt: line 25: 6070 Killed $TPACPIBAT -g FD 1 > /dev/null 2>&1 --- TLP 1.3.1 --------------------------------------------
+++ Battery Features: Charge Thresholds and Recalibrate natacpi = active (data, thresholds) tpacpi-bat = unknown status tp-smapi = inactive (ThinkPad not supported)
/usr/share/tlp/func.d/35-tlp-func-batt: line 25: 6117 Killed $TPACPIBAT -g FD 1 > /dev/null 2>&1 /usr/share/tlp/func.d/35-tlp-func-batt: line 25: 6163 Killed $TPACPIBAT -g FD 1 > /dev/null 2>&1 +++ ThinkPad Battery Status: BAT0 /sys/class/power_supply/BAT0/manufacturer = LGC /sys/class/power_supply/BAT0/model_name = 01AV445 /sys/class/power_supply/BAT0/cycle_count = 250 /sys/class/power_supply/BAT0/energy_full_design = 45000 [mWh] /sys/class/power_supply/BAT0/energy_full = 38140 [mWh] /sys/class/power_supply/BAT0/energy_now = 37400 [mWh] /sys/class/power_supply/BAT0/power_now = 0 [mW] /sys/class/power_supply/BAT0/status = Unknown
/sys/class/power_supply/BAT0/charge_start_threshold = 65 [%] /sys/class/power_supply/BAT0/charge_stop_threshold = 65 [%]
Charge = 98.1 [%] Capacity = 84.8 [%]
/usr/share/tlp/func.d/35-tlp-func-batt: line 25: 6263 Killed $TPACPIBAT -g FD 1 > /dev/null 2>&1
As you can see, I am getting error "/usr/share/tlp/func.d/35-tlp-func-batt: line 25: xxxx Killed $TPACPIBAT -g FD 1 > /dev/null 2>&1". The TLP developer told me that I should use a recent version of acpi_call (https://github.com/linrunner/TLP/issues/571#issuecomment-920318813). Actually, I guess that the following should be done to fix this issue: 1. Update acpi_call to the recent version 2. Install the acpi_call-kmp-default package as a dependency of the acpi_call package System information
$ lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20210913 Codename: n/a
$ uname -a Linux localhost.localdomain 5.14.1-1-default #1 SMP Sat Sep 4 08:22:51 UTC 2021 (67af907) x86_64 x86_64 x86_64 GNU/Linux
$ zypper info acpi_call Information for package acpi_call: ---------------------------------- Repository : Base:System Factory Devel Project (openSUSE_Tumbleweed) Name : acpi_call Version : 1.1.0-3.112 Arch : x86_64 Vendor : obs://build.opensuse.org/Base:System Installed Size : 3,0 KiB Installed : Yes Status : up-to-date Source package : acpi_call-1.1.0-3.112.src Summary : The acpi-call kernel module Description : A kernel simple module that enables you to call ACPI methods by writing the method name followed by arguments to /proc/acpi/call.
This module is to be considered a proof-of-concept and has been superseeded by projects like bbswitch. It allows you to tamper with your system and should be used with caution.
$ zypper info acpi_call-kmp-default Information for package acpi_call-kmp-default: ---------------------------------------------- Repository : Base:System Factory Devel Project (openSUSE_Tumbleweed) Name : acpi_call-kmp-default Version : 1.1.0_k5.14.1_1-3.112 Arch : x86_64 Vendor : obs://build.opensuse.org/Base:System Installed Size : 15,2 KiB Installed : Yes Status : up-to-date Source package : acpi_call-1.1.0-3.112.src Summary : The acpi-call kernel module Description : A kernel simple module that enables you to call ACPI methods by writing the method name followed by arguments to /proc/acpi/call.
This module is to be considered a proof-of-concept and has been superseeded by projects like bbswitch. It allows you to tamper with your system and should be used with caution.
-- You are receiving this mail because: You are the assignee for the bug.