bedHedd's NixOS Adventure

[bedHedd]

replacing peak windows with minimize all windows

I wanted to have kde minimize all windows instead of show desktop

@bedHedd

customizing kde panel to include stats on the panel

I used a similar process for network activity, cpu and memory usage. I ran the command
cat ~/.config/plasma-org.kde.plasma.desktop-appletsrc to get the configurations for the panels. Unfortunately, the customizations I made to duplicate the cpu did not work for the gpu when I had chatgpt translate it into a plasma manager config so I excluded it.

I passed the full config, but you might want to be a bit more selective and get the relevant configs for the system monitor section

I reused the same process of setting it in the gui, then dumping the config, only this time for minimize windows. Then I had chatgpt give the updated entry

@bedhedd

how do I add a entry for minimize windows within my plasma manager config?

...
        widgets = [
          {
            name = "org.kde.plasma.kickoff";
            config = {
              PreloadWeight   = 100;
              popupHeight     = 508;
              popupWidth      = 647;
              "General/icon"  = "distributor-logo-steamdeck";
            };
          }
          "org.kde.plasma.pager"
          {
            name = "org.kde.plasma.icontasks";
            config = {
              "launchers" = [
                "preferred://browser"
                "preferred://filemanager"
                "applications:org.strawberrymusicplayer.strawberry.desktop"
                "applications:steam.desktop"
              ];
              "General/sortingStrategy"   = 0;
              "General/separateLaunchers" = true;
            };
          }
          {
            name = "org.kde.plasma.systemmonitor.net";
            config = {
              CurrentPreset = "org.kde.plasma.systemmonitor";
              PreloadWeight = 90;
              popupHeight   = 200;
              popupWidth    = 210;
              "Appearance/chartFace" = "org.kde.ksysguard.linechart";
              "Appearance/title"     = "Network Speed";
              "Sensors/highPrioritySensorIds" = [
                "network/all/download"
                "network/all/upload"
              ];
              "SensorColors/network/all/download" = "0,255,255";
              "SensorColors/network/all/upload"   = "170,0,255";
            };
          }
          {
            name = "org.kde.plasma.systemmonitor.cpucore";
            config = {
              CurrentPreset = "org.kde.plasma.systemmonitor";
              PreloadWeight = 65;
              popupHeight   = 386;
              popupWidth    = 306;
              "Appearance/chartFace" = "org.kde.ksysguard.barchart";
              "Appearance/title"     = "Individual Core Usage";
              "Sensors/highPrioritySensorIds" = [ "cpu/cpu.*/usage" ];
              "Sensors/totalSensors"          = [ "cpu/all/usage" ];
            };
          }
          {
            name = "org.kde.plasma.systemmonitor.memory";
            config = {
              CurrentPreset = "org.kde.plasma.systemmonitor";
              PreloadWeight = 95;
              popupHeight   = 240;
              popupWidth    = 244;
              "Appearance/chartFace" = "org.kde.ksysguard.piechart";
              "Appearance/title"     = "Memory Usage";
              "Sensors/highPrioritySensorIds" = [ "memory/physical/used" ];
              "Sensors/lowPrioritySensorIds"  = [ "memory/physical/total" ];
              "Sensors/totalSensors"          = [ "memory/physical/usedPercent" ];
              "SensorColors/memory/physical/used" = "0,0,255";
            };
          }
          "org.kde.plasma.marginsseparator"
          "org.kde.plasma.systemtray"
          {
            name = "org.kde.plasma.digitalclock";
            config = {
              popupHeight = 400;
              popupWidth  = 560;
              "Appearance/fontWeight" = 400;
            };
          }
          "org.kde.plasma.showdesktop"
        ];

for this when I did cat ~/.config/plasma-org.kde.plasma.desktop-appletsrc

[Containments][1069][Applets][1096]
immutability=1
plugin=org.kde.plasma.minimizeall

@chatgpt

Perfect — you’re very close.

You already found that the “Minimize All Windows” widget (also called “Show Desktop”) has the plugin ID:
org.kde.plasma.minimizeall

If you want to add that explicitly to your Plasma Manager config (kde-home.nix) under the widgets list, it should look like this:

{
  name = "org.kde.plasma.minimizeall";
  config = {
    immutability = 1;
  };
}

So your full widgets array will look like (for example):

widgets = [
  {
    name = "org.kde.plasma.kickoff";
    config = {
      PreloadWeight   = 100;
      popupHeight     = 508;
      popupWidth      = 647;
      "General/icon"  = "distributor-logo-steamdeck";
    };
  }
  "org.kde.plasma.pager"
  {
    name = "org.kde.plasma.icontasks";
    config = {
      "launchers" = [
        "preferred://browser"
        "preferred://filemanager"
        "applications:org.strawberrymusicplayer.strawberry.desktop"
        "applications:steam.desktop"
      ];
      "General/sortingStrategy"   = 0;
      "General/separateLaunchers" = true;
    };
  }
  # Add minimize all
  {
    name = "org.kde.plasma.minimizeall";
    config = {
      immutability = 1;
    };
  }
  "org.kde.plasma.marginsseparator"
  "org.kde.plasma.systemtray"
  {
    name = "org.kde.plasma.digitalclock";
    config = {
      popupHeight = 400;
      popupWidth  = 560;
      "Appearance/fontWeight" = 400;
    };
  }
  "org.kde.plasma.showdesktop"
];

---

Notes

• Both org.kde.plasma.minimizeall and org.kde.plasma.showdesktop appear to “minimize everything,” but:

  • showdesktop toggles between showing/hiding the desktop (like Win+D).

  • minimizeall literally minimizes all windows (like Win+M).

  You can safely use just one, depending on your behavior preference.

• If you want it at a specific panel position, Plasma Manager typically maps this widgets array in order (left → right on a bottom panel, or top → bottom on a vertical panel). So just insert it wherever you want it to appear visually.

---

Would you like me to show how to add it with a separator and space before the clock (like many default KDE layouts do)?

[bedHedd]

issues building rocm

I have been getting issues building rocm when I try to update my flake. First it was this error

(buildPhase): ValueError: Cannot register /loky-71561-czmiym1q for automatic cleanup: unknown resource type semlock

Asking chatgpt, it was able to find this github issue, which has a similar

Build failure: rocmPackages.hipblaslt

it was apparently fixed here

rocmPackages.hipblaslt: massively reduce peak disk space usage

Chatgpt suggested the following

@chatgpt

Yep—that’s a known hiccup coming from joblib/loky during the Tensile step of the hipBLASLt build. It shows up like:

ValueError: Cannot register /loky-XXXX for automatic cleanup: unknown resource type semlock

It isn’t your config; it’s a current nixpkgs/ROCm build bug (Python 3.13 + loky resource tracking). See the open nixpkgs issue for rocmPackages.hipblaslt from Oct 8, 2025. (GitHub)

Fast ways to get unstuck

Option A — Pin nixpkgs to a good rev

• Temporarily pin to a nixpkgs revision from before Oct 8, 2025 (or to 25.05) where hipblaslt still built. This avoids the regression entirely. (GitHub)

Option B — Disable loky’s multiprocessing just for this build
Add a tiny overlay to force Tensile’s internal joblib to use threads (or a safer start method), which dodges the semlock registration:

# in your flake or overlays
(final: prev: {
  rocmPackages = prev.rocmPackages // {
    hipblaslt = prev.rocmPackages.hipblaslt.overrideAttrs (old: {
      env = (old.env or {}) // {
        JOBLIB_MULTIPROCESSING = "0";   # force threading backend
        JOBLIB_START_METHOD   = "forkserver"; # safer than fork on modern Python
        LOKY_MAX_CPU_COUNT    = "1";    # be conservative
      };
    });
  };
})

JOBLIB_MULTIPROCESSING and JOBLIB_START_METHOD are recognized knobs in joblib/loky to change how workers are spawned. (joblib.readthedocs.io)

Option C — Temporarily drop whatever pulls in hipBLASLt
If you don’t actually need ROCm libraries for this build (e.g., you’re just gaming), remove packages that depend on ROCm (e.g., pytorchWithRocm, ROCm dev stuff) from your system profile until nixpkgs lands a fix. The open issue confirms it’s tracked on nixpkgs’ side. (GitHub)

---

If you want, paste your flake/system package set and I’ll point out exactly which input is dragging in hipblaslt and give you the minimal edit to proceed.

Doing some more digging, I found the commit that had the change applied

rocmPackages.hipblaslt: massively reduce peak disk space usage (#451188)

I asked chatgpt the following

@bedhedd

there was a commit 9hrs ago, how do I check if I have it
rocmPackages.hipblaslt: massively reduce peak disk space usage (#451188) · NixOS/nixpkgs@1b3f5cf · GitHub

it suggested the following

@chatgpt

Here’s how to check whether your flake is locked to that exact nixpkgs commit
1b3f5cfe80ed35a6f25e884abe291e224560d2f5 (a hipBLASLt-related change) (GitHub)

1) See what your flake is currently locked to

# From the repo that has your flake.nix / flake.lock
jq -r '.nodes.nixpkgs.locked.rev' flake.lock
jq -r '.nodes.nixpkgs.locked.lastModified' flake.lock

(or)

nix flake metadata --json | jq -r '.locks.nodes.nixpkgs.locked.rev,.locks.nodes.nixpkgs.locked.lastModified'

If the printed rev equals:

1b3f5cfe80ed35a6f25e884abe291e224560d2f5

…then you already have it.

2) Update to that specific commit (if you don’t have it yet)

One-shot, no code changes:

nix flake lock \
  --update-input nixpkgs \
  --override-input nixpkgs github:NixOS/nixpkgs/1b3f5cfe80ed35a6f25e884abe291e224560d2f5

Verify:

jq -r '.nodes.nixpkgs.locked.rev' flake.lock

3) (Optional) Pin in flake.nix

If you want it pinned in the flake itself (not just the lock file), change:

inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";

to:

inputs.nixpkgs.url = "github:NixOS/nixpkgs?rev=1b3f5cfe80ed35a6f25e884abe291e224560d2f5";

Then refresh the lock:

nix flake lock --update-input nixpkgs

4) Rebuild

sudo nixos-rebuild switch --flake .#<your-host>

If you want, paste the output of step (1) and I’ll confirm whether you’re on that commit or not.

I checked the nixpkgs entry in flake.lock and it returned the following:

...
    "nixpkgs": {
      "locked": {
        "lastModified": 1760524057,
        "narHash": "sha256-EVAqOteLBFmd7pKkb0+FIUyzTF61VKi7YmvP1tw4nEw=",
        "owner": "NixOS",
        "repo": "nixpkgs",
        "rev": "544961dfcce86422ba200ed9a0b00dd4b1486ec5",
        "type": "github"
      },

I then ran chatgpt suggeste I run this flake command

nix flake lock \
  --update-input nixpkgs \
  --override-input nixpkgs github:NixOS/nixpkgs/1b3f5cfe80ed35a6f25e884abe291e224560d2f5

which returned the following output

warning: '--update-input' is a deprecated alias for 'flake update' and will be removed in a future version.
warning: Git tree '/home/bedhedd/Documents/development_projects/bedhedd_projects/nix-config-local' is dirty
warning: updating lock file '"/home/bedhedd/Documents/development_projects/bedhedd_projects/nix-config-local/flake.lock"':
• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/544961dfcce86422ba200ed9a0b00dd4b1486ec5?narHash=sha256-EVAqOteLBFmd7pKkb0%2BFIUyzTF61VKi7YmvP1tw4nEw%3D' (2025-10-15)
  → 'github:NixOS/nixpkgs/1b3f5cfe80ed35a6f25e884abe291e224560d2f5?narHash=sha256-xa7%2BXcnBxrWFN9UWAM8wY9Ub4/sLq1sggKFosZsaXcc%3D' (2025-10-16)
warning: Git tree '/home/bedhedd/Documents/development_projects/bedhedd_projects/nix-config-local' is dirty

I then ran

sudo nixos-rebuild switch --flake .#master-of-cooling

which the error went away

[bedHedd]

grouping librewolf windows by profile

I have multiple librewolf profiles to allow me to have separate browsing profiles for research and hobbies.

By default, wayland and kde’s window grouping will merge all librewolf windows together.

separating the profiles

If you want to see the config, it is here

create separte profiles

I started by asking chatgpt how to add multiple librewolf profiles to launch specific profiles. It suggested I create a profile then apply these home manager configs.

@chatgpt

You can make separate launchers that pin each LibreWolf profile. Two steps:

1) Create/confirm your profiles

Either open the profile manager:

librewolf --ProfileManager

…or create by name:

librewolf -CreateProfile "Work"
librewolf -CreateProfile "Personal"

(You can also just run librewolf -P Work once; it’ll create the profile on first launch.)

Tip: Use -no-remote --new-instance so profiles can run side-by-side.

---

2) Add desktop shortcuts

Option A — Home-Manager (recommended for you)

Add this to your Home-Manager config:

xdg.desktopEntries = {
  librewolf-work = {
    name = "LibreWolf (Work)";
    genericName = "Web Browser";
    comment = "LibreWolf with the Work profile";
    exec = "librewolf -P Work -no-remote --new-instance %u";
    terminal = false;
    type = "Application";
    categories = [ "Network" "WebBrowser" ];
    mimeType = [ "text/html" "x-scheme-handler/http" "x-scheme-handler/https" ];
    icon = "librewolf";
    startupWMClass = "LibreWolf";
  };

  librewolf-personal = {
    name = "LibreWolf (Personal)";
    genericName = "Web Browser";
    comment = "LibreWolf with the Personal profile";
    exec = "librewolf -P Personal -no-remote --new-instance %u";
    terminal = false;
    type = "Application";
    categories = [ "Network" "WebBrowser" ];
    mimeType = [ "text/html" "x-scheme-handler/http" "x-scheme-handler/https" ];
    icon = "librewolf";
    startupWMClass = "LibreWolf";
  };
};

Then rebuild your HM config. You’ll get two separate launchers in your menu and you can pin each to your taskbar.

Option B — Manual .desktop files (any distro/DE)

Create files like these in ~/.local/share/applications/:

librewolf-work.desktop

[Desktop Entry]
Name=LibreWolf (Work)
GenericName=Web Browser
Comment=LibreWolf with the Work profile
Exec=librewolf -P Work -no-remote --new-instance %u
Terminal=false
Type=Application
Categories=Network;WebBrowser;
MimeType=text/html;x-scheme-handler/http;x-scheme-handler/https;
Icon=librewolf
StartupWMClass=LibreWolf

librewolf-personal.desktop

[Desktop Entry]
Name=LibreWolf (Personal)
GenericName=Web Browser
Comment=LibreWolf with the Personal profile
Exec=librewolf -P Personal -no-remote --new-instance %u
Terminal=false
Type=Application
Categories=Network;WebBrowser;
MimeType=text/html;x-scheme-handler/http;x-scheme-handler/https;
Icon=librewolf
StartupWMClass=LibreWolf

Run:

update-desktop-database ~/.local/share/applications  # optional

---

Flatpak variant (if you use it)

Replace Exec= with:

Exec=flatpak run io.gitlab.librewolf-community -P Work -no-remote --new-instance %u

(and same for Personal).

---

Nice touches

• Give each profile its own icon by changing Icon= and placing custom icons in ~/.local/share/icons/.
• For KDE, right-click each launcher → “Add to Panel” or “Pin to Task Manager” for one-click access.

If you share your Home-Manager repo, I can drop this directly into your module with your exact profile names.

The config worked in setting up new shortcuts from the start menu. After realizing the xdg configs, I decided it would be a good idea to consolidate all my xdg configs into a single place. You can find the file here

BedHedd/nix-config/blob/master/modules/xdg.nix

Once I got it all consolidated into the xdg file, I then wanted to fix the taskbar to also be separated. Chatgpt suggested I use xwayland, but I wanted to set it up for the long term

@chatgpt

Gotcha — that happens on KDE Wayland because LibreWolf’s windows all look like the same app (same Wayland app-id), so Plasma groups them under one icon. You’ve got two reliable fixes:

Fix A (most reliable): run these profile launchers under XWayland

This lets us use a unique WM_CLASS per profile, which Plasma will keep as separate icons.

xdg.desktopEntries = {
  librewolf-work = {
    name = "LibreWolf (Work)";
    exec = ''env MOZ_ENABLE_WAYLAND=0 librewolf --class LibreWolf-Work -P Work -no-remote --new-instance %u'';
    icon = "librewolf";
    terminal = false;
    type = "Application";
    categories = [ "Network" "WebBrowser" ];
    mimeType = [ "text/html" "x-scheme-handler/http" "x-scheme-handler/https" ];
    settings = { StartupWMClass = "LibreWolf-Work"; };
  };

  librewolf-personal = {
    name = "LibreWolf (Personal)";
    exec = ''env MOZ_ENABLE_WAYLAND=0 librewolf --class LibreWolf-Personal -P Personal -no-remote --new-instance %u'';
    icon = "librewolf";
    terminal = false;
    type = "Application";
    categories = [ "Network" "WebBrowser" ];
    mimeType = [ "text/html" "x-scheme-handler/http" "x-scheme-handler/https" ];
    settings = { StartupWMClass = "LibreWolf-Personal"; };
  };
}

Why this works:

• MOZ_ENABLE_WAYLAND=0 forces XWayland.
• --class gives each profile a unique WM_CLASS.
• StartupWMClass ties each window class to its launcher so each stays on its own taskbar icon.

(You can confirm with xprop WM_CLASS on each window.)

Fix B (Wayland-native, may or may not work on your build)

Some GTK apps let you set a unique Wayland app-id via --name. If your LibreWolf build honors it, do:

xdg.desktopEntries.librewolf-work = {
  name = "LibreWolf (Work)";
  exec = ''librewolf --name LibreWolf-Work -P Work -no-remote --new-instance %u'';
  settings = {
    # Helps Plasma map the Wayland app-id to this launcher
    X-KDE-WaylandAppId = "LibreWolf-Work";
  };
};
xdg.desktopEntries.librewolf-personal = {
  name = "LibreWolf (Personal)";
  exec = ''librewolf --name LibreWolf-Personal -P Personal -no-remote --new-instance %u'';
  settings = {
    X-KDE-WaylandAppId = "LibreWolf-Personal";
  };
};

If LibreWolf ignores --name, stick with Fix A.

---

Extra checks (quick wins)

• Make sure there’s no top-level startupWMClass = ... in your entries; only put it under settings = { StartupWMClass = "..."; };

• Profile names are case-sensitive: -P Work vs -P work.

• After rebuilding HM, refresh KDE’s app cache:

  kbuildsycoca6 --noincremental || kbuildsycoca5 --noincremental
  

• Task Manager settings: right-click the panel → Configure Task Manager → set Grouping to “By program name” (or “Do not group” while testing) and Show only tasks from current screen/activity to taste.

Pick A if you want it to “just work” today; try B if you want native Wayland and your build supports per-window app-ids.

While checking the two options, I kept getting a bug where launching the individual profile would always start the choose profile

the solution chatgpt suggested was

@chatgpt

Got it — let’s keep it Wayland-native. Use a unique Wayland app-id per profile and tell Plasma to map it to each launcher.

What to do

1. Give each launcher a unique app-id via --name.
2. In the .desktop entry, set X-KDE-WaylandAppId to the same value.
3. Don’t use StartupWMClass (that’s X11/XWayland).

Nix (Home-Manager) snippet

xdg.desktopEntries = {
  librewolf-personal = {
    name = "LibreWolf (Personal)";
    comment = "LibreWolf with the Personal profile";
    exec = ''librewolf --name librewolf-personal -P personal --no-remote --new-instance %u'';
    icon = "librewolf";
    terminal = false;
    type = "Application";
    categories = [ "Network" "WebBrowser" ];
    mimeType = [ "text/html" "x-scheme-handler/http" "x-scheme-handler/https" ];
    settings = {
      X-KDE-WaylandAppId = "librewolf-personal";
    };
  };

  librewolf-professional = {
    name = "LibreWolf (Professional)";
    comment = "LibreWolf with the Professional profile";
    exec = ''librewolf --name librewolf-professional -P professional --no-remote --new-instance %u'';
    icon = "librewolf";
    terminal = false;
    type = "Application";
    categories = [ "Network" "WebBrowser" ];
    mimeType = [ "text/html" "x-scheme-handler/http" "x-scheme-handler/https" ];
    settings = {
      X-KDE-WaylandAppId = "librewolf-professional";
    };
  };
}

Notes

• --name <id> sets the Wayland app-id for that window.

• X-KDE-WaylandAppId tells Plasma to attach windows with that app-id to this launcher → separate taskbar icons, no merging.

• Keep --no-remote --new-instance so an already-running window doesn’t grab the request and ignore -P.

• Profile names are case-sensitive. Use exactly what’s shown in your profile list (personal, professional, etc.).

• After rebuilding, refresh KDE’s app cache:

  kbuildsycoca6 --noincremental || kbuildsycoca5 --noincremental
  

  Then (re)pin each launcher.

If windows still group, open Task Manager settings and set Grouping to “By application” (or temporarily “Do not group” to verify). This setup is fully Wayland-native—no XWayland needed.

This got it working

changing and recoloring the librewolf icons

I was hoping that the librewolf icons would be in a svg format as it is easier to swap colors out.

looking at the files in /nix/store/r1qc6s4mgapnbhzx10gi8g0rvw82g0m1-librewolf-143.0.3-1/share/icons/hicolor

tree /nix/store/r1qc6s4mgapnbhzx10gi8g0rvw82g0m1-librewolf-143.0.3-1/share/icons/hicolor

