Package Details: zenpower-dkms 0.1.12-2

Git Clone URL: https://aur.archlinux.org/zenpower-dkms.git (read-only, click to copy)
Package Base: zenpower-dkms
Description: Linux kernel driver for reading sensors for AMD Zen family CPUs
Upstream URL: https://github.com/ocerman/zenpower
Keywords: amd ryzen zen zenpower
Licenses: GPL2
Conflicts: zenpower
Provides: zenpower
Submitter: xythrez
Maintainer: xythrez
Last Packager: xythrez
Votes: 5
Popularity: 0.28
First Submitted: 2020-02-22 23:40
Last Updated: 2020-11-14 17:07

Dependencies (1)

Required by (2)

Sources (2)

Pinned Comments

xythrez commented on 2020-07-10 13:52

For dkms packages to work, you need to install your corresponding kernel headers (i.e if you are using linux, then install linux-headers). These are not included in the dependencies per dkms package guidelines on the wiki and you be able to take care of this yourself (not everyone uses the default kernel, this is why dkms packages exist)

Latest Comments

xythrez commented on 2020-11-14 17:08

@Xorg Thanks for catching that! I can't believe nobody noticed that typo for so long. It has now been fixed.

Xorg commented on 2020-11-14 15:04

post_remove function is wrong in zenpower.install, it must be:

post_remove() {
  echo 'The zenpower kernel module will be removed on reboot. To remove it now, run "rmmod zenpower && modprobe k10temp" as root'
}

xythrez commented on 2020-07-10 13:52

For dkms packages to work, you need to install your corresponding kernel headers (i.e if you are using linux, then install linux-headers). These are not included in the dependencies per dkms package guidelines on the wiki and you be able to take care of this yourself (not everyone uses the default kernel, this is why dkms packages exist)

xythrez commented on 2020-07-10 13:29

@ludenticus unlike the git version of this package, a blacklist config for k10temp is already included so it should automatically blacklist on install and be removed upon uninstall. The only time this would pose a problem would be right after installing the package, where modprobe.d is not reloaded and having the package reload all modprobe configs is a BAD idea. This is why there is a post-install message asking you to reboot or manually load the module (while also disabling k10temp first). In any other cases you shouldn't have to manually blacklist k10temp though.

ludenticus commented on 2020-07-10 13:02

It is a good idea to add some module activation instructions, because you have to disable the k10temp module first.