Package Details: linux-cachyos-headers 6.19.8-1

Git Clone URL: https://aur.archlinux.org/linux-cachyos.git (read-only, click to copy)
Package Base: linux-cachyos
Description: Headers and scripts for building modules for the Linux EEVDF + LTO + AutoFDO + Propeller Cachy Sauce Kernel by CachyOS with other patches and improvements. kernel
Upstream URL: https://github.com/CachyOS/linux-cachyos
Keywords: cachyos kernel linux
Licenses: GPL-2.0-only
Provides: linux-cachyos-lto-headers, LINUX-HEADERS
Replaces: linux-cachyos-lto-headers
Submitter: ptr1337
Maintainer: ptr1337 (sir_lucjan)
Last Packager: sir_lucjan
Votes: 42
Popularity: 0.55
First Submitted: 2021-10-12 18:31 (UTC)
Last Updated: 2026-03-13 18:19 (UTC)

Required by (302)

Sources (3)

Latest Comments

1 2 3 4 5 6 .. 13 Next › Last »

enihcam commented on 2026-03-02 06:20 (UTC)

Can we add one extra option for building the package based on the config from a specific local path? Take linux-xanmod for example:

  # This is intended for the people that want to build this package with their own config
  # Put the file "myconfig" at the package folder (this will take preference) or "${XDG_CONFIG_HOME}/linux-xanmod/myconfig"
  # If we detect partial file with scripts/config commands, we execute as a script
  # If not, it's a full config, will be replaced
  for _myconfig in "${SRCDEST}/myconfig" "${HOME}/.config/linux-xanmod/myconfig" "${XDG_CONFIG_HOME}/linux-xanmod/myconfig" ; do
    if [ -f "${_myconfig}" ] && [ "$(wc -l <"${_myconfig}")" -gt "0" ]; then
      if grep -q 'scripts/config' "${_myconfig}"; then
        # myconfig is a partial file. Executing as a script
        msg2 "Applying myconfig..."
        bash -x "${_myconfig}"
      else
        # myconfig is a full config file. Replacing default .config
        msg2 "Using user CUSTOM config..."
        cp -f "${_myconfig}" .config
      fi
      echo
      break
    fi
  done

ptr1337 commented on 2026-02-27 12:34 (UTC)

@zerout

We have reworked now the patch handling and it uses now a complete tarball. This will help with future updates.

See: https://aur.archlinux.org/cgit/aur.git/log/?h=linux-cachyos

Zerout commented on 2026-02-27 12:14 (UTC)

Why do I get all the time errors regarding checksums on this particular AUR package? "Integrity checks (b2) differ in size from the source array."

Mr.Zero88 commented on 2026-02-01 20:09 (UTC)

the 0001-cachyos-base-all.patch checksum is wrong. It should be: 39e1bc95e388c10c4fd923965dbddee9c2c42aa721220d857f0fc9c64e6c000bb0cfc9173b569b39d46c8fe41f53584ed6b01d5842d424b2b69ba092feeca798

stagware commented on 2026-01-24 11:24 (UTC)

As far as Paru goes, -Scc should clear your helper cache for it.

grappas commented on 2026-01-18 20:12 (UTC) (edited on 2026-01-18 20:12 (UTC) by grappas) 

 0001-cachyos-base-all.patch ... FAILED
==> ERROR: One or more files did not pass the validity check!

Fails to build due to this error.

Bitals commented on 2026-01-15 08:46 (UTC)

Just remove the patches, and the config for good measure, from cache directory of whatever your AUR package manager is every time there's an update. Maybe it's possible to write a hook for paru/yay/whatever to do that, but as I personally don't use those to build I didn't look into that. Versioning the patches upstream will fix the checksum failure, but will result in all those patches accumulating on your machine over time.

ptr1337 commented on 2026-01-13 16:47 (UTC)

Yeah, it is what it is. Its the best and easiest way maintaining it for us

patlefort commented on 2026-01-13 16:42 (UTC)

makepkg also will cache the patch. The issue is that the patch file isn't properly versioned upstream. Every changes should generate a new file with a new name.

ptr1337 commented on 2026-01-13 16:37 (UTC)

The issue is that many of you are using paru or yay, which caches the patch. So the new updated patches does not get fetched from yay and it says then that the checksums are wrong.

Use makepkg to build this kernel

1 2 3 4 5 6 .. 13 Next › Last »