.
├── 128x128
│   └── apps
│       └── librewolf.png -> /nix/store/1yy909syv1dhb5y5v4zjg5kddw80l0m5-librewolf-unwrapped-143.0.3-1/lib/librewolf/browser/chrome/icons/default/default128.png
├── 16x16
│   └── apps
│       └── librewolf.png -> /nix/store/1yy909syv1dhb5y5v4zjg5kddw80l0m5-librewolf-unwrapped-143.0.3-1/lib/librewolf/browser/chrome/icons/default/default16.png
├── 32x32
│   └── apps
│       └── librewolf.png -> /nix/store/1yy909syv1dhb5y5v4zjg5kddw80l0m5-librewolf-unwrapped-143.0.3-1/lib/librewolf/browser/chrome/icons/default/default32.png
├── 48x48
│   └── apps
│       └── librewolf.png -> /nix/store/1yy909syv1dhb5y5v4zjg5kddw80l0m5-librewolf-unwrapped-143.0.3-1/lib/librewolf/browser/chrome/icons/default/default48.png
└── 64x64
    └── apps
        └── librewolf.png -> /nix/store/1yy909syv1dhb5y5v4zjg5kddw80l0m5-librewolf-unwrapped-143.0.3-1/lib/librewolf/browser/chrome/icons/default/default64.png

Unfortunately, it is only a png. I tried having chatgpt write code to recolor the icons. It would either leave a blue outline, miss the wolf icon, or miss the wolf and still have a blue icon

code it generated if you want it

{ config, lib, pkgs, ... }:

let
  # Your palette
  colorPersonal     = "#8d4953";
  colorProfessional = "#5b7b65";
  colorMaster       = "#0e0e0e";

  sizes = [ 16 32 48 64 128 256 512 ];
  candidateBlues = [ "#00acff" "#00a9e0" "#23a3dc" "#1ea0db" ];

  # Prefer SVG if present (sharper at big sizes); else choose the largest PNG available.
  svgPath = "${pkgs.librewolf}/share/icons/hicolor/scalable/apps/librewolf.svg";
  pngCandidates =
    map (sz: "${pkgs.librewolf}/share/icons/hicolor/${sz}/apps/librewolf.png")
      [ "512x512" "256x256" "128x128" "64x64" "48x48" "32x32" ];

  baseIsSvg = builtins.pathExists svgPath;
  basePng =
    let xs = builtins.filter (p: builtins.pathExists p) pngCandidates;
    in if xs == [] then
         throw "LibreWolf icon PNG not found under ${pkgs.librewolf}"
       else
         builtins.head xs;

  mkPngSet = name: hex:
    pkgs.runCommand "icons-${name}" {
      buildInputs = [ pkgs.imagemagick pkgs.librsvg pkgs.coreutils ];
    } ''
      set -eu
      outdir="$out/share/icons/hicolor"
      mkdir -p "$outdir"

      # Nix-escaped values
      HEX=${lib.escapeShellArg hex}

      render_base () {
        # $1 = target size (e.g. 128)
        # print path to a temp PNG at that size
        sz="$1"
        tmp="$(mktemp --suffix=.png)"
        if ${lib.boolToString baseIsSvg}; then
          ${pkgs.librsvg}/bin/rsvg-convert -w "$sz" -h "$sz" ${lib.escapeShellArg svgPath} -o "$tmp"
        else
          ${pkgs.imagemagick}/bin/convert ${basePng} -resize ''${sz}x''${sz} "$tmp"
        fi
        printf "%s\n" "$tmp"
      }

      recolor_into () {
        # $1 = inpng, $2 = outpng
        inpng="$1"; outpng="$2"
        # Work on RGB only; keep alpha untouched to avoid halos
        work="$(mktemp --suffix=.png)"
        cp "$inpng" "$work"

        # Slightly stricter fuzz to avoid re-coloring greys/whites unintentionally
        for BLUE in ${lib.concatStringsSep " " (map (b: "'${b}'") candidateBlues)}; do
          ${pkgs.imagemagick}/bin/convert "$work" \
            -alpha on -channel RGB -fuzz 20% -fill "$HEX" -opaque "$BLUE" +channel \
            "$work"
        done
        mv "$work" "$outpng"
      }

      for sz in ${lib.concatStringsSep " " (map toString sizes)}; do
        dir="$outdir/''${sz}x''${sz}/apps"
        mkdir -p "$dir"
        base_png="$(render_base "$sz")"
        recolor_into "$base_png" "$dir/librewolf-${name}.png"
      done
    '';

  pngPersonal     = mkPngSet "personal"     colorPersonal;
  pngProfessional = mkPngSet "professional" colorProfessional;
  pngMaster       = mkPngSet "master"       colorMaster;

  mkXdgPngFiles = name: drv:
    lib.listToAttrs (map (sz: {
      name  = "icons/hicolor/${toString sz}x${toString sz}/apps/librewolf-${name}.png";
      value = { source = "${drv}/share/icons/hicolor/${toString sz}x${toString sz}/apps/librewolf-${name}.png"; };
    }) sizes);

in {
  xdg.dataFile =
    mkXdgPngFiles "personal"      pngPersonal
    // mkXdgPngFiles "professional" pngProfessional
    // mkXdgPngFiles "master"        pngMaster;
}

code it generated if you want it

let
  # … your colors …
  candidateBlues = [
    # originals
    "#00acff" "#00a9e0" "#23a3dc" "#1ea0db"
    # common ring/halo variants (lighter/darker cyans)
    "#00b4ff" "#00bfff" "#00c0ff" "#00ccff" "#00d4ff" "#00e5ff" "#18ffff"
    "#26c6da" "#29b6f6" "#33b5e5" "#40c4ff" "#4dd0e1" "#80deea"
  ];

  mkPngSet = name: hex:
    pkgs.runCommand "icons-${name}" {
      buildInputs = [ pkgs.imagemagick pkgs.librsvg pkgs.coreutils ];
    } ''
      set -eu
      outdir="$out/share/icons/hicolor"
      mkdir -p "$outdir"

      HEX=${lib.escapeShellArg hex}

      # 1) Make a large master (do this once)
      master="$(mktemp --suffix=.png)"
      if ${lib.boolToString (builtins.pathExists svgPath)}; then
        ${pkgs.librsvg}/bin/rsvg-convert -w 1024 -h 1024 ${lib.escapeShellArg svgPath} -o "$master"
      else
        ${pkgs.imagemagick}/bin/convert ${basePng} -resize 1024x1024 "$master"
      fi

      # 2) Recolor ONCE at full res: broader fuzz to catch halo pixels; RGB only to preserve alpha
      work="$(mktemp --suffix=.png)"
      cp "$master" "$work"
      for BLUE in ${lib.concatStringsSep " " (map (b: "'${b}'") candidateBlues)}; do
        ${pkgs.imagemagick}/bin/convert "$work" \
          -alpha on -channel RGB -fuzz 40% -fill "$HEX" -opaque "$BLUE" +channel \
          "$work"
      done

      # Optional: clamp tiny remaining cyan halos by desaturating very-blue remnants a touch
      ${pkgs.imagemagick}/bin/convert "$work" \
        -alpha on -modulate 100,98,100 +alpha "$work"

      # 3) Downscale the recolored master to all sizes (no new blue is introduced)
      for sz in ${lib.concatStringsSep " " (map toString sizes)}; do
        dir="$outdir/''${sz}x''${sz}/apps"
        mkdir -p "$dir"
        ${pkgs.imagemagick}/bin/convert "$work" \
          -filter Lanczos -define filter:lobes=3 -resize ''${sz}x''${sz} \
          "$dir/librewolf-${name}.png"
      done
    '';

code it generated if you want it

mkPngSet = name: hex:
pkgs.runCommand “icons-${name}” { buildInputs = [ pkgs.imagemagick pkgs.coreutils ]; } ‘’
set -eu
outdir=“$out/share/icons/hicolor”
mkdir -p “$outdir”

  # 1) Make a single high-res recolor using a mask (preserves anti-aliasing)
  workdir="$(${pkgs.coreutils}/bin/mktemp -d)"
  master="$workdir/master.png"
  mask="$workdir/mask.png"
  tmp="$workdir/tmp.png"

  # Start from the best available base (your basePng), do NOT resize yet.
  ${pkgs.coreutils}/bin/cp ${basePng} "$master"

  # Build a mask that ORs all candidate blues together, with a small blur to soften edges.
  # Result: white where the cyan stroke is, black elsewhere.
  ${pkgs.imagemagick}/bin/convert -size "$(${pkgs.imagemagick}/bin/identify -format '%wx%h' "$master")" xc:black "$mask"
  for BLUE in ${lib.concatStringsSep " " (map (b: "'${b}'") candidateBlues)}; do
    ${pkgs.imagemagick}/bin/convert "$master" \
      -colorspace sRGB -fuzz 18% -fill white -opaque "$BLUE" \
      -alpha extract -threshold 50% "$tmp"
    ${pkgs.imagemagick}/bin/convert "$mask" "$tmp" -compose Lighten -composite "$mask"
  done
  # Feather the mask slightly to avoid crunchy edges.
  ${pkgs.imagemagick}/bin/convert "$mask" -morphology close disk:1 -blur 0x0.6 "$mask"

  # Create a solid color layer and copy the mask into its alpha, then composite over original.
  ${pkgs.imagemagick}/bin/convert "$master" -fill '${hex}' -colorize 100 "$tmp"
  ${pkgs.imagemagick}/bin/convert "$tmp" "$mask" -compose CopyOpacity -composite "$tmp"
  ${pkgs.imagemagick}/bin/convert "$master" "$tmp" -compose Over -composite "$workdir/recolored.png"

  # 2) Now generate all sizes from the recolored master (better resampling, consistent edges).
  for sz in ${lib.concatStringsSep " " (map toString sizes)}; do
    dir="$outdir/''${sz}x''${sz}/apps"
    ${pkgs.coreutils}/bin/mkdir -p "$dir"
    ${pkgs.imagemagick}/bin/convert "$workdir/recolored.png" \
      -filter Lanczos -define filter:lobes=3 \
      -resize ''${sz}x''${sz} \
      -unsharp 0x0.75+0.75+0.02 \
      "$dir/librewolf-${name}.png"
  done
'';

After getting nowhere with having chatgpt write code to recolor the png, I decided to have it write code to modify the librewolf svg from wikipedia

File:LibreWolf icon.svg

I used the dev tools to get the svg code and passed this prompt to chatgpt

@bedhedd

librewolf’s svg is here. can we just update our code for this svg text

<svg xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" width="67.733337mm" height="67.733337mm" viewBox="0 0 67.733337 67.733337" version="1.1" id="svg8" inkscape:version="0.92.4 5da689c313, 2019-01-14" sodipodi:docname="LibreWolf.svg">
  <defs id="defs2"/>
  <sodipodi:namedview id="base" pagecolor="#ffffff" bordercolor="#666666" borderopacity="1.0" inkscape:pageopacity="0.0" inkscape:pageshadow="2" inkscape:zoom="0.9899495" inkscape:cx="-15.106575" inkscape:cy="110.91343" inkscape:document-units="mm" inkscape:current-layer="layer1" showgrid="false" inkscape:window-width="1366" inkscape:window-height="711" inkscape:window-x="0" inkscape:window-y="30" inkscape:window-maximized="1" inkscape:showpageshadow="false" units="px" fit-margin-top="0" fit-margin-left="0" fit-margin-right="0" fit-margin-bottom="0"/>
  <metadata id="metadata5">
    <rdf:RDF>
      <cc:Work rdf:about="">
        <dc:format>image/svg+xml</dc:format>
        <dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage"/>
        <dc:title/>
      </cc:Work>
    </rdf:RDF>
  </metadata>
  <g inkscape:label="Layer 1" inkscape:groupmode="layer" id="layer1" transform="translate(-42.106554,-153.8982)">
    <circle style="fill:#00acff;fill-opacity:1;stroke:none;stroke-width:0.53545821;stroke-miterlimit:4;stroke-dasharray:none" id="path875" cx="75.973221" cy="187.76486" r="33.866669"/>
    <path style="fill:#ffffff;stroke-width:0.13229167" d="m 72.543594,214.67719 c -4.744093,-0.60875 -9.281981,-2.49991 -13.241953,-5.51858 -1.29157,-0.98455 -3.714943,-3.42363 -4.772834,-4.80375 -2.96241,-3.86476 -4.804479,-8.2508 -5.41218,-12.88661 -0.260164,-1.98464 -0.258719,-5.63349 0.0029,-7.44738 1.308078,-9.0677 7.01463,-16.8454 15.20915,-20.72918 3.811512,-1.80647 7.300266,-2.57114 11.730683,-2.57114 7.165903,0 13.5265,2.56749 18.680882,7.54063 2.483054,2.39575 4.148141,4.66808 5.573968,7.60677 1.92868,3.9751 2.70979,7.43276 2.70979,11.99526 0,6.00619 -1.7345,11.24407 -5.336957,16.11672 -1.070527,1.44797 -3.161747,3.64749 -4.549468,4.78507 -3.806562,3.12041 -8.658642,5.23183 -13.473174,5.86296 -1.663528,0.21807 -5.593318,0.24524 -7.120854,0.0492 z m 10.041381,-4.86547 c 2.898391,-0.91366 5.260364,-2.14146 7.540624,-3.91979 1.212494,-0.9456 3.308223,-3.06144 4.186916,-4.22711 2.38328,-3.16162 4.004927,-7.12196 4.482067,-10.94597 0.229814,-1.84182 0.09634,-5.73827 -0.2545,-7.4296 -0.9294,-4.48046 -2.931647,-8.26499 -6.086007,-11.50342 -1.966575,-2.01898 -3.756882,-3.34972 -6.060203,-4.50458 -3.495001,-1.75236 -6.489835,-2.46043 -10.423481,-2.46442 -4.164073,-0.004 -7.815325,0.95024 -11.429055,2.98766 -3.289753,1.85476 -6.690628,5.25952 -8.553227,8.563 -1.371786,2.43299 -2.37583,5.32029 -2.767595,7.95869 -0.256867,1.72991 -0.261933,5.16508 -0.01006,6.82145 0.504067,3.31489 1.761474,6.59111 3.584314,9.33904 0.995409,1.50058 0.964154,1.48393 1.842248,0.98153 1.570774,-0.8987 1.980396,-1.33342 2.836087,-3.00984 1.000624,-1.96036 2.070459,-3.6735 3.037094,-4.86332 1.115822,-1.37347 1.269228,-1.61793 1.828988,-2.9147 0.281654,-0.65249 0.786977,-1.61074 1.122938,-2.12943 l 0.61084,-0.94309 -0.79023,-0.77671 c -1.049647,-1.03168 -1.922751,-2.2016 -2.087012,-2.79651 -0.167761,-0.60758 0.03021,-0.9466 0.818744,-1.40207 0.797354,-0.46057 1.367585,-0.5929 3.498657,-0.81193 1.037629,-0.10665 2.164153,-0.30199 2.518962,-0.43681 0.353024,-0.13414 1.407825,-0.70824 2.344001,-1.27579 2.702947,-1.63863 2.931619,-1.72344 4.552111,-1.68831 1.368686,0.0297 1.371262,0.0291 2.182813,-0.46143 1.700674,-1.02802 4.14305,-2.88289 7.357044,-5.58733 0.61632,-0.5186 1.21002,-0.92569 1.31934,-0.90464 0.45462,0.0876 1.289567,2.13636 1.416407,3.47562 0.07693,0.81225 -0.08023,1.6155 -0.562014,2.87261 -0.13146,0.34301 -0.19208,0.67043 -0.134706,0.7276 0.13774,0.13726 0.610706,-0.4535 0.610706,-0.76279 0,-0.39435 0.261127,-0.43936 0.616327,-0.10623 0.258235,0.24218 0.480842,0.31151 1.000202,0.31151 0.567073,0 0.707447,0.0526 0.928773,0.3479 0.375574,0.50112 0.463647,1.86688 0.176201,2.73231 -0.279641,0.84191 -1.124801,1.81287 -1.891829,2.17341 -0.686334,0.32262 -2.075841,1.67928 -2.726081,2.66164 -0.248906,0.37604 -0.715586,1.15995 -1.037066,1.74204 -0.321487,0.58208 -0.86074,1.46154 -1.19834,1.95436 -0.664294,0.96972 -1.233147,2.3224 -1.782214,4.23798 -0.322553,1.1253 -0.34962,1.41826 -0.362953,3.92797 -0.01613,3.0317 -0.172894,3.77561 -0.9925,4.7091 -0.931805,1.06126 -1.861937,3.39186 -1.940127,4.8613 -0.04935,0.92751 -0.192246,1.83164 -0.395304,2.50122 -0.08942,0.29484 0.07752,0.2914 1.072102,-0.0221 z" id="path847" inkscape:connector-curvature="0"/>
    <path sodipodi:type="star" style="fill:#00acff;fill-opacity:1;stroke:none;stroke-width:1.5;stroke-miterlimit:4;stroke-dasharray:none" id="path814" sodipodi:sides="4" sodipodi:cx="18.854025" sodipodi:cy="172.98837" sodipodi:r1="1.6036172" sodipodi:r2="1.1339285" sodipodi:arg1="1.5707963" sodipodi:arg2="2.3561945" inkscape:flatsided="true" inkscape:rounded="0" inkscape:randomized="0" d="m 18.854025,174.59199 -1.603617,-1.60362 1.603617,-1.60361 1.603617,1.60361 z" transform="matrix(0.23203125,0.40188991,-0.99392962,0.57384553,246.21921,73.888081)"/>
  </g>
</svg>

embed this file into the config

I tested the code and it worked

BedHedd/nix-config/blob/master/modules/xdg-librewolf-icons.nix

I then added the librewolf icons to my user import

BedHedd/nix-config/blob/e17b36db5a3484de195c95a22d2d515eb5f588f3/users/bedhedd.nix#L53

in

BedHedd/nix-config/blob/master/users/bedhedd.nix

[bedHedd]

f3 - Fight Flash Fraud

I wanted a linux equivalent of H2testw from windows

bedHedd's blog because discourse > twitter

Boy this took a while [image] Got a new Samsung 512 EVO Micro SD card, so I needed to verify it was legit by using H2testw Which was referenced here https://www.maketecheasier.com/check-sd-card-speed-capacity/

based on the suggestions from reddit and ask ubuntu channel
https://old.reddit.com/r/linux4noobs/comments/14zjcfu/how_to_test_real_capacity_of_an_internal_drive/jry2z5f/

Check real size of USB thumb drive

F3 was suggested
https://fight-flash-fraud.readthedocs.io/en/stable/usage.html

Since I didn’t feel like adding it to my config, I ran it in a nix shell

nix-shell -p f3

I then looked for sd card using the volume using the properties to find where it is mounted

After finding the path, I then ran

f3write /run/media/bedhedd/1D07-3000/

f3 write output

F3 write 9.0
Copyright (C) 2010 Digirati Internet LTDA.
This is free software; see the source for copying conditions.

