After a recent upgrade, when I attempt to use cpupower, I get the following
message:cpupower: /usr/lib/libpci.so.3: verion `LIBPCI_3.5' not found (required by cpupower)I haven't changed any of the setting for cpupower recently and everything was
running smoothly before. Now I can't query the cpu settings any longer.$ ls /usr/lib/libpci.so* /usr/lib/libpci.so /usr/lib/libpci.so.3 /usr/lib/libpci.so.3.4.1
Then, the temporary solution is to downgrade cpupower to version 4.6.1. Follow the general downgrade guide at https://wiki.archlinux.org/index.php/Downgrading_packages. For comparison sake, this is the log of failed cpupower at start-up in my machine:
root@jeez /var/cache/pacman/pkg # systemctl status cpupower.service — cpupower.service - Apply cpupower configuration Loaded: loaded (/usr/lib/systemd/system/cpupower.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2016-06-06 22:07:38 SGT; 44min ago Process: 328 ExecStart=/usr/lib/systemd/scripts/cpupower (code=exited, status=1/FAILURE) Main PID: 328 (code=exited, status=1/FAILURE) Jun 06 22:07:37 jeez systemd[1]: Starting Apply cpupower configuration... Jun 06 22:07:37 jeez cpupower[328]: cpupower: /usr/lib/libpci.so.3: version `LIBPCI_3.5' Jun 06 22:07:38 jeez systemd[1]: cpupower.service: Main process exited, code=exited, sta Jun 06 22:07:38 jeez systemd[1]: Failed to start Apply cpupower configuration. Jun 06 22:07:38 jeez systemd[1]: cpupower.service: Unit entered failed state. Jun 06 22:07:38 jeez systemd[1]: cpupower.service: Failed with result 'exit-code'.
This is the excerpt the steps that I did to fix the issue via package downgrade:
root@jeez /var/cache/pacman/pkg # pacman -U cpupower-4.6-1-x86_64.pkg.tar.xz loading packages... warning: downgrading package cpupower (4.6-2 => 4.6-1) resolving dependencies... looking for conflicting packages... Packages (1) cpupower-4.6-1 Total Installed Size: 0.41 MiB Net Upgrade Size: -0.10 MiB :: Proceed with installation? [Y/n] Y (1/1) checking keys in keyring [###############################] 100% (1/1) checking package integrity [###############################] 100% (1/1) loading package files [###############################] 100% (1/1) checking for file conflicts [###############################] 100% (1/1) checking available disk space [###############################] 100% :: Processing package changes... (1/1) downgrading cpupower [###############################] 100% :: Running post-transaction hooks... (1/1) Updating manpage index... root@jeez /var/cache/pacman/pkg # systemctl restart cpupower.service root@jeez /var/cache/pacman/pkg # journalctl -xe Jun 06 22:51:51 jeez systemd[1]: Starting Apply cpupower configuration... -- Subject: Unit cpupower.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit cpupower.service has begun starting up. Jun 06 22:51:52 jeez systemd[1]: Started Apply cpupower configuration. -- Subject: Unit cpupower.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit cpupower.service has finished starting up. -- -- The start-up result is done. pinczakko@jeez Mon Jun 06 10:52:07pm ~/ systemctl status cpupower.service — cpupower.service - Apply cpupower configuration Loaded: loaded (/usr/lib/systemd/system/cpupower.service; enabled; vendor preset: disabled) Active: active (exited) since Mon 2016-06-06 22:51:52 SGT; 26s ago Process: 2672 ExecStart=/usr/lib/systemd/scripts/cpupower (code=exited, status=0/SUCCESS) Main PID: 2672 (code=exited, status=0/SUCCESS) Jun 06 22:51:51 jeez systemd[1]: Starting Apply cpupower configuration... Jun 06 22:51:52 jeez systemd[1]: Started Apply cpupower configuration.
As you see in the shell log above, after downgrading cpupower to version 4.6.1, everything went back to normal. This is only temporary fix until libpci 3.5 promoted from testing to stable. We can go back to cpupower version 4.6.2 by then.
Post a Comment
No comments:
Post a Comment