NixOS RISC-V | 205 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 | 62 Servers |
| Sender | Message | Time |
|---|---|---|
| 17 Feb 2024 | ||
| wait, is this a problem? | 19:55:50 | |
| xorgxrdp wouldn't be properly spliced here... but that still doesn't explain what's going on | 19:56:22 | |
In reply to @SeTSeR:matrix.org Unfortunately, such errors seem to be fairly common in wrapped packages (which is the case with I couldn't tell you why the splicing is going wrong, but perhaps overriding | 21:10:37 | |
| 18 Feb 2024 | ||
| 00:19:40 | ||
| 03:52:38 | |
| The problem is not about splicing but it checking for the wrong pkg-config binary. | 03:53:00 | |
| It shall be riscv64-unknown-linux-gnu-pkg-config | 03:53:13 | |
| (This won't completely fix cross compilation either, there are still other issues like: https://github.com/neutrinolabs/xrdp/issues/1292) | 03:53:39 | |
| If you really want some decent remote desktop experience, I would recommend wayvnc (or others), rather than this poorly packaged xrdp. | 03:54:27 | |
| Thanks, I’ll try wayvnc. I also tried TigerVNC, but it also fails, trying to run the wrong gettext, hope `wayvnc` will work | 08:17:35 | |
| I also encountered a kernel panic on upstream kernel: https://github.com/starfive-tech/linux/issues/132 I was able to stable reproduce this on any nix-related command, so I’m currently unable to use nix on my machine. For a long time I used 5.15 kernel from old `devel` branch, but after update of default GCC to 13 I was unable to boot this kernel, as the old kernel doesn’t seem to support modules built by new GCC. I think I can set old compiler for kernel explicitly, but maybe there is a way to debug this kernel panic? The problem seems to be very old, I think I tried to switch to upstream kernel from the start of my journey with VF2, and on every attempt I encountered this panic. | 10:18:09 | |
| Sometimes I ran into this problem just by running soulseek client or fsck on incorrectly shut down drive | 10:20:23 | |
| 19 Feb 2024 | ||
| 02:27:58 | ||
| 02:28:28 | ||
| * | 10:28:18 | |
| FYI: Please don't use the Pioneer or the Lichee 4A in any of the build machines. The C<something> cores from T-Head have hardware erratas about incorrect Atomic implementation and it should only be used for "oh cool thing" instad of a build machine. | 10:37:32 | |
| Also, the above "PSA" was for using these machines for building nixpkgs. Not against their inclusion in nixos-hardware :) | 10:54:37 | |
| So far, the only machines I trust for building nixpkgs are the HiFive Unmatched and the VisionFive 2. | 10:55:27 | |
| Might add the Milk-V Oasis to that list once it's launched, since it uses SiFive's cores (which I trust to have no major issues), but only after testing things out :) | 10:56:12 | |
| Do you have any specific silicon erratas you are referring to? I'm only interested in those that impact user-mode functionality, rather than being solely kernel-mode concerns. I know about the linux ERRATA_THEAD_QSPINLOCK, but I would like to know about others, if they exist. The information is a bit hard to find. | 11:35:18 | |
| All the RISC-V related erratas that I know: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/riscv/include/asm/errata_list.h | 11:38:14 | |
| ahh ok. as far as i understand it, the current erratas in upstream linux do not affect user-mode. | 11:44:43 | |
| but correct me if i'm wrong, I would really like to know ;) | 11:44:55 | |
| that's for the core though, pretty sure both kernel-space and user-space are affected | 11:45:17 | |
| also, these erratas are errors in implementing the RISC-V spec in the actual Linux-capable core, individual or on SoC | 11:50:05 | |
| That said, I do wish to buy that Lichee 4A cluster board with 7 slots so I can parallel build to check for build failures since we're still bootstrapping. Once a build succeeds, I'd build it on the VF2 that I own. | 11:54:03 | |
In reply to @thefossguy:matrix.org Yes, the behaviour may differ from the official spec, but you still have to consider the impact.
| 12:15:49 | |
| That being said, I would trust none of these as production machines for a database or something. | 12:16:06 | |
| For the pioneer: the sg2042-dev vendor kernel is not stable, and the PCIe support is a bit wonky which I would consider as a bigger issue at this point. But hopefully those can be resolved. | 12:17:20 | |
| Agreed, while the kernel does handle most of this to have workarounds, they're exactly what they are, workarounds. :) | 12:36:35 | |