Arch Linux User Repository

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)

Applying the patch for Zen3 (Ryzen5xxx series support) from the Github issue tracker:

Addition to the end of the "source()" array: "https://crazy.dev.frugalware.org/ZEN3-test4.patch"

Addition to the end of the "sha256sums" array: 'bc72955d1cf1d56c347d2444a13ea707f9402512ce211a013e5dee8ff3a8632d'

Addition to the end of the "prepare" function: patch -d "$srcdir/zenpower-$pkgver" -p1 -i ../ZEN3-test4.patch

Zenmonitor requires a patch as well, see my comment on the zenmonitor-git package.

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

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'
}

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)

@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.

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