xddxdd / nix-cachyos-kernel

# Nix packages for CachyOS Kernel
This repo contains Linux kernels with both CachyOS patches and CachyOS tunings, as well as CachyOS-patched ZFS module.
## Which kernel versions are provided?
This repo provides the following kernel variants, consistent with the upstream definitions:
 [code] 
The kernel versions are automatically kept in sync with upstream CachyOS releases via a daily GitHub Action (see update.py), so once CachyOS updates their kernels, this repo will automatically catch up.
Use `nix flake show github:xddxdd/nix-cachyos-kernel/release` to see the current effective versions.
The kernels ending in `-lto` have Clang+ThinLTO enabled.
For each linux kernel entry under `packages`, we have a corresponding `linuxPackages` entry under `legacyPackages` for easier use in your NixOS configuration, e.g.:
- `linux-cachyos-latest` -> `inputs.nix-cachyos-kernel.legacyPackages.x86_64-linux.linuxPackages-cachyos-latest`
- `linux-cachyos-lts-lto` -> `inputs.nix-cachyos-kernel.legacyPackages.x86_64-linux.linuxPackages-cachyos-lts-lto`
## How to use kernels
#### Flakes
Add the `release` branch of this repo to the inputs section of your `flake.nix`:
 [code] 
The `release` branch contains the latest kernel that has been built by my Hydra CI and is present in binary cache.
> If you want the absolute latest version with or without binary cache, use the `master` branch (default branch) instead:
>
> [code] 
Add the repo's overlay in your NixOS configuration, this will expose the packages in this flake as `pkgs.cachyosKernels.*`.
 [code] 
Then specify `pkgs.cachyosKernels.linuxPackages-cachyos-latest` (or other variants you'd like) in your `boot.kernelPackages` option.
> **`pinned` overlay is recommended** to ensure binary cache hits. The `pinned` overlay uses the exact nixpkgs revision defined in this flake, matching what was used to build the cached kernels. With the `default` overlay, a different nixpkgs revision may cause cache misses and trigger local kernel compilation even if a cached kernel is available.
>
> Use `pinned` if:
>
> - You want to ensure that you can fetch kernel from binary cache.
> - You want to make sure that the kernel can be built successfully.
>
> Use `default` if:
>
> - You want to avoid initializing multiple instances of nixpkgs.
> - You want to use latest kernel modules that are just merged/updated within nixpkgs.
> - You want to customize `nixpkgs.config` options.
#### Non-Flakes
This flake is usable in non-flakes nix configuration using npins and the following snippet:
Npins commands:
 [code] 
 [code] 
You may also fetch the flakes directly using fetchFromGitHub,
but note that you will have to manually update the revision and hash to update your kernel, which is tedious.
### Binary cache
The binary cache is automatically configured via `nixConfig` in this flake, so Nix will prompt you to accept it when you first use this repo.
I'm running a Hydra CI to build the kernels and push them to my Attic binary cache. You can see the bu