nixos-hardware
nixos-hardware copied to clipboard
NixOS
surface: linux 6.6.13 -> 6.7.6
Description of changes
Things done
- [ ] Tested the changes in your own NixOS Configuration
- [ ] Tested the changes end-to-end by using your fork of
nixos-hardwareand importing it via<nixos-hardware>or Flake input
Is it possible to build the kernel locally from inside the nixos-hardware repository? @stigtsp
this didn't work
nix-build -E "(import <nixpkgs> {}).callPackage ./microsoft/surface/common/kernel/linux-pac
kage.nix {}"
Is it possible to build the kernel locally from inside the nixos-hardware repository? @stigtsp
this didn't work
nix-build -E "(import <nixpkgs> {}).callPackage ./microsoft/surface/common/kernel/linux-pac kage.nix {}"
Because nixos-hardware tends to be trying to provide config at the machine-level, I've found it tricky to avoid running a build+install on real hardware.
Running the test suite def. catches things like syntax errors, but I personally also try to use nixos-rebuild build-vm on a faster machine, against a copy of the MS Surface's Nixos config, to pre-test it better.
If it builds at that stage, it's (so far) always been good enough to try installing on the Surface itself — which you'll ultimately have to do to check the kernel changes are working, of course!
Because nixos-hardware tends to be trying to provide config at the machine-level, I've found it tricky to avoid running a build+install on real hardware.
@mexisme , @onny Just though I'd share my workflow; what I do is from my flake;
nix build .#nixosConfigurations.<hostname>.config.system.build.toplevel -L
Then I push that result to my surface with nix copy --to "ssh://<username>@<hostname>" ./result. That allows me to build the kernel and other packages on my desktop at least, verifying it runs on the device is still necessary.
Since 6.7 is EOL, can this PR be updated to 6.8? I'm happy to test on my Surfaces :)
I think this was superseeded by https://github.com/NixOS/nixos-hardware/pull/912/files