Thanks @mabod for locating the patch. It worked zfs module built w/o errors
Search Criteria
Package Details: zfs-dkms 2.4.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: | 197 |
| Popularity: | 0.95 |
| First Submitted: | 2015-08-31 12:01 (UTC) |
| Last Updated: | 2026-05-13 05:21 (UTC) |
Dependencies (2)
- dkms (dkms-gitAUR)
- zfs-utilsAUR (zfs-linux-gitAUR, zfs-utils-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)
baslking commented on 2026-05-20 11:15 (UTC)
mabod commented on 2026-05-20 10:43 (UTC)
@baslking: They have a fix merged already. You could give this fix a try and apply it in zfs-dkms PKGBUILD to zfs 2.4.2:
https://patch-diff.githubusercontent.com/raw/openzfs/zfs/pull/18532.patch
baslking commented on 2026-05-20 09:53 (UTC) (edited on 2026-05-20 09:55 (UTC) by baslking)
Update on my previous deleted post. The module build now fails on aarch64. It failed for me first on 6.18.32. I'm not 100% sure which update broke the build, I had a 6.18.29 kernel that built the module correctly, dkms was also updated, in between. I've tried downgrading both, but the problem is elsewhere. It seems that the breakage is likely with the gcc 16.x toolchain
The error that fails is:
/var/lib/dkms/zfs/2.4.2/build/module/zfs/vdev_raidz_math_aarch64_neon_common.h:30:15: error: invalid hard register usage between earlyclobber operand and input operand
30 | #define __asm __asm__ __volatile__
| ^~~~~~~
/var/lib/dkms/zfs/2.4.2/build/module/zfs/vdev_raidz_math_aarch64_neon_common.h:145:17: note: in expansion of macro ‘__asm’
145 | __asm( \
| ^~~~~
/var/lib/dkms/zfs/2.4.2/build/module/zfs/vdev_raidz_math_impl.h:1396:17: note: in expansion of macro ‘XOR_ACC’
...etc
This seems to be known and could potentially be fixed in 2.4.3
mabod commented on 2026-05-20 08:13 (UTC)
@baslking: Seems to be an issue with aarch64 architecture. You need to address this issue to the zfs developers. You can open an issue on the zfs github page: https://github.com/openzfs/zfs/issues
malibu commented on 2026-01-14 08:18 (UTC)
I removed the repo definition and it looks like yay is finding 2.4.0. Thanks I will try that. My fault for trusting an AI answer.
mabod commented on 2026-01-14 08:18 (UTC)
@malibu: zfs-dkms 2.4.0 should automatically be installed when you do a "yay -S zfs-dkms zfs-utils". You seem to have an old package database. A simple "yay -Syyu" should to the trick. This is all in the AUR. You do not need https://archzfs.com .
malibu commented on 2026-01-14 08:13 (UTC)
How do I switch my package source? I installed native arch, then installed yay, then did yay -S zfs-dkms zfs-utils. Should that not give me the latest version? Admittedly I did try the zfs repository first, does it have the wrong version? Would yay pull the package from the repository instead of from AUR? This is the repo I have configured: https://archzfs.com/$repo/$arch.
Pinned Comments
kstolp commented on 2025-04-29 16:56 (UTC) (edited on 2026-05-13 05:23 (UTC) by kstolp)
OpenZFS currently supports Linux kernel versions 4.18 - 7.0, 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
validpgpkeysarray. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheckargument tomakepkgwhen building. (not recommended)