Linux kernel - Revision history

Pandapip1: rev -> tag

2026-05-07T03:44:41Z

rev -> tag

← Older revision		Revision as of 03:44, 7 May 2026
Line 292:		Line 292:
	owner = "aramg";		owner = "aramg";
	repo = "droidcam";		repo = "droidcam";
	~~rev~~ = "v${version}";		tag = "v${version}";
	hash = "1d9qpnmqa3pfwsrpjnxdz76ipk4w37bbxyrazchh4vslnfc886fx";		hash = "1d9qpnmqa3pfwsrpjnxdz76ipk4w37bbxyrazchh4vslnfc886fx";
	};		};

Averymt: Update as of today

2026-05-04T00:06:59Z

Update as of today

← Older revision		Revision as of 00:06, 4 May 2026
Line 27:		Line 27:
	Added 12607 variables.		Added 12607 variables.

	nix-repl> pkgs.~~linuxPackages~~		nix-repl> pkgs.linuxKernel.packages
	pkgs.linuxPackages pkgs.linuxPackages_custom		pkgs.linuxPackages pkgs.linuxPackages_custom
	pkgs.linuxPackages-libre pkgs.linuxPackages_custom_tinyconfig_kernel		pkgs.linuxPackages-libre pkgs.linuxPackages_custom_tinyconfig_kernel

Sandro: Remove stub troubleshooting section

2026-01-18T09:51:14Z

Remove stub troubleshooting section

← Older revision		Revision as of 09:51, 18 January 2026
Line 614:		Line 614:
	}		}
	</syntaxhighlight>		</syntaxhighlight>

	~~== Troubleshooting ==~~
	~~=== Build fails ===~~
	~~==== Too high ram usage ====~~
	~~turn off <code>DEBUG_INFO_BTF</code>~~

	== See also ==		== See also ==

Pta2002: Update Arch kernel config link

2025-12-23T09:35:38Z

Update Arch kernel config link

← Older revision		Revision as of 09:35, 23 December 2025
Line 241:		Line 241:

	Please provide a comparison with other distributions' kernel:		Please provide a comparison with other distributions' kernel:
	~~- arch~~: https://~~github~~.~~com~~/archlinux/~~svntogit-~~packages/~~blob~~/~~packages~~/~~linux~~/~~trunk~~/config
	~~- debian~~: https://salsa.debian.org/kernel-team/linux/blob/master/debian/config/config and the ARCH specific ones		* Arch: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/blob/main/config
			* Debian: https://salsa.debian.org/kernel-team/linux/blob/master/debian/config/config and the ARCH specific ones

	== Booting a kernel from a custom source ==		== Booting a kernel from a custom source ==

Nanoyaki: /* Overriding kernel packages */ typo

2025-12-13T04:09:50Z

Overriding kernel packages: typo

← Older revision		Revision as of 04:09, 13 December 2025
Line 474:		Line 474:
	=== Overriding kernel packages ===		=== Overriding kernel packages ===

	In order to override <code>linuxPackages</code>, an alias of <code>~~linuxKernels~~.packages</code>, use the <code>extend</code> attribute. Example:		In order to override <code>linuxPackages</code>, an alias of <code>linuxKernel.packages</code>, use the <code>extend</code> attribute. Example:

	<syntaxHighlight lang=nix>		<syntaxHighlight lang=nix>
Line 500:		Line 500:
	</syntaxHighlight>		</syntaxHighlight>

	You can also use <code>kernelPackagesExtensions</code> in a similar fashion to override <code>~~linuxKernels~~.packages</code>:		You can also use <code>kernelPackagesExtensions</code> in a similar fashion to override <code>linuxKernel.packages</code>:

	<syntaxHighlight lang=nix>		<syntaxHighlight lang=nix>

Nanoyaki: /* Overriding kernel packages */ Add documentation for kernelPackagesExtensions

2025-12-13T03:53:14Z

Overriding kernel packages: Add documentation for kernelPackagesExtensions

@@ Line 474: / Line 474: @@
 === Overriding kernel packages ===
