Index of /pub/alt/risc-v/archive/testing/f41_unmatched_no_init_setup

Icon  Name                                                  Last modified      Size  Description
[PARENTDIR] Parent Directory                                                           -   
[   ] firmware.img                                          2025-02-19 15:56   32M  
[TXT] README                                                2025-02-19 16:11  1.6K  
[   ] Fedora-Server-Host-Generic-41.20250219.riscv64.raw.xz 2025-02-19 15:59  1.0G  

# Flash new firmware (U-Boot SPL, U-Boot, OpenSBI, DTB):

1. Load mtblock kernel module

  modprobe mtdblock

2. Write SPI-NOR Flash from kernel userspace

  sudo dd of=/dev/mtdblock0 if=./firmware.img bs=1K iflag=fullblock oflag=direct conv=fsync status=progress

If this fails the board will fail to boot, and you will need to switch DIP switches to pull firmware from microSD card.

In that case follow README.md and use Fedora-Developer-38-20230519.n.0-mmc.raw.img.xz image from:

  https://dl.fedoraproject.org/pub/alt/risc-v/archive/disk_images/Fedora-Developer-38-20230519.n.0.SiFive.Unmatched.and.QEMU/

# Prepare Fedora 41 image (applies to this particular image)

The image in this directory has initial-setup disabled, root password was deleted, and there are no other user created as in older Fedora/RISCV releases.

Flash the image to NVMe and mount 3rd partition (btrfs).

Use systemd-firstboot to do initial setup from a host system (modify example below as needed):

  sudo systemd-firstboot --force --root=/run/media/$USER/fedora/root --setup-machine-id --root-password=fedora_rocks --hostname=fedoratest

Note, that --force might not be needed. Basically systemd-firstboot will avoid changing anything that is already configured (e.g. at Kiwi creation stage).

You can try initially without --force and the tool should print which files were written out. If it doesn't look write (i.e. no files were created/modified) use --force.

Note, --image option cannot be used due to the way Fedora setups defaults. Fedora is not compliant with Discoverable Partitions Specification (DPS) if Btrfs is used, and the tool expect DPS compliant image for --image option.