Removing old file 1.h2w ...
Removing old file 2.h2w ...
Removing old file 3.h2w ...
Removing old file 4.h2w ...
Removing old file 5.h2w ...
Removing old file 6.h2w ...
Removing old file 7.h2w ...
Removing old file 8.h2w ...
Removing old file 9.h2w ...
Removing old file 10.h2w ...
Removing old file 11.h2w ...
Removing old file 12.h2w ...
Removing old file 13.h2w ...
Removing old file 14.h2w ...
Removing old file 15.h2w ...
Removing old file 16.h2w ...
Removing old file 17.h2w ...
Removing old file 18.h2w ...
Removing old file 19.h2w ...
Removing old file 20.h2w ...
Removing old file 21.h2w ...
Removing old file 22.h2w ...
Removing old file 23.h2w ...
Removing old file 24.h2w ...
Removing old file 25.h2w ...
Removing old file 26.h2w ...
Removing old file 27.h2w ...
Removing old file 28.h2w ...
Removing old file 29.h2w ...
Removing old file 30.h2w ...
Removing old file 31.h2w ...
Removing old file 32.h2w ...
Removing old file 33.h2w ...
Removing old file 34.h2w ...
Removing old file 35.h2w ...
Removing old file 36.h2w ...
Removing old file 37.h2w ...
Removing old file 38.h2w ...
Removing old file 39.h2w ...
Removing old file 40.h2w ...
Removing old file 41.h2w ...
Removing old file 42.h2w ...
Removing old file 43.h2w ...
Removing old file 44.h2w ...
Removing old file 45.h2w ...
Removing old file 46.h2w ...
Removing old file 47.h2w ...
Removing old file 48.h2w ...
Removing old file 49.h2w ...
Removing old file 50.h2w ...
Removing old file 51.h2w ...
Removing old file 52.h2w ...
Removing old file 53.h2w ...
Removing old file 54.h2w ...
Removing old file 55.h2w ...
Removing old file 56.h2w ...
Removing old file 57.h2w ...
Removing old file 58.h2w ...
Removing old file 59.h2w ...
Removing old file 60.h2w ...
Removing old file 61.h2w ...
Removing old file 62.h2w ...
Removing old file 63.h2w ...
Removing old file 64.h2w ...
Removing old file 65.h2w ...
Removing old file 66.h2w ...
Removing old file 67.h2w ...
Removing old file 68.h2w ...
Removing old file 69.h2w ...
Removing old file 70.h2w ...
Removing old file 71.h2w ...
Removing old file 72.h2w ...
Removing old file 73.h2w ...
Removing old file 74.h2w ...
Removing old file 75.h2w ...
Removing old file 76.h2w ...
Removing old file 77.h2w ...
Removing old file 78.h2w ...
Removing old file 79.h2w ...
Removing old file 80.h2w ...
Removing old file 81.h2w ...
Removing old file 82.h2w ...
Removing old file 83.h2w ...
Removing old file 84.h2w ...
Removing old file 85.h2w ...
Removing old file 86.h2w ...
Removing old file 87.h2w ...
Removing old file 88.h2w ...
Removing old file 89.h2w ...
Removing old file 90.h2w ...
Free space: 232.19 GB
Creating file 1.h2w ... OK!                           
Creating file 2.h2w ... OK!                           
Creating file 3.h2w ... OK!                           
Creating file 4.h2w ... OK!                           
Creating file 5.h2w ... OK!                           
Creating file 6.h2w ... OK!                           
Creating file 7.h2w ... OK!                           
Creating file 8.h2w ... OK!                           
Creating file 9.h2w ... OK!                           
Creating file 10.h2w ... OK!                           
Creating file 11.h2w ... OK!                           
Creating file 12.h2w ... OK!                           
Creating file 13.h2w ... OK!                           
Creating file 14.h2w ... OK!                           
Creating file 15.h2w ... OK!                           
Creating file 16.h2w ... OK!                           
Creating file 17.h2w ... OK!                           
Creating file 18.h2w ... OK!                           
Creating file 19.h2w ... OK!                           
Creating file 20.h2w ... OK!                           
Creating file 21.h2w ... OK!                           
Creating file 22.h2w ... OK!                           
Creating file 23.h2w ... OK!                           
Creating file 24.h2w ... OK!                            
Creating file 25.h2w ... OK!                            
Creating file 26.h2w ... OK!                            
Creating file 27.h2w ... OK!                            
Creating file 28.h2w ... OK!                            
Creating file 29.h2w ... OK!                            
Creating file 30.h2w ... OK!                            
Creating file 31.h2w ... OK!                            
Creating file 32.h2w ... OK!                            
Creating file 33.h2w ... OK!                            
Creating file 34.h2w ... OK!                            
Creating file 35.h2w ... OK!                            
Creating file 36.h2w ... OK!                            
Creating file 37.h2w ... OK!                            
Creating file 38.h2w ... OK!                            
Creating file 39.h2w ... OK!                            
Creating file 40.h2w ... OK!                            
Creating file 41.h2w ... OK!                            
Creating file 42.h2w ... OK!                            
Creating file 43.h2w ... OK!                            
Creating file 44.h2w ... OK!                            
Creating file 45.h2w ... OK!                            
Creating file 46.h2w ... OK!                            
Creating file 47.h2w ... OK!                            
Creating file 48.h2w ... OK!                            
Creating file 49.h2w ... OK!                            
Creating file 50.h2w ... OK!                            
Creating file 51.h2w ... OK!                            
Creating file 52.h2w ... OK!                            
Creating file 53.h2w ... OK!                            
Creating file 54.h2w ... OK!                            
Creating file 55.h2w ... OK!                            
Creating file 56.h2w ... OK!                            
Creating file 57.h2w ... OK!                            
Creating file 58.h2w ... OK!                            
Creating file 59.h2w ... OK!                            
Creating file 60.h2w ... OK!                            
Creating file 61.h2w ... OK!                            
Creating file 62.h2w ... OK!                            
Creating file 63.h2w ... OK!                            
Creating file 64.h2w ... OK!                            
Creating file 65.h2w ... OK!                            
Creating file 66.h2w ... OK!                            
Creating file 67.h2w ... OK!                            
Creating file 68.h2w ... OK!                            
Creating file 69.h2w ... OK!                            
Creating file 70.h2w ... OK!                            
Creating file 71.h2w ... OK!                            
Creating file 72.h2w ... OK!                            
Creating file 73.h2w ... OK!                            
Creating file 74.h2w ... OK!                            
Creating file 75.h2w ... OK!                            
Creating file 76.h2w ... OK!                            
Creating file 77.h2w ... OK!                            
Creating file 78.h2w ... OK!                            
Creating file 79.h2w ... OK!                            
Creating file 80.h2w ... OK!                            
Creating file 81.h2w ... OK!                            
Creating file 82.h2w ... OK!                            
Creating file 83.h2w ... OK!                            
Creating file 84.h2w ... OK!                            
Creating file 85.h2w ... OK!                            
Creating file 86.h2w ... OK!                            
Creating file 87.h2w ... OK!                            
Creating file 88.h2w ... OK!                            
Creating file 89.h2w ... OK!                            
Creating file 90.h2w ... OK!                            
Creating file 91.h2w ... OK!                            
Creating file 92.h2w ... OK!                            
Creating file 93.h2w ... OK!                            
Creating file 94.h2w ... OK!                            
Creating file 95.h2w ... OK!                            
Creating file 96.h2w ... OK!                            
Creating file 97.h2w ... OK!                            
Creating file 98.h2w ... OK!                            
Creating file 99.h2w ... OK!                            
Creating file 100.h2w ... OK!                            
Creating file 101.h2w ... OK!                            
Creating file 102.h2w ... OK!                            
Creating file 103.h2w ... OK!                            
Creating file 104.h2w ... OK!                            
Creating file 105.h2w ... OK!                            
Creating file 106.h2w ... OK!                            
Creating file 107.h2w ... OK!                            
Creating file 108.h2w ... OK!                            
Creating file 109.h2w ... OK!                            
Creating file 110.h2w ... OK!                            
Creating file 111.h2w ... OK!                            
Creating file 112.h2w ... OK!                            
Creating file 113.h2w ... OK!                            
Creating file 114.h2w ... OK!                            
Creating file 115.h2w ... OK!                            
Creating file 116.h2w ... OK!                            
Creating file 117.h2w ... OK!                            
Creating file 118.h2w ... OK!                            
Creating file 119.h2w ... OK!                            
Creating file 120.h2w ... OK!                            
Creating file 121.h2w ... OK!                            
Creating file 122.h2w ... OK!                            
Creating file 123.h2w ... OK!                            
Creating file 124.h2w ... OK!                            
Creating file 125.h2w ... OK!                            
Creating file 126.h2w ... OK!                            
Creating file 127.h2w ... OK!                            
Creating file 128.h2w ... OK!                            
Creating file 129.h2w ... OK!                            
Creating file 130.h2w ... OK!                            
Creating file 131.h2w ... OK!                            
Creating file 132.h2w ... OK!                            
Creating file 133.h2w ... OK!                            
Creating file 134.h2w ... OK!                            
Creating file 135.h2w ... OK!                            
Creating file 136.h2w ... OK!                            
Creating file 137.h2w ... OK!                            
Creating file 138.h2w ... OK!                            
Creating file 139.h2w ... OK!                            
Creating file 140.h2w ... OK!                            
Creating file 141.h2w ... OK!                            
Creating file 142.h2w ... OK!                            
Creating file 143.h2w ... OK!                            
Creating file 144.h2w ... OK!                            
Creating file 145.h2w ... OK!                            
Creating file 146.h2w ... OK!                            
Creating file 147.h2w ... OK!                            
Creating file 148.h2w ... OK!                            
Creating file 149.h2w ... OK!                            
Creating file 150.h2w ... OK!                            
Creating file 151.h2w ... OK!                            
Creating file 152.h2w ... OK!                            
Creating file 153.h2w ... OK!                            
Creating file 154.h2w ... OK!                            
Creating file 155.h2w ... OK!                            
Creating file 156.h2w ... OK!                            
Creating file 157.h2w ... OK!                            
Creating file 158.h2w ... OK!                            
Creating file 159.h2w ... OK!                            
Creating file 160.h2w ... OK!                            
Creating file 161.h2w ... OK!                            
Creating file 162.h2w ... OK!                            
Creating file 163.h2w ... OK!                            
Creating file 164.h2w ... OK!                            
Creating file 165.h2w ... OK!                            
Creating file 166.h2w ... OK!                            
Creating file 167.h2w ... OK!                            
Creating file 168.h2w ... OK!                            
Creating file 169.h2w ... OK!                            
Creating file 170.h2w ... OK!                            
Creating file 171.h2w ... OK!                            
Creating file 172.h2w ... OK!                            
Creating file 173.h2w ... OK!                            
Creating file 174.h2w ... OK!                          
Creating file 175.h2w ... OK!                          
Creating file 176.h2w ... OK!                          
Creating file 177.h2w ... OK!                          
Creating file 178.h2w ... OK!                          
Creating file 179.h2w ... OK!                          
Creating file 180.h2w ... OK!                          
Creating file 181.h2w ... OK!                          
Creating file 182.h2w ... OK!                          
Creating file 183.h2w ... OK!                          
Creating file 184.h2w ... OK!                          
Creating file 185.h2w ... OK!                          
Creating file 186.h2w ... OK!                          
Creating file 187.h2w ... OK!                          
Creating file 188.h2w ... OK!                          
Creating file 189.h2w ... OK!                          
Creating file 190.h2w ... OK!                          
Creating file 191.h2w ... OK!                          
Creating file 192.h2w ... OK!                          
Creating file 193.h2w ... OK!                          
Creating file 194.h2w ... OK!                          
Creating file 195.h2w ... OK!                          
Creating file 196.h2w ... OK!                          
Creating file 197.h2w ... OK!                          
Creating file 198.h2w ... OK!                          
Creating file 199.h2w ... OK!                          
Creating file 200.h2w ... OK!                          
Creating file 201.h2w ... OK!                          
Creating file 202.h2w ... OK!                          
Creating file 203.h2w ... OK!                          
Creating file 204.h2w ... OK!                          
Creating file 205.h2w ... OK!                          
Creating file 206.h2w ... OK!                          
Creating file 207.h2w ... OK!                          
Creating file 208.h2w ... OK!                          
Creating file 209.h2w ... OK!                          
Creating file 210.h2w ... OK!                          
Creating file 211.h2w ... OK!                          
Creating file 212.h2w ... OK!                          
Creating file 213.h2w ... OK!                          
Creating file 214.h2w ... OK!                          
Creating file 215.h2w ... OK!                          
Creating file 216.h2w ... OK!                          
Creating file 217.h2w ... OK!                          
Creating file 218.h2w ... OK!                          
Creating file 219.h2w ... OK!                          
Creating file 220.h2w ... OK!                          
Creating file 221.h2w ... OK!                          
Creating file 222.h2w ... OK!                          
Creating file 223.h2w ... OK!                          
Creating file 224.h2w ... OK!                         
Creating file 225.h2w ... OK!                         
Creating file 226.h2w ... OK!                         
Creating file 227.h2w ... OK!                         
Creating file 228.h2w ... OK!                         
Creating file 229.h2w ... OK!                         
Creating file 230.h2w ... OK!                         
Creating file 231.h2w ... OK!                         
Creating file 232.h2w ... OK!                         
Creating file 233.h2w ... OK!                        
Free space: 0.00 Byte
Average writing speed: 17.08 MB/s

After F3 finished the write, I then ran f3read

 f3read /run/media/bedhedd/1D07-3000

f3 read output

F3 read 9.0
Copyright (C) 2010 Digirati Internet LTDA.
This is free software; see the source for copying conditions.

                  SECTORS      ok/corrupted/changed/overwritten
Validating file 1.h2w ... 2097152/        0/      0/      0
Validating file 2.h2w ... 2097152/        0/      0/      0
Validating file 3.h2w ... 2097152/        0/      0/      0
Validating file 4.h2w ... 2097152/        0/      0/      0
Validating file 5.h2w ... 2097152/        0/      0/      0
Validating file 6.h2w ... 2097152/        0/      0/      0
Validating file 7.h2w ... 2097152/        0/      0/      0
Validating file 8.h2w ... 2097152/        0/      0/      0
Validating file 9.h2w ... 2097152/        0/      0/      0
Validating file 10.h2w ... 2097152/        0/      0/      0
Validating file 11.h2w ... 2097152/        0/      0/      0
Validating file 12.h2w ... 2097152/        0/      0/      0
Validating file 13.h2w ... 2097152/        0/      0/      0
Validating file 14.h2w ... 2097152/        0/      0/      0
Validating file 15.h2w ... 2097152/        0/      0/      0
Validating file 16.h2w ... 2097152/        0/      0/      0
Validating file 17.h2w ... 2097152/        0/      0/      0
Validating file 18.h2w ... 2097152/        0/      0/      0
Validating file 19.h2w ... 2097152/        0/      0/      0
Validating file 20.h2w ... 2097152/        0/      0/      0
Validating file 21.h2w ... 2097152/        0/      0/      0
Validating file 22.h2w ... 2097152/        0/      0/      0
Validating file 23.h2w ... 2097152/        0/      0/      0
Validating file 24.h2w ... 2097152/        0/      0/      0
Validating file 25.h2w ... 2097152/        0/      0/      0
Validating file 26.h2w ... 2097152/        0/      0/      0
Validating file 27.h2w ... 2097152/        0/      0/      0
Validating file 28.h2w ... 2097152/        0/      0/      0
Validating file 29.h2w ... 2097152/        0/      0/      0
Validating file 30.h2w ... 2097152/        0/      0/      0
Validating file 31.h2w ... 2097152/        0/      0/      0
Validating file 32.h2w ... 2097152/        0/      0/      0
Validating file 33.h2w ... 2097152/        0/      0/      0
Validating file 34.h2w ... 2097152/        0/      0/      0
Validating file 35.h2w ... 2097152/        0/      0/      0
Validating file 36.h2w ... 2097152/        0/      0/      0
Validating file 37.h2w ... 2097152/        0/      0/      0
Validating file 38.h2w ... 2097152/        0/      0/      0
Validating file 39.h2w ... 2097152/        0/      0/      0
Validating file 40.h2w ... 2097152/        0/      0/      0
Validating file 41.h2w ... 2097152/        0/      0/      0
Validating file 42.h2w ... 2097152/        0/      0/      0
Validating file 43.h2w ... 2097152/        0/      0/      0
Validating file 44.h2w ... 2097152/        0/      0/      0
Validating file 45.h2w ... 2097152/        0/      0/      0
Validating file 46.h2w ... 2097152/        0/      0/      0
Validating file 47.h2w ... 2097152/        0/      0/      0
Validating file 48.h2w ... 2097152/        0/      0/      0
Validating file 49.h2w ... 2097152/        0/      0/      0
Validating file 50.h2w ... 2097152/        0/      0/      0
Validating file 51.h2w ... 2097152/        0/      0/      0
Validating file 52.h2w ... 2097152/        0/      0/      0
Validating file 53.h2w ... 2097152/        0/      0/      0
Validating file 54.h2w ... 2097152/        0/      0/      0
Validating file 55.h2w ... 2097152/        0/      0/      0
Validating file 56.h2w ... 2097152/        0/      0/      0
Validating file 57.h2w ... 2097152/        0/      0/      0
Validating file 58.h2w ... 2097152/        0/      0/      0
Validating file 59.h2w ... 2097152/        0/      0/      0
Validating file 60.h2w ... 2097152/        0/      0/      0
Validating file 61.h2w ... 2097152/        0/      0/      0
Validating file 62.h2w ... 2097152/        0/      0/      0
Validating file 63.h2w ... 2097152/        0/      0/      0
Validating file 64.h2w ... 2097152/        0/      0/      0
Validating file 65.h2w ... 2097152/        0/      0/      0
Validating file 66.h2w ... 2097152/        0/      0/      0
Validating file 67.h2w ... 2097152/        0/      0/      0
Validating file 68.h2w ... 2097152/        0/      0/      0
Validating file 69.h2w ... 2097152/        0/      0/      0
Validating file 70.h2w ... 2097152/        0/      0/      0
Validating file 71.h2w ... 2097152/        0/      0/      0
Validating file 72.h2w ... 2097152/        0/      0/      0
Validating file 73.h2w ... 2097152/        0/      0/      0
Validating file 74.h2w ... 2097152/        0/      0/      0
Validating file 75.h2w ... 2097152/        0/      0/      0
Validating file 76.h2w ... 2097152/        0/      0/      0
Validating file 77.h2w ... 2097152/        0/      0/      0
Validating file 78.h2w ... 2097152/        0/      0/      0
Validating file 79.h2w ... 2097152/        0/      0/      0
Validating file 80.h2w ... 2097152/        0/      0/      0
Validating file 81.h2w ... 2097152/        0/      0/      0
Validating file 82.h2w ... 2097152/        0/      0/      0
Validating file 83.h2w ... 2097152/        0/      0/      0
Validating file 84.h2w ... 2097152/        0/      0/      0
Validating file 85.h2w ... 2097152/        0/      0/      0
Validating file 86.h2w ... 2097152/        0/      0/      0
Validating file 87.h2w ... 2097152/        0/      0/      0
Validating file 88.h2w ... 2097152/        0/      0/      0
Validating file 89.h2w ... 2097152/        0/      0/      0
Validating file 90.h2w ... 2097152/        0/      0/      0
Validating file 91.h2w ... 2097152/        0/      0/      0
Validating file 92.h2w ... 2097152/        0/      0/      0
Validating file 93.h2w ... 2097152/        0/      0/      0
Validating file 94.h2w ... 2097152/        0/      0/      0
Validating file 95.h2w ... 2097152/        0/      0/      0
Validating file 96.h2w ... 2097152/        0/      0/      0
Validating file 97.h2w ... 2097152/        0/      0/      0
Validating file 98.h2w ... 2097152/        0/      0/      0
Validating file 99.h2w ... 2097152/        0/      0/      0
Validating file 100.h2w ... 2097152/        0/      0/      0
Validating file 101.h2w ... 2097152/        0/      0/      0
Validating file 102.h2w ... 2097152/        0/      0/      0
Validating file 103.h2w ... 2097152/        0/      0/      0
Validating file 104.h2w ... 2097152/        0/      0/      0
Validating file 105.h2w ... 2097152/        0/      0/      0
Validating file 106.h2w ... 2097152/        0/      0/      0
Validating file 107.h2w ... 2097152/        0/      0/      0
Validating file 108.h2w ... 2097152/        0/      0/      0
Validating file 109.h2w ... 2097152/        0/      0/      0
Validating file 110.h2w ... 2097152/        0/      0/      0
Validating file 111.h2w ... 2097152/        0/      0/      0
Validating file 112.h2w ... 2097152/        0/      0/      0
Validating file 113.h2w ... 2097152/        0/      0/      0
Validating file 114.h2w ... 2097152/        0/      0/      0
Validating file 115.h2w ... 2097152/        0/      0/      0
Validating file 116.h2w ... 2097152/        0/      0/      0
Validating file 117.h2w ... 2097152/        0/      0/      0
Validating file 118.h2w ... 2097152/        0/      0/      0
Validating file 119.h2w ... 2097152/        0/      0/      0
Validating file 120.h2w ... 2097152/        0/      0/      0
Validating file 121.h2w ... 2097152/        0/      0/      0
Validating file 122.h2w ... 2097152/        0/      0/      0
Validating file 123.h2w ... 2097152/        0/      0/      0
Validating file 124.h2w ... 2097152/        0/      0/      0
Validating file 125.h2w ... 2097152/        0/      0/      0
Validating file 126.h2w ... 2097152/        0/      0/      0
Validating file 127.h2w ... 2097152/        0/      0/      0
Validating file 128.h2w ... 2097152/        0/      0/      0
Validating file 129.h2w ... 2097152/        0/      0/      0
Validating file 130.h2w ... 2097152/        0/      0/      0
Validating file 131.h2w ... 2097152/        0/      0/      0
Validating file 132.h2w ... 2097152/        0/      0/      0
Validating file 133.h2w ... 2097152/        0/      0/      0
Validating file 134.h2w ... 2097152/        0/      0/      0
Validating file 135.h2w ... 2097152/        0/      0/      0
Validating file 136.h2w ... 2097152/        0/      0/      0
Validating file 137.h2w ... 2097152/        0/      0/      0
Validating file 138.h2w ... 2097152/        0/      0/      0
Validating file 139.h2w ... 2097152/        0/      0/      0
Validating file 140.h2w ... 2097152/        0/      0/      0
Validating file 141.h2w ... 2097152/        0/      0/      0
Validating file 142.h2w ... 2097152/        0/      0/      0
Validating file 143.h2w ... 2097152/        0/      0/      0
Validating file 144.h2w ... 2097152/        0/      0/      0
Validating file 145.h2w ... 2097152/        0/      0/      0
Validating file 146.h2w ... 2097152/        0/      0/      0
Validating file 147.h2w ... 2097152/        0/      0/      0
Validating file 148.h2w ... 2097152/        0/      0/      0
Validating file 149.h2w ... 2097152/        0/      0/      0
Validating file 150.h2w ... 2097152/        0/      0/      0
Validating file 151.h2w ... 2097152/        0/      0/      0
Validating file 152.h2w ... 2097152/        0/      0/      0
Validating file 153.h2w ... 2097152/        0/      0/      0
Validating file 154.h2w ... 2097152/        0/      0/      0
Validating file 155.h2w ... 2097152/        0/      0/      0
Validating file 156.h2w ... 2097152/        0/      0/      0
Validating file 157.h2w ... 2097152/        0/      0/      0
Validating file 158.h2w ... 2097152/        0/      0/      0
Validating file 159.h2w ... 2097152/        0/      0/      0
Validating file 160.h2w ... 2097152/        0/      0/      0
Validating file 161.h2w ... 2097152/        0/      0/      0
Validating file 162.h2w ... 2097152/        0/      0/      0
Validating file 163.h2w ... 2097152/        0/      0/      0
Validating file 164.h2w ... 2097152/        0/      0/      0
Validating file 165.h2w ... 2097152/        0/      0/      0
Validating file 166.h2w ... 2097152/        0/      0/      0
Validating file 167.h2w ... 2097152/        0/      0/      0
Validating file 168.h2w ... 2097152/        0/      0/      0
Validating file 169.h2w ... 2097152/        0/      0/      0
Validating file 170.h2w ... 2097152/        0/      0/      0
Validating file 171.h2w ... 2097152/        0/      0/      0
Validating file 172.h2w ... 2097152/        0/      0/      0
Validating file 173.h2w ... 2097152/        0/      0/      0
Validating file 174.h2w ... 2097152/        0/      0/      0
Validating file 175.h2w ... 2097152/        0/      0/      0
Validating file 176.h2w ... 2097152/        0/      0/      0
Validating file 177.h2w ... 2097152/        0/      0/      0
Validating file 178.h2w ... 2097152/        0/      0/      0
Validating file 179.h2w ... 2097152/        0/      0/      0
Validating file 180.h2w ... 2097152/        0/      0/      0
Validating file 181.h2w ... 2097152/        0/      0/      0
Validating file 182.h2w ... 2097152/        0/      0/      0
Validating file 183.h2w ... 2097152/        0/      0/      0
Validating file 184.h2w ... 2097152/        0/      0/      0
Validating file 185.h2w ... 2097152/        0/      0/      0
Validating file 186.h2w ... 2097152/        0/      0/      0
Validating file 187.h2w ... 2097152/        0/      0/      0
Validating file 188.h2w ... 2097152/        0/      0/      0
Validating file 189.h2w ... 2097152/        0/      0/      0
Validating file 190.h2w ... 2097152/        0/      0/      0
Validating file 191.h2w ... 2097152/        0/      0/      0
Validating file 192.h2w ... 2097152/        0/      0/      0
Validating file 193.h2w ... 2097152/        0/      0/      0
Validating file 194.h2w ... 2097152/        0/      0/      0
Validating file 195.h2w ... 2097152/        0/      0/      0
Validating file 196.h2w ... 2097152/        0/      0/      0
Validating file 197.h2w ... 2097152/        0/      0/      0
Validating file 198.h2w ... 2097152/        0/      0/      0
Validating file 199.h2w ... 2097152/        0/      0/      0
Validating file 200.h2w ... 2097152/        0/      0/      0
Validating file 201.h2w ... 2097152/        0/      0/      0
Validating file 202.h2w ... 2097152/        0/      0/      0
Validating file 203.h2w ... 2097152/        0/      0/      0
Validating file 204.h2w ... 2097152/        0/      0/      0
Validating file 205.h2w ... 2097152/        0/      0/      0
Validating file 206.h2w ... 2097152/        0/      0/      0
Validating file 207.h2w ... 2097152/        0/      0/      0
Validating file 208.h2w ... 2097152/        0/      0/      0
Validating file 209.h2w ... 2097152/        0/      0/      0
Validating file 210.h2w ... 2097152/        0/      0/      0
Validating file 211.h2w ... 2097152/        0/      0/      0
Validating file 212.h2w ... 2097152/        0/      0/      0
Validating file 213.h2w ... 2097152/        0/      0/      0
Validating file 214.h2w ... 2097152/        0/      0/      0
Validating file 215.h2w ... 2097152/        0/      0/      0
Validating file 216.h2w ... 2097152/        0/      0/      0
Validating file 217.h2w ... 2097152/        0/      0/      0
Validating file 218.h2w ... 2097152/        0/      0/      0
Validating file 219.h2w ... 2097152/        0/      0/      0
Validating file 220.h2w ... 2097152/        0/      0/      0
Validating file 221.h2w ... 2097152/        0/      0/      0
Validating file 222.h2w ... 2097152/        0/      0/      0
Validating file 223.h2w ... 2097152/        0/      0/      0
Validating file 224.h2w ... 2097152/        0/      0/      0
Validating file 225.h2w ... 2097152/        0/      0/      0
Validating file 226.h2w ... 2097152/        0/      0/      0
Validating file 227.h2w ... 2097152/        0/      0/      0
Validating file 228.h2w ... 2097152/        0/      0/      0
Validating file 229.h2w ... 2097152/        0/      0/      0
Validating file 230.h2w ... 2097152/        0/      0/      0
Validating file 231.h2w ... 2097152/        0/      0/      0
Validating file 232.h2w ... 2097152/        0/      0/      0
Validating file 233.h2w ...  403968/        0/      0/      0

  Data OK: 232.19 GB (486943232 sectors)
