Instead, build but don't install both packages. Then install both packages at the same time w/ pacman
.
Search Criteria
Package Details: zfs-dkms 2.3.2-1
Package Actions
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: | 188 |
Popularity: | 2.32 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2025-05-03 09:40 (UTC) |
Dependencies (2)
- dkms (dkms-gitAUR)
- zfs-utilsAUR (zfs-utils-gitAUR, zfs-linux-gitAUR, zfs-utils-staging-gitAUR)
Required by (20)
- cockpit-zfs-manager (requires zfs)
- prepare-lastboot (requires zfs)
- python-pyzfscmds (requires zfs)
- targetd (optional)
- targetd-git (optional)
- zbectl-git (requires zfs)
- zectl (requires zfs)
- zectl-git (requires zfs)
- zedenv (requires zfs)
- zedenv-git (requires zfs)
- zedenv-grub (requires zfs)
- zfs-auto-snapshot (requires zfs)
- zfs-auto-snapshot-git (requires zfs)
- zfs-openrc
- zfsbootmenu (requires zfs)
- zfsbootmenu-efi-bin (requires zfs)
- znapzend (requires zfs)
- znapzupport (requires zfs)
- zsnapd (requires zfs)
- zxfer (requires zfs)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 .. 66 Next › Last »
fryfrog commented on 2021-07-22 03:51 (UTC)
nesv commented on 2021-07-22 03:45 (UTC)
If anyone runs into an issue where zfs-dkms
and zfs-utils
cannot be updated due to zfs-dkms
being locked to a version of zfs-utils
, you can fix it by removing the zfs-dkms
package first, updating zfs-utils
, then re-installing zfs-dkms
.
itoffshore commented on 2021-06-29 20:29 (UTC) (edited on 2021-07-29 10:37 (UTC) by itoffshore)
I had to downgrade gcc
to 10.2.0-6
to get the modules to build for zfs-2.0.5
& 2.1.0
on linux-hardened-5.9.12-a-1
For linux-hardened-5.12.19
the modules build successfully with gcc-11.1.0
& zfs-dkms 2.1.0
eschwartz commented on 2021-06-08 15:32 (UTC)
Nice speech. Totally irrelevant though.
When I say I'm not going to apply the patch, what I mean is I can't. If you try applying it, you'll find out why you can't either.
To save you the time, I'll tell you the error message you'd get.
Reversed (or previously applied) patch detected! Assume -R? [n]
P.S. check the author of that PR, then check the commit message for the latest version of this PKGBUILD.
eschwartz commented on 2021-06-08 12:17 (UTC)
No
tuxzz commented on 2021-06-08 11:44 (UTC)
Please apply this patch https://github.com/openzfs/zfs/pull/12178
bone commented on 2021-05-25 18:25 (UTC)
I don't know if it was just me beeing stupid, or if it is a thing, but I downgraded the kernel to 5.11 on a new machine to install zfs-dkms 2.0.4 and I all the time got the error "make: *** No targets specified and no makefile found. Stop." during the dkms install. Solution (for me) was to downgrade gcc (to e.g. 10.2.0). And then the dkms install worked as always.
btw: Thank you very much for maintaining the package! Appreciate the effort!
fryfrog commented on 2021-05-07 14:57 (UTC)
@iusrlinearb: The patches in the recent PKGBUILD update make it compatible, they're backported from master, so it is compatible. But once zol does the same thing and releases 2.0.5, it'll be official and also compatible.
Pinned Comments
kstolp commented on 2025-04-29 16:56 (UTC) (edited on 2025-05-03 09:40 (UTC) by kstolp)
OpenZFS currently supports Linux kernel versions 4.18 - 6.14, as declared in the META file.
Options if your Linux kernel's version is not within that range:
1) Switch to another Linux kernel, such as
linux-lts
.2) Prevent your kernel package from upgrading to an unsupported version until OpenZFS increases the maximum supported kernel version.
3) Modify this package to support your kernel by patching it on your local machine.
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)