| 23 May 2022 |
 Linux Hackerman | In reply to @j-k:matrix.org
Just building a fresh sd image for visionfive, I'm guessing for the ZFS broken warning just NIXPKGS_ALLOW_BROKEN=1? It's likely to genuinely not work. Are you using linuxPackages_latest? | 18:30:40 |
| Linux Hackerman | There's an attr in zfs called latestSupportedLinuxPackages or something, try setting boot.kernelPackages to that. If that's too old to support the hardware, I think you'll have to do without zfs for now | 18:32:01 |
 j-k | I'm just building https://github.com/zhaofengli/nixos-riscv64/blob/master/pkgs/default.nix#L24 | 18:32:46 |
| j-k | it mentions zfs here but IDK if it's actually used at all in the sd card image
https://github.com/zhaofengli/nixos-riscv64/blob/f0b105b7671289c3fc17849532afe4fceb95bfd6/binary-cache/world.nix#L38 | 18:33:13 |
 Zhaofeng Li | Yeah, I'm passing NIXPKGS_ALLOW_BROKEN=1. ZFS is pulled in by the installation image profile and was marked broken for 5.16 back then. | 18:37:06 |
| Zhaofeng Li | But I don't recommend building my branch right now, probably try https://github.com/NixOS/nixpkgs/pull/168826 | 18:38:47 |
| Zhaofeng Li | * But I don't recommend building my branch right now, probably try https://github.com/NixOS/nixpkgs/pull/168826 to be more up-to-date | 18:39:05 |
| j-k | well I'm a couple hours into building so maybe I'll just hang in there 😅 Do you recommend binfmt or crosscompile?
Also I manually tweaked the config to have ssh and my public key so I'm hoping I can just ssh in headless first try 🤞we'll see | 20:49:47 |
| 24 May 2022 |
| Zhaofeng Li | For my branch I always did native and it may not even cross-compile, and my cache only contains native builds. | 00:33:55 |
|  alyaeanyx changed their display name from Alexandra to alyaeanyx. | 03:16:37 |
| j-k | What am I doing wrong here? 🙃
required (system, features): (riscv64-linux, )
4 available machines:
(systems, maxjobs, supportedFeatures, mandatoryFeatures)
# ...
# vvvvvvvvvvvvv
(x86_64-linux, i686-linux, riscv64-linux, 2, benchmark, big-parallel, kvm, nixos-test, )
# ^^^^^^^^^^^^^
error: unable to start any build; remote machines may not have all required system features.
https://nixos.org/manual/nix/stable/advanced-topics/distributed-builds.html
| 12:58:23 |
 qbit | boot.binfmt.emulatedSystems have riscv64-linux in it? | 13:08:20 |
| j-k | yep. I've been trying to test it's set up properly on that remote machine, looks like it is
# downloaded rustc
$ ./rust-1.60.0-riscv64gc-unknown-linux-gnu/rustc/bin/rustc --help
qemu-riscv64: Could not open '/lib/ld-linux-riscv64-lp64d.so.1': No such file or directory
and
nix --extra-experimental-features "nix-command flakes" build .#packages.riscv64-linux.hello
looks good in htop
| 13:21:16 |
| j-k | 
Download image.png | 13:21:21 |
| j-k | $ cat flake.nix
{
outputs = { self, nixpkgs }: {
packages.riscv64-linux.hello = nixpkgs.legacyPackages.riscv64-linux.hello;
};
}
| 13:21:35 |
| j-k | ok, it was an ssh issue I had to fix | 13:36:45 |
| j-k | 
Download image.png | 15:30:39 |
| j-k | beautiful | 15:30:40 |
| qbit | Brummm | 15:31:52 |
 Rick (Mindavi) | Qemu x 32 | 15:32:30 |
| j-k | 3 failed tests on bison | 15:41:07 |
| 25 May 2022 |
 Alyssa Ross | Ericson2314: I'm looking at https://github.com/NixOS/nixpkgs/pull/169793 again. I think to do this properly we need to change the release.nix infrastructure to just use full triples everywhere. But that's going to be a huge amount of work, so I think I'm going to have to try to split it up. | 10:34:27 |
 John Ericson | Alyssa Ross: yeah I see | 13:50:09 |
| John Ericson | that change sounds good to me! | 13:50:18 |
| Alyssa Ross | cool :) | 13:56:17 |
| Alyssa Ross | hopefully I'll have a start by tomorrow | 13:56:38 |
| j-k | In reply to @j-k:matrix.org
3 failed tests on bison I'm just assuming this is an issue introduced by binfmt so I'm back to x86_64-linux cross compiling. currently on the kernel | 14:18:06 |
| j-k | nixos-sd-image-22.05pre-git-riscv64-linux-visionfive.img.zst 🎉 | 14:36:14 |
| j-k | the sd image from the visionfive PR just has sda1 and sda2, I thought it needed stuff in sda3 to play nice with the really weird boot config? Is there something else I need to do to the board first? | 14:45:20 |
| j-k |
We have to use custom boot firmware since we do not support
StarFive's Fedora MMC partition layout. Thus, we include this in
the image's firmware partition so the user can flash the custom firmware.
anything I need to do here or will it be done automatically?
| 14:46:07 |
