Exotic Nix Targets | 339 Members | |
| 104 Servers |
| Sender | Message | Time |
|---|---|---|
| 18 Jun 2023 | ||
| * I wonder what the custom instructions are on the jh7110 | 15:10:18 | |
| 25 Jun 2023 | ||
| ugh, loongarch64 linux includes the kernel version number in the name of the image it installs, so we can't use our normal kernelTarget mechanism | 13:49:13 | |
| (although tbh, I've been wanting to change how kernelTarget works for a while. It doesn't really make sense for it to be a platform property. It should be an option + passthru on the kernel derivation.) | 13:49:39 | |
| 26 Jun 2023 | ||
| https://twitter.com/Houge_Langley/status/1673110240647331840 | 09:38:52 | |
In reply to @raitobezarius:matrix.orgIf they're using upstream Nixpkgs, it's probably going to fail on LLVM 11; adding an overlay for llvmPackages = self.llvmPackages_15 should fix it. | 09:42:38 | |
| Redacted or Malformed Event | 09:42:48 | |
| We will see what OP says :) | 09:43:06 | |
In reply to @alex:tunstall.xyzit builds fine on native afaik | 14:43:53 | |
In reply to @misuzu:matrix.org I'm talking about native. The commit I'm on (7c67f006ea0e7d0265f16d7df07cc076fdffd91f) failed on LLVM 11. Or maybe it's because I have added | 14:56:01 | |
| 18:37:18 | ||
In reply to @qyliss:fairydust.spaceI definitely join you on this as I was fiddling with the zboot PR | 22:00:25 | |
| 27 Jun 2023 | ||
In reply to @alex:tunstall.xyzWorks for me (I didn't mess with build options) | 06:42:01 | |
| Anyone in here with a DevTerm? Specifically with a CM4 core | 20:25:05 | |
| * Anyone in here with a clockwork pi DevTerm? Specifically with a CM4 core | 20:25:32 | |
| Having some issue getting any kernel to work, although maybe I'm just missing some kernel modules or sth | 20:35:10 | |
| 28 Jun 2023 | ||
| bootstrap file issue? https://github.com/NixOS/nixpkgs/issues/211120 https://discourse.nixos.org/t/nix-on-armv7l-fails-to-build-any-packge/16819 | 23:21:56 | |
/nix/store/yx05p52ik9j1ws4x035pyfi4w8ns9zy8-bootstrap-stage1-stdenv-linux/setup: ./configure: /bin/sh: bad interpreter: No such file or directory | 23:22:25 | |
| 29 Jun 2023 | ||
| 00:33:16 | ||
| 00:33:28 | ||
| chuang: I'm booting your image for the MQ Pro D1 board, but it seems to not be doing anything on HDMI, any ideas? | 09:41:51 | |
| https://github.com/chuangzhu/nixos-sun20iw1p1/releases | 09:41:56 | |
| I'm referring to the latest release here | 09:42:00 | |
| Using revision 1.2 of the board | 09:45:22 | |
| 1 Jul 2023 | ||
| 09:50:03 | ||
| 13:54:38 | ||
| Hello everyone, I am the "maintainer" of the unmaintained minimal Arch Linux image for the VisionFive 2. Recently I tried out NixOS and am using it on my Raspberry Pi as the "main computer" (my current x86 pc died so this is a temporary measure; but it works even with 'llvmpipe' because I'm using UEFI). I came to know about the RISC-V effort and got curious. I was checking this issue on NixOS/nixpkgs and a thread mentioned about this IRC channel. So here I am. Are there any "Here's how to get started on the VF2" guides? | 14:04:28 | |
| Me being new to NixOS doesn't help me understand how to test the waters with RISC-V on NixOS, haha | 14:05:49 | |
In reply to @thefossguy:matrix.org There's the official documentation from the vendor and a few enthusiasts, but they're mostly for Debian. For NixOS, there are a few repositories here and there that contain a bootable configuration. I've based my system configuration off of https://github.com/misuzu/nixos-vf2 (note that this was written for rev 1.3B; it has DTBs for other revisions, but might not work as well). | 14:11:18 | |
Given that you've (presumably) managed to boot Arch on the system, it should mostly be a matter of figuring out how to translate what you already know into NixOS configuration. The boot.* options should be of interest. | 14:12:22 | |
| Pratham Patel: I probably won't be able to help much since I know ~nothing about VF2, but here's some generic explanation that may or may not be a missing piece of understanding: Nix is at its core a build tool, and while most of its usage is for building packages for a system, there's no reason it has to be limited to that, and so it is also used as a build tool for the install image itself. essentially, the various ISOs that you can have for NixOS are "just" attributes of nixpkgs that you can evaluate and build like they are any other package. the architecture is an argument when initializing nixpkgs, though in this case I'm guessing you'd be cross-compiling so additional machinery (that I am not familiar with) may be necessary | 14:12:51 | |