NixOS on ROC-RK3328-CC Renegade

Start Boot
1

I know this has already been asked multiple times by others, but I just can’t get it to boot.

(Sorry for the weird links. This forum only allows 2 links for new users)
I already tried

  • any and every method described in the official NixOS wiki
https://nixos.wiki/wiki/NixOS_on_ARM/Libre_Computer_ROC-RK3328-CC
  • the Hydra build method of this other topic post
https://hub.libre.computer/t/how-to-install-nixos-in-each-sbc/3753

I found on the Libre.Computer forum

  • I tried what this Reddit post suggested, though I did not write a package to replicate the official flashing tool

but they don’t seem to work.

I also read this topic post

https://hub.libre.computer/t/nixos-for-aml-s905x-cc-le-potato/3273

to try and figure something out, as well as this topic post

https://hub.libre.computer/t/le-potato-networking-unavilable-when-booting-in-uefi-mode/3825.

For full disclosure, this is my first SBC experience. I am not too familiar with u-boot, but I know that I have to flash the u-boot image after the OS image.

I also made a pretty detailed post over on the NixOS forum explaining my attempts before I stumbled upon the topics on the Libre.Computer forum. Then I tried basically everything I explained in the NixOS forum post again with 1. the downloaded Hydra build and 2. a self-compiled version of the Hydra build.

I have since then already realized that trying to boot from a USB stick does not work, but it doesn’t really matter since I tried everything on a SanDisk 128GB Ultra microSDXC

https://www.amazon.com/SanDisk-microSDXC-Speicherkarte-Smartphones-Lesegeschwindigkeit/dp/B0B7NTY2S6

that should work with the board, as I previously got LibreELEC running on it (but only after using some patched version of u-boot specifically for this OS that I found on some Russian blog).

If anyone can help me figure this out, it would be much appreciated.

1 Like
2

The concept is simple. You have a normally UEFI booting arm64 Linux operating system partitioned with MBR flashed on one of the bootable media (usually eMMC/SD). GPT conflicts with our bootloader for the boards without onboard bootloader. Then you slap on our bootloader which passes the board device tree directly to the operating system. Done.

Ignore the overly complex instructions. This process applies for all of our boards. For UEFI boards (all designs after 2018), there’s no need to flash the bootloader since it’s built into the board. This allows those boards to support GPT disk images as well since the bootloader doesn’t conflict with the image partition table layout.