Data LOST: 0.00 Byte (0 sectors)
	       Corrupted: 0.00 Byte (0 sectors)
	Slightly changed: 0.00 Byte (0 sectors)
	     Overwritten: 0.00 Byte (0 sectors)
Average reading speed: 21.21 MB/s

Once it finished, I formatted the microsd with gnome disks so that the camera would be ready to use it

[teltersat]

Maybe try this tool? Not sure if it’s legitimate but it sounds like it is:

GitHub - c0xc/CapacityTester: Use CapacityTester to check if your USB...

[bedHedd]

I didn’t see it on the nix packages search, also f3 was nice because it won’t overwrite any files. It took about a day to run write and read, but it worked good enough that I didn’t feel the need to look for alternatives

[bedHedd]

unable to sleep and suspend to ram with latest update

I had some issues with my computer not sleeping properly after a recent nix flake update. It would be unresponsive and broken. The about this system that had issues was:

Operating System: NixOS 25.11
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: AMD Radeon RX 7900 XTX
Manufacturer: Micro-Star International Co., Ltd
Product Name: MS-7C02
System Version: 1.0

Fortunately I had committed my flake lock file to github so I was able to revert to a previously working version. Here’s what the panel reported

Operating System: NixOS 25.11
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.9 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: AMD Radeon RX 7900 XTX
Manufacturer: Micro-Star International Co., Ltd
Product Name: MS-7C02
System Version: 1.0

debugging with chatgpt why the sleep caused issues

While retreading the threads for other people reporting issues with sleep/suspend

Cannot resume from hibernate (NixOS 25.11, GNOME 48)

I came across this thread

Long Wake Time from Sleep

Which had a good command to check for what a proper suspend log looks like

journalctl -b -xu systemd-suspend
Nov 04 20:48:05 master-of-cooling systemd[1]: Starting System Suspend...
░░ Subject: A start job for unit systemd-suspend.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-suspend.service has begun execution.
░░ 
░░ The job identifier is 3753.
Nov 04 20:48:05 master-of-cooling systemd-sleep[10895]: Successfully froze unit 'user.slice'.
Nov 04 20:48:05 master-of-cooling systemd-sleep[10895]: Performing sleep operation 'suspend'...
░░ Subject: System sleep state suspend entered
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The system has now entered the suspend sleep state.
Nov 04 20:48:20 master-of-cooling systemd[1]: systemd-suspend.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit systemd-suspend.service has successfully entered the 'dead' state.
Nov 04 20:48:20 master-of-cooling systemd[1]: Finished System Suspend.
░░ Subject: A start job for unit systemd-suspend.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-suspend.service has finished successfully.
░░ 
░░ The job identifier is 3753.

In my case, when I had the latest update, I got a no entries output

journalctl -b -xu systemd-suspend
-- No entries --

To see if I could get some logs for why it bugged out, I purposefully updated my flake using nix flake update to pull the latest version. I rebuilt my system using sudo nixos-rebuild switch --flake .#master-of-cooling. To fully check it, I rebooted.

I had a previous chat with chatgpt, but I decided to retry with the journalctl -b -xu systemd-suspend to see if it could help me debug futher

@bedhedd

journalctl -b -xu systemd-suspend
– No entries –

so the suspend failed because it locked up, can we query the journal to see the last suspend attempt

@chatgpt

Yep. Since the box hard-reset during suspend, the evidence lives in the previous boot’s logs, mostly from the kernel and logind/systemd-sleep. Here are a few dead-simple ways to pull “the last suspend attempt” out of the journal.

1) Find the most recent suspend marker (across boots)

# Kernel’s own suspend markers (works on all distros)
journalctl -a -k --grep='PM: suspend entry' --reverse | head -n1

That prints the newest “PM: suspend entry (…)” line. Copy the timestamp it shows.

If you don’t see anything, widen the search:

journalctl -a --grep='(PM: suspend entry|Suspending system|Going to sleep|Reached target Sleep|systemd-sleep|s2idle|deep)' --reverse | head -n20

2) Show context around that time

Replace the times below with the timestamp you just found (a ~7-minute window usually captures freeze + reboot):

journalctl -a --since "2025-11-04 09:50:00" --until "2025-11-04 09:57:00" -o short-iso

3) Look at the previous boot explicitly (most useful after a crash)

# Kernel messages (previous boot)
journalctl -k -b -1 | less

# Only the suspend/resume/GPU bits from prev boot
journalctl -k -b -1 | grep -iE 'PM:|suspend|resume|amdgpu|pcie|acpi|lockup'

# systemd helpers from prev boot
journalctl -b -1 -u systemd-logind
journalctl -b -1 -t systemd-sleep    # filter by SYSLOG_IDENTIFIER

4) If systemd-suspend shows “No entries”

That unit often doesn’t exist; systemd-sleep is the helper and sleep.target / suspend.target are the targets. Check these instead:

systemctl status sleep.target suspend.target
journalctl -b -1 -u sleep.target -u suspend.target
journalctl -b -1 -t systemd-sleep

5) Pinpoint the failing stage (no real sleep; auto-resumes in ~5s)

This writes exact stage logs to the kernel ring buffer:

for s in freezer devices platform processors; do
  echo "$s" | sudo tee /sys/power/pm_test
  echo mem | sudo tee /sys/power/state
done
echo none | sudo tee /sys/power/pm_test

• If it fails at platform/processors, it’s almost certainly a platform/ACPI/PCIe/GPU interaction.

6) Make the next attempt extra verbose

Add temporarily (no rebuild):

# keep console awake during suspend; more logs survive
echo N | sudo tee /sys/module/printk/parameters/console_suspend

Or persist via NixOS for a clean repro:

boot.kernelParams = [
  "no_console_suspend" "ignore_loglevel" "log_buf_len=8M"
  "drm.debug=0x1e" "amdgpu.vm_update_mode=3"
];

---

If you paste the last 200 lines of:

• journalctl -k -b -1 and
• journalctl -b -1 -t systemd-sleep (if any)

I’ll read them and suggest the minimal kernel params/Nix patch to keep suspend stable on your rig.

I tried running the commands and passed it to chatgpt to interpret

@bedhedd

journalctl -a -k --grep=‘PM: suspend entry’ --reverse | head -n1
– No entries –

journalctl -a --grep=‘(PM: suspend entry|Suspending system|Going to sleep|Reached target Sleep|systemd-sleep|s2idle|deep)’ --reverse | head -n20
– Boot a7d419b6c3dd4952abdff6212e0fa92c –
Nov 04 20:09:17 master-of-cooling kernel: PM: suspend entry (deep)
Nov 04 20:09:17 master-of-cooling systemd[1]: Reached target Sleep.
– Boot d1e384da712745dbb3e6a593b99de6f0 –
– Boot db78bd58313949c3b487ebdae6bbd843 –
Nov 04 20:03:38 master-of-cooling kernel: PM: suspend entry (deep)
Nov 04 20:03:38 master-of-cooling systemd[1]: Reached target Sleep.
– Boot 094a7ae25da64ca9adc0b361c58665c3 –
Nov 04 20:01:18 master-of-cooling kernel: PM: suspend entry (deep)
Nov 04 20:01:18 master-of-cooling systemd[1]: Reached target Sleep.
– Boot 6880bad8b0894086b55e84a468c697ba –
Nov 04 19:57:57 master-of-cooling kernel: PM: suspend entry (deep)
Nov 04 19:57:57 master-of-cooling systemd[1]: Reached target Sleep.
Nov 04 19:35:23 master-of-cooling kernel: PM: suspend entry (deep)
Nov 04 19:35:23 master-of-cooling systemd[1]: Reached target Sleep.
– Boot 91ba20bc47e04c5488c386d47941fe1e –
Nov 04 19:18:28 master-of-cooling kernel: PM: suspend entry (deep)
Nov 04 19:18:28 master-of-cooling systemd[1]: Reached target Sleep.
– Boot 60358505560a4c5fb1c935304da43278 –
Nov 04 19:00:02 master-of-cooling kernel: PM: suspend entry (deep)

@chatgpt

Nice—those lines give us exact suspend timestamps per boot. Here’s how to pull the full context from the boot that tried to sleep and then crashed.

1) Identify the boot you care about

List boots with indexes (easiest to reference by -1, -2, etc.):

journalctl --list-boots

Pick the boot that shows your latest PM: suspend entry (deep) (e.g., the one at 20:09:17).

2) Grab the kernel + helpers around the suspend moment

Replace BOOTID and TS with your values (e.g., TS="2025-11-04 20:09:17"). Use either the boot ID or the boot offset (e.g., -1):

# Kernel messages around the suspend entry (±120s window)
BOOTID=a7d419b6c3dd4952abdff6212e0fa92c
TS="2025-11-04 20:09:17"
journalctl -b $BOOTID -k -o short-iso --since "$TS - 60s" --until "$TS + 120s"

# Same window, but include user-space/systemd messages too
journalctl -b $BOOTID -o short-iso --since "$TS - 60s" --until "$TS + 120s"

# Focus on GPU/ACPI/PCIe bits in that boot
journalctl -b $BOOTID -k | grep -iE 'amdgpu|drm|pcie|acpi|watchdog|lockup|rcu|iommu' | tail -n +1

3) See everything after the suspend trigger (often shows the fault)

journalctl -b $BOOTID -k -o short-iso | sed -n '/PM: suspend entry/,$p' | head -n 200

4) Systemd “sleep path” logs for that boot

journalctl -b $BOOTID -u sleep.target -u suspend.target
journalctl -b $BOOTID -t systemd-sleep
journalctl -b $BOOTID -u systemd-logind

5) Dump it all to files (so you can paste/share)

OUT="/tmp/suspend-$BOOTID"
journalctl -b $BOOTID -k > "${OUT}-kernel.log"
journalctl -b $BOOTID    > "${OUT}-all.log"
journalctl -b $BOOTID -t systemd-sleep > "${OUT}-systemd-sleep.log"
echo "wrote: ${OUT}-kernel.log  ${OUT}-all.log  ${OUT}-systemd-sleep.log"

6) If your journal isn’t persistent yet (so you don’t lose these next time)

# /etc/nixos/configuration.nix
services.journald.extraConfig = ''
  Storage=persistent
  SystemMaxUse=1G
'';

sudo nixos-rebuild switch and you’re set.

---

If you paste the last ~200 kernel lines starting at PM: suspend entry from that boot, I’ll read them and point to the exact failing stage (GPU/PCIe/ACPI) and the narrowest kernel param to stabilize it.

I ran the command journalctl --list-boots, found the latest boot and sent it to chatgpt

@bedhedd

-1 a7d419b6c3dd4952abdff6212e0fa92c Tue 2025-11-04 20:08:40 CST Tue 2025-11-04 20:09:17 CST
0 dfbbfab0405e41bb94c84cfa20f51477 Tue 2025-11-04 20:10:43 CST Tue 2025-11-04 20:14:48 CST

these are probably the entries

@chatgpt

Perfect. Let’s pull everything from that previous boot (-1) right around the suspend and see what the kernel said just before the reset.

Grab the key slices from boot -1

# 1) Show the last 200 kernel lines of boot -1
journalctl -k -b -1 -o short-iso | tail -n 200

# 2) Show everything from the suspend trigger to the end of boot -1
journalctl -k -b -1 -o short-iso | sed -n '/PM: suspend entry/,$p'

# 3) Narrow window around the suspend moment (±2 minutes)
journalctl -b -1 -o short-iso --since "20:07:17" --until "20:11:17"

# 4) Kernel-only in that window
journalctl -k -b -1 -o short-iso --since "20:07:17" --until "20:11:17"

# 5) GPU/ACPI/PCIe suspects from boot -1
journalctl -k -b -1 | grep -iE 'amdgpu|drm|pcie|acpi|iommu|watchdog|lockup|rcu' | tail -n +1

# 6) systemd sleep path for boot -1
journalctl -b -1 -u sleep.target -u suspend.target
journalctl -b -1 -t systemd-sleep
journalctl -b -1 -u systemd-logind

Tip: the timestamps in your --list-boots show boot -1 ran 20:08:40 → 20:09:17 CST and then the machine rebooted to boot 0. If the output in step 2 stops immediately after PM: suspend entry (deep) with nothing else, that’s a classic hard reset during suspend (no resume path executed).

Save to files (easy to share/paste)

OUT=/tmp/suspend-boot-1
journalctl -k -b -1 > "${OUT}-kernel.log"
journalctl    -b -1 > "${OUT}-all.log"
journalctl -b -1 -t systemd-sleep > "${OUT}-systemd-sleep.log"
echo "wrote: ${OUT}-kernel.log  ${OUT}-all.log  ${OUT}-systemd-sleep.log"

---

If those logs show only PM: suspend entry (deep) and then the next thing is the next boot, we won’t get more from that attempt. In that case, do one repro with extra verbosity enabled, then repeat the same commands:

# Runtime (no rebuild) – keep console awake during suspend
echo N | sudo tee /sys/module/printk/parameters/console_suspend

# If you’re willing to rebuild for a higher-signal repro:
# Add to boot.kernelParams and reboot once:
#   no_console_suspend ignore_loglevel log_buf_len=8M drm.debug=0x1e amdgpu.gfxoff=0 amdgpu.vm_update_mode=3

Paste the tail of *-kernel.log (last ~200 lines) here and I’ll call out the failing stage and the minimal kernel params to keep suspend stable on your box.

I decided to run journalctl -k -b -1 -o short-iso | sed -n '/PM: suspend entry/,$p' and
journalctl -k -b -1 -o short-iso | tail -n 200 to see what it could gleam from it

@bedhedd

journalctl -k -b -1 -o short-iso | sed -n ‘/PM: suspend entry/,$p’
2025-11-04T20:09:17-06:00 master-of-cooling kernel: PM: suspend entry (deep)
2025-11-04T20:09:17-06:00 master-of-cooling kernel: Filesystems sync: 0.003 seconds

