| 3 Dec 2025 |
 hexa | after renaming you need to toggle the jobsets for them to work again | 09:52:00 |
| hexa | otherwise they just | 09:52:10 |
| hexa |
evaluation failed with exit code 255
| 09:52:15 |
| hexa | as can be seen here https://hydra.nixos-cuda.org/jobset/nixos-cuda/cuda-packages-unstable#tabs-errors | 09:52:24 |
| hexa | and here https://hydra.nixos-cuda.org/jobset/nixos-cuda/cuda-packages-legacy#tabs-errors | 09:52:38 |
| hexa | https://github.com/NixOS/hydra/issues/1288 | 09:52:56 |
 Gaétan Lepage | Thanks for the tip hexa (UTC+1)! | 09:54:14 |
| hexa | Gaétan Lepage: you probably also want a lower priority (higher value) than cache.nixos.org | 15:58:01 |
| hexa | * Gaétan Lepage: you probably also want a lower priority (higher value) than cache.nixos.org, which has prio 30 | 15:58:10 |
| Gaétan Lepage | What are you referring to? Something in the nix-cuda infra? | 17:36:09 |
| hexa | https://cache.nixos-cuda.org/nix-cache-info | 18:22:39 |
| hexa | https://cache.nixos.org/nix-cache-info | 18:22:52 |
| hexa | harmonia is greedy | 18:23:00 |
| hexa | this makes everyone who wants to substitute prefer nixos-cuda over c.n.o | 18:23:28 |
| Gaétan Lepage | Ok makes sense! Done. | 19:23:21 |
| Gaétan Lepage | connor (burnt/out) (UTC-8) the onnx bump should be good to go. | 20:50:50 |
 teto | I wonder what priority to set the cache.nixos-cuda.org cache to ? it's the defualt on the webpage but shouldn't a typical user fetch from cache.nixos.org first ? in terms of cost etc, is there any preference ? | 21:17:23 |
| hexa | the priority is set on the server-side no? | 21:18:07 |
| hexa | and yes, you'll always want to prefer c.n.o | 21:18:28 |
| Gaétan Lepage | You can also append ?priority=3 to the substituters in /etc/nix/nix.conf | 21:20:09 |
| hexa | ah ok | 21:20:19 |
| teto | ha yeah the server shows 50 as default https://cache.nixos-cuda.org/ so I have nothing to do nice :) | 22:22:24 |
| teto | (I was indeed thinking of ?priority ) | 22:22:39 |
| hexa | it does now 😛 | 22:24:16 |
|  corroding556 joined the room. | 23:55:01 |
| 4 Dec 2025 |
| corroding556 | Hi all! Very much appreciate the work that's been put into CUDA support in nixpkgs/NixOS.
Recently updated my system configuration to a more recent version of nixpkgs and had to pin cudaCapabilities to 6.1 now that CUDA 13.0 has dropped support for Pascal, started getting some confusing build failures as a result.
Spent several hours looking into how the CUDA packaging ecosystem works only to realize using --trace-verbose gave the answer straight up >.<.
It seems nixpkgs updating to use cuDNN 9.13 means that other packages pulling in cudaPackages_12_{6,8,9} no longer support compute capabilities < 7.5 even though CUDA supports compute capabilities >= 5.0 up until the jump to 13.0.
I noticed 9.13 is not the only version in nixpkgs though, what is the strategy around how many legacy versions of CUDA packages to maintain in nixpkgs?
Does it make sense to add cuDNN 9.11 as a pinned version to bridge the gap since 9.12 has dropped support for compute capabilities < 7.5?
If that's not appropriate 8.9.7 is the most recent version available in nixpkgs which still supports my hardware, how would I/how reasonable is it to force my config to use that?
Sorry for all the questions, appreciate any advice 😅
| 01:57:08 |
 Alexandros Liarokapis | any idea what is the difference between torch-bin and torchWithCuda ? | 12:28:06 |
 Robbie Buxton | In reply to @aliarokapis:matrix.org
any idea what is the difference between torch-bin and torchWithCuda ? Iirc torch-bin is torch not built from source and torchWithCuda is torch built from source with cuda enabled forced regardless of global configuration? | 13:34:25 |
| Gaétan Lepage | Yes, this is it. | 13:46:25 |
| Alexandros Liarokapis | and it is apparently in the nixos cache by defualt? | 14:05:18 |
