HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
NixOS
nixos-hardware
Nix2017–2026
NixOS / nixos-hardware

nixos-hardware

A collection of NixOS modules covering hardware quirks.

16Distinct people
18Mentions
1Explicit recommenders
3.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A collection of NixOS modules covering hardware quirks.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

> People who complain about Linux usually either insist on customizing it (as you noted) or run it on hardware that it doesn't work well on. Even as someone who has customized…

tombert used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year18 dated mentions

Observed mentions: 2017-05-23 19:54:37 UTC to 2026-09-15 18:22:16 UTC.

012342017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC303
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC303

What Hacker News says

3 sources
> Part of the reason that it’s painful to use is because while it’s marketed as “declarative”, in actuality it’s functional You're correct, with a twist: NixOS is declarative, nix is not - it's indeed functional machinery. This exposes a declarative interface: https://github.com/NixOS/nixpkgs/tree/master/nixos/modules https://github.com/NixOS/nixos-hardware https://github.com/LnL7/nix-darwin/tree/master/modules This does not: https://github.com/NixOS/nixpkgs/tree/master/pkgs but being functional makes it easier for the declarative bits to exist, e.g the next step in this case (PR pending on my side to contribute just that upstream) is: - creating systemd.services."nqptp" with enabled = false as a default - transforming services.shairport-sync to reference systemd.services."nqptp".enabled = true when enableAirpla
Read the rest
y2 = true https://github.com/NixOS/nixpkgs/issues/258643 It also makes pinning/rollback to a specific version without touching the remainder of the system a spectacular non-event: https://github.com/NixOS/nixpkgs/issues/245769 Even when `.package` is not made available it's only slightly harder to use another module with disabledModules + import. > Another evening I sat down to make a minor feature to a Python library and decided to use a nix environment. In theory, this should have been better than a virtualenv. In practice, there’s no in-tree support for specifying specific versions of Python libraries, and mach-nix had trouble with the dependencies Maybe you tried too hard to "nixify" everything, including managing the whole of python stuff. That's what I use: # shell.nix { pkgs ? import <nixpkgs> {}, }: let # get these python packages from nix python_packages = python-packages: [ python-packages.pip ]; # use this pyton version, and include the above packages python = pkgs.python39.withPackages python_packages; in pkgs.mkShell { buildInputs = [ python ]; shellHook = '' # get python version export PYTHON_VERSION="$(python -c 'import platform; import re; print(re.sub(r"\.\d+$", "", platform.python_version()))')" # replicate virtualenv behaviour export PIP_PREFIX="$PWD/vendor/python/$PYTHON_VERSION/packages" export PYTHONPATH="$PIP_PREFIX/lib/python$PYTHON_VERSION/site-packages:$PYTHONPATH" unset SOURCE_DATE_EPOCH export PATH="$PIP_PREFIX/bin:$PATH" ''; } And then just `pip -r requirements` or whatever poetry you fancy. On a specific project I needed a bit more control, and some fix because of a braindead build system. Fix once and be done with it. # shell.nix { pinned ? import(fetchTarball("https://github.com/NixOS/nixpkgs/archive/88f63d51109.tar.gz")) {}, }: let # get these python packages from nix python_packages = python-packages: [ python-packages.pip ]; # use this pyton version, and include the above packages python = pinned.python39.withPackages python_packages; # control llvm/clang version (e.g for packages built from source) llvm = pinned.llvmPackages_12; in llvm.stdenv.mkDerivation { # unique project name for this environment derivation name = "whatevs.shell"; buildInputs = [ # version to use + default packages are declared above python # linters pinned.shellcheck # for scripts pinned.bash pinned.fswatch pinned.rsync # for c++ dependencies such as grpcio-tools llvm.libcxx.dev ]; shellHook = '' # get python version export PYTHON_VERSION="$(python -c 'import platform; import re; print(re.sub(r"\.\d+$", "", platform.python_version()))')" # replicate virtualenv behaviour export PIP_PREFIX="$PWD/vendor/python/$PYTHON_VERSION/packages" export PYTHONPATH="$PIP_PREFIX/lib/python$PYTHON_VERSION/site-packages:$PYTHONPATH" unset SOURCE_DATE_EPOCH export PATH="$PIP_PREFIX/bin:$PATH" # for grpcio-tools, which is building from source but doesn't pick up the proper include export CFLAGS="-I${llvm.libcxx.dev}/include/c++/v1" ''; } Sure that's not pure nix or flakesy or whatever, but simply delegating python things to python-land is a very pragmatic move, idealistic purity and reproducibility of everything be damned, it is instantly better than homebrew or docker because that setup gets you a consistent tooling environment on any Darwin (Intel or ARM, at whatever version) or Linux (whether it's NixOS or just nixpkgs). Also it's super amenable to collaborators who don't know the first thing about nix: they can blindly type `nix-shell` and be all the merrier, handling their python stuff as usual, and completely removing a whole class of "it works/breaks on my machine".
In macOS Sonoma Broke Grep

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.