| 25 Mar 2025 |
|  Find me at aleksana:qaq.li changed their display name from aleksana (force me to bed after 18:00 UTC) to aleksana 🏳️⚧️ (force me to bed after 18:00 UTC). | 17:00:21 |
| 26 Mar 2025 |
|  hive ⬡ changed their profile picture. | 03:50:17 |
|  @burntk:matrix.org left the room. | 07:00:42 |
 misuzu | 
Download 1000002138.jpg | 18:00:50 |
| misuzu | In reply to @misuzu:matrix.org
https://liliputing.com/orange-pi-rv2-is-a-single-board-pc-with-an-8-core-risc-v-processor/ Ordered one | 18:00:59 |
| hive ⬡ changed their profile picture. | 19:28:35 |
| 27 Mar 2025 |
 implr | Anyone tried to build something without crosscompiling (so system=riscv64-linux; no crossSystem), via qemu-user or natively recently? | 20:40:33 |
| implr | On current unstable, bison is failing doCheck for me, but it's in one of the bootstrap stages, so it's a huge pain in the ass to override | 20:40:58 |
| implr | * On current unstable, bison is failing doInstallCheck for me, but it's in one of the bootstrap stages, so it's a huge pain in the ass to override | 20:42:42 |
 Alex | NixOS compiled fine for commit 3a228057.
(See https://github.com/AlexandreTunstall/nixos-riscv/blob/6fc5181216631eaeec703fb09028b127c01d27a1/flake.lock#L9) | 20:42:47 |
| Alex | So the regression has happened in the past month or so. | 20:43:11 |
| implr | Let me double check if that commit works for me, maybe I did something dumb | 20:43:37 |
| implr | hm, it does not, fails the same way | 23:13:52 |
| implr | I'll try your flake as-is | 23:13:57 |
| Alex | In reply to @implr:hackerspace.pl
I'll try your flake as-is See the instructions in README. As-is, it requires some x86 cross-compilation for GHC (or you can edit out the Haskell dependencies). | 23:14:55 |
| implr | I just want to see if the bootstrap builds, so I'm doing .#nixosConfigurations.nixos.pkgs.bash | 23:15:37 |
| implr | if that passes it's already further than I got | 23:15:45 |
| Alex | Well, if that evaluates and doesn't complain about needing an x86_64 machine, it should be OK (it could still require GHC because of ShellCheck being used in writeShellScript). | 23:16:59 |
| implr | Oh, I am on a amd64 machine with extra-platforms = riscv64-linux right now, so that should just work, but that might be the difference which makes bison work for you and not me | 23:20:01 |
| implr | Redacted or Malformed Event | 23:20:04 |
| 28 Mar 2025 |
| implr | the flake does not build either, so it must be somethign with qemu-user that breaks the test | 12:35:02 |
|  scottytheengineer joined the room. | 18:16:21 |
 White Whale | Hello! I’m trying to build `nicotine-plus` on my visionfive 2, and I stumbled upon failing test of `watchdog`. I tried overriding this with following overlay:
```nix
python3Packages = super.python3Packages.overrideScope (self: super: {
sphinx = overrideSphinx super.sphinx;
pytest-timeout = disablePythonTests super.pytest-timeout;
hypothesis = disablePythonTests super.hypothesis;
eventlet = disableTests super.eventlet;
watchdog = super.watchdog.overridePythonAttrs (old: {
disabledTests = [ "test_select_fd" ];
});
werkzeug = super.werkzeug.overridePythonAttrs (old: {
nativeCheckInputs = old.nativeCheckInputs ++ [ self.watchdog ];
});
});
```
but problematic version is still built and thus failing build. `nix why-depends` shows dependency on watchdog from werkzeug. How should I resolve this problem?
I came here with similar question some time ago, I tried suggestions from thread and did some investigation with GPT, but I was unable to compile `watchdog`. Should I resort to modifying nixpkgs? | 20:41:18 |
| Alex | Sometimes problematic packages can be dropped from the build closure altogether. Have you looked at why it's needed with nix why-depends --derivation --all? | 21:57:25 |
| 29 Mar 2025 |
 12b | Hello.
I'm a little bit of a newvie on NixOS. I've been using it on my x86_64 laptop for a couple of months. And I did some install on a few ARM boards.
I'm now trying to install NixOS on RISC-V.
I first tried on a Vision Five 2. I managed to have NixOS running on it. But it was kinf of a pain. And I faced the slow build times and the compilaiton errors mentioned In this channel when doing nixos-rebuild on it.
I bough myself an OrangePi RV2 and it just arrived yesterday.
I installed the official Ubuntu image on it, on an SSD. So far I'm quite pleased. The partiioning scheme they use has only one partition on the SSD. Quite different from the many partitions nonsense I had to creaté to install NixOS on an SSD for the Vision Five 2. Also the performances of the board are better.
But now, I'm clueless at how I could install NixOS on it. | 06:59:21 |
| Alex | "Official" as in an image distributed by Ubuntu maintainers and not the manufacturer? | 07:01:32 |
| 12b | no sorry I meant distributed by the manufacturer | 21:35:06 |
| Alex | Try to find the sources for the Linux kernel and whatever bootloader they're using (they probably have custom patches).
You can customise NixOS to use those sources.
You may also need to search for documentation on how to setup the bootloader and replicate it with a bit of Nix.
Other than that, it's no different from doing a regular NixOS install.
Of course, you still can't expect to have riscv64 from the official NixOS binary cache, so expect the system build to take a while.
Some things can be disabled to save time, but most of the things that are enabled by default are somewhat "essential". | 21:39:11 |
| 12b | the kernel source they are using is in https://github.com/orangepi-xunlong/orangepi-build
for the bootloader I don't know. | 21:56:26 |
| 30 Mar 2025 |
|  98765abc joined the room. | 02:13:47 |
