Package Details: linux-xanmod-linux-bin-x64v3 6.8.7-2

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: 13
Popularity: 1.58
First Submitted: 2022-10-27 20:59 (UTC)
Last Updated: 2024-04-17 22:25 (UTC)

Pinned Comments

SoftExpert commented on 2023-08-12 11:09 (UTC)

⚠ INFO: We had to switch to SourceForge for retrieving the binaries.

Unfortunately, the bandwidth will not always be satisfactory - so the download time could be 20x longer. Plan your updates accordingly.

Latest Comments

1 2 3 4 5 Next › Last »

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:

WARNING: errors were encountered during the build. The image may not be complete.

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.

SoftExpert commented on 2023-08-12 11:09 (UTC)

⚠ INFO: We had to switch to SourceForge for retrieving the binaries.

Unfortunately, the bandwidth will not always be satisfactory - so the download time could be 20x longer. Plan your updates accordingly.

SoftExpert commented on 2023-04-05 09:01 (UTC)

@sommio: GitHub API has a limit of 60 calls per hour; I got the same error yesterday and I just built my package later. Our package makes 2 calls to the API; we will decrease that to a single call. eget --rate https://api.github.com/repos/xanmod/linux/releases/tags/6.2.9-xanmod1 will give me, for example, the number of calls remaining for the current hour.

sommio commented on 2023-04-04 18:16 (UTC) (edited on 2023-04-04 18:17 (UTC) by sommio)

Failed to build

❯ makepkg
jq: error (at <stdin>:1): Cannot iterate over null (null)
jq: error (at <stdin>:1): Cannot iterate over null (null)
==> Making package: linux-xanmod-linux-bin-x64v3 6.2.9-3 (Tue 04 Apr 2023 18:16:50 UTC)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
==> ERROR:  was not found in the build directory and is not a URL.

jeois commented on 2023-04-02 17:22 (UTC)

@figue Ok thanks. I also had to rename /etc/mkinitcpio.d/6.2.9-x64v3-xanmod1.preset.old

figue commented on 2023-04-02 16:48 (UTC)

@jeois just check if in /boot you have the "old" vmlinuz and initrd files, and remove them. Then recreate your grub menu.

jeois commented on 2023-04-02 16:16 (UTC)

With latest build, the name change created an additional entry in Grub without replacing the previous. How do we safely remove the previous one?

figue commented on 2023-04-02 15:23 (UTC)

@MikeDee I'll revert the kernel name to $pkgbase.

Also @SoftExpert is digging to try to correct the name in Grub.

1 2 3 4 5 Next › Last »