journalctl -k -b -1 -o short-iso | tail -n 200
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Create List of Static Device Nodes…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Load Kernel Module configfs…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Load Kernel Module drm was skipped because of an unmet condition check (ConditionKernelModuleLoaded=!drm).
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Load Kernel Module efi_pstore…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Load Kernel Module fuse…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: File System Check on Root Device was skipped because of an unmet condition check (ConditionPathIsReadWrite=!/).
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Journal Service…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Load Kernel Modules…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Remount Root and Kernel File Systems…
2025-11-04T20:08:41-06:00 master-of-cooling kernel: pstore: Using crash dump compression: deflate
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Coldplug All udev Devices…
2025-11-04T20:08:41-06:00 master-of-cooling kernel: pstore: Registered efi_pstore as persistent store backend
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Mounted Huge Pages File System.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Mounted POSIX Message Queue File System.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Mounted Kernel Debug File System.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Mounted Kernel Trace File System.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Finished Create List of Static Device Nodes.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: [email protected]: Deactivated successfully.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Finished Load Kernel Module configfs.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Finished Load Kernel Module efi_pstore.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Mounting Kernel Configuration File System…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Create Static Device Nodes in /dev gracefully…
2025-11-04T20:08:41-06:00 master-of-cooling kernel: fuse: init (API version 7.44)
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: [email protected]: Deactivated successfully.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Finished Load Kernel Module fuse.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Mounting FUSE Control File System…
2025-11-04T20:08:41-06:00 master-of-cooling systemd-journald[734]: Collecting audit messages is enabled.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Mounted Kernel Configuration File System.
2025-11-04T20:08:41-06:00 master-of-cooling kernel: EXT4-fs (nvme0n1p2): re-mounted ef72fbe4-5bc6-465a-bf6e-31e079df6165.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Finished Remount Root and Kernel File Systems.
2025-11-04T20:08:41-06:00 master-of-cooling kernel: loop: module loaded
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Mounted FUSE Control File System.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Finished Load Kernel Modules.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Firewall…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore).
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Load/Save OS Random Seed…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Apply Kernel Variables…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Network Time Synchronization…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Finished Create Static Device Nodes in /dev gracefully.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Create Static Device Nodes in /dev…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Finished Load/Save OS Random Seed.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Finished Apply Kernel Variables.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Finished Create Static Device Nodes in /dev.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Reached target Preparation for Local File Systems.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Starting Rule-based Manager for Device Events and Files…
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Started Network Time Synchronization.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Started Rule-based Manager for Device Events and Files.
2025-11-04T20:08:41-06:00 master-of-cooling systemd[1]: Started Journal Service.
2025-11-04T20:08:41-06:00 master-of-cooling systemd-journald[734]: Received client request to flush runtime journal.
2025-11-04T20:08:41-06:00 master-of-cooling kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input34
2025-11-04T20:08:41-06:00 master-of-cooling kernel: ACPI: button: Power Button [PWRB]
2025-11-04T20:08:41-06:00 master-of-cooling kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input35
2025-11-04T20:08:41-06:00 master-of-cooling kernel: ACPI: button: Power Button [PWRF]
2025-11-04T20:08:41-06:00 master-of-cooling kernel: usbcore: registered new interface driver uas
2025-11-04T20:08:41-06:00 master-of-cooling kernel: rtc_cmos 00:02: RTC can wake from S4
2025-11-04T20:08:41-06:00 master-of-cooling kernel: mc: Linux media interface: v0.10
2025-11-04T20:08:42-06:00 master-of-cooling kernel: rtc_cmos 00:02: registered as rtc0
2025-11-04T20:08:42-06:00 master-of-cooling kernel: rtc_cmos 00:02: setting system clock to 2025-11-05T02:08:42 UTC (1762308522)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram
2025-11-04T20:08:42-06:00 master-of-cooling kernel: tpm_crb MSFT0101:00: Disabling hwrng
2025-11-04T20:08:42-06:00 master-of-cooling kernel: mousedev: PS/2 mouse device common for all mice
2025-11-04T20:08:42-06:00 master-of-cooling kernel: raid6: avx2x4 gen() 28593 MB/s
2025-11-04T20:08:42-06:00 master-of-cooling kernel: ccp 0000:2a:00.1: enabling device (0000 → 0002)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: raid6: avx2x2 gen() 28042 MB/s
2025-11-04T20:08:42-06:00 master-of-cooling kernel: ccp 0000:2a:00.1: ccp: unable to access the device: you might be running a broken BIOS.
2025-11-04T20:08:42-06:00 master-of-cooling kernel: ccp 0000:2a:00.1: psp enabled
2025-11-04T20:08:42-06:00 master-of-cooling kernel: usbcore: registered new device driver onboard-usb-dev
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Bluetooth: Core ver 2.22
2025-11-04T20:08:42-06:00 master-of-cooling kernel: NET: Registered PF_BLUETOOTH protocol family
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Bluetooth: HCI device and connection manager initialized
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Bluetooth: HCI socket layer initialized
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Bluetooth: L2CAP socket layer initialized
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Bluetooth: SCO socket layer initialized
2025-11-04T20:08:42-06:00 master-of-cooling kernel: raid6: avx2x1 gen() 16504 MB/s
2025-11-04T20:08:42-06:00 master-of-cooling kernel: raid6: using algorithm avx2x4 gen() 28593 MB/s
2025-11-04T20:08:42-06:00 master-of-cooling kernel: piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
2025-11-04T20:08:42-06:00 master-of-cooling kernel: piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection
2025-11-04T20:08:42-06:00 master-of-cooling kernel: i2c i2c-9: Successfully instantiated SPD at 0x52
2025-11-04T20:08:42-06:00 master-of-cooling kernel: i2c i2c-9: Successfully instantiated SPD at 0x53
2025-11-04T20:08:42-06:00 master-of-cooling kernel: piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
2025-11-04T20:08:42-06:00 master-of-cooling kernel: raid6: … xor() 8140 MB/s, rmw enabled
2025-11-04T20:08:42-06:00 master-of-cooling kernel: raid6: using avx2x2 recovery algorithm
2025-11-04T20:08:42-06:00 master-of-cooling kernel: xor: automatically using best checksumming function avx
2025-11-04T20:08:42-06:00 master-of-cooling kernel: RAPL PMU: API unit is 2^-32 Joules, 2 fixed counters, 163840 ms ovfl timer
2025-11-04T20:08:42-06:00 master-of-cooling kernel: RAPL PMU: hw unit of domain package 2^-16 Joules
2025-11-04T20:08:42-06:00 master-of-cooling kernel: RAPL PMU: hw unit of domain core 2^-16 Joules
2025-11-04T20:08:42-06:00 master-of-cooling kernel: sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
2025-11-04T20:08:42-06:00 master-of-cooling kernel: sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
2025-11-04T20:08:42-06:00 master-of-cooling kernel: sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Loaded X.509 cert ‘wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600’
2025-11-04T20:08:42-06:00 master-of-cooling kernel: amd_atl: AMD Address Translation Library initialized
2025-11-04T20:08:42-06:00 master-of-cooling kernel: usbcore: registered new interface driver btusb
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Adding 9227464k swap on /dev/nvme0n1p3. Priority:-2 extents:1 across:9227464k SS
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Bluetooth: hci0: Firmware revision 0.0 build 14 week 44 2021
2025-11-04T20:08:42-06:00 master-of-cooling kernel: EDAC MC: Ver: 3.0.0
2025-11-04T20:08:42-06:00 master-of-cooling kernel: r8169 0000:22:00.0: enabling device (0000 → 0003)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: r8169 0000:22:00.0 eth0: RTL8168h/8111h, 00:d8:61:6e:f2:56, XID 541, IRQ 80
2025-11-04T20:08:42-06:00 master-of-cooling kernel: r8169 0000:22:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Bluetooth: hci0: Reading supported features failed (-16)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Bluetooth: hci0: Error reading debug features
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_intel 0000:28:00.1: enabling device (0000 → 0002)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_intel 0000:28:00.1: Force to non-snoop mode
2025-11-04T20:08:42-06:00 master-of-cooling kernel: MCE: In-kernel MCE decoding enabled.
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_intel 0000:2a:00.4: enabling device (0000 → 0002)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: enabling device (0000 → 0002)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: ACPI: : failed to evaluate _DSM 2c176672-0b22-294b-814f-75e4dd26b5fd rev:0 func:0 (0x1001)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: ACPI: : failed to evaluate _DSM 2c176672-0b22-294b-814f-75e4dd26b5fd rev:0 func:0 (0x1001)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: Detected crf-id 0xbadcafe, cnv-id 0x3000000 wfpm id 0x80000000
2025-11-04T20:08:42-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: PCI dev 24f3/0010, rev=0x201, rfid=0xd55555d5
2025-11-04T20:08:42-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: Detected Intel(R) Dual Band Wireless-AC 8260
2025-11-04T20:08:42-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: loaded firmware version 36.c8e8e144.0 8000C-36.ucode op_mode iwlmvm
2025-11-04T20:08:42-06:00 master-of-cooling kernel: intel_rapl_common: Found RAPL domain package
2025-11-04T20:08:42-06:00 master-of-cooling kernel: intel_rapl_common: Found RAPL domain core
2025-11-04T20:08:42-06:00 master-of-cooling kernel: r8169 0000:22:00.0 enp34s0: renamed from eth0
2025-11-04T20:08:42-06:00 master-of-cooling kernel: pps_core: LinuxPPS API ver. 1 registered
2025-11-04T20:08:42-06:00 master-of-cooling kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [email protected]
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_intel 0000:28:00.1: bound 0000:28:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:26:00.0/0000:27:00.0/0000:28:00.1/sound/card0/input36
2025-11-04T20:08:42-06:00 master-of-cooling kernel: PTP clock support registered
2025-11-04T20:08:42-06:00 master-of-cooling kernel: ee1004 9-0052: 512 byte EE1004-compliant SPD EEPROM, read-only
2025-11-04T20:08:42-06:00 master-of-cooling kernel: ee1004 9-0053: 512 byte EE1004-compliant SPD EEPROM, read-only
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: autoconfig for ALC892: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: mono: mono_out=0x0
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: inputs:
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: Rear Mic=0x18
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: Front Mic=0x19
2025-11-04T20:08:42-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: Line=0x1a
2025-11-04T20:08:42-06:00 master-of-cooling kernel: Btrfs loaded, zoned=yes, fsverity=no
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input40
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:26:00.0/0000:27:00.0/0000:28:00.1/sound/card0/input37
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input41
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input42
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:26:00.0/0000:27:00.0/0000:28:00.1/sound/card0/input38
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:26:00.0/0000:27:00.0/0000:28:00.1/sound/card0/input39
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HD-Audio Generic Line Out Front as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input43
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HD-Audio Generic Line Out Surround as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input44
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HD-Audio Generic Line Out CLFE as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input45
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HD-Audio Generic Line Out Side as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input46
2025-11-04T20:08:42-06:00 master-of-cooling kernel: input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input47
2025-11-04T20:08:42-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: base HW address: 7c:76:35:e2:4c:80, OTP minor version: 0x4
2025-11-04T20:08:42-06:00 master-of-cooling kernel: ieee80211 phy0: Selected rate control algorithm ‘iwl-mvm-rs’
2025-11-04T20:08:42-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0 wlo1: renamed from wlan0
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 3-2.4: Quirk or no altset; falling back to MIDI 1.0
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.2: New USB device found, idVendor=0bda, idProduct=4c15, bcdDevice= 0.15
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.2: Product: USB Audio
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.2: Manufacturer: Generic
2025-11-04T20:08:43-06:00 master-of-cooling kernel: BTRFS: device label MassStorage devid 1 transid 20079 /dev/sda1 (8:1) scanned by mount (1026)
2025-11-04T20:08:43-06:00 master-of-cooling kernel: BTRFS info (device sda1): first mount of filesystem 027f2550-4813-20d9-ac54-fc87dc4612eb
2025-11-04T20:08:43-06:00 master-of-cooling kernel: BTRFS info (device sda1): using crc32c (crc32c-lib) checksum algorithm
2025-11-04T20:08:43-06:00 master-of-cooling kernel: BTRFS warning (device sda1): devid 1 physical 0 len 134217728 inside the reserved space
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.2: Warning! Unlikely big volume range (=799), cval->res is probably wrong.
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.2: [22] FU [PCM Playback Volume] ch = 2, val = -25600/-1/32
2025-11-04T20:08:43-06:00 master-of-cooling kernel: input: Generic USB Audio Consumer Control as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-8/1-8.2/1-8.2.2/1-8.2.2:1.3/0003:0BDA:4C15.0012/input/input48
2025-11-04T20:08:43-06:00 master-of-cooling kernel: BTRFS info (device sda1): enabling ssd optimizations
2025-11-04T20:08:43-06:00 master-of-cooling kernel: BTRFS info (device sda1): turning on async discard
2025-11-04T20:08:43-06:00 master-of-cooling kernel: BTRFS info (device sda1): enabling free space tree
2025-11-04T20:08:43-06:00 master-of-cooling kernel: BTRFS info (device sda1): use zstd compression, level 3
2025-11-04T20:08:43-06:00 master-of-cooling kernel: input: Generic USB Audio as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-8/1-8.2/1-8.2.2/1-8.2.2:1.3/0003:0BDA:4C15.0012/input/input49
2025-11-04T20:08:43-06:00 master-of-cooling kernel: hid-generic 0003:0BDA:4C15.0012: input,hiddev100,hidraw7: USB HID v1.11 Device [Generic USB Audio] on usb-0000:03:00.0-8.2.2/input3
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usbcore: registered new interface driver snd-usb-audio
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.3: new full-speed USB device number 10 using xhci_hcd
2025-11-04T20:08:43-06:00 master-of-cooling kernel: Generic FE-GE Realtek PHY r8169-0-2200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-2200:00, irq=MAC)
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.3: New USB device found, idVendor=03f0, idProduct=0580, bcdDevice= 2.00
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.3: Product: QHMD A85V
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.3: Manufacturer: Quanta Inc.
2025-11-04T20:08:43-06:00 master-of-cooling kernel: usb 1-8.2.3: SerialNumber: 8CC220Z054
2025-11-04T20:08:43-06:00 master-of-cooling kernel: hid-generic 0003:03F0:0580.0013: hiddev103,hidraw14: USB HID v1.11 Device [Quanta Inc. QHMD A85V] on usb-0000:03:00.0-8.2.3/input0
2025-11-04T20:08:43-06:00 master-of-cooling kernel: r8169 0000:22:00.0 enp34s0: Link is Down
2025-11-04T20:08:44-06:00 master-of-cooling kernel: ACPI: : failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:0 (0x1001)
2025-11-04T20:08:44-06:00 master-of-cooling kernel: NET: Registered PF_PACKET protocol family
2025-11-04T20:08:47-06:00 master-of-cooling kernel: r8169 0000:22:00.0 enp34s0: Link is Up - 1Gbps/Full - flow control off
2025-11-04T20:08:51-06:00 master-of-cooling kernel: [drm:amdgpu_job_submit [amdgpu]] ERROR Trying to push to a killed entity
2025-11-04T20:08:51-06:00 master-of-cooling kernel: logitech-hidpp-device 0003:046D:407B.0010: HID++ 4.5 device connected.
2025-11-04T20:08:51-06:00 master-of-cooling kernel: nvme nvme0: using unchecked data buffer
2025-11-04T20:08:51-06:00 master-of-cooling kernel: block nvme0n1: No UUID available providing old NGUID
2025-11-04T20:08:53-06:00 master-of-cooling kernel: warning: `.kdeconnectd-wr’ uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
2025-11-04T20:08:54-06:00 master-of-cooling kernel: NET: Registered PF_QIPCRTR protocol family
2025-11-04T20:08:55-06:00 master-of-cooling kernel: wlo1: authenticate with 44:1e:98:58:44:1c (local address=5a:da:78:8e:29:23)
2025-11-04T20:08:55-06:00 master-of-cooling kernel: wlo1: send auth to 44:1e:98:58:44:1c (try 1/3)
2025-11-04T20:08:55-06:00 master-of-cooling kernel: wlo1: authenticated
2025-11-04T20:08:55-06:00 master-of-cooling kernel: wlo1: associate with 44:1e:98:58:44:1c (try 1/3)
2025-11-04T20:08:55-06:00 master-of-cooling kernel: wlo1: RX AssocResp from 44:1e:98:58:44:1c (capab=0x11 status=0 aid=7)
2025-11-04T20:08:55-06:00 master-of-cooling kernel: wlo1: associated
2025-11-04T20:08:55-06:00 master-of-cooling kernel: wlo1: Limiting TX power to 36 (36 - 0) dBm as advertised by 44:1e:98:58:44:1c
2025-11-04T20:08:58-06:00 master-of-cooling kernel: amdgpu: Freeing queue vital buffer 0x7f2a45200000, queue evicted
2025-11-04T20:08:58-06:00 master-of-cooling kernel: [drm:amdgpu_job_submit [amdgpu]] ERROR Trying to push to a killed entity
2025-11-04T20:09:16-06:00 master-of-cooling kernel: r8169 0000:22:00.0 enp34s0: Link is Down
2025-11-04T20:09:16-06:00 master-of-cooling kernel: wlo1: deauthenticating from 44:1e:98:58:44:1c by local choice (Reason: 3=DEAUTH_LEAVING)
2025-11-04T20:09:17-06:00 master-of-cooling kernel: PM: suspend entry (deep)
2025-11-04T20:09:17-06:00 master-of-cooling kernel: Filesystems sync: 0.003 seconds

chatgpt then suggested I check the pstore

@chatgpt

Great, this tells us a lot:

• Boot -1 shows:
  20:09:17 PM: suspend entry (deep) → Filesystems sync → nothing else → next boot.
  That’s a hard crash during suspend (no resume path ran).

Also earlier in that boot you had AMDGPU errors (“Trying to push to a killed entity”), i.e. the GPU was already unhappy before suspend.

Here’s how to pull the last breadcrumbs and then make the next repro produce useful evidence.

Pull any crash crumbs from the failed suspend

1. Check firmware crash storage (pstore). Your log shows efi_pstore registered, so if firmware captured anything it’ll be here:

# See if crash logs exist for that failure
sudo ls -l /sys/fs/pstore
# If files exist, copy them out and view
sudo cp -av /sys/fs/pstore /var/tmp/pstore-$(date +%F-%T)
sudo sed -n '1,200p' /var/tmp/pstore-*/dmesg-ramoops* /var/tmp/pstore-*/*efi-*

2. See if systemd already archived pstore at the next boot:

systemctl status systemd-pstore
journalctl -b 0 -t systemd-pstore

Make the next attempt high-signal

Do these, then try one suspend, then collect -b -1 again.

A) Turn on verbose kernel logging for suspend

# runtime (no rebuild)
echo N | sudo tee /sys/module/printk/parameters/console_suspend
sudo dmesg -n 8                     # maximum log level
sudo sysctl kernel.printk='8 8 1 7' # be chatty

B) Enable the kernel’s PM tracing/timeline (auto-resumes in ~5s per stage; doesn’t actually sleep the platform):

for s in freezer devices platform processors; do
  echo "$s" | sudo tee /sys/power/pm_test
  echo mem | sudo tee /sys/power/state
done
echo none | sudo tee /sys/power/pm_test

If it fails at platform/processors, that points squarely at ACPI/PCIe/GPU.

C) One real suspend with DRM/AMDGPU debug (persistent)
Add these, rebuild, reboot, then suspend once:

# /etc/nixos/configuration.nix
boot.kernelParams = [
  "no_console_suspend"
  "ignore_loglevel"
  "log_buf_len=8M"
  "drm.debug=0x1e"
  "amdgpu.gfxoff=0"
  "amdgpu.vm_update_mode=3"
];
# keep firmware current; consider LTS kernel for stability
hardware.enableRedistributableFirmware = true;
# Try the LTS track while debugging:
boot.kernelPackages = pkgs.linuxPackages_lts;

Then reproduce a single systemctl suspend, and after the reboot grab:

journalctl -k -b -1 | tail -n 400 > /tmp/suspend-prev-kernel.log
journalctl    -b -1                > /tmp/suspend-prev-all.log

While we stabilize it (workarounds that often stop the crash)

Try these (smallest change first). Apply one at a time, rebuild, test systemctl suspend.

1) Tame GPU/PCIe power transitions

boot.kernelParams = [
  "amdgpu.runpm=0"   # disable BACO runtime power-gating
  "amdgpu.gfxoff=0"  # avoid deep GFX idle state
  "pcie_aspm=off"    # avoid aggressive PCIe link power saving
  "iommu=pt"         # simpler DMA mappings on resume
];

2) If you don’t need S3 right now, use s2idle as a stopgap

boot.kernelParams = [ "mem_sleep_default=s2idle" ];

(Combine with the GPU/PCIe params above if s2idle alone still crashes.)

3) Kernel track
You’re on 6.17.x. Test LTS 6.6 or the distro latest—suspend regressions swing both ways:

# one of:
boot.kernelPackages = pkgs.linuxPackages_lts;
# or
# boot.kernelPackages = pkgs.linuxPackages_latest;

Quality-of-life: don’t auto-suspend while testing

services.logind.extraConfig = ''
  IdleAction=ignore
  HandleSuspendKey=ignore
'';

---

If /sys/fs/pstore contains files from the crash, paste the first 100–200 lines of any dmesg-ramoops-* (or the tail of /tmp/suspend-prev-kernel.log). From there I can tell you whether it’s tripping in the AMDGPU DC path vs. ACPI platform handoff and give you a minimal final Nix patch.

I ran sudo ls -l /sys/fs/pstore like it suggested

@bedhedd

sudo ls -l /sys/fs/pstore total 0

it suggested I run the following

echo N | sudo tee /sys/module/printk/parameters/console_suspend

sudo dmesg -n 8
sudo sysctl kernel.printk='8 8 1 7'

@chatgpt

Got it — pstore is empty, so firmware didn’t save a crash dump. That means the only bread-crumbs are what we already saw: the kernel hit PM: suspend entry (deep) and then the box hard-reset. Let’s (A) capture much richer logs next attempt, and (B) apply a stabilizing kernel/Nix patch you can try immediately.

A) Capture more signal next time (copy–paste)

1. Make the kernel chatty during suspend (no rebuild):

echo N | sudo tee /sys/module/printk/parameters/console_suspend
sudo dmesg -n 8
sudo sysctl kernel.printk='8 8 1 7'

2. Pinpoint the failing stage without really sleeping (auto-resumes in ~5s per stage):

for s in freezer devices platform processors; do
  echo "$s" | sudo tee /sys/power/pm_test
  echo mem | sudo tee /sys/power/state
done
echo none | sudo tee /sys/power/pm_test

• If it fails at platform or processors, that’s a platform/ACPI/PCIe/AMDGPU handoff issue (likely on your rig).

3. Do one real suspend with DRM/AMDGPU debug persisted, then pull previous-boot logs:

• Add this, rebuild, reboot:

# /etc/nixos/configuration.nix
boot.kernelParams = [
  "no_console_suspend"
  "ignore_loglevel"
  "log_buf_len=8M"
  "drm.debug=0x1e"
  "amdgpu.gfxoff=0"
  "amdgpu.vm_update_mode=3"
];
services.journald.extraConfig = ''
  Storage=persistent
  SystemMaxUse=1G
'';

• After one systemctl suspend (it will likely crash), on the next boot:

journalctl -k -b -1 | tail -n 400 > /tmp/suspend-prev-kernel.log
journalctl    -b -1                > /tmp/suspend-prev-all.log

(If you want maximum detail later, we can set up ftrace or netconsole, but the above usually suffices.)

B) Try a stabilizing patch right now (common RDNA3 fixes)

Apply this minimal set and test systemctl suspend again:

# /etc/nixos/configuration.nix
{ config, pkgs, ... }:
{
  boot.kernelPackages = pkgs.linuxPackages_lts;   # try 6.6 LTS first for suspend stability

  hardware.enableRedistributableFirmware = true;

  boot.kernelParams = [
    # Power/suspend stability
    "mem_sleep_default=s2idle"   # safer on many desktops; switch to deep later if you want
    "amdgpu.runpm=0"             # disable BACO runtime power gating
    "amdgpu.gfxoff=0"            # avoid deep GFX idle state
    "pcie_aspm=off"              # avoid aggressive PCIe link power states
    "iommu=pt"                   # simpler DMA mappings on resume

    # Keep logs during suspend (also used above)
    "no_console_suspend" "ignore_loglevel" "log_buf_len=8M"
  ];

  # Don’t let the system auto-suspend while testing
  services.logind.extraConfig = ''
    IdleAction=ignore
    HandleSuspendKey=ignore
  '';
}

Then:

sudo nixos-rebuild switch && systemctl reboot
# after reboot:
systemctl suspend

C) (Nice to have) Save a pre-suspend snapshot automatically

This drops a quick “what’s happening” file just before suspend:

environment.etc."systemd/system-sleep/10-prelog".text = ''
  #!/bin/sh
  case "$1" in
    pre)
      TS=$(date +%F-%T)
      mkdir -p /var/log/sleep
      dmesg | tail -n 400 > /var/log/sleep/dmesg-pre-$TS.log
      journalctl -k -n 200 > /var/log/sleep/journal-kernel-pre-$TS.log
    ;;
  esac
'';

---

If the LTS + amdgpu.runpm=0 + amdgpu.gfxoff=0 combo lets it suspend/resume cleanly, we can trim to the smallest necessary set. If it still crashes, run the pm_test loop and paste its output (or the tail of /tmp/suspend-prev-kernel.log) and I’ll zero in on the exact failing handoff.

I then posted the outputs and asked for a fish equivalent command

@bedhedd

echo N | sudo tee /sys/module/printk/parameters/console_suspend
N
sudo dmesg -n 8
sudo sysctl kernel.printk=‘8 8 1 7’
kernel.printk = 8 8 1 7

for step 2 is that fish/

I ran the fish suggestion

for s in freezer devices platform processors
    echo $s | sudo tee /sys/power/pm_test
    echo mem | sudo tee /sys/power/state
end
echo none | sudo tee /sys/power/pm_test

@chatgpt

Good catch — that little for …; do …; done loop is written in Bash syntax, not Fish.

Fish will choke on it unless you either:

1. Temporarily run it in Bash, or
2. Rewrite it using Fish’s for style.

---

Easiest: run it in Bash directly

bash -c 'for s in freezer devices platform processors; do
  echo "$s" | sudo tee /sys/power/pm_test
  echo mem | sudo tee /sys/power/state
done
echo none | sudo tee /sys/power/pm_test'

---

Native Fish version

If you prefer staying inside Fish, use its own syntax:

for s in freezer devices platform processors
    echo $s | sudo tee /sys/power/pm_test
    echo mem | sudo tee /sys/power/state
end
echo none | sudo tee /sys/power/pm_test

Either version will run a suspend-self-test for each stage (freezer, devices, platform, processors) and automatically wake the system after ~5 seconds each time.
The stage where it freezes or reboots pinpoints which suspend phase is failing (likely platform on your system).

When I ran the fish version this was the log.

I passed it to chatgpt, and it interpreted it as the first stage working

@chatgpt

Perfect — that screenshot shows the kernel PM test passed through freezer and devices successfully, and then automatically resumed after the 5-second simulated sleep.

That means the early suspend stages (freezing userspace & devices) are working fine.
The next step is to test the deeper phases where the hardware/firmware actually gets power-gated.

---

Continue the test sequence

You’re now ready for the later stages:

# In Fish (or Bash, same idea)
for s in platform processors
    echo $s | sudo tee /sys/power/pm_test
    echo mem | sudo tee /sys/power/state
end
echo none | sudo tee /sys/power/pm_test

Each phase will again sleep for ~5 seconds, auto-wake, and print messages like
PM: suspend debug: Waiting for 5 second(s) then Restarting tasks: Done.

---

How to interpret the results

Stage	What it tests	Meaning if it hangs/crashes
freezer	Freeze userspace tasks	Not your issue — this one already passed
devices	Suspend all drivers	Passed too
platform	ACPI/platform firmware handoff	If it hangs/reboots here → firmware or ACPI/PCIe/GPU suspend routine bug
processors	CPU low-power transition	Rarely fails alone; often coupled with GPU/platform
(none)	Normal operation again	Return to default

If the crash appears only when testing platform, it confirms a platform/firmware/GPU suspend problem — exactly what the earlier amdgpu “killed entity” hints suggest.

---

Next step once you know which one fails

If platform fails → it’s safe to conclude the hardware power-gating handoff is broken on your BIOS or GPU driver.
Then we’d:

• Keep mem_sleep_default=s2idle (to stay in a safer suspend mode).
• Keep amdgpu.runpm=0 amdgpu.gfxoff=0 pcie_aspm=off in your boot.kernelParams.
• Optionally test a different kernel (linuxPackages_lts or latest).

Run those after confirming which pm_test stage trips.
Let me know whether platform or processors crashes — that decides whether we focus on ACPI or CPU/GPU power management next.

I rebooted and let it know it had a blinking cursor.

Chatgpt suggested running the following

# Test "platform" only (ACPI/PCIe/GPU handoff)
echo platform | sudo tee /sys/power/pm_test
echo mem      | sudo tee /sys/power/state

@chatgpt

Got it — a frozen screen with a lone blinking cursor during the PM test means the kernel got stuck transitioning into a deeper suspend phase. Let’s pin down which phase and then apply the fix.

1) Confirm the failing phase (run one stage at a time)

From a VT (Ctrl+Alt+F3), do one command at a time and wait ~10 seconds for each:

# Test "platform" only (ACPI/PCIe/GPU handoff)
echo platform | sudo tee /sys/power/pm_test
echo mem      | sudo tee /sys/power/state

• If you don’t see:

  • PM: suspend debug: Waiting for 5 second(s).
  • Restarting tasks: Starting/Done
    within ~7s and instead get that blinking cursor → platform is the culprit.

If platform passes, test processors:

echo processors | sudo tee /sys/power/pm_test
echo mem        | sudo tee /sys/power/state

Then reset testing:

echo none | sudo tee /sys/power/pm_test

2) Stabilize suspend (most likely fixes for a platform/GPU handoff stall)

Add these to your NixOS config, rebuild, reboot, then try a normal systemctl suspend:

# /etc/nixos/configuration.nix
{ config, pkgs, ... }:
{
  # Kernel: try LTS first for suspend stability
  boot.kernelPackages = pkgs.linuxPackages_lts;

  hardware.enableRedistributableFirmware = true;

  # Power/suspend workarounds (RDNA3/ACPI handoff)
  boot.kernelParams = [
    "mem_sleep_default=s2idle"   # avoid S3 while we stabilize
    "amdgpu.runpm=0"             # disable BACO runtime power gating
    "amdgpu.gfxoff=0"            # avoid deep GFX idle state
    "pcie_aspm=off"              # keep PCIe links from entering low-power
    "iommu=pt"                   # simpler DMA mappings on resume

    # Keep logs during suspend, bigger buffer
    "no_console_suspend" "ignore_loglevel" "log_buf_len=8M"
  ];

  # Don’t auto-suspend while testing
  services.logind.extraConfig = ''
    IdleAction=ignore
    HandleSuspendKey=ignore
  '';
}

sudo nixos-rebuild switch && systemctl reboot
# then test:
systemctl suspend

3) BIOS knobs that often help (quick check)

In firmware setup:

• PCIe ASPM: Disabled (or “Auto” → try Disabled).
• Global C-State Control: Enabled but set Power Supply Idle Control = Typical Current Idle (prevents hangs).
• Re-Size BAR: leave Enabled (usually fine).
• Update to the latest motherboard BIOS if you haven’t.

4) If it still stalls

Turn on maximum logging for a single high-signal repro (you already set no_console_suspend, etc.). After the crash/reboot:

journalctl -k -b -1 | tail -n 400 > /tmp/suspend-prev-kernel.log

Paste the tail of that file here. If the PM test confirmed platform is the failing stage, we can keep s2idle and try relaxing the set (e.g., remove iommu=pt), or, if you want to use deep later, we can iterate with amdgpu.runpm=0 + pcie_aspm=off on deep.

running sudo tee /sys/power/state caused the system to hang. I decided to hard reboot and get it the output of journalctl -k -b -1 -o short-iso | tail -n 200

I passed this in

@bedhedd

journalctl -k -b -1 -o short-iso | tail -n 200
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Create List of Static Device Nodes…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Load Kernel Module configfs…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Load Kernel Module drm was skipped because of an unmet condition check (ConditionKernelModuleLoaded=!drm).
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Load Kernel Module efi_pstore…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Load Kernel Module fuse…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: File System Check on Root Device was skipped because of an unmet condition check (ConditionPathIsReadWrite=!/).
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Journal Service…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Load Kernel Modules…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Remount Root and Kernel File Systems…
2025-11-04T20:31:58-06:00 master-of-cooling kernel: pstore: Using crash dump compression: deflate
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Coldplug All udev Devices…
2025-11-04T20:31:58-06:00 master-of-cooling kernel: pstore: Registered efi_pstore as persistent store backend
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Mounted Huge Pages File System.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Mounted POSIX Message Queue File System.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Mounted Kernel Debug File System.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Mounted Kernel Trace File System.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Finished Create List of Static Device Nodes.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: [email protected]: Deactivated successfully.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Finished Load Kernel Module configfs.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Finished Load Kernel Module efi_pstore.
2025-11-04T20:31:58-06:00 master-of-cooling kernel: fuse: init (API version 7.44)
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Mounting Kernel Configuration File System…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Create Static Device Nodes in /dev gracefully…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: [email protected]: Deactivated successfully.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Finished Load Kernel Module fuse.
2025-11-04T20:31:58-06:00 master-of-cooling systemd-journald[760]: Collecting audit messages is enabled.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Mounting FUSE Control File System…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Mounted Kernel Configuration File System.
2025-11-04T20:31:58-06:00 master-of-cooling kernel: loop: module loaded
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Finished Load Kernel Modules.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Firewall…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Apply Kernel Variables…
2025-11-04T20:31:58-06:00 master-of-cooling kernel: EXT4-fs (nvme0n1p2): re-mounted ef72fbe4-5bc6-465a-bf6e-31e079df6165.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Mounted FUSE Control File System.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Finished Remount Root and Kernel File Systems.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore).
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Load/Save OS Random Seed…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Network Time Synchronization…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Finished Create Static Device Nodes in /dev gracefully.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Create Static Device Nodes in /dev…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Finished Apply Kernel Variables.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Finished Load/Save OS Random Seed.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Finished Create Static Device Nodes in /dev.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Reached target Preparation for Local File Systems.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Starting Rule-based Manager for Device Events and Files…
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Started Network Time Synchronization.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Started Rule-based Manager for Device Events and Files.
2025-11-04T20:31:58-06:00 master-of-cooling systemd[1]: Started Journal Service.
2025-11-04T20:31:58-06:00 master-of-cooling systemd-journald[760]: Received client request to flush runtime journal.
2025-11-04T20:31:58-06:00 master-of-cooling systemd-journald[760]: File /var/log/journal/95529aa7b5bc4b6ead824aadefc30924/system.journal corrupted or uncleanly shut down, renaming and replacing.
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input34
2025-11-04T20:31:58-06:00 master-of-cooling kernel: ACPI: button: Power Button [PWRB]
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input35
2025-11-04T20:31:58-06:00 master-of-cooling kernel: ACPI: button: Power Button [PWRF]
2025-11-04T20:31:58-06:00 master-of-cooling kernel: usbcore: registered new interface driver uas
2025-11-04T20:31:58-06:00 master-of-cooling kernel: rtc_cmos 00:02: RTC can wake from S4
2025-11-04T20:31:58-06:00 master-of-cooling kernel: rtc_cmos 00:02: registered as rtc0
2025-11-04T20:31:58-06:00 master-of-cooling kernel: rtc_cmos 00:02: setting system clock to 2025-11-05T02:31:58 UTC (1762309918)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram
2025-11-04T20:31:58-06:00 master-of-cooling kernel: tpm_crb MSFT0101:00: Disabling hwrng
2025-11-04T20:31:58-06:00 master-of-cooling kernel: mc: Linux media interface: v0.10
2025-11-04T20:31:58-06:00 master-of-cooling kernel: ccp 0000:2a:00.1: enabling device (0000 → 0002)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: ccp 0000:2a:00.1: ccp: unable to access the device: you might be running a broken BIOS.
2025-11-04T20:31:58-06:00 master-of-cooling kernel: ccp 0000:2a:00.1: psp enabled
2025-11-04T20:31:58-06:00 master-of-cooling kernel: raid6: avx2x4 gen() 28176 MB/s
2025-11-04T20:31:58-06:00 master-of-cooling kernel: usbcore: registered new device driver onboard-usb-dev
2025-11-04T20:31:58-06:00 master-of-cooling kernel: piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
2025-11-04T20:31:58-06:00 master-of-cooling kernel: piix4_smbus 0000:00:14.0: Using register 0x02 for SMBus port selection
2025-11-04T20:31:58-06:00 master-of-cooling kernel: i2c i2c-9: Successfully instantiated SPD at 0x52
2025-11-04T20:31:58-06:00 master-of-cooling kernel: i2c i2c-9: Successfully instantiated SPD at 0x53
2025-11-04T20:31:58-06:00 master-of-cooling kernel: piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
2025-11-04T20:31:58-06:00 master-of-cooling kernel: raid6: avx2x2 gen() 31205 MB/s
2025-11-04T20:31:58-06:00 master-of-cooling kernel: sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
2025-11-04T20:31:58-06:00 master-of-cooling kernel: RAPL PMU: API unit is 2^-32 Joules, 2 fixed counters, 163840 ms ovfl timer
2025-11-04T20:31:58-06:00 master-of-cooling kernel: RAPL PMU: hw unit of domain package 2^-16 Joules
2025-11-04T20:31:58-06:00 master-of-cooling kernel: RAPL PMU: hw unit of domain core 2^-16 Joules
2025-11-04T20:31:58-06:00 master-of-cooling kernel: sp5100-tco sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
2025-11-04T20:31:58-06:00 master-of-cooling kernel: sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: raid6: avx2x1 gen() 21039 MB/s
2025-11-04T20:31:58-06:00 master-of-cooling kernel: raid6: using algorithm avx2x2 gen() 31205 MB/s
2025-11-04T20:31:58-06:00 master-of-cooling kernel: r8169 0000:22:00.0: enabling device (0000 → 0003)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: r8169 0000:22:00.0 eth0: RTL8168h/8111h, 00:d8:61:6e:f2:56, XID 541, IRQ 80
2025-11-04T20:31:58-06:00 master-of-cooling kernel: r8169 0000:22:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
2025-11-04T20:31:58-06:00 master-of-cooling kernel: amd_atl: AMD Address Translation Library initialized
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_intel 0000:28:00.1: enabling device (0000 → 0002)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_intel 0000:28:00.1: Force to non-snoop mode
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_intel 0000:2a:00.4: enabling device (0000 → 0002)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: raid6: … xor() 32876 MB/s, rmw enabled
2025-11-04T20:31:58-06:00 master-of-cooling kernel: raid6: using avx2x2 recovery algorithm
2025-11-04T20:31:58-06:00 master-of-cooling kernel: xor: automatically using best checksumming function avx
2025-11-04T20:31:58-06:00 master-of-cooling kernel: EDAC MC: Ver: 3.0.0
2025-11-04T20:31:58-06:00 master-of-cooling kernel: MCE: In-kernel MCE decoding enabled.
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_intel 0000:28:00.1: bound 0000:28:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:26:00.0/0000:27:00.0/0000:28:00.1/sound/card1/input36
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: autoconfig for ALC892: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: mono: mono_out=0x0
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: inputs:
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: Rear Mic=0x18
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: Front Mic=0x19
2025-11-04T20:31:58-06:00 master-of-cooling kernel: snd_hda_codec_alc662 hdaudioC2D0: Line=0x1a
2025-11-04T20:31:58-06:00 master-of-cooling kernel: ee1004 9-0052: 512 byte EE1004-compliant SPD EEPROM, read-only
2025-11-04T20:31:58-06:00 master-of-cooling kernel: ee1004 9-0053: 512 byte EE1004-compliant SPD EEPROM, read-only
2025-11-04T20:31:58-06:00 master-of-cooling kernel: r8169 0000:22:00.0 enp34s0: renamed from eth0
2025-11-04T20:31:58-06:00 master-of-cooling kernel: intel_rapl_common: Found RAPL domain package
2025-11-04T20:31:58-06:00 master-of-cooling kernel: intel_rapl_common: Found RAPL domain core
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Adding 9227464k swap on /dev/nvme0n1p3. Priority:-2 extents:1 across:9227464k SS
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input40
2025-11-04T20:31:58-06:00 master-of-cooling kernel: usb 1-8.2.2: New USB device found, idVendor=0bda, idProduct=4c15, bcdDevice= 0.15
2025-11-04T20:31:58-06:00 master-of-cooling kernel: usb 1-8.2.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0
2025-11-04T20:31:58-06:00 master-of-cooling kernel: usb 1-8.2.2: Product: USB Audio
2025-11-04T20:31:58-06:00 master-of-cooling kernel: usb 1-8.2.2: Manufacturer: Generic
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Btrfs loaded, zoned=yes, fsverity=no
2025-11-04T20:31:58-06:00 master-of-cooling kernel: mousedev: PS/2 mouse device common for all mice
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:26:00.0/0000:27:00.0/0000:28:00.1/sound/card1/input37
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input41
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:26:00.0/0000:27:00.0/0000:28:00.1/sound/card1/input38
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input42
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:26:00.0/0000:27:00.0/0000:28:00.1/sound/card1/input39
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HD-Audio Generic Line Out Front as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input43
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HD-Audio Generic Line Out Surround as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input44
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HD-Audio Generic Line Out CLFE as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input45
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HD-Audio Generic Line Out Side as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input46
2025-11-04T20:31:58-06:00 master-of-cooling kernel: input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:08.1/0000:2a:00.4/sound/card2/input47
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Bluetooth: Core ver 2.22
2025-11-04T20:31:58-06:00 master-of-cooling kernel: NET: Registered PF_BLUETOOTH protocol family
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Bluetooth: HCI device and connection manager initialized
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Bluetooth: HCI socket layer initialized
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Bluetooth: L2CAP socket layer initialized
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Bluetooth: SCO socket layer initialized
2025-11-04T20:31:58-06:00 master-of-cooling kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Loaded X.509 cert ‘wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600’
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Bluetooth: hci0: Firmware revision 0.0 build 14 week 44 2021
2025-11-04T20:31:58-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: enabling device (0000 → 0002)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: ACPI: : failed to evaluate _DSM 2c176672-0b22-294b-814f-75e4dd26b5fd rev:0 func:0 (0x1001)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: ACPI: : failed to evaluate _DSM 2c176672-0b22-294b-814f-75e4dd26b5fd rev:0 func:0 (0x1001)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: Detected crf-id 0xbadcafe, cnv-id 0x3000000 wfpm id 0x80000000
2025-11-04T20:31:58-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: PCI dev 24f3/0010, rev=0x201, rfid=0xd55555d5
2025-11-04T20:31:58-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: Detected Intel(R) Dual Band Wireless-AC 8260
2025-11-04T20:31:58-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: loaded firmware version 36.c8e8e144.0 8000C-36.ucode op_mode iwlmvm
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Bluetooth: hci0: Reading supported features failed (-16)
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Bluetooth: hci0: Error reading debug features
2025-11-04T20:31:58-06:00 master-of-cooling kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
2025-11-04T20:31:58-06:00 master-of-cooling kernel: usbcore: registered new interface driver btusb
2025-11-04T20:31:58-06:00 master-of-cooling kernel: pps_core: LinuxPPS API ver. 1 registered
2025-11-04T20:31:58-06:00 master-of-cooling kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [email protected]
2025-11-04T20:31:58-06:00 master-of-cooling kernel: PTP clock support registered
2025-11-04T20:31:59-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0: base HW address: 7c:76:35:e2:4c:80, OTP minor version: 0x4
2025-11-04T20:31:59-06:00 master-of-cooling kernel: usb 1-8.2.2: Warning! Unlikely big volume range (=799), cval->res is probably wrong.
2025-11-04T20:31:59-06:00 master-of-cooling kernel: usb 1-8.2.2: [22] FU [PCM Playback Volume] ch = 2, val = -25600/-1/32
2025-11-04T20:31:59-06:00 master-of-cooling kernel: input: Generic USB Audio Consumer Control as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-8/1-8.2/1-8.2.2/1-8.2.2:1.3/0003:0BDA:4C15.0012/input/input48
2025-11-04T20:31:59-06:00 master-of-cooling kernel: ieee80211 phy0: Selected rate control algorithm ‘iwl-mvm-rs’
2025-11-04T20:31:59-06:00 master-of-cooling kernel: iwlwifi 0000:21:00.0 wlo1: renamed from wlan0
2025-11-04T20:31:59-06:00 master-of-cooling kernel: BTRFS: device label MassStorage devid 1 transid 20079 /dev/sda1 (8:1) scanned by mount (1050)
2025-11-04T20:31:59-06:00 master-of-cooling kernel: BTRFS info (device sda1): first mount of filesystem 027f2550-4813-20d9-ac54-fc87dc4612eb
2025-11-04T20:31:59-06:00 master-of-cooling kernel: BTRFS info (device sda1): using crc32c (crc32c-lib) checksum algorithm
2025-11-04T20:31:59-06:00 master-of-cooling kernel: input: Generic USB Audio as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-8/1-8.2/1-8.2.2/1-8.2.2:1.3/0003:0BDA:4C15.0012/input/input49
2025-11-04T20:31:59-06:00 master-of-cooling kernel: hid-generic 0003:0BDA:4C15.0012: input,hiddev101,hidraw9: USB HID v1.11 Device [Generic USB Audio] on usb-0000:03:00.0-8.2.2/input3
2025-11-04T20:31:59-06:00 master-of-cooling kernel: BTRFS warning (device sda1): devid 1 physical 0 len 134217728 inside the reserved space
2025-11-04T20:31:59-06:00 master-of-cooling kernel: usb 3-2.4: Quirk or no altset; falling back to MIDI 1.0
2025-11-04T20:31:59-06:00 master-of-cooling kernel: usb 1-8.2.3: new full-speed USB device number 10 using xhci_hcd
2025-11-04T20:31:59-06:00 master-of-cooling kernel: BTRFS info (device sda1): enabling ssd optimizations
2025-11-04T20:31:59-06:00 master-of-cooling kernel: BTRFS info (device sda1): turning on async discard
2025-11-04T20:31:59-06:00 master-of-cooling kernel: BTRFS info (device sda1): enabling free space tree
2025-11-04T20:31:59-06:00 master-of-cooling kernel: BTRFS info (device sda1): use zstd compression, level 3
2025-11-04T20:31:59-06:00 master-of-cooling kernel: usbcore: registered new interface driver snd-usb-audio
2025-11-04T20:31:59-06:00 master-of-cooling kernel: usb 1-8.2.3: New USB device found, idVendor=03f0, idProduct=0580, bcdDevice= 2.00
2025-11-04T20:31:59-06:00 master-of-cooling kernel: usb 1-8.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2025-11-04T20:31:59-06:00 master-of-cooling kernel: usb 1-8.2.3: Product: QHMD A85V
2025-11-04T20:31:59-06:00 master-of-cooling kernel: usb 1-8.2.3: Manufacturer: Quanta Inc.
2025-11-04T20:31:59-06:00 master-of-cooling kernel: usb 1-8.2.3: SerialNumber: 8CC220Z054
2025-11-04T20:31:59-06:00 master-of-cooling systemd-journald[760]: File /var/log/journal/95529aa7b5bc4b6ead824aadefc30924/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
2025-11-04T20:31:59-06:00 master-of-cooling kernel: hid-generic 0003:03F0:0580.0013: hiddev103,hidraw14: USB HID v1.11 Device [Quanta Inc. QHMD A85V] on usb-0000:03:00.0-8.2.3/input0
2025-11-04T20:31:59-06:00 master-of-cooling kernel: Generic FE-GE Realtek PHY r8169-0-2200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-2200:00, irq=MAC)
2025-11-04T20:31:59-06:00 master-of-cooling kernel: r8169 0000:22:00.0 enp34s0: Link is Down
2025-11-04T20:32:00-06:00 master-of-cooling kernel: ACPI: : failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:0 (0x1001)
2025-11-04T20:32:00-06:00 master-of-cooling kernel: NET: Registered PF_PACKET protocol family
2025-11-04T20:32:03-06:00 master-of-cooling kernel: r8169 0000:22:00.0 enp34s0: Link is Up - 1Gbps/Full - flow control off
2025-11-04T20:32:07-06:00 master-of-cooling kernel: [drm:amdgpu_job_submit [amdgpu]] ERROR Trying to push to a killed entity
2025-11-04T20:32:10-06:00 master-of-cooling kernel: nvme nvme0: using unchecked data buffer
2025-11-04T20:32:10-06:00 master-of-cooling kernel: block nvme0n1: No UUID available providing old NGUID
2025-11-04T20:32:11-06:00 master-of-cooling kernel: warning: `.kdeconnectd-wr’ uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
2025-11-04T20:32:13-06:00 master-of-cooling kernel: NET: Registered PF_QIPCRTR protocol family
2025-11-04T20:32:13-06:00 master-of-cooling kernel: wlo1: authenticate with 44:1e:98:58:44:1c (local address=5a:da:78:8e:29:23)
2025-11-04T20:32:13-06:00 master-of-cooling kernel: wlo1: send auth to 44:1e:98:58:44:1c (try 1/3)
2025-11-04T20:32:13-06:00 master-of-cooling kernel: wlo1: authenticated
2025-11-04T20:32:13-06:00 master-of-cooling kernel: wlo1: associate with 44:1e:98:58:44:1c (try 1/3)
2025-11-04T20:32:13-06:00 master-of-cooling kernel: wlo1: RX AssocResp from 44:1e:98:58:44:1c (capab=0x11 status=0 aid=7)
2025-11-04T20:32:13-06:00 master-of-cooling kernel: wlo1: associated
2025-11-04T20:32:13-06:00 master-of-cooling kernel: wlo1: Limiting TX power to 36 (36 - 0) dBm as advertised by 44:1e:98:58:44:1c
2025-11-04T20:32:13-06:00 master-of-cooling kernel: logitech-hidpp-device 0003:046D:407B.0010: HID++ 4.5 device connected.
2025-11-04T20:32:14-06:00 master-of-cooling kernel: amdgpu: Freeing queue vital buffer 0x7f9f8d200000, queue evicted
2025-11-04T20:32:14-06:00 master-of-cooling kernel: [drm:amdgpu_job_submit [amdgpu]] ERROR Trying to push to a killed entity
2025-11-04T20:33:30-06:00 master-of-cooling kernel: PM: suspend entry (deep)
2025-11-04T20:33:30-06:00 master-of-cooling kernel: Filesystems sync: 0.003 seconds

