Closed poutnikl closed 6 years ago
I have realized that /lib/modules/3.10.0-693.11.6.el7.x86_64/build does exist, but its properties says link (broken ) (inode/symlink) with the target /usr/src/kernels/3.10.0-693.11.6.el7.x86_64.
There is no item 3.10.0-693.11.6.el7.x86_64 in the folder /usr/src/kernels.
I suppose it may be related with missing kernel sources, but I am not use how to deal with that.
yea, most likely you need to install kernel sources for your (incredibly ancient) kernel. i think you just do yum install kernel-devel
but redhat is very much not my style.
also, this is a problem with installing one of tpacpi-bat's dependencies, acpi-call
. its not a problem with installing tpacpi-bat per se.
good luck!
p.s.: latest rhel is based on the latest and greatest of 2013? its a miracle that any modern hardware or software works...
Just to provide the feedback - after yum installing of the kernel-devel ( and also missing gcc compiler ) I was successful with the acpi_call installation via install.pl.
The set thresholds seem to work now. The forced discharging does not, but it seems to be in agreement with the tpacpi-bat legend text.
Correction: Forced discharging FD does work, if just 1 of 2 T470 batteries is chosen.
Ignore Charging IC does not work. tpacpi-bat -g IC 1/2 returns "no" whatever I set by tpacpi-bat -s IC 1/2 0/1
thx
Hi,
I admit I am rather a novice in any Linux Hw configuration. I usually follow provided step by step cookbooks. If it fails, I am out of luck unless some guide is provided by experienced users.
In recent past I was successful in installing tpacpi-bat management with battery thresholds 40-80 for T430 / RHOC 6.x / Gnome.
When I tried to do the same for my new work laptop T470 / RHOC 7.4 / Gnome ( As SU cloning the TPACPI-BAT repo, going to its base folder and running ./install.pl ) , it fails at the make step as below.
The stumble stone seems to be:
/lib/modules/3.10.0-693.11.6.el7.x86_64/build: No such file or directory
In my understanding, it should be T470 compatible. But it seems to me the failure is not HW related, but rather OS config related. Perhaps RHOC 7.3 makes some trouble. Could you advice the proper procedure ?
List of terminal output: