zfs-dkms 2.1.4-1
all ok with 5.15.27.hardened1-1
I had to clean up some old config with rm -rf /var/lib/dkms/zfs/2.1.2
to fix Unable to build an empty module
Git Clone URL: | https://aur.archlinux.org/zfs-dkms.git (read-only, click to copy) |
---|---|
Package Base: | zfs-dkms |
Description: | Kernel modules for the Zettabyte File System. |
Upstream URL: | https://zfsonlinux.org/ |
Licenses: | CDDL |
Provides: | SPL-MODULE, zfs, ZFS-MODULE |
Submitter: | isiachi |
Maintainer: | kstolp |
Last Packager: | kstolp |
Votes: | 186 |
Popularity: | 1.40 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2025-03-11 07:23 (UTC) |
« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 64 Next › Last »
zfs-dkms 2.1.4-1
all ok with 5.15.27.hardened1-1
I had to clean up some old config with rm -rf /var/lib/dkms/zfs/2.1.2
to fix Unable to build an empty module
@jonathon Correct, also with archzfs now. Tried it again. Issues solved with 5.15.23-2-lts.
If you're having an issue at this point it's because you have a partial upgrade. All kernels have been built with GCC 11.2.0, and DKMS will rebuild the ZFS module accordingly.
Currently I am using the archzfs version (but also keeping a copy of this AUR one in a folder so that I can switch things easily), but yesterday the update to LTS kernel 5.15.23-1-lts gave me that exact same ZFS build error, about that it could not build an empty module (I verified it by manually running the dkms build command again to see it's output). Luckily on the regular kernel 5.16.9-arch1-1 it did still build fine (with that same archzfs version) in my case. So with having both kernels installed on my system it wasn't a direct issue. But if it's also gonna happen with the regular kernel.
did some experiments and concur largely with @razielgn re: synchronous changes:
My system was running gcc-11.1.0-1 and binutils-2.36.1-3 and linux-5.15.13 and zfs was working fine. As soon as I upgraded to linux-5.16.8 nfs-dkms failed to build. I downgraded the kernel back to 5.15.13 and everything is fine again. So maybe it is just the kernel not the gcc and binutils?
dkms apparently cannot build 2.1.2-2 with gcc 11.2 and binutils 2.38: I get "checking whether modules can be built... no". make was failing due to missing target when invoked (sorry, I lost the logs). It's easy to reproduce if you include [testing] packages. I downgraded gcc to 11.1, binutils to 2.36 and got it working again. Also cannot build zfs module with gcc 11.1/bintuils 2.36 for linux-tls 5.15.23 (also in testing), I guess the maintainers have made synchronous changes across all those packages.
Thanks a lot fryfrog for confirming about this, I use the same archzfs/zfs-dkms but didnt know the right place to ask this question. I have updated now, and it indeed works all fine.
Pinned Comments
kstolp commented on 2023-09-29 00:34 (UTC)
When requesting changes, please include detailed reasoning for the change.
kstolp commented on 2023-01-07 09:31 (UTC)
If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.
You have two options:
1) Import the two keys into your keyring. ArchWiki article. You can find the key IDs in the PKGBUILD file, in the
validpgpkeys
array. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheck
argument tomakepkg
when building. (not recommended)