chatgpt identified the error as a amd issue

2025-11-04T20:32:14-06:00 master-of-cooling kernel: [drm:amdgpu_job_submit [amdgpu]] *ERROR* Trying to push to a killed entity

@chatgpt

Thanks—this is exactly what we needed. Here’s what your previous-boot tail shows and what to do next.

What your log says (high-signal bits)

• 20:32:07/14 — AMDGPU spits repeated: *ERROR* Trying to push to a killed entity and “queue evicted.”
  That means the GPU driver was already in a bad state before suspend.
• 20:33:30 — PM: suspend entry (deep) → Filesystems sync → no further messages → reboot.
  Classic hard hang during the platform/GPU handoff into S3 (deep).
• Journald notes “journal … uncleanly shut down,” which matches a hard lock.

So: it’s the deep sleep path (S3) wedging, very likely tied to the AMDGPU DC/PCIe/ACPI transition.

---

Quick, no-rebuild workaround (try right now)

Switch from S3 (deep) to s2idle just for this session, then test suspend:

# Show supported modes: one will be [bracketed] as current
cat /sys/power/mem_sleep

# Switch to s2idle for this boot only
echo s2idle | sudo tee /sys/power/mem_sleep

# Verify it took (should show [s2idle] ...)
cat /sys/power/mem_sleep

