Package Details: zenpower3-dkms 0.2.0-3

Git Clone URL: (read-only, click to copy)
Package Base: zenpower3-dkms
Description: Linux kernel driver for reading sensors for AMD Zen family CPUs
Upstream URL:
Keywords: amd dkms driver ryzen sensors zen zenpower
Licenses: GPL2
Conflicts: zenpower3
Provides: zenpower3
Submitter: Ta180m
Maintainer: Ta180m
Last Packager: Ta180m
Votes: 16
Popularity: 1.42
First Submitted: 2021-06-19 23:55 (UTC)
Last Updated: 2022-09-06 15:39 (UTC)

Dependencies (1)

Required by (1)

Sources (2)

Latest Comments

1 2 Next › Last »

ginnokami commented on 2022-09-13 14:23 (UTC)

Checking the github link directly, the correct source link should be

geekmiki commented on 2022-09-06 08:31 (UTC) (edited on 2022-09-06 08:31 (UTC) by geekmiki)

Trying to install and getting: ERROR: One or more files did not pass the validity check! error downloading sources: zenpower3-dkms context: exit status 1

harre commented on 2022-09-01 20:21 (UTC)

@jonathon That new link gives me 404

jonathon commented on 2022-09-01 19:48 (UTC) (edited on 2022-09-01 19:52 (UTC) by jonathon)

Upstream URL has changed:

diff --git a/PKGBUILD b/PKGBUILD
index 9fda9b0..e1bc585 100644
@@ -9,7 +9,7 @@ pkgver=0.2.0
 pkgdesc='Linux kernel driver for reading sensors for AMD Zen family CPUs'
 arch=('x86_64' 'i686')

bear0king commented on 2022-07-27 02:54 (UTC)

@Ta180m I had pinged and did not get a response, maybe it's my network problem. Would you mind send zenpower3-0.2.0.tar.gz to my email Thanks.

Ta180m commented on 2022-07-26 17:01 (UTC)

@bear0king That's weird, since I don't think has had an outage in the past few days. Can you try ping

bear0king commented on 2022-07-26 11:16 (UTC)

Hello, I can't download zenpower3-0.2.0.tar.gz, it seems is down.

Ta180m commented on 2022-06-25 15:54 (UTC) (edited on 2022-06-25 15:58 (UTC) by Ta180m)

@jongeduard It looks like your zenpower3-0.2.0.tar.gz is from the old GitHub upstream and not a copy downloaded from the new upstream. The two zenpower3-0.2.0.tar.gzs are different but have the same name, which I think is causing the validation problems.

Perhaps I should have just kept the pkgrel the same when updating the upstream URL, since it wasn't a change that needed a rebuild, but it might be too late to do that now.

Edit: I changed the pkgrel back to 1, maybe that fixes things, maybe that just makes it worse...

jongeduard commented on 2022-06-25 11:26 (UTC) (edited on 2022-06-25 12:05 (UTC) by jongeduard)

Same issue here!

And not only that: I permanently maintain copies inside my home folder of everything I install AUR, and normally I can always simply "git pull" to update anything before I run my "makepkg -csi" - which I have both automated using a self-written script, but this time I got the error from git that I have made local changes, while I am certain that this is not the case.

I needed a "git reset --hard" to solve the issue.

Sadly after that I got this validation problem as well.

So clearly there is something wrong.

Update: I have manually checked things myself now:

The PKGBUILD mentions 2 files and 2 checksums:

source=("$_pkgname-$pkgver.tar.gz::$url/archive/v$pkgver.tar.gz" "$_pkgname.conf")

sha256sums=('6c48f7e07d13658f357a02005da1689cb6935fac34e21a4bf5b7483c7d0c4476' '7bff3a5ea2c8b8abf56ce1d79b9724b1aea89e2564d244e09691070113d60f6a')

But when I manually check the sums of the files which I have:

eduard@eduard-laptop ~/Software/AUR/zenpower3-dkms (git)-[master] % sha256sum zenpower3-0.2.0.tar.gz

b206c1dfd8ea742a802126d012404d31ae62f2a23ae4723ea1c0f9f54581f6a3 zenpower3-0.2.0.tar.gz

eduard@eduard-laptop ~/Software/AUR/zenpower3-dkms (git)-[master] % sha256sum zenpower3.conf
7bff3a5ea2c8b8abf56ce1d79b9724b1aea89e2564d244e09691070113d60f6a zenpower3.conf

eduard@eduard-laptop ~/Software/AUR/zenpower3-dkms (git)-[master] %
7bff3a5ea2c8b8abf56ce1d79b9724b1aea89e2564d244e09691070113d60f6a zenpower3.conf

Extra info: My zenpower3-0.2.0.tar.gz is still from 2022-01-06, whhich is the same version as the one mentioned here

My guess: You forgot to update the version number while making changes, so the new one is not going to be downloaded?

Ta180m commented on 2022-06-24 16:00 (UTC)

Huh, I don't get a validity check error when building this package in a clean environment, so I think those errors might be caused by your AUR helper. Upstream (AKA me) changed URLs so the tar.gz has changed, but it still has the same name so it might be confusing your AUR helper.