-In order to override <code>linuxPackages</code>, use the <code>extend</code> attribute. Example:
+In order to override <code>linuxPackages</code>, an alias of <code>linuxKernels.packages</code>, use the <code>extend</code> attribute. Example:
 <syntaxHighlight lang=nix>
@@ Line 498: / Line 498: @@
      })
    ];
 </syntaxHighlight>

Redchess64: fix listing kernel example

2025-12-09T03:49:08Z

fix listing kernel example

← Older revision		Revision as of 03:49, 9 December 2025
Line 24:		Line 24:
	</syntaxHighlight>		</syntaxHighlight>
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	nix-repl> :l <nixpkgs>		nix-repl> pkgs = import <nixpkgs> {}
	Added 12607 variables.		Added 12607 variables.

Axka: extraConfig in boot.kernelPatches and pkgs.buildLinux is deprecated

2025-11-05T09:50:17Z

extraConfig in boot.kernelPatches and pkgs.buildLinux is deprecated

← Older revision		Revision as of 09:50, 5 November 2025
Line 130:		Line 130:
	name = "crashdump-config";		name = "crashdump-config";
	patch = null;		patch = null;
	structuredExtraConfig = {		structuredExtraConfig = with lib.kernel; {
	CRASH_DUMP = ~~lib.kernel.~~yes;		CRASH_DUMP = yes;
	DEBUG_INFO = ~~lib.kernel.~~yes;		DEBUG_INFO = yes;
	PROC_VMCORE = ~~lib.kernel.~~yes;		PROC_VMCORE = yes;
	LOCKUP_DETECTOR = ~~lib.kernel.~~yes;		LOCKUP_DETECTOR = yes;
	HARDLOCKUP_DETECTOR = ~~lib.kernel.~~yes;		HARDLOCKUP_DETECTOR = yes;
	};		};
	} ];		} ];