# Now try a safe suspend
systemctl suspend

• If it resumes cleanly: that confirms S3 is the culprit; keep s2idle while we stabilize deep.
• If it still hangs (unlikely): we’ll add the kernel params below and re-test.

---

Make it stick + tame the GPU/PCIe transitions (Nix snippet)

Apply this, rebuild, reboot, then test systemctl suspend again:

{ config, pkgs, ... }:
{
  # LTS often behaves better with suspend
  boot.kernelPackages = pkgs.linuxPackages_lts;

  hardware.enableRedistributableFirmware = true;

  boot.kernelParams = [
    "mem_sleep_default=s2idle"   # stay on s2idle for stability
    "amdgpu.runpm=0"             # disable BACO runtime pg
    "amdgpu.gfxoff=0"            # avoid deep GFX idle
    "pcie_aspm=off"              # keep PCIe links active
    "iommu=pt"                   # simpler DMA mappings on resume

    # keep logs alive if we test deep again
    "no_console_suspend" "ignore_loglevel" "log_buf_len=8M"
    "drm.debug=0x1e"
  ];

  # optional: make Magic SysRq available for safe reboots
  boot.kernel.sysctl."kernel.sysrq" = 1;

  # keep previous-boot logs
  services.journald.extraConfig = ''
    Storage=persistent
    SystemMaxUse=1G
  '';
}

Rebuild + reboot:

sudo nixos-rebuild switch && systemctl reboot

Then confirm and test:

cat /sys/power/mem_sleep      # should show [s2idle]
cat /proc/cmdline             # confirm params present
systemctl suspend             # should resume cleanly

If that works, you can daily-drive s2idle (most desktops do fine), or later we can try to re-enable deep selectively by removing params one at a time and seeing which one is essential.

---

If you want deep (S3) later

When you’re ready to try S3 again:

1. In BIOS:

• PCIe ASPM: Disabled
• Power Supply Idle Control: Typical Current Idle
• Update motherboard BIOS if available.

2. In Nix, keep only these at first:

boot.kernelParams = [
  "no_console_suspend" "ignore_loglevel" "log_buf_len=8M" "drm.debug=0x1e"
  "amdgpu.runpm=0" "amdgpu.gfxoff=0" "pcie_aspm=off" "iommu=pt"
  "mem_sleep_default=deep"
];

Test systemctl suspend. If it succeeds, we can reduce the set (drop iommu=pt, then try enabling ASPM, etc.) to find the minimal fix.

---

If you’d like, paste the output of:

cat /sys/power/mem_sleep
cat /proc/cmdline

after the change, and I’ll suggest the next smallest trim to keep things stable.

[bedHedd]

After fixing kernel issues from last time, I haven’t had too many major updates to my config.

A couple weeks back I started migrating my windows drive games drive to linux so that I can start using NixOS full time.

Commits · BedHedd/nix-config

Recently I feel chatgpt’s responses for 5.1 have gotten much worse. It has suggested me commands and configs that have shot me in the foot faster than before. I’m not sure if the cause is the model or if it is the custom instructions, but I had to roll back to a backup after messing up nix pretty bad

[bedHedd]

nixos living room pc

After crashing out about Fedora a couple of nights ago, I put my money where my mouth was and took time to get NixOS setup

bedHedd's blog because discourse > twitter

I’m fed up with fedora (nobara). I burned an hour and a half for a update task that should have only taken 20 minutes. This happens every time I go to update my htpc for holiday gatherings. First the updates bork my Xbox wireless controller adapter, then when I attempt to reinstall the controller xone drivers, my gpu drivers get wrecked. After r…

For reference this is my home theater living room pc

Bedhedd's home theater adventure

background I am in the progress of upgrading my living room audio setup. This was initially going to be a post to the lounge, but after some skim research I figure I’d ask the community. Feel free to follow as I figure out what I need initial setup Right now I have a LG C3 OLED, some cheapo speakers from my brother’s karaoke setup. I use the livi…

This update corresponds to these commits on November 22nd

Commits · BedHedd/nix-config

getting nixos installed

I started by using the graphical installer and burning the image to a usb with fedora media writer
https://search.nixos.org/packages?channel=25.05&query=fedora+media+writer
I also tried out the setup wizard that @progressEdd pushed a while back where running
nix run .#setup-wizard
would start up the script

bedHedd's NixOS Adventure

I ran into some git issues around history, but here is the pr also updated your instructions

Unfortunately, the default nixos installation did not have flakes enabled, so I kept getting the error

--experimental-features next command is disabled 

The solution was to change the system configuration to the one

Flakes - Official NixOS Wiki

using the parameters from the wiki

  nix.settings.experimental-features = [ "nix-command" "flakes" ];

I probably should have instructions similar to this shell script if I ever package up my install

Zaney/zaneyos/-/blob/main/install-zaneyos.sh

from

Tyler Kelley / ZaneyOS 🟰 Best ❄️ NixOS Configs · GitLab

How To Install My NixOS 🌨️ Flake, ZaneyOS

getting my nvidia 2070 working

Nvidia has always been a challenge on Fedora as it needed the proprietary drivers and a kernel mod

Need help with gpu folding, Folding@home, Fedora 31, Nvidia, Nvidia rtx 2070 [solved]

Figured it out, going to mark this post as the solution! The issue was the conflicting OpenCL libraries, I had installed. The toughest part of setting this up was figuring out what was broken. If you have similar issues to this viewing the outputs of FAHClient from terminal the terminal would help solve this issue. The types of OpenCL errors as se…

I started by applying this config from the thread here

Nvidia Drivers Not loading

{ pkgs, config, lib, inputs, ... }: {
  imports = [
    inputs.nixos-hardware.nixosModules.common-gpu-nvidia

    # TODO: why do I get the below error?
    # error: The option `hardware.intelgpu.loadInInitrd' in `/nix/store/4mgg9mrh8g0qj4g3z9zvqhrniig10bsn-source/systems/evo/hardware/gpus.nix' is already declared in `/nix/store/75hvhrfigcnckibdlg877157bpwjmy85-source/common/gpu/intel'.
    # Where is the other coming from?g
    # inputs.nixos-hardware.nixosModules.common-gpu-intel
  ];

  boot = {
    # TODO: confirm this works
    # https://forums.developer.nvidia.com/t/550-54-14-cannot-create-sg-table-for-nvkmskapimemory-spammed-when-launching-chrome-on-wayland/284775/26
    initrd.kernelModules = [ "nvidia" "i915" "nvidia_modeset" "nvidia_uvm" "nvidia_drm" ];
    # extraModulePackages = [ config.boot.kernelPackages.nvidia_x11 ];
    kernelParams = [ "nvidia-drm.fbdev=1" ];
  };

  hardware = {
    # deprecated for graphics.enable
    # opengl = {
    #   enable = true;
    #   # extraPackages = [ pkgs.intel-media-driver pkgs.vaapiVdpau ];
    # };

    graphics = {
      # For 32 bit applications
      # enable32Bit = true;
      enable = true;
    };

    nvidia = {
      # Modesetting is required.
      modesetting.enable = true;

      # Nvidia power management. Experimental, and can cause sleep/suspend to fail.
      # Enable this if you have graphical corruption issues or application crashes after waking
      # up from sleep. This fixes it by saving the entire VRAM memory to /tmp/ instead
      # of just the bare essentials.
      powerManagement.enable = true;

      # Fine-grained power management. Turns off GPU when not in use.
      # Experimental and only works on modern Nvidia GPUs (Turing or newer).
      powerManagement.finegrained = false;

      # Use the NVidia open source kernel module (not to be confused with the
      # independent third-party "nouveau" open source driver).
      # Support is limited to the Turing and later architectures. Full list of
      # supported GPUs is at:
      # https://github.com/NVIDIA/open-gpu-kernel-modules#compatible-gpus
      # Only available from driver 515.43.04+
      # Currently alpha-quality/buggy, so false is currently the recommended setting.
      open = false;

      forceFullCompositionPipeline = true;

      prime = {
        intelBusId = "PCI:0:2:0";
        nvidiaBusId = "PCI:1:0:0";
        offload = {
          enable = true;
          enableOffloadCmd = true;
        };
        # Make the Intel iGP default. The NVIDIA Quadro is for CUDA/NVENC
        # reverseSync.enable = true;
        # sync.enable = true;
      };
      nvidiaSettings = true;

      # Optionally, you may need to select the appropriate driver version for your specific GPU.
      package = config.boot.kernelPackages.nvidiaPackages.beta;
    };
  };

  services.xserver.videoDrivers = [ "nvidia" ];

}

After a rebuild worked. I moved on to getting steam to launch

getting steam to launch

Although I was able to boot into desktop, steam refused to startup. When I launched it from the terminal, I got these logs

steam
steam.sh[32374]: Running Steam on nixos 25.11 64-bit
steam.sh[32374]: STEAM_RUNTIME is enabled automatically
setup.sh[32430]: Steam runtime environment up-to-date!
steam.sh[32374]: Log already open
steam.sh[32374]: Steam client's requirements are satisfied
CProcessEnvironmentManager is ready, 6 preallocated environment variables.
[2025-11-21 21:03:59] Startup - updater built Nov 21 2025 01:25:02
[2025-11-21 21:03:59] Startup - Steam Client launched with: '/home/bedhedd/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened'
11/21 21:03:59 minidumps folder is set to /tmp/dumps
11/21 21:03:59 Init: Installing breakpad exception handler for appid(steam)/version(1763757504)/tid(32473)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
CProcessEnvironmentManager is ready, 6 preallocated environment variables.
[2025-11-21 21:03:59] Process started with command-line: '/home/bedhedd/.local/share/Steam/ubuntu12_32/steam' '-child-update-ui' '-child-update-ui-socket' '8' '-srt-logger-opened'
11/21 21:03:59 minidumps folder is set to /tmp/dumps
[2025-11-21 21:03:59] Using update UI: xwin
11/21 21:03:59 Init: Installing breakpad exception handler for appid(steam)/version(0)/tid(32474)
[2025-11-21 21:03:59] Create window
[2025-11-21 21:03:59] Loading cached metrics from disk (/home/bedhedd/.local/share/Steam/package/steam_client_metrics.bin)
[2025-11-21 21:03:59] Failed to load cached hosts file (File 'update_hosts_cached.vdf' not found), using defaults
[2025-11-21 21:03:59] Using the following download hosts for Public, Realm steamglobal
[2025-11-21 21:03:59] 1. https://client-update.steamstatic.com, /, Realm 'steamglobal', weight was 1, source = 'baked in'
[2025-11-21 21:03:59] Checking for update on startup
[2025-11-21 21:03:59] Set percent complete: 0
[2025-11-21 21:03:59] Checking for available updates...
[2025-11-21 21:03:59] Downloading manifest: https://client-update.steamstatic.com/steam_client_ubuntu12
[2025-11-21 21:03:59] Manifest download: send request
[2025-11-21 21:03:59] Set status message: Checking for available updates...
[2025-11-21 21:03:59] Set percent complete: -1
[2025-11-21 21:04:00] Manifest download: waiting for download to finish
[2025-11-21 21:04:00] Manifest download: finished
[2025-11-21 21:04:00] Download skipped: /steam_client_ubuntu12 version 1763757504, installed version 1763757504, existing pending version 0
[2025-11-21 21:04:00] Nothing to do
[2025-11-21 21:04:00] Verifying installation...
[2025-11-21 21:04:00] Verifying all executable checksums
[2025-11-21 21:04:00] Set percent complete: -1
[2025-11-21 21:04:00] Set status message: Verifying installation...
[2025-11-21 21:04:00] Verification complete
UpdateUI: skip show logo
[2025-11-21 21:04:00] Destroy window
[2025-11-21 21:04:00] Shutdown

Steam logging initialized: directory: /home/bedhedd/.local/share/Steam/logs

XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xf6187370
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xf6185cc0
11/21 21:04:01 minidumps folder is set to /tmp/dumps
11/21 21:04:01 Init: Installing breakpad exception handler for appid(steamsysinfo)/version(1763757504)/tid(32483)
Running query: 1 - GpuTopology
CVulkanTopology: failed create vulkan instance: -9
CVulkanTopology: failed to create vulkan instanceFailed to query vulkan gpu topology

Failed to query vulkan gpu topology
Response: 
Exit code: -2
Fontconfig warning: line 5: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 4: unknown element "description"
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 72: non-double matrix element
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 72: non-double matrix element
Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 80: saw unknown, expected number
Fontconfig warning: "/etc/fonts/conf.d/10-sub-pixel-none.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/10-yes-antialias.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/45-generic.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/48-spacing.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/49-sansserif.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/51-local.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/60-generic.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/65-nonlatin.conf", line 4: unknown element "description"
src/vgui2/src/surface_linux.cpp (1956) : glXChooseVisual failed
src/vgui2/src/surface_linux.cpp (1956) : glXChooseVisual failed
src/vgui2/src/surface_linux.cpp (1956) : Fatal assert; application exiting
src/vgui2/src/surface_linux.cpp (1956) : Fatal assert; application exiting
11/21 21:04:01 Init: Installing breakpad exception handler for appid(steam)/version(1763757504)/tid(32473)
steamwebhelper.sh[32487]: Starting steamwebhelper under bootstrap steamrt steam runtime via: /home/bedhedd/.local/share/Steam/steamrt64/steam-runtime-steamrt/_v2-entry-point
steamwebhelper.sh[32487]: Starting steamwebhelper with steamrt steam runtime at /home/bedhedd/.local/share/Steam/steamrt64/steam-runtime-steamrt/_v2-entry-point
assert_20251121210401_9.dmp[32519]: Uploading dump (out-of-process)
/tmp/dumps/assert_20251121210401_9.dmp
bedhedd@HT-RL06-PC ~> assert_20251121210401_9.dmp[32519]: Finished uploading minidump (out-of-process): success = yes
assert_20251121210401_9.dmp[32519]: response: CrashID=bp-14cb03b0-144b-43e1-8efc-8ba1a2251121
assert_20251121210401_9.dmp[32519]: file ''/tmp/dumps/assert_20251121210401_9.dmp'', upload yes: ''CrashID=bp-14cb03b0-144b-43e1-8efc-8ba1a2251121''
pressure-vessel-wrap[32487]: W: Using libGLX_mesa.so.0 from provider system for some but not all architectures! Will take /usr/share/drirc.d from provider.
pressure-vessel-wrap[32487]: W: "run/opengl-driver/share/drirc.d" is unlikely to appear in "/run/host"
exec ./steamwebhelper -nocrashdialog -lang=en_US -cachedir=/home/bedhedd/.local/share/Steam/config/htmlcache -steampid=32473 -buildid=1763757504 -steamid=0 -logdir=/home/bedhedd/.local/share/Steam/logs -uimode=7 -startcount=0 -steamuniverse=Public -realm=Global -clientui=/home/bedhedd/.local/share/Steam/clientui -steampath=/home/bedhedd/.local/share/Steam/ubuntu12_32/steam -launcher=0 -use_xcomposite_workaround --valve-initial-threadpool-size=4 --valve-enable-site-isolation --enable-smooth-scrolling --disable-gpu-compositing --disable-gpu --password-store=basic --log-file=/home/bedhedd/.local/share/Steam/logs/cef_log.txt --disable-quick-menu --disable-component-update --gaia-url=http://disabled.invalid --disable-features=WinRetrieveSuggestionsOnlyOnDemand,SpareRendererForSitePerProcess,DcheckIsFatal,BlockPromptsIfIgnoredOften,ValveFFmpegAllowLowDelayHEVC

I passed the log into chatgpt which was able to identified these issues

@chatgpt

Main points from the log:

1. Vulkan fails:

   • CVulkanTopology: failed create vulkan instance: -9
   • Failed to query vulkan gpu topology

2. OpenGL/GLX then fails hard:

   • glXChooseVisual failed
   • Fatal assert; application exiting

3. Fontconfig warnings:

   • Noisy but not the reason Steam dies.

So Steam is starting fine, then the Steam sysinfo helper fails to create a Vulkan instance and then the UI crashes because it can’t get a GLX visual. On NixOS that almost always means missing or misconfigured 32-bit graphics drivers.

I then passed my config from the nvidia section

@bedhedd

current nix setup

