!xmLtiCaAJxfhURjrXl:matrix.org

NixOS RISC-V

208 Members
NixOS on RISC-V https://wiki.nixos.org/wiki/RISC-V https://pad.lassul.us/NixOS-riscv64-linux 64 Servers

Load older messages


SenderMessageTime
25 Sep 2025
@dramforever:matrix.orgdramforeverthere fixed21:07:27
@dramforever:matrix.orgdramforever
In reply to @outfoxxed:outfoxxed.me
so overriding it should help if possible?
it should, yes. i would consider coming up with a test case before rebuilding the world but unfortunately i don't really know how to trigger it
21:09:01
@outfoxxed:outfoxxed.meoutfoxxedIt only takes like 1.5 hours on my machine to rebuild whats necessary to test that, so I'm fine doing that21:09:30
@outfoxxed:outfoxxed.meoutfoxxedthat would require actually overriding it which I havent been able to figure out how to do without breaking nixpkgs though21:10:00
@dramforever:matrix.orgdramforeveryeah, i don't actually know how to trigger it21:19:07
@outfoxxed:outfoxxed.meoutfoxxedtrigger what?21:19:21
@outfoxxed:outfoxxed.meoutfoxxedthe vector crash or the nixpkgs eval fail21:19:35
@dramforever:matrix.orgdramforeverthe vector misalignment21:19:42
@dramforever:matrix.orgdramforeveryeah what would be vector crash on k121:19:55
@outfoxxed:outfoxxed.meoutfoxxedit looked like it happened during kernel module loading21:20:02
@outfoxxed:outfoxxed.meoutfoxxedby systemd21:20:06
@rosscomputerguy:matrix.orgTristan RossWtf21:20:09
@dramforever:matrix.orgdramforeverthat's not really significant21:20:10
@dramforever:matrix.orgdramforeverit could be anywhere21:20:13
@outfoxxed:outfoxxed.meoutfoxxedits linux 6.6.6321:20:12
@outfoxxed:outfoxxed.meoutfoxxedI don't really know what else I can tell you21:20:25
@dramforever:matrix.orgdramforeversince you set v in gcc.arch it could happen to anything and anywhere21:20:40
@dramforever:matrix.orgdramforeverkernel module loading is just one of the first thing it does on boot21:21:54
@alex:tunstall.xyzAlex
In reply to @rosscomputerguy:matrix.org
I want to try a RISC-V + LLVM kernel
NB: this will likely take longer to build because of needing to change stdenv.
22:41:06
@rosscomputerguy:matrix.orgTristan RossIk22:41:23
@rosscomputerguy:matrix.orgTristan RossI run an LLVM kernel on my desktop22:41:31
@alex:tunstall.xyzAlex
In reply to @rosscomputerguy:matrix.org
I run an LLVM kernel on my desktop
Is there any noticeable difference?
22:42:04
@rosscomputerguy:matrix.orgTristan RossKinda22:42:24
@rosscomputerguy:matrix.orgTristan RossThe noise from my audio interface is less noticable22:42:34
@rosscomputerguy:matrix.orgTristan Ross And pkgsLLVM.linux took 20 minutes with a GCC built kernel where with the LLVM kernel, it took 15 minutes 22:43:02
@rosscomputerguy:matrix.orgTristan RossI ran the same build under the two kernels 3 times in a row on each kernel and got the same 5 minutes difference22:43:45
@alex:tunstall.xyzAlex
In reply to @rosscomputerguy:matrix.org
The noise from my audio interface is less noticable
It sounds like there is interference between your CPU and your audio interface...
I mean, it shouldn't be driving the sound card differently just because of differences in compiler optimisations and code layout, right?
22:44:24
@rosscomputerguy:matrix.orgTristan RossThe thing is I'm not sure22:44:56
@rosscomputerguy:matrix.orgTristan RossI shouldn't even be getting noise in the first place since it's over USB. Even on my dedicated USB card, I actually get worse audio quality.22:45:22
@alex:tunstall.xyzAlex
In reply to @rosscomputerguy:matrix.org
I ran the same build under the two kernels 3 times in a row on each kernel and got the same 5 minutes difference
This could be due to ld.bfd vs lld (assuming these are what the two stdenvs use for linking). Worth exploring...
22:45:31

Show newer messages


Back to Room ListRoom Version: 10