In reply to @thefossguy:matrix.org
Me neither but I would prefer it over the HiFive Pro...

In reply to @thefossguy:matrix.org
not in SPI mode (with the firmware flashed using nix run github:misuzu/nixos-vf2#flash-visionfive2-vendor /dev/ttyUSB0)

You probably have changed some settings is u-boot. To reset u-boot settings to default values you can use these commands:

env default -a
saveenv

In reply to @misuzu:matrix.org

You probably have changed some settings is u-boot. To reset u-boot settings to default values you can use these commands:

env default -a
saveenv

In reply to @thefossguy:matrix.org
I didn’t modify your uboot settings. I flashed the image and flashed the firmware using aforementioned method.   

misuzu is nixos-cross-image-efi supposed to require RISC-V emulation to build?

alex@alex-pc3 ~/r/A/n/master (master)> nix build .#nixos-cross-image-efi --print-build-logs
error: a 'riscv64-linux' with features {} is required to build '/nix/store/03w7yyb2cqw3blz9biawkypig49lx2fc-bootstrap-tools.drv', but I am a 
'x86_64-linux' with features {benchmark, big-parallel, kvm, nixos-test}

In reply to @alex:tunstall.xyz

misuzu is nixos-cross-image-efi supposed to require RISC-V emulation to build?

alex@alex-pc3 ~/r/A/n/master (master)> nix build .#nixos-cross-image-efi --print-build-logs
error: a 'riscv64-linux' with features {} is required to build '/nix/store/03w7yyb2cqw3blz9biawkypig49lx2fc-bootstrap-tools.drv', but I am a 
'x86_64-linux' with features {benchmark, big-parallel, kvm, nixos-test}

Nevermind, this is the consequence of my own changes.

Now to figure out why.

In reply to @alex:tunstall.xyz

misuzu is nixos-cross-image-efi supposed to require RISC-V emulation to build?

alex@alex-pc3 ~/r/A/n/master (master)> nix build .#nixos-cross-image-efi --print-build-logs
error: a 'riscv64-linux' with features {} is required to build '/nix/store/03w7yyb2cqw3blz9biawkypig49lx2fc-bootstrap-tools.drv', but I am a 
'x86_64-linux' with features {benchmark, big-parallel, kvm, nixos-test}

In reply to @thefossguy:matrix.org
I noticed that the image (https://github.com/misuzu/nixos-vf2) didn't boot with all combinations of DIP switches so me being extra smart, I dd-ed uboot SPL and SBI firmware on /dev/sda1 and /dev/sda2 respectively and mvoed /boot to /dev/sda3 and / to /dev/sda4. Now, your derivation doesn't work because it expects "/dev/sda1" to be EFI?

In reply to @misuzu:matrix.org
https://github.com/misuzu/nixos-vf2/tree/master#u-boot-on-an-sd-card follow this if you want u-boot on an sdcard

In reply to @alex:tunstall.xyz
Oh neat, that means I can cancel building my dodgy attempt at tweaking your make-efi-image script.

In reply to @misuzu:matrix.org
The image uses labels to mount partitions, so partition numbers shouldn't matter

In reply to @alex:tunstall.xyz
Doesn't that mean I could shrink my root partition a bit and put u-boot at the end of the disk?

In reply to @0x4a6f:matrix.org
Not enough funds, maybe NixOS foundation could chim in. Maybe raitobezarius has some better understanding of this platform.

In reply to @misuzu:matrix.org
It's not enough to flash u-boot to reset u-boot settings

In reply to @alex:tunstall.xyz
Doesn't that mean I could shrink my root partition a bit and put u-boot at the end of the disk?

In reply to @alex:tunstall.xyz

I'm currently compiling with a few patches applied to try to fix the compilation problems without disabling DRM, since I'd really like to get working HDMI on my VF2.

I'll share the configuration if I'm able to get it working. Given the similarities between the two SBCs (and their respective Linux fork), it might work for the Star64 too.

The serial console stops displaying messages after these:

EFI stub: Booting Linux Kernel...
EFI stub: Loaded initrd from command line option
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services...
clk u2_dw_i2c_clk_core already disabled
clk u2_dw_i2c_clk_apb already disabled
clk u5_dw_i2c_clk_core already disabled
clk u5_dw_i2c_clk_apb already disabled

the kernel doesn't even start...