boot = {
    # TODO: confirm this works
    # https://forums.developer.nvidia.com/t/550-54-14-cannot-create-sg-table-for-nvkmskapimemory-spammed-when-launching-chrome-on-wayland/284775/26
    initrd.kernelModules = [ "nvidia" "i915" "nvidia_modeset" "nvidia_uvm" "nvidia_drm" ];
    # extraModulePackages = [ config.boot.kernelPackages.nvidia_x11 ];
    kernelParams = [ "nvidia-drm.fbdev=1" ];
  };

  hardware = {
    # deprecated for graphics.enable
    # opengl = {
    #   enable = true;
    #   # extraPackages = [ pkgs.intel-media-driver pkgs.vaapiVdpau ];
    # };

    graphics = {
      # For 32 bit applications
      # enable32Bit = true;
      enable = true;
    };

    nvidia = {
      # Modesetting is required.
      modesetting.enable = true;

      # Nvidia power management. Experimental, and can cause sleep/suspend to fail.
      # Enable this if you have graphical corruption issues or application crashes after waking
      # up from sleep. This fixes it by saving the entire VRAM memory to /tmp/ instead
      # of just the bare essentials.
      powerManagement.enable = true;

      # Fine-grained power management. Turns off GPU when not in use.
      # Experimental and only works on modern Nvidia GPUs (Turing or newer).
      powerManagement.finegrained = false;

      # Use the NVidia open source kernel module (not to be confused with the
      # independent third-party "nouveau" open source driver).
      # Support is limited to the Turing and later architectures. Full list of
      # supported GPUs is at:
      # https://github.com/NVIDIA/open-gpu-kernel-modules#compatible-gpus
      # Only available from driver 515.43.04+
      # Currently alpha-quality/buggy, so false is currently the recommended setting.
      open = false;

      forceFullCompositionPipeline = true;

      prime = {
        intelBusId = "PCI:0:2:0";
        nvidiaBusId = "PCI:1:0:0";
        offload = {
          enable = true;
          enableOffloadCmd = true;
        };
        # Make the Intel iGP default. The NVIDIA Quadro is for CUDA/NVENC
        # reverseSync.enable = true;
        # sync.enable = true;
      };
      nvidiaSettings = true;

      # Optionally, you may need to select the appropriate driver version for your specific GPU.
      package = config.boot.kernelPackages.nvidiaPackages.beta;
    };
  };

  services.xserver.videoDrivers = [ "nvidia" ];

Chatgpt suggested the following:

@chatgpt

You’re missing the 32-bit GL/Vulkan libs. That’s almost certainly why Steam’s Vulkan/GLX init is dying.

Key change: turn this on:

hardware.graphics = {
  enable = true;
  enable32Bit = true;  # <- needed for Steam & other 32-bit stuff
};

Right now enable32Bit is commented out, so /run/opengl-driver-32/lib isn’t populated and 32-bit clients (Steam’s sysinfo helper, some games, etc.) can’t get a GLX visual or Vulkan instance.

A minimal, Steam-friendly block based on what you posted:

boot = {
  initrd.kernelModules = [ "nvidia" "i915" "nvidia_modeset" "nvidia_uvm" "nvidia_drm" ];
  kernelParams = [ "nvidia-drm.fbdev=1" ];
};

hardware = {
  graphics = {
    enable = true;
    enable32Bit = true;
    # optional but nice to have:
    # extraPackages = with pkgs; [ vaapiVdpau libvdpau-va-gl intel-media-driver nvidia-vaapi-driver ];
  };

  nvidia = {
    modesetting.enable = true;
    powerManagement.enable = true;
    powerManagement.finegrained = false;
    open = false;
    forceFullCompositionPipeline = true;

    prime = {
      intelBusId = "PCI:0:2:0";
      nvidiaBusId = "PCI:1:0:0";
      offload = {
        enable = true;
        enableOffloadCmd = true;
      };
    };

    nvidiaSettings = true;
    package = config.boot.kernelPackages.nvidiaPackages.beta;
  };
};

services.xserver.videoDrivers = [ "nvidia" ];

Then:

1. sudo nixos-rebuild switch.

2. Reboot.

3. Test graphics stack:

   vulkaninfo | head
   glxinfo -B
   

   If both succeed and show Nvidia/Intel (not llvmpipe), Steam should stop hitting glXChooseVisual failed and the Vulkan topology query should succeed.

If you paste glxinfo -B and vulkaninfo | head after enabling enable32Bit, we can double-check for any remaining issues.

You can see the git commit and diff here

add nvidia gpu

The relevant lines are here

BedHedd/nix-config/blob/61c4bf8a33beb21b7aa7eb853267b36c8bbcabd3/machines/HT-RL06-PC/default.nix#L44-L82

getting my xbox dongle working

I bought the microsoft third party adapter and got it working with steamos

Getting official third party controller dongles working on my Steam Deck

getting xbox dongle working on my steam deck I got some xbox controllers and a dongle recently as I noticed that I was hitting the max pairing limit on bluetooth on my steam deck. I bought this dongle because it was small and supported by Microsoft https://www.amazon.com/dp/B0CN6HT6JZ?language=en-US In terms of setup, this guide + script was sup…

It has been a while since I last got it setup, so the arch wiki’s section on the different drivers were helpful in figuring out which packages I needed
https://wiki.archlinux.org/title/Gamepad#Xbox_Wireless_Controller_/_Xbox_One_Wireless_Controller

@arch wiki

xpadneo

A relatively new driver which does support the Xbox One S and Xbox Series X|S controller via Bluetooth is called xpadneo. In addition to these two models, it has also basic support for the Xbox Elite Series 2 Wireless controller. In exchange for fully supporting just two controllers so far, it enables one to read out the correct battery level, supports rumble (even the one on the trigger buttons - L2/R2), corrects the (sometimes wrong) button mapping and more.

Installation is done using DKMS: xpadneo-dkmsAUR.

Note Pairing a new Xbox One S controller for the first time may prove difficult, from not pairing at all to entering a connect/disconnect loop. These problems are described there. The best way to reliably pair the controller is to first pair it in Windows 10. However, this needs be done using the same Bluetooth adapter. A solution is to install a free copy of Windows 10 Evaluation on a Virtual machine (using QEMU or VirtualBox, taking care of the Bluetooth adapter passthrough requirements, e.g. as an USB device) using Arch Linux as your host, and pair in Windows 10 first, then do the same again under your Arch Linux system. Then pairing will succeed and there will be no need of further Windows 10 use.

Connect Xbox Wireless Controller with Microsoft Xbox Wireless Adapter

xone is a Linux kernel driver for Xbox One and Xbox Series X|S accessories. It serves as a modern replacement for and supersedes xpad and xow. Currently working via wired or with the Microsoft Xbox Wireless Adapter “dongle”. Bugfixes for this driver are now being mainted by the dlundqvist fork of the original driver.

Install xone-dkmsAUR and, if using the wireless dongle, xone-dongle-firmwareAUR. Installation requires a reboot of your system.

Note

• The headers corresponding to your kernel are required; see DKMS#Installation.
• The adapter uses a mt76 based 802.11/15 chipset which can result in interference with other wireless adapters connected to the same system or close by.

I needed the xpadneo and xone. While looking for relevant install configs, I came across this post which helped explain xone further
https://old.reddit.com/r/NixOS/comments/1inbiy5/getting_xbox_controllers_to_work_on_nixos/mcatp5f/

@u/abakune

That’s right - by driver:

xone:

• Dongle (for use with two xbox controllers)

xpad-noone:

• A wired GameSir (Great controller btw)
• Two custom hitboxes with Brook Universal PCB

xpadneo config parameters

This post was helpful in figuring out what I needed for xpadneo to work
https://old.reddit.com/r/NixOS/comments/1ch5d2p/help_needed_to_install_and_debug_xpadneo_xbox/lkbabax/

@u/grnqrtr

I got it working! For initial problem of controller not even showing up in a scan, I was dumb and didn’t have it in “pair” mode. I thought the flashing light meant pair mode, but I had to hold another button to get it into “pair” mode where the light flashes faster.

In case it helps anyone else, I ended up with this in my config to eventually get it to connect stably:

# Enable xbox controller
hardware.xpadneo.enable = true;

hardware.bluetooth.settings = {
  General = {
    Privacy = "device";
    JustWorksRepairing = "always";
    Class = "0x000100";
    FastConnectable = true;
  };
};

boot = {
  extraModulePackages = with config.boot.kernelPackages; [ xpadneo ];
  extraModprobeConfig = ''
    options bluetooth disable_ertm=Y
  '';
};

xone config

I had some issues consistently getting 4 controllers to pair with the dongle. Fortunately this config worked
https://old.reddit.com/r/NixOS/comments/ywzo6t/anyone_know_how_to_the_get_the_xone_driver_to/iwmykia/

@u/samjk14

This is working for me. I don’t actually know if the linux_zen bit is needed. I tried a few things and when it started working I stopped experimenting.

hardware.xone.enable = true; environment.systemPackages = with pkgs; [ linuxKernel.packages.linux_zen.xone ];

A restart was required after this.

You see the commits here
xpad neo

BedHedd/nix-config/blob/e90c48324d45f6a585093f77fd02c24bbe053f9e/machines/HT-RL06-PC/default.nix#L57-L59

xone

BedHedd/nix-config/blob/b6e3d7830180d051d964f4b5b40c91312e445a1b/machines/HT-RL06-PC/default.nix#L86-L100

[bedHedd]

@bedHedd

getting my xbox dongle working

I bought the microsoft third party adapter and got it working with steamos

getting xbox dongle working on my steam deck I got some xbox controllers and a dongle recently as I noticed that I was hitting the max pairing limit on bluetooth on my steam deck. I bought this dongle because it was small and supported by Microsoft https://www.amazon.com/dp/B0CN6HT6JZ?language=en-US In terms of setup, this guide + script was sup…

It has been a while since I last got it setup, so the arch wiki’s section on the different drivers were helpful in figuring out which packages I needed
https://wiki.archlinux.org/title/Gamepad#Xbox_Wireless_Controller_/_Xbox_One_Wireless_Controller

xpadneo

A relatively new driver which does support the Xbox One S and Xbox Series X|S controller via Bluetooth is called xpadneo. In addition to these two models, it has also basic support for the Xbox Elite Series 2 Wireless controller. In exchange for fully supporting just two controllers so far, it enables one to read out the correct battery level, supports rumble (even the one on the trigger buttons - L2/R2), corrects the (sometimes wrong) button mapping and more.

Installation is done using DKMS: xpadneo-dkmsAUR.

Note Pairing a new Xbox One S controller for the first time may prove difficult, from not pairing at all to entering a connect/disconnect loop. These problems are described there. The best way to reliably pair the controller is to first pair it in Windows 10. However, this needs be done using the same Bluetooth adapter. A solution is to install a free copy of Windows 10 Evaluation on a Virtual machine (using QEMU or VirtualBox, taking care of the Bluetooth adapter passthrough requirements, e.g. as an USB device) using Arch Linux as your host, and pair in Windows 10 first, then do the same again under your Arch Linux system. Then pairing will succeed and there will be no need of further Windows 10 use.

Connect Xbox Wireless Controller with Microsoft Xbox Wireless Adapter

xone is a Linux kernel driver for Xbox One and Xbox Series X|S accessories. It serves as a modern replacement for and supersedes xpad and xow. Currently working via wired or with the Microsoft Xbox Wireless Adapter “dongle”. Bugfixes for this driver are now being mainted by the dlundqvist fork of the original driver.

Install xone-dkmsAUR and, if using the wireless dongle, xone-dongle-firmwareAUR. Installation requires a reboot of your system.

Note

• The headers corresponding to your kernel are required; see DKMS#Installation.
• The adapter uses a mt76 based 802.11/15 chipset which can result in interference with other wireless adapters connected to the same system or close by.

I needed the xpadneo and xone. While looking for relevant install configs, I came across this post which helped explain xone further
https://old.reddit.com/r/NixOS/comments/1inbiy5/getting_xbox_controllers_to_work_on_nixos/mcatp5f/

That’s right - by driver:

xone:

• Dongle (for use with two xbox controllers)

xpad-noone:

• A wired GameSir (Great controller btw)
• Two custom hitboxes with Brook Universal PCB

xpadneo config parameters

This post was helpful in figuring out what I needed for xpadneo to work
https://old.reddit.com/r/NixOS/comments/1ch5d2p/help_needed_to_install_and_debug_xpadneo_xbox/lkbabax/

I got it working! For initial problem of controller not even showing up in a scan, I was dumb and didn’t have it in “pair” mode. I thought the flashing light meant pair mode, but I had to hold another button to get it into “pair” mode where the light flashes faster.

In case it helps anyone else, I ended up with this in my config to eventually get it to connect stably:

# Enable xbox controller
hardware.xpadneo.enable = true;

hardware.bluetooth.settings = {
  General = {
    Privacy = "device";
    JustWorksRepairing = "always";
    Class = "0x000100";
    FastConnectable = true;
  };
};

boot = {
  extraModulePackages = with config.boot.kernelPackages; [ xpadneo ];
  extraModprobeConfig = ''
    options bluetooth disable_ertm=Y
  '';
};

xone config

I had some issues consistently getting 4 controllers to pair with the dongle. Fortunately this config worked
https://old.reddit.com/r/NixOS/comments/ywzo6t/anyone_know_how_to_the_get_the_xone_driver_to/iwmykia/

This is working for me. I don’t actually know if the linux_zen bit is needed. I tried a few things and when it started working I stopped experimenting.

hardware.xone.enable = true; environment.systemPackages = with pkgs; [ linuxKernel.packages.linux_zen.xone ];

A restart was required after this.

You see the commits here
xpad neo

nix-config/machines/HT-RL06-PC/default.nix at e90c48324d45f6a585093f77fd02c24bbe053f9e · BedHedd/nix-config · GitHub

xone

nix-config/machines/HT-RL06-PC/default.nix at b6e3d7830180d051d964f4b5b40c91312e445a1b · BedHedd/nix-config · GitHub

The config worked and I had no issues with the controllers in my work area, but I kept getting controller drop outs with the dongle in the living room. I suspect the batteries were causing the drop outs, so until the replacement rechargeable batteries arrive, I looked into updating the controller firmware. I recalled that the arch wiki had this section

@arch wiki

Note

Pairing a new Xbox One S controller for the first time may prove difficult, from not pairing at all to entering a connect/disconnect loop. These problems are described there. The best way to reliably pair the controller is to first pair it in Windows 10. However, this needs be done using the same Bluetooth adapter. A solution is to install a free copy of Windows 10 Evaluation on a Virtual machine (using QEMU or VirtualBox, taking care of the Bluetooth adapter passthrough requirements, e.g. as an USB device) using Arch Linux as your host, and pair in Windows 10 first, then do the same again under your Arch Linux system. Then pairing will succeed and there will be no need of further Windows 10 use.

learning virtualization in NixOS

The arch wiki suggested using qemu and virtualbox.

I started by adding virtualbox to my packages, but I got the following vboxdrv error:

VirtualBox kernel driver not Installed. The vboxdrv kernel module was either not loaded, /dev/vboxdrv is not set up properly, or you are using EFI Secure Boot and the module is not signed in the right way for your system. If necessary, try setting up the kernel module again by executing '/sbin/vboxconfig' as root (VERR_VM_DRIVER_NOT_INSTALLED).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

I asked chatgpt which suggested the following

@chatgpt

You’re on NixOS, so that /sbin/vboxconfig hint from VirtualBox is not what you should run. On NixOS you fix this via config, rebuild, and making sure you’re in the right groups.

Below is the minimal checklist to get rid of VERR_VM_DRIVER_NOT_INSTALLED on NixOS.

---

1. Enable VirtualBox in your NixOS config

In /etc/nixos/configuration.nix (or your flake host module), add:

{ config, pkgs, ... }:

{
  virtualisation.virtualbox.host = {
    enable = true;

    # Optional but usually needed for USB support etc.
    enableExtensionPack = true;
  };

  # Make sure your user is in the vboxusers group
  users.users.yourusername = {
    isNormalUser = true;
    extraGroups = [ "wheel" "vboxusers" ];
  };
}

Replace yourusername with your actual user.

If you’re using Home Manager or split modules, this might live in a host module like hosts/your-machine.nix instead, but the options are the same.

---

2. Rebuild and switch

Run as root:

sudo nixos-rebuild switch

This will:

• Build VirtualBox and the kernel modules against your current kernel.
• Set up /dev/vboxdrv and friends via systemd services/udev.

---

3. Re-login (or reboot) so groups apply

Your user has to be in vboxusers in the current session.

Either:

# check groups
groups

If you don’t see vboxusers, log out and log back in, or reboot once:

sudo reboot

---

4. Verify the kernel module

After the rebuild and a fresh login:

lsmod | grep vbox

You should see something like vboxdrv, vboxnetflt, etc.

If not, check the service:

systemctl status virtualbox

On NixOS, VirtualBox auto-loads the module via services; you do not run /sbin/vboxconfig.

---

5. Secure Boot note (if relevant)

If you’re using Secure Boot with a custom shim, unsigned out-of-tree modules may be blocked. On NixOS, most setups either:

• Run without Secure Boot, or
• Use a custom signing setup for kernel modules.

If VirtualBox still fails and dmesg shows messages about module signature / Secure Boot:

• Either disable Secure Boot in firmware, or
• Set up module signing and include VirtualBox modules in that flow (more involved NixOS config; can go through that if you need).

---

Quick sanity checks

If the error persists after steps 1–4, run:

# 1) Check device
ls -l /dev/vboxdrv

# 2) Check kernel messages
dmesg | grep -i vbox

If you paste the output of those two commands plus your virtualisation.virtualbox section, I can pinpoint the exact issue.

Since chatgpt 5.1 has hallucinated more recently, I decided to look it up and found this thread

Install virtualbox in NixOS?

@meltingscales

Interesting, because @dtannock it seems to work, even though it might be bad.

I mean…if something has the intended effect…then it works!

And, I got it to work! Here’s my config:

github.com

meltingscales/dotfiles/blob/c8ec849871dc4c195fced89374a73ff3086eaa02/nix/etc/nixos/configuration.nix#L157

      
            steam
            prismlauncher #minecraft launcher
          
            # messaging apps
            # discord # i favor vesktop tbqh...
            vesktop
            signal-desktop
            telegram-desktop
          ];
          
          # virtualization
          virtualisation.virtualbox.host.enable = true;
          virtualisation.virtualbox.guest.enable = true;
          virtualisation.virtualbox.guest.dragAndDrop = true;
          users.extraGroups.vboxusers.members = [ "melty" ];
          virtualisation.virtualbox.host.enableHardening = false;
          
          # mullvad vpn
          services.mullvad-vpn.enable = true;
          services.mullvad-vpn.package = pkgs.mullvad-vpn;
          

When I launched virtuabox again, I got the following error

AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

chatgpt recommended I enable it in my motherboard. Looking back, it must have gotten disabled when I flashed the new bios.

After enabling virtualization I got the following error:

Failed to acquire display parameter.
Unsupported resolution for screen shot: 0x0 (screen 0).
Result Code:
NS_ERROR_INVALID_ARG (0x80070057)
Component:
DisplayWrap
Interface:
IDisplay {14fd6676-ee6b-441a-988b-c83025ab693a}

At this point I decided it was more effort to setup virtualbox, so I pivoted to qemu. While reading the the nixos wiki page, I came across the section on quickemu

QEMU - Official NixOS Wiki

@nixos wiki

Quick EMU

Quickly create and run highly optimised desktop virtual machines for Linux, macOS and Windows; with just two commands.

GitHub - quickemu-project/quickemu: Quickly create and run optimised Windows, macOS and Linux virtual machines

quickget windows 11
quickemu --vm windows-11.conf

The wiki setup looked pretty straightforward, so I went ahead and followed the instructions

01 Installation

04 Create Windows virtual machines

The defaults worked for windows 10, but my xbox controller didn’t show up in the xbox accessories app in windows 10.

patch for windows 11

This section might be outdated, as there seems to be a new patch, but at the time of writing, the nix package hadn’t been updated

May we have a new version? =)

I decided to try again with windows 11 but I encountered some issues getting it installed to the vm
The first issue was booting into the installer.
I modified the windows-11 conf per the suggestion of this post

@lj3954

Please try removing the fixed_iso line from your config file.

This is the conf that worked

#!/etc/profiles/per-user/bedhedd/bin/quickemu --vm
guest_os="windows"
disk_img="windows-11/disk.qcow2"
iso="windows-11/Win11_25H2_EnglishInternational_x64.iso"
# fixed_iso="windows-11/virtio-win.iso"
disk_size="64G"
tpm="on"
secureboot="off"

bug: win11 installation encountered an unexpected error.

I was able to get into the installer, but then encountered the same issue of hardware recognition

bug: win11 installation encountered an unexpected error.

@axlroden

There is another fix, by only keeping the drivers needed on the virtio cd.
Keeps only NetKVM vioscsi, viostor and the msi/exe files in root.

This allows normal install.

Thats what I’m using at least till a real fix is done, even though its quite hacky…
Why this works? No idea…

export VM_PATH="$HOME/windows-11"
echo "Fixing virtio iso"
mkdir -p "${VM_PATH}/virtio-cd" 
7z x "${VM_PATH}/virtio-win.iso" -o"${VM_PATH}/virtio-cd" -bso0 -bsp0
[[ -d "${VM_PATH}/virtio-cd" && "$(ls -A "${VM_PATH}/virtio-cd")" ]] || { echo "Error: Extraction of virtio-cd failed!"; exit 1; }
pushd "${VM_PATH}/virtio-cd"
find . -mindepth 1 -maxdepth 1 ! -name "NetKVM" ! -name "vioscsi" ! -name "viostor" ! -name "*.msi" ! -name "*.exe" -exec rm -rf {} +
popd
rm -rf "${VM_PATH}/virtio-win.iso"
mkisofs -quiet -o "${VM_PATH}/virtio-win.iso" -V "fixed-cd" -J -R "${VM_PATH}/virtio-cd"

I ran the script and selected the fixed drive. To launch the script I used this command with the suggestions
from

bug: win11 installation encountered an unexpected error.

@axlroden

commenting out fixed iso and adding:
--extra_args "--drive media=cdrom,index=3,file=windows-11/virtio-win.iso"
Seems to get me to be able to load drivers from it, without just a black screen after some selections otherwise.

quickemu --vm windows-11.conf  --extra_args "--drive media=cdrom,index=3,file=windows-11/virtio-win.iso" -display spice

When selecting the driver, I picked the NetKVM drivers from the cd from the am64 folder. After applying these patches, I was able to boot into windows. When I tried passing my xbox controller with spice, Windows detected it initially then stopped working. Pairing with the bluetooth dongle worked, but I couldn’t update the controller firmware.