Line 142:		Line 142:
	</syntaxhighlight>		</syntaxhighlight>

	~~Alternatively, you can pass a string as <code>extraConfig</code>, with option names and answers formatted like so:~~		Another way is to create an overlay to configure {{ic\|structuredExtraConfig}}. This allows for more flexibility, since you can basically override any available kernel option<ref>[https://github.com/NixOS/nixpkgs/blob/e6db435973160591fe7348876a5567c729495175/pkgs/os-specific/linux/kernel/generic.nix#L11-L56<tt>pkgs/os-specific/linux/kernel/generic.nix#L11-L56</tt>]</ref>.

	~~<pre>~~
	~~CRASH_DUMP y~~
	~~DEBUG_INFO y~~
	~~PROC_VMCORE y~~
	~~LOCKUP_DETECTOR y~~
	~~HARDLOCKUP_DETECTOR y~~
	~~</pre>~~

	Another way is to create an overlay to configure ~~either {{ic\|extraConfig}} or~~ {{ic\|structuredExtraConfig}}. This allows for more flexibility, since you can basically override any available kernel option<ref>[https://github.com/NixOS/nixpkgs/blob/e6db435973160591fe7348876a5567c729495175/pkgs/os-specific/linux/kernel/generic.nix#L11-L56<tt>pkgs/os-specific/linux/kernel/generic.nix#L11-L56</tt>]</ref>~~. Using {{ic\|structuredExtraConfig}} is recommended as it checks if the configured option are correct~~.

	{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>		{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>
Line 276:		Line 266:
	kernelPatches = [];		kernelPatches = [];

	~~extraConfig~~ = ''		structuredExtraConfig = with lib.kernel; {
	INTEL_SGX y		INTEL_SGX = yes;
	'';		};

	extraMeta.branch = "5.4";		extraMeta.branch = "5.4";

Fidgetingbits: /* Pinning a kernel version */

2025-10-21T11:54:32Z

Pinning a kernel version

← Older revision		Revision as of 11:54, 21 October 2025
Line 189:		Line 189:
	}		}
	</nowiki>}}		</nowiki>}}

			Note that pinning the kernel version will likely require manual recompilation, which may be slow on older hardware. See [https://discourse.nixos.org/t/pin-kernel-version/50630/3 this thread] for a related discussion.

	=== Debugging a failed configuration ===		=== Debugging a failed configuration ===

Sorrel: /* Custom configuration */ emphasise structuredExtraConfig and note what actually causes the "unused option" errors

2025-09-09T16:58:20Z

Custom configuration: emphasise structuredExtraConfig and note what actually causes the "unused option" errors

← Older revision		Revision as of 16:58, 9 September 2025
Line 127:		Line 127:
	<syntaxhighlight lang=nix>		<syntaxhighlight lang=nix>
	{		{
	boot.kernelPatches = [ {		boot.kernelPatches = [ {
	name = "crashdump-config";		name = "crashdump-config";
	patch = null;		patch = null;
	~~extraConfig~~ = ''		structuredExtraConfig = {
	CRASH_DUMP y		CRASH_DUMP = lib.kernel.yes;
	DEBUG_INFO y		DEBUG_INFO = lib.kernel.yes;
	PROC_VMCORE y		PROC_VMCORE = lib.kernel.yes;
	LOCKUP_DETECTOR y		LOCKUP_DETECTOR = lib.kernel.yes;
	HARDLOCKUP_DETECTOR y		HARDLOCKUP_DETECTOR = lib.kernel.yes;
	'';		};
	} ];		} ];
	}		}

	</syntaxhighlight>		</syntaxhighlight>

	Another way is to create an overlay to configure either {{ic\|extraConfig}} or {{ic\|structuredExtraConfig}}. This allows for more flexibility, since you can basically override any available kernel option<ref>[https://github.com/NixOS/nixpkgs/blob/e6db435973160591fe7348876a5567c729495175/pkgs/os-specific/linux/kernel/generic.nix#L11-L56<tt>pkgs/os-specific/linux/kernel/generic.nix#L11-L56</tt>]</ref>. Using {{ic\|structuredExtraConfig}} is recommended as it checks if the configured option are correct~~. You may also want to set {{ic\|ignoreConfigErrors}} to avoid {{ic\|error: unused option}} during builds~~.		Alternatively, you can pass a string as <code>extraConfig</code>, with option names and answers formatted like so:

			<pre>
			CRASH_DUMP y
			DEBUG_INFO y
			PROC_VMCORE y
			LOCKUP_DETECTOR y
			HARDLOCKUP_DETECTOR y
			</pre>

			Another way is to create an overlay to configure either {{ic\|extraConfig}} or {{ic\|structuredExtraConfig}}. This allows for more flexibility, since you can basically override any available kernel option<ref>[https://github.com/NixOS/nixpkgs/blob/e6db435973160591fe7348876a5567c729495175/pkgs/os-specific/linux/kernel/generic.nix#L11-L56<tt>pkgs/os-specific/linux/kernel/generic.nix#L11-L56</tt>]</ref>. Using {{ic\|structuredExtraConfig}} is recommended as it checks if the configured option are correct.

	{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>		{{file\|/etc/nixos/configuration.nix\|nix\|<nowiki>
Line 152:		Line 163:
	SCHED_MUQSS = yes;		SCHED_MUQSS = yes;
	};		};
	ignoreConfigErrors = true;		ignoreConfigErrors = true; # not necessarily a good idea
	});		});
	})		})
Line 159:		Line 170:
	}		}
	</nowiki>}}		</nowiki>}}

			If the kernel config fails to build with messages like <code>error: unused option: DRM_I915_GVT</code>, try setting e.g. <code>DRM_I915_GVT = lib.kernel.unset</code>. Setting {{ic\|ignoreConfigErrors}} will also silence these errors, at the cost of ignoring potential problems. ([https://github.com/NixOS/nixpkgs/blob/3ab9a9d12ba76f6a544c207e1364da5b3087b77c/pkgs/os-specific/linux/kernel/generate-config.pl generate-config.pl] is responsible for these; they are often produced when [https://github.com/NixOS/nixpkgs/blob/3ab9a9d12ba76f6a544c207e1364da5b3087b77c/pkgs/os-specific/linux/kernel/common-config.nix the default config] doesn't use <code>lib.kernel.option</code> for an option that is implicitly disabled by whatever change you made.)

	=== Pinning a kernel version ===		=== Pinning a kernel version ===