Search Criteria
Package Details: linux-xanmod-linux-bin-x64v3 6.16.7-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-xanmod-linux-bin-x64v3.git (read-only, click to copy) |
---|---|
Package Base: | linux-xanmod-linux-bin-x64v3 |
Description: | The Linux kernel and modules with Xanmod patches - Current Stable (MAIN) - Prebuilt version - x64v3 |
Upstream URL: | http://www.xanmod.org/ |
Licenses: | GPL2 |
Submitter: | figue |
Maintainer: | figue (SoftExpert) |
Last Packager: | SoftExpert |
Votes: | 15 |
Popularity: | 0.20 |
First Submitted: | 2022-10-27 20:59 (UTC) |
Last Updated: | 2025-09-13 20:28 (UTC) |
Dependencies (2)
- curl (curl-gitAUR, curl-c-aresAUR) (make)
- libxml2 (libxml2-gitAUR) (make)
Required by (0)
Sources (2)
- https://sourceforge.net/projects/xanmod/files/releases/main/6.16.7-xanmod1/6.16.7-x64v3-xanmod1/linux-headers-6.16.7-x64v3-xanmod1_6.16.7-x64v3-xanmod1-0~20250912.g17312d2_amd64.deb
- https://sourceforge.net/projects/xanmod/files/releases/main/6.16.7-xanmod1/6.16.7-x64v3-xanmod1/linux-image-6.16.7-x64v3-xanmod1_6.16.7-x64v3-xanmod1-0~20250912.g17312d2_amd64.deb
Latest Comments
1 2 3 4 5 Next › Last »
SoftExpert commented on 2025-09-04 21:59 (UTC)
@xp499 & @MikeDee : sometimes Xanmod does a second release to remove a patch that had adverse effects; in this case the -xanmod2 suffix clearly indicates there has been a re-release (for example, here is the 6.16.4-xanmod2 change log)
A few times it happened that the initial DEB packages uploaded on SourceForge where truncated, but it was not immediately apparent; we had the time to release the package and soon after the binaries have been re-uploaded by Xanmod, rendering initial checksum obsolete.
xp499 commented on 2025-09-03 12:09 (UTC)
Seems like in their latest update they changed sourceforge file/URL structure now the kernel is called xanmod2 instead of xanmod1:
https://sourceforge.net/projects/xanmod/files/releases/lts/6.12.44-xanmod2/6.12.44-x64v3-xanmod2/
MikeDee commented on 2025-09-01 19:18 (UTC)
Fails sha256sums validity check (same with the LTS version of this kernel).
MikeDee commented on 2025-07-29 02:03 (UTC) (edited on 2025-08-07 22:28 (UTC) by MikeDee)
Deleted.
LFdev commented on 2025-07-01 21:20 (UTC)
Heads up: it seems that XanMod 6.15.x is build using LLVM, so many (all?) out-of-tree/dkms modules fail to build, there are some related issues in the official repo. I could fix some (Nvidia most notably, at least the open dkms driver) by installing lld package, but some still fail due to compatibility issues. I did not have this problem with the stock Arch kernel (6.15.4.arch2-1) so it seems to be a XanMod issue.
SoftExpert commented on 2024-06-13 05:16 (UTC)
@w568w: There was a new release of the binaries 4 hours after the initial release; I updated the package accordingly. Sorry for the confusion and thank you for the heads-up !
w568w commented on 2024-06-13 02:20 (UTC)
michalszmidt commented on 2024-04-17 21:51 (UTC)
==> Validating source files with sha256sums... linux-image-6.8.7-x64v3-xanmod1_6.8.7-x64v3-xanmod1-0~20240417.g9ed57b9_amd64.deb ... FAILED linux-headers-6.8.7-x64v3-xanmod1_6.8.7-x64v3-xanmod1-0~20240417.g9ed57b9_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check!
SoftExpert commented on 2024-02-02 04:45 (UTC)
@MikeDee: I'm getting the same and it is an issue independent of xanmod kernels. The kernel works normally, though.
This forum thread talks about the error message / bug with mkinitcpio scripts and references the issue 218 which failed to completely solve it.
If you feel adventurous, you could try changing the script mentioned, but you would be on your own.
MikeDee commented on 2024-01-22 18:08 (UTC) (edited on 2024-01-30 16:20 (UTC) by MikeDee)
I'm getting this error when the ram file system (mkinitcpio) is created:
It seems to boot OK though. This happens with Arch and Manjaro.
When running mkinitcpio with the -v option, I'm not seeing any errors in the output.
1 2 3 4 5 Next › Last »