| 18 Jun 2025 |
 four | I'm curious how(if?) it'll work with the 2.8k display | 19:21:25 |
 Alex | Might just be reduced frame rate. | 19:21:52 |
 Tristan Ross | In reply to @bivsk22:matrix.org
Have you got your hands on the framework board yet? No, it doesn't ship yet | 19:24:11 |
| Tristan Ross | In reply to @dramforever:matrix.org
is this what happens when you want to stick with the most well-supported-by-mainline-linux riscv board Yeah, by the time this iteration of my config has built, a century will have passed lol. | 19:25:51 |
| Alex | It'll finish just in time for the next world rebuild. :) | 19:26:26 |
| Tristan Ross | It'll finish and we'll have already had like 4 world rebuilds | 19:34:25 |
| 21 Jun 2025 |
|  ocfox joined the room. | 03:36:15 |
 @lotte:chir.rs | https://github.com/NixOS/nixpkgs/commit/88c1caa7d016c401082a44979bfde7e5e276048f seems to maybe have broken riscv cross compilation? | 10:59:14 |
| @lotte:chir.rs | https://hydra.chir.rs/build/235667/nixlog/1/tail | 10:59:21 |
 misuzu | https://github.com/NixOS/nixpkgs/pull/418640 | 13:23:56 |
| @lotte:chir.rs | ah, nice | 13:24:39 |
| @lotte:chir.rs | so that nixpkgs tree is slapped on my now incredibly complex system update pr :D | 13:43:24 |
|  GenericNerdyUsername joined the room. | 18:59:54 |
| GenericNerdyUsername | Whats the absolute bare minimum riscv config nixos would need to get something on screen? | 20:03:27 |
| Alex | In reply to @genericnerdyusername:matrix.org
Whats the absolute bare minimum riscv config nixos would need to get something on screen? Depends on your hardware. | 20:37:16 |
| GenericNerdyUsername | i think i phrased that badly | 20:37:39 |
| GenericNerdyUsername | whats the minimum hardware that nixos needs? | 20:37:49 |
| GenericNerdyUsername | like do you need the floating point extensions? | 20:37:59 |
| Alex | In reply to @genericnerdyusername:matrix.org
whats the minimum hardware that nixos needs? If you don't plan to evaluate Nixpkgs on the machine, anything that can run Linux will do.
It's pretty hard (but still possible) to trim the system below a few hundred MiBs of disk usage. | 20:39:34 |
| GenericNerdyUsername | and if you do want to evaluate nixpkgs? | 20:39:55 |
| Alex | Nixpkgs takes a fair bit of memory to evaluate.
I can't recall, but it's probably on the order of a few hundred MiB minimum.
I've seen some evals go beyond 1 GiB, though I think most cases aren't that large. | 20:41:31 |
| Alex | In reply to @genericnerdyusername:matrix.org
like do you need the floating point extensions? Probably not needed. | 20:44:16 |
 fgaz | In reply to @alex:tunstall.xyz
Nixpkgs takes a fair bit of memory to evaluate.
I can't recall, but it's probably on the order of a few hundred MiB minimum.
I've seen some evals go beyond 1 GiB, though I think most cases aren't that large. 4 GB if you want to nix search 🫠| 20:44:28 |
| Alex | ^ Requires evaluating all of Nixpkgs lol | 20:44:43 |
| fgaz | In reply to @alex:tunstall.xyz
^ Requires evaluating all of Nixpkgs lol i'm still of the opinion that it doesn't need to and could do with a small fraction of that https://discourse.nixos.org/t/nix-search-a-faster-better-nix-search/48568/19 | 20:49:00 |
| Alex | It absolutely shouldn't need to (e.g. why not pre-evaluate it into a DB you can quickly search).
But it does. | 20:49:50 |
| fgaz | it does pre-eval on the first search you perform. but even that first search shouldn't require all that memory, see the post I linked above | 20:51:03 |
| fgaz | or did you mean a downloadable db? | 20:51:39 |
| Alex | It could be downloaded.
That's just an idea of one way of implementing it. There are probably others.
And yeah, I can imagine how it could be possible to trim a lot of the memory usage if you only evaluate the metadata you need and not the whole derivation graph. | 21:05:24 |
| GenericNerdyUsername | like nix-index? | 21:15:22 |
