Guix on the Framework 13 AMD

Original Article ↗ Hacker News Discussion ↗

Guix, a GNU project offering functional package management similar to Nix, is praised for its declarative configuration, strong emphasis on software freedom, and ability to run as both a full Linux distribution and a package manager atop other distros. Commenters weigh these advantages against practical trade-offs, such as limited official support for proprietary firmware, drivers, and applications—often mitigated through unofficial channels like “nonguix”—and note that this ideological stance can complicate hardware support on modern laptops like the Framework 13. The thread also touches on broader Linux usability issues, including Wayland’s fractional scaling behavior, rolling-release security updates, and how Guix compares to NixOS for stability, package availability, and real-world development workflows.

Guix vs Nix

  • Guix is inspired by Nix but is a separate implementation of functional package management.
  • Key differences:
    • Uses Guile Scheme instead of the Nix language; Scheme is used for package definitions, build scripts, initrd, and service manager (GNU Shepherd).
    • Stronger emphasis on reproducibility, bootstrapping “from source all the way down,” and supply-chain security.
    • Guix System targets GNU/Linux (and Hurd), unlike Nix which supports macOS and other Unixes.
    • Guix reuses the Nix daemon (forked C++), but most Guix usage is Guile-based; learning Nix doesn’t translate much.

Free Software stance & Nonguix

  • Core Guix channels only ship free software; nonfree components like Chrome, Nvidia drivers, firmware, and microcode are excluded.
  • Nonguix and other channels provide nonfree or “tainted” packages (full Linux kernel, firmware, CUDA, Steam, etc.).
  • Nonguix explicitly asks users not to promote it on official Guix channels, to respect Guix’s anti-nonfree policy.
  • Some see this as overly ideological and a barrier to “getting things done”; others argue it preserves clear principles while still allowing users to opt-in to nonfree channels.
  • Tension around firmware blobs and CPU microcode:
    • Critics: lack of blobs breaks hardware (wifi, GPUs, Ethernet) and leaves security issues unpatched.
    • Defenders: line-drawing is necessary to keep a truly free system and avoid expanding reliance on opaque firmware.

Wayland, GNOME, KDE, and fractional scaling

  • Many comments discuss blurry fractional scaling on Wayland, especially under GNOME with XWayland apps.
  • Conflicting reports:
    • Some say Wayland scaling is excellent and Xorg is worse; others experience the opposite.
    • KDE/Hyprland reportedly handle fractional scaling and XWayland better (e.g., options not to scale, Qt6/Chromium support).
  • Technical debate:
    • Fractional scaling of bitmaps inevitably introduces blur; vector-based rendering can look crisp.
    • New Wayland protocols (fractional scale) can avoid compositor-side scaling when apps support them, but support is incomplete.
  • Specific pain: laptops like Framework 13 or ThinkPads with “non-1x/2x” DPI often need 1.5× scaling, exposing these issues.

Guix use cases, ecosystem, and stability

  • Guix can be:
    • A Linux distro (like NixOS).
    • A package manager atop another distro.
    • A tool for reproducible dev environments (guix shell).
    • A way to build VMs/containers (guix pack, declarative OS configs, guix deploy).
  • Package coverage:
    • Core channel smaller than Nixpkgs, but many extras in separate channels (CRAN, HPC, nonfree, etc.).
    • Guix and Nix each provide services to run the other’s daemon.
  • Stability perceptions:
    • Supporters say transactional upgrades, rollbacks, and declarative configs make Guix more stable than traditional distros.
    • Skeptics report rough edges, missing or delayed package updates, and confusion when mixing Guix with native package managers.
  • Rolling-release nature means frequent updates; good for fast-moving software, less ideal for conservative server setups.

Framework 13, hardware support, and firmware

  • On Framework laptops (especially AMD), Guix can work well but:
    • Install media may lack firmware needed for Ethernet, wifi, and some GPUs, causing network or driver issues until nonguix is added.
  • Broader Linux-libre complaints:
    • Some deblobbing decisions remove even GPL’d binary arrays in drivers, making finding compatible wifi hardware difficult.
  • Several users express desire for Framework to have “no asterisks” Linux support and perhaps ship with Linux preinstalled; current official focus is on Ubuntu LTS and Fedora.