# /var/log/openrc.log
...
* Loading acpi_call ...
* Failed to load acpi_call :(
...
All the ACPI, uPower, eLoginD packages are installed before the reboot, but the system still doesn’t load the battery.
Please, post the output of
$ sudo modprobe acpi_call
$ lsmod | grep acpi
If you try to start it manually /usr/sbin/acpid what do you get as output? I think all that acpid-openrc does is this.
[hd_scania@hd-scania ~]$ sudo modprobe acpi_call && lsmod|grep acpi
modprobe: FATAL: Module acpi_call not found in directory /lib/modules/4.20.12-artix1-1-ARTIX
[hd_scania@hd-scania ~]$
Kernel-specific issue should be ... Since other systems don’t occur this
‘‘sudo acpid’’ command just runs without any logs. :)
Your kernel installation is incomplete or botched, run
find /usr/lib/modules -name "*acpi_call*"
and post results. If it comes back empty, re-install your kernel.
[hd_scania@hd-scania ~]$ sudo updatedb && locate acpi_call|grep -e /usr/lib/modules
/usr/lib/modules/extramodules-ARCH/acpi_call.ko.xz
/usr/lib/modules-load.d/acpi_call.conf
[hd_scania@hd-scania ~]$ cat /usr/lib/modules-load.d/acpi_call.conf
acpi_call
[hd_scania@hd-scania ~]$
I have these acpi_call modules and what to do now? After kernel reinstallation the above results are remained the same. After a reboot then nothing wrong? :)
Are you by any chance using the new arch kernel 5.0 or 5.0.1?
I tried it and had some problems, USB disks sticks, etc, wouldn't list on /dev/disk
Hwinfo would show that the system read the hw but this didn't translate in being able to access them or mount them.
I switched back to artix 4.19 and the problem went away.
Please, run the commands exactly as I requested. Not updatedbs, no locates, no greps. It makes it hard to get meaningful information. Even so, your result only showed a module in extramodules-ARCH and you seem to be running 4.20.12-artix1-1-ARTIX. No wonder your kernel can't load it.
Follow the instructions of my previous post and also show us your running kernel with
uname -a.
My kernel is 4.20.12-ARTIX, and the outputs from the command you request are the same from:
/usr/lib/modules/extramodules-ARCH/acpi_call.ko.xz
Install acpi_call-dkms, it should fix your problem.
[hd_scania@hd-scania ~]$ cat /var/log/rc*.log|grep -e acpi && pacman -Ss acpi_call-dkms
* Stopping acpid ...
* Stopping acpid ...
* Loading module acpi_call ...
* Failed to load acpi_call
* Starting acpid ...
community/acpi_call-dkms 1.1.0-199 [installed]
A linux kernel module that enables calls to ACPI methods through /proc/acpi/call
galaxy/acpi_call-dkms 1.1.0-199 [installed]
A linux kernel module that enables calls to ACPI methods through /proc/acpi/call
[hd_scania@hd-scania ~]$ sudo rc-update|grep -e elogind -e acpi
acpid | boot
elogind | boot
[hd_scania@hd-scania ~]$
Seems useless :(
Try re-installing, the acpi_call is missing from your kernel modules directory.
This is what you should be seeing:
hyperion:[nous]:~% uname -a
Linux hyperion 4.20.14-1-ck-haswell #1 SMP PREEMPT Tue Mar 5 16:47:13 EST 2019 x86_64 GNU/Linux
hyperion:[nous]:~% find /usr/lib/modules/`uname -r` -name "acpi_call*"
/usr/lib/modules/4.20.14-1-ck-haswell/kernel/drivers/acpi/acpi_call.ko
hyperion:[nous]:~% lsmod|grep acpi
acpi_call 16384 0
hyperion:[nous]:~% pacman -Q | grep acpi_call
acpi_call-dkms 1.1.0-195
hyperion:[nous]:~%
[hd_scania@hd-scania ~]$ uname -a && find /usr/lib/modules/`uname -r` -name "acpi_call*" && lsmod|grep -e acpi && pacman -Q|grep -e acpi_call
Linux hd-scania 5.0.2-artix1-1-ARTIX #1 SMP PREEMPT Thu Mar 14 22:57:06 UTC 2019 x86_64 GNU/Linux
pata_acpi 16384 0
libata 278528 3 ata_piix,pata_acpi,ata_generic
acpi_call-dkms 1.1.0-199
[hd_scania@hd-scania ~]$
Note that I’m already 5.0.2 kernel that misses acpi kernel object somewhy. So downgrade the kernel as casually proposed before?
My guess is acpi_call-dkms fails to build the module for kernel 5. Perhaps, until this is fixed upstream, you should downgrade your kernel.
(depreciated)
(depreciated)
[hd_scania@hd-scania ~]$ ls -l /usr/lib/modules/$(uname -r)/kernel/drivers/acpi && dmesg|grep -e battery -e acpi
total 88
-rw-r--r-- 1 root root 3896 Apr 4 05:15 ac.ko.xz
-rw-r--r-- 1 root root 14632 Apr 10 09:40 acpi_call.ko
-rw-r--r-- 1 root root 3584 Apr 4 05:15 acpi_configfs.ko.xz
-rw-r--r-- 1 root root 4128 Apr 4 05:15 acpi_extlog.ko.xz
-rw-r--r-- 1 root root 5380 Apr 4 05:15 acpi_ipmi.ko.xz
-rw-r--r-- 1 root root 5140 Apr 4 05:15 acpi_tad.ko.xz
drwxr-xr-x 2 root root 4096 Apr 10 09:39 apei
-rw-r--r-- 1 root root 8484 Apr 4 05:15 battery.ko.xz
-rw-r--r-- 1 root root 2328 Apr 4 05:15 custom_method.ko.xz
drwxr-xr-x 2 root root 4096 Apr 10 09:39 dptf
drwxr-xr-x 2 root root 4096 Apr 10 09:39 nfit
-rw-r--r-- 1 root root 6092 Apr 4 05:15 sbs.ko.xz
[ 0.570923] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 1.152618] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 1.152714] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[ 1.220183] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[ 18.876645] battery: ACPI: Battery Slot [BAT1] (battery present)
[ 19.040426] acpi_call: loading out-of-tree module taints kernel.
[ 19.040457] acpi_call: module verification failed: signature and/or required key missing - tainting kernel
[ 22.340320] acpi device:4b: registered as cooling_device7
[hd_scania@hd-scania ~]$
What does this mean thanks?
I don't know exactly, but here is what I get on a laptop with a working battery:
-rw-r--r-- 1 root root 3896 Apr 3 22:15 ac.ko.xz
-rw-r--r-- 1 root root 3584 Apr 3 22:15 acpi_configfs.ko.xz
-rw-r--r-- 1 root root 4128 Apr 3 22:15 acpi_extlog.ko.xz
-rw-r--r-- 1 root root 5380 Apr 3 22:15 acpi_ipmi.ko.xz
-rw-r--r-- 1 root root 5140 Apr 3 22:15 acpi_tad.ko.xz
drwxr-xr-x 1 root root 48 Apr 11 01:53 apei
-rw-r--r-- 1 root root 8484 Apr 3 22:15 battery.ko.xz
-rw-r--r-- 1 root root 2328 Apr 3 22:15 custom_method.ko.xz
drwxr-xr-x 1 root root 32 Apr 11 01:53 dptf
drwxr-xr-x 1 root root 20 Apr 11 01:53 nfit
-rw-r--r-- 1 root root 4028 Apr 3 22:15 sbshc.ko.xz
-rw-r--r-- 1 root root 6092 Apr 3 22:15 sbs.ko.xz
[ 0.103904] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.103905] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.497201] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.685735] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.685749] acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.706078] acpiphp: Slot [1] registered
[ 0.792908] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[ 0.971882] acpi device:37: registered as cooling_device0
[ 5.057902] battery: ACPI: Battery Slot [BAT0] (battery present)
[ 5.057965] battery: ACPI: Battery Slot [BAT1] (battery absent)
I have this which you don't
-rw-r--r-- 1 root root 4028 Apr 3 22:15 sbshc.ko.xz
You have some error messages that I don't:
[ 1.152714] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[ 19.040426] acpi_call: loading out-of-tree module taints kernel.
[ 19.040457] acpi_call: module verification failed: signature and/or required key missing - tainting kernel
The last two probably come from a module you have which I don't:
-rw-r--r-- 1 root root 14632 Apr 10 09:40 acpi_call.ko
So wherever that acpi_call.ko module is from, it isn't built for the kernel you are using so doesn't work. Fix that and you will probably just have the first error.