NixOS RISC-V | 235 Members | |
| NixOS on RISC-V https://wiki.nixos.org/wiki/RISC-V https://pad.lassul.us/NixOS-riscv64-linux https://github.com/orgs/NixOS/teams/risc-v | 70 Servers |
| Sender | Message | Time |
|---|---|---|
| 18 Feb 2025 | ||
| Gotcha. Yeah, I have one of those, 2 BeagleV Ahead, a couple smaller Milk-V targets and just got the Framework RISC-V Mainboard. So it's not much, but was wondering whether I can throw these boards into a corner in my Uni's lab and have them do something more useful than collect dust until I or someone else finds out how to get NixOS running on the Framework mainboard haha | 23:08:31 | |
| Yeah, most systems use the JH7110 which isn't that powerful lol | 23:08:54 | |
| Right right. | 23:09:01 | |
| There's the newer P550 but the price | 23:09:04 | |
| FWIW, I'm running the pre-built Fedora 41 image on the Framework mainboard right now, and running GNOME + Firefox, listening to music, etc. is somewhat usable. Definitely better than what I remember from my VF2 | 23:10:41 | |
| (I don't know how much frequency scaling this thing does, could thermals have an impact?) | 23:11:08 | |
| That silicon is probably more mature than the one I've got | 23:11:19 | |
| The VF2 is older so I wouldn't doubt the Framework being more mature | 23:11:36 | |
| I've ran into some oddities in my VF2 like NIC DMA not working | 23:11:59 | |
| Well they both use the JH7110 SoC, so shouldn't be much of a difference I guess. | 23:12:27 | |
| Yeah but the rest of the board matters too | 23:12:45 | |
| And it's possible there's different revisions | 23:12:55 | |
| But it sounds like there's not yet a Hydra or something I could hook this up to? | 23:13:49 | |
| Not currently | 23:13:56 | |
| @matthewcroughan:defenestrate has floated the idea | 23:14:35 | |
| Cool, excited to maybe build something. | 23:16:19 | |
| 19 Feb 2025 | ||
| I got a Milk-V Megrez waiting for me to have time working on it... | 00:01:19 | |
| 21 Feb 2025 | ||
procmail fails to build in a funny way | 17:49:05 | |
| Looks to be the same as https://github.com/NixOS/nixpkgs/issues/334916 | 17:58:10 | |
| 26 Feb 2025 | ||
| 07:36:18 | ||
| 07:36:21 | ||
| 10:09:09 | ||
| 6 Mar 2025 | ||
| 13:04:46 | ||
| 7 Mar 2025 | ||
| Hello! How can I override Python package `watchdog` from within overlay? I tried this: ```nix python3Packages = super.python3Packages.overrideScope (self: super: { watchdog = super.watchdog.overrideAttrs (self: super: { doCheck = false; } }); ``` However, `nix why-depends` still shows that dependency on old `watchdog` is still in place. It shows that `werkzeug` depends on this library. In Nixpkgs I found, that `werkzeug` has `watchdog` in `nativeBuildInputs`. However, neither putting `watchdog` override in `buildPackages` nor removing the library from `nativeBuildInputs` didn’t do a trick. What else could I try? | 19:05:07 | |
In reply to @SeTSeR:matrix.orgIt might be coming from one of the other Python package sets. Maybe look at the definition of python3Packages in Nixpkgs, because I suspect that it's actually an alias for one of the other sets. | 20:48:14 | |
In reply to @alex:tunstall.xyzIt’s strange, because I had to disable tests for some other packages and such override did the trick for them. But now I see the problem more clearly: werkzeug sees the updated watchdog, but for some reason this updated watchdog still runs tests. | 21:28:52 | |
In reply to @SeTSeR:matrix.orgYou're not using overridePythonAttrs. That's probably why. | 21:30:00 | |
| White Whale: that's what I usually do: https://nixos.org/manual/nixpkgs/stable/#how-to-override-a-python-package-for-all-python-versions-using-extensions | 22:36:04 | |
| 8 Mar 2025 | ||
| 08:27:44 | ||
| 9 Mar 2025 | ||
| https://liliputing.com/orange-pi-rv2-is-a-single-board-pc-with-an-8-core-risc-v-processor/ | 20:07:50 | |