kvm kernel modules clash with the VirtualBox one when accessing hardware
accelleration. Maybe the kvm module is even loaded automatically when
required, but even if that is not the case I am currently still using
VirtualBox more often than KVM-based virtualisation.
Hopefully the hardware is old enough now to work with LTS kernels. This
way we avoid build failures with 3rd party kernel modules (e.g.
virtualbox) that are not adapted yet.
- switching to NixOS 24.11 family of inputs
- after th branchoff, no channel bump or home-manager release has been
made yet, thus pointing towards some preliminary branches so far
- had to disable a few packages for now
- patch PPD to properly set the powersave level for the spu as well
- enable adaptive backlight management at lowest level
inspired by 1cbeaa156b/packages/default.nix
Inspired by https://jade.fyi/blog/flakes-arent-real/, this is better for
composability:
> it also doesn't work outside of the flake that's actually invoking nixpkgs.lib.nixosSystem. The latter is the much more sinister part, and the reason I would strongly recommend inline modules with closures instead of specialArgs: they break flake composition.
For now, the `system` remains a specialArg, until I decide what to do
with that.
