| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This option allows to use portions of the system RAM as block devices.
It was configured to 'y' (built-in, therefore not unloadable or
reconfigurable) and configured 16 4MB RAM disks which, to my knowledge,
currently have no purpose in NixOS.
Removing the option restores it to it's default value of 'm', which
enables it to be loaded at runtime (which is also required to be able to
change it's configuration without rebuilding the kernel).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Nixpkgs hasn't supported grsecurity kernels since 2017, so unless
anybody is manually enabling the grsecurity feature to make these
small kernel tweaks this is dead code.
This means we don't actually support any "features" in the kernel
common-config any more, but I've left the argument there because it's
conceivable we could have some again in future.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
I don't think there's any reason to have a seperate kernel variant
because of this, with all the maintenance burden that imposes. Debian
and Fedora both enable all these options on their normal kernels.
Alias the Linux Xen attributes, so this change should be seemless for
people who were using the Xen kernels up to now.
All the Xen options are marked as optional anyway, so it should be
fine to try to enable them on non-x86 platforms as well.
Fixes: https://github.com/NixOS/nixpkgs/issues/115182
|
|\ |
|
| |
| |
| |
| |
| | |
It doesn't build on i686 and I don't consider it worth deep
investigation. I tried a VM test, too (nixosTests.knot).
|
|\| |
|
| | |
|
|\ \
| |/
|/| |
linux: Enable SRv6 options
|
| | |
|
|/
|
|
|
|
|
|
| |
- Sound SOC support was refactored in
torvalds/linux@43df5242af4ed67e8811257ab1bfe6a07e4a5858
- GMA3600 is part of GMA500 as of
torvalds/linux@26499e0518a77de29e7db2c53fb0d0e9e15be8fb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Enable NVME_MULTIPATH so that a single /dev/nvmeXnY device will show
up for each NVMe namespaces, even if it is accessible through multiple
controllers. Can be disabled at boot with `nvme_core.multipath=0`.
This is default enabled in Debian [1], Ubuntu 20.04 [2] , Arch [3] and
Fedora 33 [4].
[1]: https://salsa.debian.org/kernel-team/linux/-/blob/debian/5.10.19-1/debian/config/config#L4362
[2]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/debian.master/config/config.common.ubuntu?h=Ubuntu-5.4.0-67.75#n6722
[3]: https://git.archlinux.org/svntogit/packages.git/tree/trunk/config?h=packages/linux#n2423
[4]: https://src.fedoraproject.org/rpms/kernel/blob/f33/f/kernel-x86_64-fedora.config#_4338
|
|\
| |
| | |
linux: make sure all config options have the same value
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The parent commit forbids conflicting kernel config options.
Fix the hardened kernels by allowing options in common-config.nix to
be overridden by conflicting ones in hardened/config.nix.
I'm explicitly avoiding using a higher priority (e.g. using mkForce)
in hardened/config.nix so that the user can easily override the
options in that file.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allows the RDRAND instruction to seed the kernel RNG. This should lead
to faster CRNG initialization, since the kernel can use the processors
capabilities directly. This is default enabled in Debian [1] and Fedora
[2] as well.
[1]: https://salsa.debian.org/kernel-team/linux/-/blob/debian/5.10.13-1/debian/config/config#L459
[2]: https://src.fedoraproject.org/rpms/kernel/blob/rawhide/f/kernel-x86_64-fedora.config#_4907
|
|/
|
|
| |
Required to mount filesystems with casefold enabled. Fixes #109432
|
|\
| |
| |
| |
| |
| |
| | |
Resolved the following conflicts:
- kernel flags between 09176d28a0ebbd8bae35f92406a48cded78ac9f7 and 2b28822d8dec38fd62ef17643ec71da3bb488619
- clojure-lsp between 3fa00685ce21fb1a4218d444d0862ebcb2b99706 and e03c068af5c9ca950214cd6c3b5cfe67f595da88
|
| |
| |
| |
| | |
This reverts commit b2f79fe7e74647e133b786d01fbf0065f73970fd.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
DRM_AMD_DC_DCN3_0 has been renamed DRM_AMD_DC_DCN in linux 5.11
see:
https://github.com/torvalds/linux/commit/20f2ffe504728612d7b0c34e4f8280e34251e704
https://github.com/NixOS/nixpkgs/pull/113194#issuecomment-781766471
Signed-off-by: Arthur Gautier <baloo@superbaloo.net>
|
|\ \
| | |
| | | |
linux: enable kcmp() system call
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since 2020, Mesa requires the kcmp() system call to be available for
some of its functionality. At the moment, this system call is enabled
when CHECKPOINT_RESTORE is enabled in the Linux kernel. This option is
also enabled by default in Fedora and Debian.
This patch enables CHECKPOINT_RESTORE by default on all kernel
versions where it is not marked as EXPERT, i.e. everything after and
including 4.19.
Fixes #112082.
|
|\| |
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
both https://github.com/NixOS/nixpkgs/pull/111177 and
https://github.com/NixOS/nixpkgs/pull/109105
introduced the same option.
|
|\ \ \
| |/ /
|/| | |
linux: enable display core support for all amd gpus
|
| | |
| | |
| | |
| | | |
newer amd gpus require display core to function normally
|
|\ \ \
| | | |
| | | | |
common-config: Enable RX 6000 Series AMDGPU
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
The kernel config parameter `DRM_AMD_DC_DCN3_0` is required to enable
the RX 6000 series GPUs, and is supported on kernels at least `5.9.12`.
Source: https://wiki.gentoo.org/wiki/AMDGPU#Installation
|
|\ \ \ |
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | | |
linux: enable F2FS compression
|
| | |/
| |/|
| | |
| | | |
Fixes https://github.com/NixOS/nixpkgs/issues/110534
|
|\ \ \
| |_|/
|/| | |
|
| |/ |
|
|\| |
|
| |
| |
| |
| | |
The option has been removed in the most recent dot releases
|
|/
|
|
|
|
|
|
|
|
| |
Starting from Linx 5.6, there is partial upstream support for the Multipath TCP
protocol. There are no downsides to enabling it afaict, since
applications need to opt-in when creating a socket.
From https://github.com/multipath-tcp/mptcp_net-next/wiki:
"[...] users of regular TCP continue to get the same type of connection and
performance unless MPTCP is requested."
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As per the in-line comment, this is where distros should configure it.
Not via kernel command line parameters.
As found by looking at the implementation, while exploring the cause of
a bug on the Raspberry Pi 4, it was found that `cma=` on the command
line parameters will overwrite the values a device tree will have
configured for a given platform.
With this, the more recent 5.4 vendor kernel boots just fine on the
Raspberry Pi 4 using our common configuration.
|
|\ \
| | |
| | | |
kernel: disable module signing
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Without this, the kernel would generate a random one for us which obviously
isn't reproducible.
`nix-build -A linux --check` succeeds now!
(Tested at different times with different kernel)
|
|/ |
|
|
|
|
| |
This is needed for EDAC support.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We currently build CONFIG_IPV6=m.
This seems to be not really well-supported in mainline kernels - see
https://lore.kernel.org/netdev/20201115224509.2020651-1-flokli@flokli.de/T/#u
Compiling it as a module doesn't give too much benefit - even for people
who did explicitly set `enableIPv6` to false, the `ipv6` module was
still loaded, as soon as another module was loaded that requires it
(bridge,br_netfilter,wireguard,ip6table_mangle,sctp,…).
By compiling it in, we only loose the possibility to not add it to
`boot.kernelModules` anymore (as it's part of the kernel directly). The
space savings are negligible.
People wanting to disable IPv6 still get the appropriate sysctls and
options set (while having the kernel code loaded), nothing is really
changing here.
|